Skip to main content

Changelog

View as Markdown (opens in a new tab)
Install AI tools

Give your assistant up-to-date guidance for our APIs, with our plugin or without it.

The plugin is still under development. See the AI tools page for details.

Run both commands, in order.

claude plugin marketplace add vippsas/agent-toolkit
claude plugin install vipps-developer@agent-toolkit

For troubleshooting, see the full instructions.

All notable changes to the current API will be documented here. To learn about API versioning, see API lifecycle.

Changes that affect multiple APIs are documented in the general changelog.

September 2026​

Changes to user information​

On January 1, 2027, a new agreement with our subcontractor takes effect which limits our ability to share nin (national identity number) for Norwegian users. See User info: scopes.

What does this mean for you?

As a merchant that is requesting scope nin in the Norwegian market, you need to transfer away from this data point by following these steps:

  • Remove the usage of nin from your internal system
  • Remove the scope nin from your integration

If NIN is still requested after January 1, 2027, the login request will still work, but the nin will no longer be provided in our userinfo and ID token response, User info: step 2. Get the information.

June 2026​

  • Added In-app confirmation, a Login flow where "remember me in browser" is disabled so the user is always required to confirm the login in their Vipps or MobilePay app.

January 2026​

  • Added new scope, customFlow, that enables merchants to fully customize their consent collection experience using the flow builder in the business portal. This is the recommended approach for new integrations. See Collecting consents for details.

September 2025​

August 2025​

  • Increased the lifetime of the id-token to 1 hour

May 2025​

  • The email and email_verified fields were added to the id-token

April 2025​

  • The gender scope was added.

March 2025​

  • Users accepting marketing consents will now be remembered on the server side. This means they will not be asked to accept the same marketing consent every time the delegatedConsents scope is present.

January 2025​

  • Vipps MobilePay users can now change their phone number. This means you can get the same sub with different phone numbers.

August 2024​

April 2024​

January 2023​

  • Removed the QR code login flow.

September 2021​

February 2021​

Launched Login API version 2​

To have a unified way of providing user information across Vipps services, we are standardizing the data formats, both within Vipps and with the OIDC standard.

Other improvements​

The merchant can choose whether the user should be automatically returned to the browser after completing the authentication in Vipps. We have also added a specific flow for integrations with native apps.

Last updated on