Changelog
Here you'll find updates about changes to our general infrastructure and other key developer resources.
For details on API-specific changes, please refer to the individual changelogs. For example:
November 2025β
- Management API: Product order prefilling improvements and deprecated field removal.
October 2025β
- Recurring API: Reduced lead time for charge creation and payment source blocking support.
September 2025β
- Recurring API: Unified rate limits.
- Login API: User data added to ID token.
- Checkout API: Helthjem integration removed.
We added rate limiting to the API Lifecycle.
August 2025β
- ePayment API: Express feature launched.
- Login API: Agreement scope support and increased ID token lifetime.
We enabled refunds of recurring transactions on portal.vippsmobilepay.com for merchants in Denmark and Finland.
Previously, manual refunds made in the portal did not immediately update the API, and outdated charge details could be returned until the same refund was performed via the API.
From 19 August 2025, the API now returns updated information immediately for refunds made in the portal, and a webhook event is also sent.
July 2025β
- Recurring API: Removed deprecated countryCode field.
We have removed some complex and unused functionality where two or more sales units could use the same ledger. All sales units now have their own unique ledger.
No new ledgers will contain information for more than one sales unit (merchant serial number).
June 2025β
- Checkout API: Delivery details enhancement.
- Recurring API: Charge processing improvements.
May 2025β
- Login API: Email fields added to ID token.
- Recurring API: Webhook and timestamp improvements.
April 2025β
- Login API: Gender scope added.
- Recurring API: Charge refund webhook.
Automatic card updatesβ
Starting in April, cards added to the Vipps
or MobilePay
app will be
automatically updated before their expiry date.
This applies to both Visa and MasterCard, leveraging their token-based update services to ensure seamless functionality.
With automatic updates, conversion rates for the Recurring API and ePayment API will see a boost, offering merchants more reliability in payments.
This feature will roll out in Norway first, followed by Denmark and Finland.
March 2025β
- Login API: Marketing consent memory.
February 2025β
- Checkout API: Bank transfer removed.
- Report API: Personal information for Vippsnummer merchants.
Partner portalβ
The partner portal is live! This empowers partners and large merchants (configured as partners) to:
- Check the status of all product orders
- Get the details for one merchant
- Get a list of all sales units
- Get a list of all sales units for one merchant
- Get details for a sales unit
- Get a list of price packages
This is our Minimum Viable Product (MVP), and your feedback is key! Let us know what features you'd like us to prioritize. For more details, visit the partner portal section.
January 2025β
- ePayment API: Reference length increase and error codes.
- Login API: Phone number changes support.
- Recurring API: Webhook improvements and new features.
- Management API: Settlement bank account changes.
Webhook retry strategyβ
(Retroactively added; originally implemented on 2024-11-28)
The webhook retry strategy has been updated to enhance reliability and performance. For details on the new approach, check out the Webhooks API guide: Retry strategy.
December 2024β
Easier payments for merchants serving Norway, Denmark, Finland, or Swedenβ
Companies based in Denmark, Finland, or Norway can now offer both
Vipps
and MobilePay
to customers in these countriesβas well as Sweden.
This makes it even simpler to reach more users across the Nordics with seamless payment options.
If you're still using one of the older APIs, some features might not be available. Upgrade from eCom to ePayment.
Learn more about cross-border options in Offering Vipps MobilePay in the Nordics.
November 2024β
- Management API: New v2 product order endpoints.
- Recurring API: Enhanced webhooks and agreement management.
Landing page: More robust handling of retriesβ
We've improved how retries are handled to prevent double payments when users navigate away from the Vipps MobilePay landing page βfor example, by using the browser's Back button or a keyboard shortcut to return to the merchant's site.
Now, if a user navigates back from the landing page, the payment will be cancelled. This ensures they can't go forward again and accidentally pay for the same transaction twice.
For more details, see the FAQ:
- What happens if the user navigates back to my checkout from the landing page? (ePayment API)
- What happens if the user navigates back to merchant checkout from the landing page? (PSP API)
- What happens if the user navigates back to merchant checkout from the landing page? (MobilePay Online API)
October 2024β
- Management API: Deprecated v1 product order endpoints.
Updated TLS cipher suite supportβ
To maintain strong security, we will no longer support very old cipher suites for TLS. The list of accepted cipher suites is available on the Server page.
September 2024β
- Recurring API: Pagination support.
Swedish users can now shop with Vippsβ
Swedish users can use the Vipps app to make purchases from Norwegian merchants. For more details, check out Payments from Sweden.
August 2024β
- Login API: Session timeout control.
- ePayment API: Decimal tax rates.
- Checkout API: Tax percentage deprecation.
July 2024β
- ePayment API: Minimum user age and cancel options.
- Management API: Sales unit configuration fields.
June 2024β
- Report API: Sales unit information as array.
- Management API: Partner commission field.
MobilePay Online facade: Fully functionalβ
The limitations for the MobilePay Online facade have been removed, and it is now fully operational. Enjoy seamless testing in the test environment.
May 2024β
- Report API: Deprecated endpoint removed.
- Management API: Completed status for product orders.
- QR API: Category field for merchant callback QR.
MobilePay facade test environmentβ
The facades for MobilePay Subscriptions, App Payments, and Online are available in the test environment. Please visit test environment limitations to read about the limitations of the facade test.
The first version of the test environment is ready for MobilePay. It supports Danish and Finnish test users, test merchants, and currency, as described in the test environment section.
April 2024β
- Login API: Marketing consent in browser.
- Checkout API: Recurring agreement creation.
- QR API: Signing key upgraded.
March 2024β
- Management API: Product order management.
- QR API: Personal QR code exchange.
February 2024β
- Report API: GDPR data parameter.
- Checkout API: Bank transfer for Finland.
- Management API: Merchant category code prefill.
- Recurring API: Unscheduled charges and flexible intervals.
- Webhooks API: Enhanced webhook functionality.
January 2024β
Business portalβ
(Retroactive note from January 2025: The "Merchant portal" is changed to "Business portal".)
The new Vipps MobilePay business portal is portal.vippsmobilepay.com. For details about logging into the portal, see Portal: How to log in.
Status pagesβ
The Vipps MobilePay status pages have been updated and moved to new locations:
- Test environment status page: https://status-test.vippsmobilepay.com
- Production environment status page: https://status.vippsmobilepay.com
October 2023β
- Management API: New merchant and sales unit endpoints.
- Webhooks API: Synchronous webhooks and partner authentication.
September 2023β
- Report API: Version 2 launched.
- ePayment API: DKK and EUR currencies.
August 2023β
- ePayment API: Metadata support.
July 2023β
- ePayment API: Order details support.
April 2023β
- ePayment API: Force Approve endpoint.
March 2023β
- Webhooks API: Webhooks API launched.