> **Description:** Details about API and platform updates for November 2024, including new features, improvements, and important changes to Vipps services. # Technical update Nov 2024 ## User age verification in the ePayment API It is now possible to specify the user's minimum age required to complete the payment: `"minimumUserAge": 20`. See [Minimum user age](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/minimum-user-age.md). ## Swedish users can now use Vipps Swedish users can now use the Vipps app and pay Norwegian merchants. For details, see: * [User requirements](https://developer.vippsmobilepay.com/docs/knowledge-base/users.md) * [Payments from Sweden](https://developer.vippsmobilepay.com/docs/knowledge-base/across-borders.md) ## Landing page: More robust handling of retries We have made some changes to prevent double payments when the user navigates from the [Vipps MobilePay landing page](https://developer.vippsmobilepay.com/docs/knowledge-base/landing-page.md) back (using the *Back* button in the browser, or with a keyboard shortcut) to the merchant's website. If the user navigates back from the landing page, we will cancel the payment. This is to prevent the user from navigating forward to the landing page again and attempting to pay the same payment twice. See "What happens if the user navigates back to my checkout from the landing page?" in the FAQs for the [ePayment API](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/faq.md#what-happens-if-the-user-navigates-back-to-my-checkout-from-the-landing-page), [PSP API](https://developer.vippsmobilepay.com/docs/APIs/psp-api/vipps-psp-api-faq.md#what-happens-if-the-user-navigates-back-to-merchant-checkout-from-the-landing-page) and [MobilePay Online API](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-faq.md#what-happens-if-the-user-navigates-back-to-merchant-checkout-from-the-landing-page). **INFO** If you always initiate a new payment each time the user attempts to pay, you don't need to take action. If you however reuse the same payment request (which will result in the same redirect URL), or reuse the redirect URL, you will need to change this setup. You must instead ensure to initiate a new payment to get a new redirect URL. ## Management API: More details about product orders The new `v2` version of `GET:/management/v2/product-orders` will return *all* product orders where you have been specified as the partner: * Product orders made with `POST:/management/v1/product-orders`. * Product orders made with *Product order templates* (the links we create for you). * Product orders made by a merchant on [portal.vippsmobilepay.com](http://portal.vippsmobilepay.com) without prefill or template. There is also a `v2` endpoint to retrieve details for one specific product order: `GET:/management/v2/product-orders/{productOrderId}/details`. More information: * [Get a list of product orders](https://developer.vippsmobilepay.com/docs/APIs/management-api/management-api-guide.md#get-a-list-of-product-orders) * [Get information about a product order](https://developer.vippsmobilepay.com/docs/APIs/management-api/management-api-guide.md#get-information-about-a-product-order) ## Recurring API: Changes to List Agreements API We observe that many integrations don't use the recommended way of using the `pageNumber` and `pageSize` filters while calling the [List Agreements endpoint](https://developer.vippsmobilepay.com/redocusaurus/recurring-swagger-id.yaml). This will result in increased response times when the number of agreements is high. The chances of causing instabilities to other endpoints cannot be ruled out either. So, we have decided to enforce the default values when merchants don't use these filters. The default value for `pageNumber` is 1 and `pageSize` is 500 agreements. This change will be rolled out from 1 Feb 2025. ## Recurring API: App changes This is a repetition from the [2024-09 technical update](https://developer.vippsmobilepay.com/docs/technical-updates/2024-09.md), because it's important: Please read [Recurring API November change log](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/CHANGELOG.md#november-2024) ## Recurring API: Webhooks improvements We have expanded Agreement and Charge webhooks with the `msn` (Merchant Serial Number) property. See [Recurring API event types](https://developer.vippsmobilepay.com/docs/APIs/webhooks-api/events.md#recurring-api-event-types) ## Recurring API: V2 turned off February 1st The Recurring API version 2 will be shut down February 1, 2025, so please make sure you're using version 3. Our migration guide will take you through all the details, if you haven't already switched. ## HTTPS and TLS Due to security risks, we will no longer support very old cipher suites for TLS. The accepted cipher suites are documented on the [Server](https://developer.vippsmobilepay.com/docs/knowledge-base/servers.md#https-and-tls) page. ## 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).