> **Description:** Details about API and platform updates for March 2023, including new features, improvements, and important changes to Vipps services. # Technical update Mar 2023 ## New to the technical updates? You're receiving this technical update, because you have admin privileges on the portal for a merchant with access to [APIs](https://developer.vippsmobilepay.com/docs/APIs/README.md). In this newsletter, we share information about changes and updates to APIs, new functionality, and other important information to ensure that your solutions run smoothly. The newsletter is sent at irregular intervals, when there is important information to share. In 2022, we sent six newsletters. Like all our [developer documentation](https://developer.vippsmobilepay.com/), the newsletter is in English. This makes it easier to forward to all developers and technical resources. See: [Newsletter information and archive](https://developer.vippsmobilepay.com/docs/technical-updates/README.md). ## ePayment API The new [ePayment API](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/README.md) is designed from scratch, based on everything we have learned through the [eCom API](https://developer.vippsmobilepay.com/docs/APIs/ecom-api/README.md) over several years. The main benefits are: * Support for different flows, like paying by QR code, out-of-the-box without the "hacks" required in the eCom API * Support for long-lived payments (payment requests from merchants) that are valid up to 60 days * Support for freestanding card payments where you can pay with VISA and MasterCard without the Vipps app * Webhooks to always reliably send information back to the merchant or partner We strongly recommend that all new integrations use the [ePayment API](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/README.md), not the eCom API. The [ePayment API specification](https://developer.vippsmobilepay.com/redocusaurus/epayment-swagger-id.yaml) and [API guide and FAQ](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/README.md) are now both available. **Please note:** The eCom API will still be available for a long time, but new development will be for the ePayment API. ## Webhooks API The [Webhooks API](https://developer.vippsmobilepay.com/docs/APIs/webhooks-api/README.md) allows merchants to receive information about when a payment has been authorized, cancelled, or expired. Merchants register one API endpoint and specify which events they want to receive. If an event is not delivered successfully, it will be retried multiple times. See: [Webhooks API](https://developer.vippsmobilepay.com/docs/APIs/webhooks-api/README.md). ## Recurring API: Look up agreements by charge The new endpoint [`GET:/charges/{chargeId}`](https://developer.vippsmobilepay.com/redocusaurus/recurring-swagger-id.yaml) makes it possible to retrieve a charge specified by `chargeId`, without knowing the `agreementId`. The resulting charge now contains the `agreementId`. Its purpose is to simplify investigations when the merchant lost track of which charge belongs to which agreement. See: [Retrieve a charge](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/recurring-api-guide.md#retrieve-a-charge). ## eCom API and Express The improved Express flow (`"useExplicitCheckoutFlow": true`) is now the only possible flow. This ensures that the user gets the item delivered to the right place in the right way. The `useExplicitCheckoutFlow` parameter no longer has any effect. See the API guide: [eCom Express](https://developer.vippsmobilepay.com/docs/APIs/ecom-api/vipps-ecom-api.md#express). ## Improved shipping options in Vipps Checkout It is essential that you provide your customers with their preferred shipping method. [Vipps Checkout](https://developer.vippsmobilepay.com/docs/APIs/checkout-api/README.md) now supports all major shipping providers in the Norwegian market, including: * Bring/Posten * Postnord * Porterbuddy * Helthjem * Instabox ## More Solutions and best practices In the [Solutions (now called "Recommended flows")](https://developer.vippsmobilepay.com/docs/recommended-flows/README.md) section of the documentation, you can now see how APIs can be combined to give the best user experience for several use cases, such as: * Electric vehicle charging * Loyalty at Point of Sale (POS) * Static QR codes at POS * Parking and "pay as you go" * Taxi companies * Vending machines See: [Solutions (now called "Recommended flows")](https://developer.vippsmobilepay.com/docs/recommended-flows/README.md). ## Report API The [Report API](https://developer.vippsmobilepay.com/docs/APIs/report-api/README.md) gives you, or a third-party acting on your behalf, the ability to fetch information about payment events that have been processed by Vipps. It is a REST API providing data in JSON format. See the [API documentation](https://developer.vippsmobilepay.com/docs/APIs/report-api/README.md). ## Change of IP addresses We will soon change the IP addresses for the publicly available servers. Make sure you follow the documentation for DNS and server configuration: [Vipps servers](https://developer.vippsmobilepay.com/docs/knowledge-base/servers.md). ## Reminders ### Please check your API calls for errors *UPDATE from 2024-01-12: The API Dashboard is deprecated.* We are working on eliminating incorrect API use to ensure the best possible user experience for all Vipps users and merchants. Please: * Monitor the responses you get when making API calls * Log all errors * Fix errors as quickly as possible * Use the API Dashboard to find problems with your integration. ## Questions or comments? We're always happy to help with code or other questions you might have! Please [contact us](https://developer.vippsmobilepay.com/docs/contact.md). > **Full site overview:** For every page in this documentation, read [https://developer.vippsmobilepay.com/llms.txt](https://developer.vippsmobilepay.com/llms.txt).