Result codes

Review the codes Adyen uses to provide information on the result of a payment.

Each payment has a resultCode that represents its current state, as well as any actions you should take:

resultCode	Description	Action to take
authorised	The payment was successfully authorised.	Inform the shopper that the payment was successful.
refused	The payment was refused.	Inform the shopper that their payment was refused. You'll receive a `refusalReason` in the same response that indicates why it was refused. We do not recommend disclosing this refusal reason to the shopper. Ask the shopper to try the payment again using a different payment method or card.
redirectShopper	The shopper needs to be redirected to an external web page or app to complete the payment.	Redirect the shopper to complete the payment. This result code only applies to our API integration.
received	This is part of the standard payment flow for methods such as SEPA Direct Debit, where it can take some time before the final status of the payment is known.	Inform the shopper that you've received their order, and are waiting for the payment to clear. It can take minutes, hours, or even days for some payments to clear.
cancelled	The payment was cancelled (by either the shopper or your own system) before processing was completed.	Inform the shopper that their payment was cancelled. Contact the shopper to check whether they want to continue with their order.
pending	It's not possible to obtain the final status of the payment at this time. This is common for payments with an asynchronous flow, such as Boleto, iDEAL, or Klarna.	Inform the shopper that you've received their order, and are waiting for the payment to be completed. When the shopper has completed the payment you will receive a successful AUTHORISATION notification. It can take minutes, hours, or even days for some payments to be completed.
error	There was an error when the payment was being processed.	Inform the shopper that there was an error processing their payment. You'll receive a `refusalReason` in the same response, indicating the cause of the error. For more information on what caused the error, contact our Support Team.