| Description | What happened for this alternative payment method. |
| Customer message | What to show the customer. |
| Next step | Recommended merchant action after the decline. |
Payment operations for alternative payments are handled asynchronously. The final result, including any decline, is delivered through a webhook notification or via the check order status endpoint.
When testing decline scenarios, the decline code and final order status appear in those asynchronous updates.
Should you need help with error codes, contact us for assistance.
General decline
Errors reflect declined alternative payment transactions stemming from session timeouts, authentication failures, or customer abandonment.
0.02 Order expired
This typically means the customer did not complete the payment or the required actions within the allowed time window. In most cases, this is attributed to customer abandonment.
"Your session has expired. Please try your payment again." APM developer action
Check whether the customer intentionally abandoned the payment. If not, retry by creating a new order and guide them to complete all required actions within the session time window.
Service access
These errors occur when authentication for an alternative payment method fails.
1.01 Authentication failed
This decline covers authentication-related failures, such as an incorrect or expired PIN or one-time code.
"Authentication failed. Please try again." APM developer action
Ask the customer to retry the authentication process, ensuring they enter a valid and unexpired PIN or one-time code. If the issue persists, advise them to reset their credentials or contact their payment provider.
Validation errors
These errors indicate invalid alternative payment request data.
2.01 Invalid data/Order not found
This error indicates that required method specific fields are missing or incorrect.
"The payment request could not be processed. Please check your details and try again." APM developer action
Validate all APM specific required fields before submission. Refer to the relevant payment method documentation to ensure all required parameters are correctly provided.
Transaction declines
3.05 Call your bank
In some cases, the decline may occur because the customer has not enabled the relevant payment method in their account settings. They should check and update their settings accordingly.
"Your bank requires you to call them before this payment can proceed. Please contact your bank and try again." APM developer action
Ask the customer to verify that the payment method is enabled in their bank or app settings and update it if needed. If the issue persists, suggest contacting their bank's support or trying a different payment method.
Restrictions or duplicate transactions
4.06 Blocked by country/IP
This code also covers cases where a specific payment method is unavailable or unsupported in the customer’s current location.
"Your payment was declined. Please try again." APM developer action
Verify whether the selected APM is supported in the customer's region. If it is not available, suggest an alternative payment method that is accessible in their location.