Error handling

SDK errors

Exactly what happens in each scenario when using the SDK solution is described in more detail in the "Making a payment" section of the SDK documentation.

Invalid card information errors: The onInvalidCard callback is called.

Errors occurring before 3DS step: The onFailurecallback is called.

Errors occurring during 3DS step: End user is redirected to the redirectOnFailUrl set in the payment creation request. A query parameter called errorCode will be appended to the redirect URL, for example: https://stage-b2b.payer.se/fail?errorCode=DECLINED .

Redirect widget errors

When things go wrong when using the widget in redirect mode, the user will be redirected to the redirectOnFailUrl set in the payment creation request, once they click the 'Cancel' button. A query parameter called errorCode will be appended to the redirect URL, for example: https://stage-b2b.payer.se/fail?errorCode=DECLINED .

Embedded widget errors

When things go wrong when using the widget in embedded mode, messages will be posted to the parent page once the user clicks the 'Cancel' button. See message types and examples for more details.

API errors

For cards, the errors can be a little different from other Payer endpoints. Below is described the general errors as well as the special cases for cards.

Details on the card endpoints are found in API documentation.

General

Payer uses HTTP response status codes to indicate the success or failure of your API requests. If your request fails, Payer returns an error using the appropriate status code.

In general, there are three status code ranges you can expect:

• 2xx success status codes confirm that your request worked as expected
• 4xx error status codes indicate an error because of the information provided, including information from you or your end user.
• 5xx error status codes are rare and indicate an error with Payer’s platform. Try again in the event of a 500 error and contact Payer if the issue persist.

Some 4xx errors

Some 4xx errors that could be handled programmatically (e.g., a card is declined) include an error code—a short string with a brief explanation—as a value for code. See tables below for possible error codes that can be returned and information about how to resolve them.

When such an error is received from the API, it’s returned in the response body code parameter.

{

    ....

    "code": "DECLINED"

    "message": "Failed to authorize payment.",

    ...

}

Error codes