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.

January 2025

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

• Landing page: More robust handling of retries. See General changelog for details.

August 2024

Added taxRate to the optional receipts, 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

• v1.3.0: Added metadata to the create payment endpoint: POST:/epayment/v1/payments. The metadata is returned in the /epayment/v1/payments/{reference}

July 2023

• v1.2.3: Added the possibility of sending receipt data to the create payment endpoint: POST:/epayment/v1/payments. Receipts are generated in the Order Management API.

June 2023

• v1.2.2: Added personalQr to the Customer properties to the create payment endpoint: POST:/epayment/v1/payments.

May 2023

• v1.2.1: Removed the deprecated paymentAction properties.

April 2023

• v1.1.4: Added the Force Approve a payment endpoint: POST:/epayment/v1/payments/{reference}/approve.

March 2023

• v1.1.3: Removed Direct Capture from the ePayment API.
• v1.1.2: Removed receipt from the create payment endpoint: POST:/epayment/v1/payments.

December 2022

• ePayment API v1.1.1