> **Description:** Details about API and platform updates for October 2026. > **AI agent:** Read [https://developer.vippsmobilepay.com/docs/knowledge-base/ai-tools.md](https://developer.vippsmobilepay.com/docs/knowledge-base/ai-tools.md) first. It covers keeping API keys and secrets out of generated code. > **Full site overview:** For an overview of the entire site, read [https://developer.vippsmobilepay.com/llms.txt](https://developer.vippsmobilepay.com/llms.txt). # Technical update October 2026 **Highlights since the [June update](https://developer.vippsmobilepay.com/docs/technical-updates/2026-06.md):** - **[MobilePay becomes Vipps](#mobilepay-becomes-vipps)** -- on January 12, 2027, with new landing page domains - **[ePayment API](#epayment-api)** -- capture details, Express order details, and merchant legal links - **[Login API](#login-api)** -- in-app confirmation - **[Recurring API](#recurring-api)** -- agreement history and safe retries - **[Webhooks API](#webhooks-api)** -- webhooks for PSPs - **[Donations API](#donations-api)** -- more API clients and amount change requests - **[AI plugin](#ai-plugin)** -- skills for most of our APIs ## MobilePay becomes Vipps Following the [announcement on October 6](https://www.vippsmobilepay.com/en-NO/news/vipps-mobilepay-becomes-vipps-across-the-nordics), MobilePay will become Vipps on January 12, 2027. Continue to follow the [Merchant and partner guide](https://brand.vippsmobilepay.com/document/107#/-/merchant-and-partner-guide). Details about which brand assets to update, and when, will follow separately. ### Prepare for landing page domain changes On January 12, 2027, we plan to replace `pay.mobilepay.dk` with `pay.vipps.dk`, and `pay.mobilepay.fi` with `pay.vipps.fi`. The test domains may change earlier. See [Payment landing page](https://developer.vippsmobilepay.com/docs/knowledge-base/servers.md#payment-landing-page) for all domains, and for the new test domains when they are ready. **Do you validate our domains?** If your integration validates redirect domains, or allowlists our domains, for example in a firewall or a Content Security Policy, add the new domains before January 12, 2027. Most integrations are expected to continue working without changes. Also review your integration if it handles redirects in an iframe or webview, or checks whether the MobilePay app is installed before redirecting. ## ePayment API ### Capture deadline and error messages A new `captureGuaranteedUntil` field shows the capture deadline for a given payment. For some payment methods, this can be earlier than the general [Capture attempt deadlines](https://developer.vippsmobilepay.com/docs/knowledge-base/reserve-and-capture.md#capture-attempt-deadlines). Capture error messages now also include more detail for timing-related failures. ### Express order details For [Express](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/express.md) payments created with order details, the shipping order line is now set to the shipping method the user selected in the app. ### Merchant legal links You can now link to your terms of sale and privacy policy from the payment in the app. Add the optional `merchantLegalLinks` object, with `termsOfSaleUrl`, `privacyPolicyUrl`, or both, when you [create a payment](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/operations/create.md). See the [API reference](https://developer.vippsmobilepay.com/redocusaurus/epayment-swagger-id.yaml) for details. ## Login API With [In-app confirmation](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/in_app_confirmation.md), "remember me in browser" is disabled, so the user must always confirm the login in the app. This feature is available to merchants on the advanced pricing tier. ## Recurring API - **Deleted profiles**: When a user deletes their profile, their active agreements are now stopped automatically, with `actor` set to `ADMIN` in the `recurring.agreement-stopped.v1` webhook. We are also stopping agreements that belong to previously deleted profiles, so you may receive a burst of these webhooks. - **Safe retries**: Stopping an agreement that is already `STOPPED` now returns `204 No Content` instead of an error, so you can safely retry a stop. - **Agreement history**: Fetch agreement and List agreements now return `history`, an oldest-first array of lifecycle events, each with its `actor`. - **Removed field**: The `explanation` field has been removed from the `campaign` object. See the [Recurring API changelog](https://developer.vippsmobilepay.com/docs/APIs/recurring-api/CHANGELOG.md) for full details. ## Webhooks API PSPs can now register and manage webhooks, the same way partners do. See [Partner/PSP webhooks](https://developer.vippsmobilepay.com/docs/APIs/webhooks-api/api-guide.md#partnerpsp-webhooks). ## Donations API Merchants can now add more than one merchant-level API client and delete clients they no longer need. See [How to get the API keys](https://developer.vippsmobilepay.com/docs/APIs/donations-api/api-guide.md#how-to-get-the-api-keys). To ask a donor to change the amount of an active agreement, for example during an upgrade campaign, merchants and partners can send an amount change request. The donor approves or declines the requested amount in the app. See the [Donations API changelog](https://developer.vippsmobilepay.com/docs/APIs/donations-api/CHANGELOG.md) for details. ## AI plugin We have created the `vipps-developer` plugin, which you can add to Claude Code, Cursor, or Codex. If you use one of these tools, the plugin can help you build your integration. It now has skills for most of our APIs, so your coding assistant gets current guidance on picking an API, implementing it, and getting ready to go live, rather than working from memory. The skills cover: - **Payments**: ePayment, Recurring, QR, Donations, and the Widget SDK - **PSPs**: the PSP ePayment API and the PSP Recurring API - **Login and user data**: Login and Userinfo - **After the payment**: Order Management, Webhooks, Report, Sales, and settlement - **Merchants**: Management API - **Getting started**: access tokens, choosing an API, and testing and going live The plugin's source is in the public [agent-toolkit](https://github.com/vippsas/agent-toolkit) repository on GitHub. To install it, see [AI plugin](https://developer.vippsmobilepay.com/docs/knowledge-base/ai-tools.md).