> **Description:** A chronological record of all significant changes, updates, and improvements made to the PSP API, including new features, bug fixes, and deprecation notices for payment service providers.

> **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).

# Vipps PSP API changelog

**Maintenance mode**

This API is in maintenance mode: we continue to support and maintain it, and no end of life date is planned.
New PSP functionality is added to the [ePayment API](https://developer.vippsmobilepay.com/docs/APIs/psp-epayment-api/README.md), so we recommend it for
new integrations.

This API is only available in the Norwegian market.

## November 2024

* Landing page: More robust handling of retries. See
[General changelog](https://developer.vippsmobilepay.com/docs/changelog.md#landing-page-more-robust-handling-of-retries) for details.

## October 2020

Launched PSP API v3:

Vipps launched the PSP API v3 to coincide with our migration of our users' cards from PAN to EMVco network
tokens. This technological migration is Vipps' strategy for achieving delegated
SCA once PSD2 comes into effect for card payments on 2021-01-01.

The PSP API v3 is functionally identical to PSP API v2 apart from the
additional payment source format. There are also minor changes to naming of
properties to bring the API in line with Vipps' API standards.

Encrypted cards will still be sent for our users' cards that have not yet been
migrated.