Error codes

An error code looks like [PREFIX]_[CODE] or:

There are different prefixes:

Errors are returned via 4 parameters:

{
  "errorCode": "INT_015",
  "errorMessage": "invalid customer email",
  "detailedErrorCode": null,
  "detailedErrorMessage": "Invalid input value [name=customer.email, value=fake-email]"
}

New error codes can be added in the future. Your implementation must imperatively take this fact into account.

These errors occur on the merchant acquirer''s side (bank).

The code of acquirer''s authorization rejection is returned in detailedErrorCode. These codes are returned without any modifications. They are specific to each acquirer.

For example, if a VISA card is rejected because it was identified as stolen, the structure of the error will be:

{
  "errorCode": "ACQ_001",
  "errorMessage": "payment refused",
  "detailedErrorCode": "43",
  "detailedErrorMessage": "Stolen card"
}

The most frequent detailed error codes (detailedErrorCode) are:

AUTH errors (as in “authentication”) are usually linked to issues with authentication servers (e.g. during 3D Secure).

These errors occur in the buyer''s browser. They occur before the payment data is sent to our servers. This concerns, for example, local form data validation errors or JavaScript client integration errors.

For more information, see the JavaScript client documentation.

INT errors (as in “integration”) are usually linked to issues with integration on the merchant side.

PSP errors (Payment Service Provider) occur when the PSP cannot process the request.