Skip to main content

Changelog

All notable changes to the current API will be documented here. See: API lifecycle.

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

May 2026​

  • Added allowedCountries to the shipping object on the create payment endpoint. Accepts a list of ISO 3166-1 alpha-2 country codes to restrict which countries are available for shipping in Express payments.

March 2026​

  • Added PSP support via the new CARD_PASSTHROUGH payment method type. PSPs can now create payments where the user's card token is sent to a PSP-controlled callback URL for processing. This requires:
    • paymentMethod.type set to CARD_PASSTHROUGH
    • A new cardPassthrough object in the create payment request body, specifying the callback URL, allowed card types, and optionally a public encryption key ID for receiving encrypted PANs
    • The Psp-Id header on all requests
    • See ePayment PSP API guide for details.

September 2025​

  • v1.8.1:
    • Profile sharing now returns userDetails directly in the GET:/epayment/v1/payments/{reference} response and the epayments.payment.authorized.v1 webhook payload. The userDetails object contains the profile fields you requested via profile.scope: email, firstName, lastName, mobileNumber, dateOfBirth, and addresses. Previously, retrieving this data required a separate call to the Userinfo API. See Profile sharing for details.

August 2025​

  • v1.8.0: Express is launched. Express lets customers select shipping options and confirm their delivery details directly inside the Vipps or MobilePay app, without being redirected to the merchant's website. Merchants can provide fixed or dynamic shipping options. The final amount — including shipping — is shown to the user before they confirm payment.

January 2025​

  • v1.7.0: We have bumped the maximum reference length from 50 to 64 characters.

  • v1.6.0: We have added error codes to the ePayment API errors. This will allow you to more accurately map the errors to your application. For details, see ePayment API errors.

The text for the following error messages have been changed as follows:

  • 5070 - "Payment cannot be created":
    • Changed HTTP status code from 400 to 422.
    • Changed detail to append "missing precondition, or incorrect merchant setup".
  • 5100 - "Refund not possible":
    • Changed detail from "Cannot refund single transferred payments" to "Cannot refund payment due to a configuration problem".
  • 6060 - "Cannot cancel pending":
    • Changed title from "Cannot cancel pending" to "Cannot cancel authorized payment".
    • Changed detail from "Cannot cancel a pending payment" to "This payment is authorized and cannot be cancelled when CancelTransactionOnly is set".
  • 6160 - "Order processing":
    • Changed detail from "Too many concurrent requests. The payment is being processed" to "Order locked and is already processing".

November 2024​

August 2024​

Added taxRate to the optional order details, to allow decimal points in the tax lines.

July 2024​

  • v1.6.0: Added minimumUserAge field to create payment endpoint payload. If set, only customers above the given age are allowed to authorize the payment.

  • v1.5.0: Added cancelTransactionOnly flag to Cancel endpoint payload. If the flag is set and the transaction has been authorized, the reserved amount will not be cancelled.

September 2023​

  • v1.4.0: Added DKK and EUR currencies. Only allowed for Danish and Finnish merchants, respectively.

August 2023​

July 2023​

June 2023​

May 2023​

  • v1.2.1: Removed the deprecated paymentAction properties.

April 2023​

March 2023​

December 2022​

  • ePayment API v1.1.1
Last updated on