Change of error messages for token based creditcard payments - External integration environment
Scheduled Maintenance Report for Swedbank Pay
The scheduled maintenance has been completed.
Posted Feb 14, 2024 - 10:30 CET
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Feb 14, 2024 - 10:00 CET
We will be making a change in the error messages that are given in response in the eCommerce API in the case that the requested Payment/One-Click/Recur/Unscheduled-token does not exist or is deleted.

The following new errorType will be introduced (only for Payment Order):

In addition to the one that is in currently in use (for both Payment Instruments and Payment Order):

The flow will be as follows:

First, a check is made to verify if the token exists or not. If it does not exist, the API returns an error of the type "InputError". If, however, the token exists but is deleted, then the API returns an error of the type "TokenInactive".

Examples of the error messages are presented below.

InputError, in this instance for RecurrenceToken:
"title":"Error in input data",
"detail":"Input validation failed, error description in problems node!",
"description":"The given RecurrenceToken does not exist."

TokenInactive, in this instance for UnscheduledToken:
"type": "",
"title": "Payment token is inactive",
"status": 422,
"instance": "
"detail": "The given UnscheduledToken is inactive.",
"name": "UnscheduledToken",
"description": "The given UnscheduledToken is inactive."

Do not hesitate to contact us via the ordinary support channels if any questions should arise.
Posted Feb 02, 2024 - 09:23 CET
This scheduled maintenance affected: Payment Solutions (m/ecom Card Payments).