Skip to main content

PSP Merchant API changelog

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.

April 2026​

  • v1.3.0:
    • Renamed this API from PSP Signup API to PSP Merchant API. The functionality is unchanged.
    • The organizationNumber field is now validated against official business registries for Nordic merchants on onboarding.
      • For Norway: the org number must be 9 digits, the merchant must be active in Brønnøysundregistrene, and must be a main entity ("hovedenhet"), not a sub-entity ("underenhet").
      • For other Nordic countries: the org number, address, and related fields are validated as much as practically possible.

February 2026​

  • v1.2.0:
    • Added termsOfServiceAccepted field to the Create merchant and Update merchant requests.
      • Optional boolean field indicating whether the merchant has accepted the Vipps MobilePay terms of service for GDPR and Privacy. Required for login, userinfo, and express features.
    • Added companyName field to the Update merchant request, allowing the merchant's legal name to be updated.

June 2025​

  • Expanded the maximum length of merchantSerialNumber from 6 to 10 digits (pattern ^\d{5,10}$) across all endpoints and response models.

September 2023​

  • Removed mccCode and logoUrl fields from the Get merchant and Get all merchants responses. These fields were only relevant for create/update operations.

June 2022​

March 2022​

  • Added logoUrl field to Create merchant and Update merchant, allowing a URL to a hosted logo image as an alternative to the Base64-encoded logo field.

June 2021​

  • v1.1.3:
    • Added support for onboarding international (non-Norwegian) merchants. The organizationNumber field is now accepted for all countries, with validation applied as much as practically possible for non-Norwegian org numbers.
Last updated on