> **Description:** All notable changes to the Login API will be documented here.

# Changelog

All notable changes to the current API will be documented here.
To learn about API versioning, see
[API lifecycle](https://developer.vippsmobilepay.com/docs/knowledge-base/api-lifecycle.md).

Changes that affect multiple APIs are documented in the [general changelog](https://developer.vippsmobilepay.com/docs/changelog.md).

## June 2026

* Added [In-app confirmation](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/in_app_confirmation.md), 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](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/collecting-consents.md) for details.

## September 2025

* Added user data to the [id-token](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/core-concepts.md#id-token)

## August 2025

* Increased the lifetime of the [id-token](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/core-concepts.md#id-token) to 1 hour

## May 2025

* The `email` and `email_verified` fields were added to the [id-token](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/core-concepts.md#id-token)

## April 2025

* The `gender` [scope](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/user-info.md#scopes) 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

* Added support for controlling session timeout via the `requested_expiry` parameter in the [Merchant-initiated login integration](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/merchant-initiated-login-integration.md) flow.

## April 2024

* Added support for [Marketing consent in browser](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/browser-flow-integration.md#browser-flow-marketing-consents).

## January 2023

* Removed the QR code login flow.

## September 2021

* Vipps Login support for logging in directly from phone number (CIBA) and QR code.
 See:
 [Merchant-initiated login integration](https://developer.vippsmobilepay.com/docs/APIs/login-api/api-guide/merchant-initiated-login-integration.md).

## 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.

> **Full site overview:** For every page in this documentation, read [https://developer.vippsmobilepay.com/llms.txt](https://developer.vippsmobilepay.com/llms.txt).