Adyen

Received

The financial institution received the request to make the payment. The shopper must still complete their authorization. When the shopper completes the authorization, the payment gets the Authorised status.

Open

The offer is pending authorization. Applies to payments where authorization is asynchronous, such as redirects to issuers, 3D Secure 2 authentication flows, or redirect-based payment methods.

Offer Cancelled

The payment was not successfully authorized by the shopper, so the offer was cancelled. Applies to asynchronous authorization flows. If funds left the shopper's account, they should contact their issuing bank. This is a final status.

Offer Expired

The payment was not successfully authorized by the shopper within the payment method's time limit, so the offer was cancelled. Applies to asynchronous authorization flows. This is a final status.

Authorised

The shopper authorized the payment, and it was approved by the financial institution. Funds are reserved and the payment gets captured automatically by default. Wait for capture before delivering goods or services.

Authorised Pending

The shopper's bank approved the payment, but the card and the payment terminal must still confirm that the payment can be made. If authorized it moves to Authorised; if cancelled it moves to Cancelled.

Cancelled

The payment was cancelled, preventing funds from being transferred. If funds are reserved in the shopper's account, ask the shopper to contact their bank to release the funds. This is a final status.

Refused

The payment request was received but not approved. Rejected by the scheme, financial institution, or Adyen's risk checks. Check the refusal reason to understand why. This is a final status.

ERROR

An error occurred while communicating with the financial institution, so funds were not processed. Ask the shopper to retry the payment and verify the payment request was correct. This is a final status.

Retried

An error occurred while communicating with the financial institution, so funds were not processed. Adyen has automatically retried authorization. If retry succeeds, payment moves to Authorised.

Expired

The payment has expired and can no longer be captured. Occurs when an Authorised payment is not captured or cancelled within the payment method's validity period (typically 28 days for cards). Ask shopper to make a new payment. This is a final status.

Handled Externally

Applies to cash payments handled outside the Adyen platform. The payment has been registered for bookkeeping purposes only and appears as a transaction without a settlement in Customer Area. This is a final status.

Received Incremental Auth

The original authorized amount was adjusted (incremental authorization). When the adjusted amount is processed, the payment returns to the Authorised status and can be captured.

Sent For Settle

The request to transfer funds has been sent to the financial institution. This payment can no longer be cancelled. Adyen is waiting to receive the funds; expect Settled status within 10 days.

Settled

The funds from the payment have been received by Adyen. Does not necessarily mean funds have been paid out to the merchant; depends on the payout model. This is a final status for successful payments.

Settled Bulk

Applies only to payments where Adyen performs acquiring. Funds have been received by Adyen. Equivalent to the Settled status. This is a final status for successful payments.

Settle Scheduled

Applies to Sales day payout transactions only. The payment was successfully captured and confirmed. Net transaction amount will be paid out per the Sales day payout schedule. Appears in reports as Settled. This is a final status.

Settled Externally

The payment was settled with an external acquirer. Adyen received confirmation from the acquirer that funds were transferred to the merchant. This is a final status.

Settled Externally With Info

The payment was settled with an external acquirer with additional info. Adyen received acquirer confirmation that funds were transferred to the merchant. This is a final status.

Settled Installment

Applies to installment payments only. One installment of this payment has been settled. When all installments have settled, the payment moves to SettledInInstallments.

Settled In Installments

Applies to installment payments only. The full payment amount has been settled across all installments. Each installment carries the SettledInstallment status. This is a final status.

Settled Installment Bulk

Applies to installment payments only. The payment has been fully settled in installments. Settlement comes in installments, each with the SettledInstallment status. This is a final status.

Settled Reversed

The payment has not been settled because Adyen did not receive funds 30 days after capture. If funds are received after 30 days, the payment moves to Settled.

Capture Failed

The attempt to capture the payment failed and the shopper did not transfer funds to the merchant. Adyen will attempt to resolve and recapture. Check the CaptureFailureReason in Transaction Events.

Captured With Other Acquirer

The payment was captured by a different acquirer than the one used for authorization. The transaction was processed as a new payment with the same merchant reference. This is a final status.

Sent For Refund

The refund request has been sent to the financial institution. Adyen is waiting for confirmation. If Refunded status is not received within 10 days, contact Support.

Refunded

Funds were deducted from the merchant's account and the financial institution intends to return them to the shopper. It can take up to 40 days for the shopper to receive the funds. This is a final status.

Refunded Bulk

Applies only to payments where Adyen performs acquiring. Funds were deducted from the merchant's account and the financial institution intends to refund the shopper. Can take up to 40 days. This is a final status.

Refund Scheduled

The payment was successfully refunded. The institution took funds from the merchant's account and refunded the shopper. Net transaction amount will be debited per the Sales day payout schedule. This is a final status.

Refunded Externally

The payment was refunded through an external acquirer and Adyen received confirmation. If the shopper did not receive funds, contact the acquiring partner. This is a final status.

Refunded Externally With Info

The payment was refunded through an external acquirer with additional info, and Adyen received confirmation. If the shopper did not receive funds, contact the acquiring partner. This is a final status.

Refunded Installment

Applies to installment payments only. A single installment was refunded. When all installments are refunded, the payment moves to RefundedInInstallments.

Refunded In Installments

Applies to installment payments only. The full payment has been refunded across all installments. Can take up to 40 days for the shopper to receive all funds. This is a final status.

Refunded Installment Bulk

Applies to installment payments only. The payment has been fully refunded in installments. Can take up to 40 days for the shopper to receive funds. This is a final status.

Refunded Reversed

The refund was attempted but the shopper did not receive the funds; Adyen returned funds to the merchant's account. Common cause: the shopper's bank account is no longer valid. Contact the shopper to arrange another transfer method. This is a final status.

Refund Failed

The refund failed and the shopper did not receive funds. Funds remain in the merchant's account. Adyen will attempt to retry. Check RefundFailureReason in Transaction Events.

Refund Not Cleared

The shopper received the funds, but the refund was not settled because the acquirer did not process the refund within 30 days of initiation. An additional Refunded record may appear if the refund is processed later.

Refund Authorised

Applies to unreferenced refunds only. The refund has been recorded but the request has not yet been sent to the financial institution. The refund can still be cancelled before it moves to Refunded.

Refund Pending

Applies to unreferenced refunds for in-person payments only. The refund has been recorded but not yet sent to the financial institution. Can still be cancelled before it moves to Refunded.

Refund Scheduled Unconfirmed

Applies to Sales day payout transactions only. An intermediary state where the institution will take funds from the merchant's account to refund the shopper, but no funds have moved yet. Moves to RefundScheduled after processing.

Unconfirmed Refund Failed

Applies to Sales day payout transactions only after a RefundScheduledUnconfirmed status. The payment method did not confirm the refund or a technical error occurred. Initiate the refund again.

Acquirer Refund Failed

Applies to Sales day payout transactions only; appears in reports as RefundFailed. The acquirer notified Adyen that funds will not be paid out because the capture failed. Funds already paid out are reverted and credited back to the merchant's account.

Chargeback

The shopper attempted to reverse the payment and the issuer has started a dispute process. Adyen withdraws the disputed funds from the merchant's account. Supply defense documents or accept the chargeback via the Dispute details page.

Chargeback Externally

An external acquirer recorded the transaction as a chargeback. The shopper attempted to reverse the payment and the issuer started a dispute process. Adyen withdraws the disputed funds from the merchant's account.

Chargeback Externally With Info

An external acquirer recorded the transaction as a chargeback with additional info. The shopper attempted to reverse the payment and the issuer started a dispute process. Adyen withdraws the disputed funds from the merchant's account.

Second Chargeback

The defense of the first chargeback was not successful and the shopper has attempted to reverse the payment again. Adyen has withdrawn or will withdraw the disputed funds from the merchant's account. This is a final status.

Chargeback Reversed

The disputed funds have been transferred back to the merchant's account. The merchant successfully defended the dispute or the shopper repaid the funds. This is a final status for successful disputes.

Chargeback Reversed Externally With Info

An external acquirer recorded that the chargeback was reversed. The disputed funds have been transferred back to the merchant's account. The merchant successfully defended the dispute or the shopper repaid the funds. This is a final status.

Received Payout

Adyen received the payout request. When the payout is authorized, funds will be sent to the receiver.

Payout Authorised

The payout is authorized and funds will be sent to the receiver. After processing, the payment moves to SentForPayout, then PaidOut.

Refused Payout

The payout was refused. Rejected by the scheme, financial institution, or Adyen's risk checks. Check the refusal reason, review risk settings, and ask the shopper to contact their issuing bank. This is a final status.

Sent For Payout

Funds have been sent to the receiver but the payout is not yet complete. Adyen is waiting for financial institution confirmation. If PaidOut status is not received within 10 days, contact Support.

Paid Out

The payout was completed. Funds have been transferred to the receiver. This is a final status.

Paid Out Scheduled

The payout was successfully processed and funds sent to the receiver. Net transaction amount will be debited per the Sales day payout schedule. Equivalent to PaidOutAcquirer. Appears in reports as PaidOut. This is a final status.

Paid Out Externally

The payout was completed with an external acquirer. Funds have been transferred to the receiver. If the receiver did not receive funds, contact the acquiring partner. This is a final status.

Paid Out Externally With Info

The payout was completed with an external acquirer with additional info. Funds have been transferred to the receiver. If the receiver did not receive funds, contact the acquiring partner. This is a final status.

Paid Out Reversed

Applies to Sales day payout accounts. The payout was reversed because Adyen did not receive funds to be paid out or could not finish the payout process. This is a final status.

Payout Error

An error occurred while communicating with the financial institution and the payout was not processed. Verify the payment request was correct with the technical team. This is a final status.

Payout Failed

Adyen received the payout request and forwarded it to the card scheme, but the card scheme did not process it. Adyen will attempt to retry. Check PayoutFailureReason in Transaction Events.

Acquirer Payout Failed

Applies to Sales day payout transactions only; appears in reports as CaptureFailed. The acquirer notified Adyen that funds will not be paid out because the capture failed. Funds already paid out are reverted and debited from the merchant's account.

Authorised (No Refusal)

refusalReasonCode 0 is sometimes returned alongside resultCode Authorised. When this occurs, the refusal reason code should be ignored "" the transaction succeeded.

Refused

The transaction was refused by the issuer or acquirer without a more specific reason provided.

Referral

The transaction requires a referral. The issuer is requesting manual review or voice authorization before proceeding.

Acquirer Error

The transaction did not go through due to an error on the acquirer's end. This is not a shopper-side issue; it is an infrastructure or connectivity problem at the acquiring bank.

Blocked Card

The card used for the transaction is blocked and therefore unusable. The shopper should contact their issuing bank to unblock or replace the card.

Expired Card

The card used for the transaction has expired and is therefore unusable. The shopper should use a different, valid card.

Invalid Amount

An amount mismatch occurred during the transaction process. The amount submitted does not match what is expected by the issuer or scheme.

Invalid Card Number

The specified card number is incorrect or invalid. The shopper should check and re-enter their card details.

Issuer Unavailable

It is not possible to contact the shopper's bank to authorize the transaction. This is typically a temporary connectivity issue.

Not Supported

The shopper's bank does not support or does not allow this type of transaction. The shopper should try a different payment method or contact their bank.

3D Not Authenticated

3D Secure authentication was not executed or did not complete successfully. The transaction was declined due to a failed or missing authentication step.

Not Enough Balance

The card does not have sufficient funds to cover the payable amount. The shopper should use a different card or payment method.

Acquirer Fraud

The transaction was flagged as possible fraud by the acquirer. The payment was declined as a precautionary measure.

Cancelled

The transaction was cancelled. This corresponds to the Cancelled payment status when a cancellation is submitted.

Shopper Cancelled

The shopper cancelled the transaction before completing it. No funds were charged.

Invalid Pin

The specified PIN is incorrect or invalid. The shopper should re-enter the correct PIN.

Pin Tries Exceeded

The shopper entered an incorrect PIN more than three times in a row. The card may now be blocked. The shopper should contact their issuing bank.

Pin Validation Not Possible

It is not possible to validate the specified PIN number. This may indicate a technical issue with PIN processing.

FRAUD

Pre-authorization risk checks resulted in a fraud score of 100 or more. The transaction was flagged as fraudulent and refused. Review your risk settings if this is unexpected.

Not Submitted

The transaction was not submitted correctly for processing. Verify the payment request structure and parameters.

FRAUD-CANCELLED

The combined sum of pre-authorization and post-authorization risk checks resulted in a fraud score of 100 or more. The transaction was flagged as fraudulent and refused.

Transaction Not Permitted

The transaction is not permitted to the issuer/cardholder, not allowed for this merchant, or not permitted to the acquirer/terminal. Maps to issuer decline codes 57 and 58.

CVC Declined

The specified CVC (card security code / CVV / CID) is invalid. The shopper should re-enter the correct CVC from the back of their card.

Restricted Card

The card is restricted. Maps to issuer decline codes for restricted cards or cards invalid in a given country. The shopper should contact their bank or use a different card.

Revocation Of Auth

The shopper requested to stop a recurring subscription. Maps to issuer codes R0 (Stop Payment Order), R1 (Revocation of Authorization Order), and R3 (Revocation of All Authorizations Order).

Declined Non Generic

Maps all response codes that cannot be reliably mapped to a specific reason. Used to distinguish generic declines (e.g., Mastercard '05: Do not honor') from more specific refusal reasons.

Withdrawal Amount Exceeded

The transaction amount was higher than the withdrawal amount permitted for the shopper's card. The shopper should contact their bank or use a different card.

Withdrawal Count Exceeded

The shopper exceeded the number of withdrawals permitted on their card. The shopper should contact their bank or wait until the limit resets.

Issuer Suspected Fraud

The issuer reported the transaction as suspected fraud. The shopper should contact their issuing bank to resolve.

AVS Declined

The address data the shopper entered does not match the address on file with the card issuer. The shopper should verify their billing address.

Card Requires Online Pin

The shopper's bank requires the shopper to enter a PIN to complete this transaction. The shopper should proceed with PIN entry.

No Checking Account Available On Card

The shopper's bank requires a checking account to complete the purchase, but none is available on the card. The shopper should use a different payment method.

No Savings Account Available On Card

The shopper's bank requires a savings account to complete the purchase, but none is available on the card. The shopper should use a different payment method.

Mobile Pin Required

The shopper's bank requires the shopper to enter a mobile PIN to authorize the transaction.

Contactless Fallback

The shopper abandoned the transaction after attempting a contactless payment and being prompted to try a different card entry method (PIN or swipe).

Authentication Required

The issuer declined the authentication exemption request and requires full 3D Secure authentication for this transaction. Retry the payment with 3D Secure enabled.

RReq Not Received From DS

The issuer or scheme was unable to communicate the authentication outcome via RReq (Results Request message in 3D Secure 2). Retry the transaction.

Current AID Is In Penalty Box

The payment network cannot be reached for the current Application Identifier (AID). Retry the transaction with a different payment method.

CVM Required Restart Payment

A PIN or signature is required to complete the transaction. The shopper should retry the transaction providing the required cardholder verification method.

3DS Authentication Error

3D Secure authentication failed due to an issue at the card network or issuer level. Retry the transaction, or retry with a different payment method.

Transaction Blocked By Adyen To Prevent Excessive Retry Fees

Adyen's excessive retry prevention service blocked the transaction to protect the merchant from penalty fees charged by card schemes for excessive retries of declined transactions.

Token Revoked

The token granted to the merchant for recurring charges was disabled by the shopper. The shopper has revoked consent for future charges using this token.

Authentication Not Required

The transaction does not require 3D Secure 2 authentication. Check the authenticationNotRequiredReason field to learn why authentication was not required.

Authentication Finished

The payment has been successfully authenticated with 3D Secure 2. Collect the 3D Secure 2 authentication data needed to authorize the payment.

Challenge Shopper

The issuer requires authentication from the shopper, for example through facial recognition or entering a code received on their phone. Initiate the challenge flow to present the challenge to the shopper.

Identify Shopper

The issuer requires authentication from the device the shopper is using. Initiate the frictionless flow to get the shopper device fingerprint and submit the result to Adyen.

Redirect Shopper

The issuer requires the shopper to provide authentication in an external web page or app. Redirect the shopper to complete the authentication.

Received

The payment request was successfully received by Adyen and will be processed. This is the initial state for all payments.

Pending

The payment order was successfully received but the final status of the payment is not available yet. Common for payment methods with an asynchronous flow.

Present To Shopper

Additional information needs to be presented to the shopper so they can use it to complete the payment, for example a voucher. Present the voucher and inform the shopper to complete the payment.

Partially Authorised

The payment was authorized for a partial amount. This happens when the cardholder has insufficient funds. The merchant can start a new transaction for the outstanding balance, cancel, capture the partial amount, or retry later for recurring.

Authorised

The payment was successfully authorised. Inform the shopper that the payment was successful. A webhook with an updated payment status will also be sent.

Cancelled

The payment was cancelled (by either the shopper or your own system) before processing was completed.

Error

There was an error when the payment was being processed. Inform the shopper that there was an error processing their payment.

Refused

The payment was refused. Inform the shopper that their payment was refused and ask them to try the payment again using a different payment method or card. A refusalReason will indicate the cause of the error.

Multiple Messages

Generic error with multiple possible causes: incorrect API key or auth credentials, or unable to parse the message body.

Not Allowed

The API credential is missing required roles, the user API is incorrect, or you are making a third-party payment/card acquisition request without the required permissions.

Required Object Amount Not Provided

Missing parameter: add the `amount` or `originalReference` field, or compare your request against a standard request for that endpoint to identify missing parameters.

Invalid Card Number

Incorrect card number or length, or incorrect capitalisation of PaRes.

Unable To Determine Variant

The card number field contains an incorrect value.

CVC Is Not The Right Length

The CVC is not valid: it may be alphanumeric instead of numeric-only, contain more than three digits (four for Amex), or otherwise be malformed.

Billing Address Problem

Missing a required field under billingAddress. Check the object for missing fields.

Invalid PaRes From Issuer

The issuer returned a URL-encoded, differently named, or empty PaRes/MD. URL-decode the values and ensure the parameter name is exactly PaRes before re-submitting to /payments/details.

Session Already Used

This session was already used previously and cannot be reused.

Recurring Not Enabled

Missing user permission. Add the Merchant Recurring role to the associated web service user.

Invalid Bank Account Number

The IBAN is incorrect.

Invalid Variant

Missing txvariant details. Check requestData and pass the details correctly.

Bank Details Missing

The IBAN is missing or incorrect.

Invalid BankCountryCode Specified

The parameter name is spelled incorrectly, or the countryCode value does not follow ISO 3166-1 alpha-2 format (e.g. use DE for Germany).

Bank Country Not Supported

The countryCode length does not follow ISO standard or the country code does not exist.

No Invoice Lines Provided

Invoice lines are missing in the requestData.

Incorrect Invoice Line

Incorrect currency used or lineReference is null. Check the invoice line against requestData.

Total Amount Mismatch With Lines

linesTotalQuantity is not equal to request.getAmount().getValue().

Invalid Date Of Birth

The dateOfBirth format is incorrect. Check the date and format in the dateOfBirth parameter.

Invalid Billing Address

The billingAddress object does not contain all required fields. Check the required parameters in the API Explorer.

Invalid Delivery Address

The deliveryAddress is null or its format is invalid.

Invalid Shopper Name

The shopperName is null.

Shopper Email Not Provided

The shopperEmail is missing or its format is invalid.

Shopper Reference Not Provided

The shopperReference is null or recurring requires shopperReference.

Telephone Number Not Provided

The phoneNumber or telephoneNumber is null.

Invalid Phone Number

The phone number provided is invalid.

Invalid Recurring Contract Specified

The recurring object is not passed correctly. Check requestData and ensure the recurring object is correct.

Bank Account Or Location Id Not Valid Or Missing

The bank account or bank location ID is missing or invalid.

Account Holder Name Not Provided

Required field accountHolderName is not provided.

Card Holder Name Not Provided

Required field card.holderName is not provided.

Expiry Date Invalid

Expiry date value is not numeric, contains an empty space, the expiry month is not set, or the month value is not between 1 and 12.

Reference Missing

The reference parameter is missing or requestData is missing multiple parameters. Check that reference is passed correctly.

Billing Address City Not Provided

Required field billingAddress.city is not provided.

Billing Address Street Not Provided

Required field billingAddress.street is not provided.

Billing Address House Number Not Provided

Required field billingAddress.houseNumberOrName is not provided.

Billing Address Country Problem

The billing address country field is invalid or missing.

Billing Address State Or Province Not Provided

Required field billingAddress.stateOrProvince is not provided.

Failed To Retrieve Open Invoice Lines

Could not retrieve OpenInvoiceLines for the request.

Amount Field Not Valid

The amount passed is greater than the limit or is not a positive number.

Currency Field Not Valid

The provided currency is not supported.

Recurring Requires Shopper Email And Reference

Both shopperReference and shopperEmail are missing for a recurring payment request.

Invalid Expiry Month Or Year Before Now

Expiry month is not in [1..12], expiry year is not > 2000, or the date is in the past.

Invalid Expiry Month Or Year

Expiry month is not in [1..12] or expiry year is not > 2000.

Bank Name Or Location Not Valid Or Missing

The bank name or bank location is not valid or is missing.

iDEAL Merchant Return URL Too Long

The submitted total iDEAL merchantReturnUrl length exceeds the maximum size allowed for this request.

Invalid Start Month Or Year

startMonth is not in [1..12], startYear is not > 2000, or the date is in the future.

Invalid Issuer Country Code

The issuer country code provided is invalid.

Invalid Social Security Number

The social security number provided is invalid.

Delivery Address City Not Provided

Required field deliveryAddress.city is not provided.

Delivery Address Street Not Provided

Required field deliveryAddress.street is not provided, or the value is empty.

Delivery Address House Number Not Provided

Required field deliveryAddress.houseNumberOrName is not provided.

Delivery Address Country Problem

The delivery address country field is invalid or missing.

Delivery Address State Or Province Not Provided

The stateOrProvince field is missing in the delivery address and is required for the selected country.

Invalid Number Of Installments

Installment value is zero or the payment method is not configured with installment. Check requestData and configure installment under the specific payment method.

Invalid CVC

The CVC is not numeric or contains invalid values.

No Additional Data Specified

No additional data was specified in the request.

No Acquirer Specified

No acquirer was specified in the request.

No Authorisation MID Specified

No authorisation merchant ID was specified in the request.

No Fields Specified

No fields were specified in the request.

Required Field Not Provided

One of the following fields is missing: initialPspReference, orderReference, ownerName, or reference. Supply the missing value.

Invalid Number Of Requests

The number of requests in the batch is invalid.

Not Allowed To Store Payout Details

The credential does not have permission to store payout details.

Invalid IBAN

The IBAN is incorrect, there is a mismatch between IBAN and country, or the bank does not support SEPA direct debit.

Inconsistent IBAN

Swift Code / BIC does not exist, payout party/account BIC/Swift is invalid, BIC does not correlate to countryCode, or IBAN characters/digits exceeded.

Invalid BIC

The BIC provided is invalid.

Auto Capture Delay Invalid Or Out Of Range

The auto capture delay value is invalid or outside the permitted range.

MandateId Does Not Match Pattern

The mandateId does not match the required pattern.

Amount Not Allowed For This Operation

The amount provided is not permitted for this operation.

Original PSP Reference Required

The original PSP reference in the requestData field is missing.

Authorisation Code Required

An authorisation code is required for this operation.

Generation Date Required But Missing

The generation date is required but was not provided.

Unable To Parse Generation Date

The generation date could not be parsed.

Encrypted Data Outside Valid Time Period

The server-side date/time is not configured correctly (e.g. set to 1975, or not within 24 hours of the current time). Check server-side date/time configuration.

Unable To Load Private Key For Decryption

The private key for decryption could not be loaded.

Unable To Decrypt Data

Decryption failed. Common causes: using HTTP GET instead of POST, environment mismatch (LIVE/TEST), incorrect origin/client key, or API key mismatch.

Unable To Parse JSON Data

Parameters sent are not correctly formatted in JSON. Read through requestData to find the error.

Invalid Shopper Reference

shopperReference is empty, does not exist, or is not found.

Invalid Shopper Email

shopperEmail is empty, does not exist, or is not found.

Invalid Selected Brand

The selected brand is not equal to the brand on the stored token, or is empty.

Invalid Recurring Contract

The recurring contract was not found in Recharge.

Invalid Recurring Detail Name

The recurring detail name is empty/null or does not match the recurringDetail name.

Invalid Additional Data

Too many fields/entries, splitPayment is missing or invalid, or adyenGivingAccount is not specified/retrievable. Check the additionalData object.

Missing Additional Data Field

A required field in additionalData is missing.

Invalid Additional Data Field

An additionalData field is invalid: too many entries, splitPayment missing/invalid, or adyenGivingAccount not specified or retrievable.

Invalid PSP Echo Data

The previous recurringDetail token was not saved correctly or does not exist.

Invalid Shopper Statement

An empty value was passed in shopperStatement in requestData.

Invalid Shopper IP

The shopperIP field is empty.

No Params Specified

No parameters were specified in the request.

Invalid Field

A field is invalid; commonly shopperInteraction contains an invalid value.

BIN Details Not Found

BIN details were not found for the given card number. Ensure correct parameters and applicable values are passed.

Billing Address Missing

Required object billingAddress is missing from the request.

Account Not Found For Key

Could not find an account with the provided key.

Invalid MCC

The MCC length is incorrect, a non-numeric value was provided, or an alphanumeric value was provided where numeric is required.

Reference Too Long

The reference contains more than 80 characters (maximum is 79).

No Key Configured For Cryptographic Operation

The cryptographic operation could not proceed because no key is configured.

Invalid Country Code

The countryCode is incorrect. Use ISO 3166-1 alpha-2 format.

Invalid Bank Account Holder Name

Account holder name is inconsistent with FATF 16 recommendations or contains numbers.

Missing Or Invalid Network Transaction Reference

Only digits provided, incorrect format, must be alphanumeric, or recurring value is null.

Social Security Number Not Provided

The socialSecurityNumber, which is required for the payment method, is missing.

Shopper Interaction Missing Or Invalid

The shopperInteraction field is missing or contains an invalid value.

Recurring Shopper Lookup Failed

The lookup for the recurring shopper failed.

No Invoice Project Provided

No InvoiceProject was provided in the request.

No Invoice Batch Provided

No InvoiceBatch was provided in the request.

No Creditor Account Specified

No creditorAccount was specified in the request.

No Project Code Specified

No projectCode was specified in the request.

No Creditor Account Found

No creditorAccount was found matching the specified identifier.

No Project Found

No project was found matching the specified identifier.

Unable To Create Invoice Project

An error occurred while attempting to create the InvoiceProject.

Invoice Batch Already Exists

An InvoiceBatch with the same identifier already exists.

Unable To Create Invoice Batch

An error occurred while attempting to create the InvoiceBatch.

Invoice Batch Validity Period Exceeded

The InvoiceBatch validity period has been exceeded.

Error While Storing Debtor

An error occurred while attempting to store the debtor.

Error While Storing Invoice

An error occurred while attempting to store the invoice.

Error Checking If Invoice Already Exists

An error occurred while checking if an invoice already exists for the creditorAccount.

Error While Searching Invoices

An error occurred while searching invoices.

No Invoice Configuration For Credit Account

No Invoice Configuration has been configured for the creditAccount.

Invalid Invoice Configuration For Credit Account

The Invoice Configuration for the creditAccount is invalid.

No Method Specified

No method was specified in the request.

Server Could Not Process Request

Incorrect POST/Content-Type, XML/HTTP sent instead of JSON, incorrect shopperReference for Pay by Link, missing API version, or invalid RequestURL.

Problem Parsing Request

The request contains an unrecognised field or invalid format (introduced in API v64), empty input resulting in a null result, or an internal error.

Required Resource Temporarily Unavailable

The data store is not available to compare the idempotency key. Retry later or omit the idempotency-key HTTP header.

Request Already Processed Or In Progress

The web service user is sending multiple authorised requests with the same reference. Ensure requests are sent only once.

Rate Limited

The API request rate limit has been exceeded. Throttle your API requests and wait before retrying.

Contract Not Found

shopperReference does not exist, or requestData is creating a contract while simultaneously using recurringDetailReference. Check if the details were saved previously.

Too Many Payment Details Defined

Too many paymentDetails exist for the same recurring or shopper reference, or the integration is incorrect.

Invalid Contract

No valid contract types (RECURRING, ONECLICK, or PAYOUT) exist, or the contract type is incorrect. Check data sent on the PAL and the recurring field.

Payment Detail Not Found

recurringDetailReference/storedPaymentMethodId does not exist, has been disabled, requestData is missing required fields (e.g. Klarna lineItems), or the payment method specified varies from the token.

No Active Payment Details For Shopper Reference

Either the shopper reference is not valid, or all payment details have been disabled.

Failed To Disable

The attempt to disable the recurring detail failed.

Recurring Detail Reference Not Available For Contract

The recurringDetailReference is not available for the provided recurring contract.

No Applicable Contract Types For Payment Method

The txvariant (e.g. Maestro) cannot have recurring because the scheme mandates 3D Secure for all transactions. Recreate the contract or change the requestData.

Invalid Combination Of Shopper Interaction And Recurring Contract

The recurring contract was not set up with shopperInteraction.

CVC Required For OneClick Card Payment

The Card Validation Code (CVC) was not supplied for a OneClick card payment. Supply the CVC number.

Invalid Merchant Account

Incorrect merchantAccount, incorrect MD value during 3DS, web service not permitted for the merchantAccount, company not active, or merchantAccount value has incorrect casing (case-sensitive).

Invalid Or Empty Request Data

The request data is invalid or empty.

Internal Error

An internal error occurred on the Adyen platform.

Unable To Process

An error occurred while communicating with Adyen.

Payment Details Not Supported

The payment method, currency, or country is not configured in Customer Area. Ensure the countryCode in requestData matches the payment method txvariant.

No Acquirer Account For Txvariant And Currency

The payment method is not set up in this merchant account. Add the payment method in your Customer Area.

No Acquirer Account For MPI Data And Acquirer

MPI data was specified without an acquirer code. Set the defaultToAcquirerSelectionRegardlessOfMPIData ADP to true via Support.

No Acquirer Account For Currency

Payment type not supported, payment method restricted to a store not specified in the request, minimum amount too low, a transaction rule is blocking, currency not configured, customRoutingFlag missing, or BIN/country/issuer restriction applies.

Cashback And Cashout Not Allowed

The merchant account does not allow cashback or cashout. This is specific to EFTPOS (Australia/New Zealand). Contact Support to enable.

No Acquirer Account Configured For Klarna

The merchant account has not been configured to accept Klarna payments. Add the payment method in Customer Area.

Both Klarna Platforms Configured

Both KlarnaPayments and Klarna have been configured for the merchant account. Only one is allowed. Remove one of the Klarna payment methods.

Original PSP Reference Invalid For Environment

LIVE/TEST PSP mismatch: a TEST PSP reference was sent to the LIVE endpoint (or vice versa). Pass the correct PSP or verify the environment.

Payment Details Not Supported For Country Or MCC

The payment method is missing or not configured for the specified country/MCC combination, or issuer restrictions apply.

Invalid Request

Using an incorrect endpoint or sending incorrect requestData to the wrong endpoint. Verify the goal of the request and send to the correct endpoint.

Invalid Store

The specified store does not match any store references or store IDs for the merchant account. Find the correct store ID in your Customer Area and retry.

TX Variant Does Not Support Redemption Type

The TX variant does not support the requested redemption type.

Transaction Amount Exceeds Card Limit

The transaction amount exceeds the allowed limit for this type of card.

Required Object Card Not Provided

The required card object is not provided in the request.

Additional Amount Currency Mismatch

The additionalAmount currency must be the same currency as the payment.

Total Payment Amount Less Than Zero

The total payment amount should be equal to or greater than zero.

MPI Data Missing Due To Three D Reference

The mpiData object is missing, but is required because threeDReference is present.

MPI Data Not Valid

The mpiData object is not valid: authenticationResponse is missing or directoryResponse does not match.

Account Updater Only For Visa And Mastercard

Account updater connections are only supported for Visa and MasterCard.

No Registered Account For Account Updater

No registered account was found for the AccountUpdater.

Not Allowed To Change Shopper Interaction

Changing the shopperInteraction is not permitted for this request.

Invalid iDEAL Issuer

The iDEAL issuer provided is invalid.

Missing Payment Details

Required payment details are missing from the request.

Invalid Forex Type Specified

The forex type specified in the request is invalid.

Invalid Base Currency Specified

The base currency specified in the request is invalid.

Invalid Target Currency Specified

The target currency specified in the request is invalid.

Merchant Not Found

There is no merchant with the specified code.

Invalid Acquirer Account

The acquirer account is invalid.

Configuration Error Acquirer Identification

Configuration error in acquirerIdentification.

Configuration Error Acquirer Password

Configuration error in acquirerPassword.

Configuration Error API Key

Configuration error in apiKey.

Configuration Error Redirect URL

Configuration error in redirectUrl.

Configuration Error Acquirer Account Data

Configuration error in AcquirerAccountData.

Configuration Error Currency Code

Configuration error in currencyCode.

Configuration Error Terminal ID

Configuration error in terminalId.

Configuration Error Serial Number

Configuration error in serialNumber.

Configuration Error Password

Configuration error in password.

Configuration Error Project ID

Configuration error in projectId.

Configuration Error Merchant Category Code

Configuration error in merchantCategoryCode.

Configuration Error Merchant Name

Configuration error in merchantName.

Invalid Company Registration Number

The company registration number provided is invalid.

Invalid Company Name

The company name provided is invalid.

Missing Company Details

Required company details are missing from the request.

Configuration Error Private Key Alias

Configuration error in privateKeyAlias.

Configuration Error Public Key Alias

Configuration error in publicKeyAlias.

Card Number Not Allowed For Incontrol Virtual Card

Card number cannot be specified for Incontrol virtual card requests.

Recurring Not Allowed For Incontrol Virtual Card

Recurring is not allowed for Incontrol virtual card requests.

Invalid Authorisation Type Supplied

An invalid authorisation type was supplied in the request.

Bank Account Details Do Not Meet Instruction Format

Bank details required for Payout are not being passed, or selectedRecurringDetailReference is set to LATEST which may not correspond to bank details.

Field Exceeds Maximum Character Limit

The value provided in a field exceeded the allowed number of characters, was placed in the wrong field, or a generation/encryption error produced a value that is too long.

Fraud Offset Out Of Range

The fraudOffset field must be between -999 and 999.

Request Exceeds Maximum Size

The request body contains more bytes than the maximum allowed for that endpoint.

Payment Data Not Provided

paymentData has not been provided in the request.

Invalid Payment Data

The paymentData provided is invalid.

Missing Payment Method Details

Payment method details are missing from the request.

Invalid Payment Method Details

Payment method details are invalid. The recurring contract on a token may be missing; for example, a payment method only supports RECURRING but a ONECLICK contract is being used.

Payment Method Object Not Provided

The paymentMethod object has not been provided in the request.

Invalid Payment Method Data

There is an error with information in the paymentMethod object, for example paymentMethod.type is missing.

Session Has Expired

The checkout session has expired.

SDK Version Not Provided For Web Channel

The request contains no sdkVersion although the channel is set to Web.

Channel Conflicts With Provided Parameters

The provided channel conflicts with the provided parameters. Provide the correct token for iOS/Android, or sdkVersion for Web — not both.

SDK Token Could Not Be Parsed

The provided SDK token could not be parsed.

Origin Required For HTML Response

For an HTML response, origin must be provided.

Endpoint Requires Version

This endpoint requires the version to be specified.

Token Is Missing

The token is missing from the request.

Invalid SDK Version

The sdkVersion provided is invalid.

SDK Token Has Invalid Timestamp

The provided SDK Token has an invalid timestamp.

Invalid Payload

The payload provided is invalid.

Request Missing SDK Version And Token

The request does not contain sdkVersion or token.

No Issuer Selected

No issuer was selected for this payment.

Missing Unique Terminal ID

The uniqueTerminalId is missing from the request.

Installments Not Configured In Setup Request

Installments were not configured in the setup request.

Invalid Open Invoice Request

The open invoice request is invalid.

Invalid Selected Flow

The selected flow is invalid.

Invalid Return URL Query String

The provided returnUrlQueryString is invalid.

3D Auth Data Incomplete

3D Auth Data is incomplete. Provide both PaRes and MD fields.

CVC Required But Not Provided

CVC is required for this payment but was not provided.

Return URL Is Missing

The return URL is missing from the request.

Bank Account Is Missing

The bank account is missing from the request.

Provide Fingerprint Or Challenge Result

Provide either threeds2.fingerprint or threeds2.challengeResult, not both.

Provided Fingerprint Is Invalid

The provided fingerprint is invalid.

Provided Fingerprint Is Invalid For Field

The provided fingerprint is invalid for the specified field. If the affected field is threeDSCompIn, the device fingerprint is not being forwarded to the /payments/details API call.

Origin Or Notification URL Required

Either origin or notificationURL must be provided.

Missing Required Field Channel

The required field channel is missing from the request.

Invalid Order Data

The provided orderData is invalid.

Invalid Recurring Expiry Format

The recurringExpiry format is invalid. Required format: yyyy-MM-dd'T'HH:mm:ssX, e.g. 2019-12-31T23:59:59+02:00.

Expiry At Exceeds Maximum Allowed Date

The expiresAt value is greater than the maximum allowed date.

Payment Data And MD Belong To Different Requests

PaymentData and MD belong to different requests. Submit the correct MD.

Missing Or Invalid Client Key Or Origin Key

The clientKey or originKey is missing or invalid.

Missing Or Invalid Checkout Attempt ID

The checkoutAttemptId is missing or invalid.

Missing Or Invalid Shopper Stage

The shopperStage is missing or invalid.

Missing Or Invalid Details For Shopper Stage

The details provided for the shopperStage are missing or invalid.

Payment Link Expired

The payment link has expired.

Hosted Session Expired

The hosted session has expired.

Payment Link Already Paid

The payment link has already been paid.

Description Too Long

The description field is too long.

POS To PayByLink QR Code Expired

The POS to PayByLink QR Code has expired.

Missing Required Field Redirect Result

The required field redirectResult is missing from the request.

Invalid Redirect Result

The provided redirectResult is invalid. The returnUrl format may be incorrect for the applicable channel (web, iOS, or Android).

Payment Details Incomplete PaRes And MD

Payment details are incomplete. Provide both PaRes and MD (authentication-only flow).

Invalid Storing Method Type

The storingMethod.type value is invalid.

Recurring Processing Model Not Provided

The required recurringProcessingModel is not provided. Include it when creating a token or using stored payment details.

Storing Method Incomplete

The storing method is incomplete.

Push Account Receipt Invalid

The push account receipt is invalid.

Order Data Expired

The order data has expired.

Order Data No Access To Merchant Account

The order data does not have access to the specified merchant account.

Invalid Push Account Data Field

The pushAccountData field is invalid.

Provisioning Request Declined

The provisioning request was declined.

3DS2 Payment Authentication Failed

Authentication of a 3DS2 payment has failed.

Missing 3DS2 Fingerprint

The 3DS2 fingerprint is missing from the request.

Missing Delegated Authentication Result

The delegated authentication result is missing from the request.

Client Data Not Allowed During Payment Link Creation

Client data is not allowed to be passed during payment link creation.

Donation Token Or Original PSP Reference Missing

The donation token, donation original PSP reference, or both are missing.

Parent PSP Reference Missing For Donation

The parent PSP reference is missing for the donation.

Missing Donation Account

The required field donationAccount is missing.

No Payment Methods Available

There are no payment methods available for the given parameters.

Unable To Generate 3DS Redirect URL

Unable to generate a redirect URL for the 3DS transaction.

Gift Card Has Zero Balance

The gift card provided for the order has 0 balance.

Payment Method Type Required For Non-Recurring

The field paymentMethod.type is required for non-recurring payments.

Payment Method Type Not Retrievable From Recurring Details

The paymentMethod.type could not be retrieved from recurring details.

Invalid 3DS2 Result

The provided 3DS2 result is invalid.

Missing Required Field Three DS Result

The required field threeDSResult is missing.

Unable To Retrieve Package Weight

Unable to retrieve the total weight of a package.

Carbon Credit Project ID Not Configured

The carbon credit project ID is not configured.

Invalid Terminal Response Or Missing Parameters

Invalid response from the terminal or missing parameters.

Donation Token Expired

The donation token has expired.

Conflicting Installment Options

Both installmentOptions.values and installmentOptions.maxValue cannot be specified in the same request.

Invalid Platform For Voucher Pass

The platform specified for the Voucher Pass is invalid.

Invalid Session Identifier Or Data

The provided session identifier or data is invalid.

Session Expired

The session has expired.

Product Has Negative Quantity

A product in the order has a negative quantity.

Terminal Not Found

The terminal with the specified uniqueTerminalId was not found.

Terminal Not Deployed

The terminal with the specified uniqueTerminalId is not deployed.

Insufficient Permissions For Terminal

Insufficient permissions for the terminal with the specified uniqueTerminalId.

Merchant Account Missing Pay By Link Permissions

The merchant account is missing Pay by Link permission(s).

Donations Not Supported For Payment Method

Donations are not supported for this payment method.

Merchant Unknown

The provided merchant is unknown.

Unknown Terminal

The terminal is unknown.

Unknown Terminal (Duplicate)

The terminal is unknown (secondary occurrence of code 14_0431).

Theme And Terms Of Service Must Be Configured

A theme and terms of service must be configured to send emails to the shopper.

Internal Error Sending Link To Shopper

An internal error occurred when sending the link to the shopper.

Theme Name Already In Use

The theme name is already in use.

Field Too Long

The specified field is too long.

Default Theme Must Be Configured

A default theme must be configured for the account.

Cannot Delete Default Theme

This theme is the default. Select another default theme before deleting it.

No Terms And Conditions Configured

No terms and conditions were configured for this account.

Specified Theme Does Not Exist

The specified theme does not exist.

File Must Be Valid JPG Image

The file specified for the field must be a valid JPG/JPEG image.

No BIN Or Encrypted BIN Provided

Neither bin nor encryptedBin was provided in the request.

Payment Data And MD From Different Payments

The provided paymentData and MD do not belong to the same payment.

Field Not Supported For Mode

The specified field is not supported when the request is in the given mode.

Session In Invalid State

The provided request cannot be processed as the session is in an invalid state.

Subset Of Options Not Specified For Field

A subset of options was not specified for the field.

Subset Of Options Specified But All Selected

A subset of options was specified for the field but all options were selected.

No Options Expected For Empty Fill Mode

No options are expected when fillMode is empty for the field.

Options Mode Not Specified

The options mode was not specified for the field.

Field Fill Mode Must Be Mandatory

The fill mode of the field must be mandatory.

Invalid Country Code

The provided country code is invalid.

Options Mode Should Be Subset

The options mode for the specified field should be subset.

Flexible Validity Field Should Not Contain Quantity Or Unit

A field with flexible validity should not contain quantity or unit.

Fixed Validity Field Should Contain Quantity And Unit

A field with fixed validity should contain both quantity and unit.

Invalid Redirect Data

The provided redirect data is invalid.

Invalid Redirect ID

The provided redirectId is invalid.

Invalid Return Query String

The provided return query string is invalid.

Invalid Recurring Processing Model

The recurringProcessingModel field is invalid.

Session ID In Return URL Mismatch

The provided request cannot be processed as the sessionID in the returnURL is different from the current sessionID.

Missing Or Invalid Session ID

The field sessionId is missing or invalid.

Invalid Session ID

The sessionId field is invalid.

Missing Or Invalid Forward URL

The field Forward-Url is missing or invalid.

Metadata Value Size Exceeds Limit

The metadata value size exceeds the allowed limit.

Option Not Supported For New Shopper Field

The option is not supported for the new shopper field.

Payment Method Data Contains Raw And Encrypted Card Details

The paymentMethodData is invalid because it contains both raw and encrypted card details.

Expire After Refusal Field Not Allowed

The field expireAfterRefusal is not allowed in this context.

QR Code Expires At Exceeds Maximum Allowed Date

The qrCodeExpiresAt value is greater than the maximum allowed date.

Details Expired

The details have expired.

Klarna Line Items Tax Or Amount Fields Invalid

Klarna lineItems fields taxAmount and amountExcludingTax are missing or not valid.

MOTO Not Allowed Due To PCI Regulations

The shopperInteraction MOTO cannot be processed because PCI compliance of the MOTO integration has not been validated. Contact Support to enable.

Amount Value Below Original Request

The amount.value cannot be less than the amount.value of the original request.

Not Allowed To Update Shipping Address

The user is not allowed to update the shipping address.

Delivery Method Amount Mismatch

The sum of the selected deliveryMethod amount and original offer amount does not match the total amount.

Only One Delivery Method Should Be Selected

Only 1 deliveryMethod should be selected.

Order Can Only Be Updated If Payment Is Pending

The order can only be updated if the payment is still pending.

Amount Currency Does Not Match Original Request

The amount.currency provided in the request does not match the amount.currency of the original request.

Invalid Return URL Parameter

The returnUrl parameter is invalid.

Invalid Session Result Field

The sessionResult field is invalid.

Missing UPI ID Or VPA

The required field UPI ID / VPA is missing.

Missing Exchange Rate Token

The exchange rate token is missing from the request.

Invalid Exchange Rate Token

The exchange rate token is invalid.

Exchange Rate Expired

The exchange rate has expired.

Missing Shopper Tax ID

The required field shopperTaxInfo.taxId is missing.

Invalid Shopper Tax ID Field

The field shopperTaxInfo.taxId is invalid.

Transaction Amount Exceeds Maximum Allowed

The transaction amount exceeds the maximum allowed amount.

Conflicting Data In Request Fields And SDK Data

Conflicting data was found on request fields and the sdkData field.

Invalid Tax ID Type For Merchant

The tax-id type is invalid for the merchant.

UPI Collect On Android No Longer Supported

UPI Collect transactions using Android are no longer supported. Use UPI Intent or UPI QR instead.

Encrypted Card Details In Payment Method Invalid

The encrypted card details in paymentMethod are invalid.

3DS2 Required Field Missing For Device Channel

A required field is missing for the specified device channel.

3DS2 Field Should Not Be Present For Device Channel

A field should not be present for the specified device channel.

3DS2 Invalid Value In Field

An invalid value was provided in the specified field.

3DS2 Unexpected Field

An unexpected field was included in the request.

3DS2 Message Category Shall Be Present

The messageCategory field shall be present in the request.

3DS2 Field Value Too Long

The value of the specified field exceeds the maximum allowed length.

Invalid Merchant Configuration For 3DS 2.0

The merchant configuration for 3DS 2.0 is invalid.

Three DS2 Token Required

The threeDS2Token is required.

Invalid Device Channel Value

Invalid deviceChannel value. Must be app, browser, or TRI.

PSP Reference Not Valid

The pspReference is not a valid pspReference.

3DS2 Result Not Present

The 3DS2 result is not present.

Cannot Add 3DS2 Authentication Values

Cannot add 3DS2 authentication values because addRawThreeDSecureDetailsResult is not enabled.

Invalid Three DS2 Token

The threeDS2Token is invalid.

Invalid Browser Info

The browserInfo provided is invalid.

Language Must Be Valid IETF BCP47 Tag

The language must be a valid tag according to the IETF BCP47 definition.

Cannot Authorise 3DS2 Transaction After 12 Hours

Cannot perform an authorisation on a 3DS2 transaction more than 12 hours after the transaction began.

Invalid Color Depth

colorDepth must be 1, 4, 8, 15, 16, 24, 32, or 48 bit.

State Or Province Invalid

The stateOrProvince value is invalid.

Invalid Trans Status

The transStatus is invalid (likely null). Check what is passed in the request and verify with the issuer.

Notification URL Cannot Be Localhost

The notificationURL cannot be localhost. Deploy a public notification server if testing a browser-based 3D Secure flow.

Invalid Authentication Only Field

The authenticationOnly field is invalid.

Three DS2 Request Data Not Supported For MD Flow

threeDS2RequestData is not supported for threeDS2InMDFlow. Remove threeDS2RequestData from the /payments request or use the native flow instead of the redirect flow.

3DS2 Authentication Older Than 60 Days

The result is not present because the authentication is older than 60 days.

Error During 3DS Authentication Process

An error occurred during the 3DS authentication process. Common causes: incorrect paReq value in the redirect form, or incorrect paResponse in the authorise3d request.

Amazon Pay Unknown Error

Amazon responded with a null errorMessage.

Amazon Pay Token Does Not Exist

The amazonPayToken is missing.

Amazon Pay Signature Corrupt

The Amazon Pay signature is corrupt.

Invalid Amazon Pay Value

An invalid Amazon Pay value was supplied.

Amazon Pay Merchant Private Key Not Found

The Encryption Key has not been set up on the web service user for the merchant account.

Amazon Pay Token Not Chargeable

The amazonPayToken is not correct or is not chargeable.

Amazon Pay Invalid Account

The Amazon Pay account is invalid.

Amazon Pay Invalid Refund Status

The Amazon Pay refund status is invalid.

Amazon Pay Missing Header Fields

Required header fields are missing from the Amazon Pay request.

Amazon Pay Not Available

Amazon Pay is not available.

Rejected By Amazon

The payment was rejected by Amazon.

Amazon Pay Internal Error

An Amazon Pay internal error occurred.

Amazon Pay Timeout

The Amazon Pay request timed out.

Amazon Pay Sent Invalid Response

Amazon Pay sent an invalid response.

Authentication Notification To Amazon Pay Failed

The authentication notification to Amazon Pay failed.

Apple Pay Token Amount Mismatch

The amount configured in Drop-in for Apple Pay differs from the final amount sent in the /payments request. Ensure the front-end amount mirrors the API request amount in the correct currency minor units.

Invalid Apple Pay Token

The web service user and/or merchant account setup is incorrect.

Incorrect Apple Pay Token Version

There is an Apple Pay version mismatch. Regenerate the token and set up the web service user again.

Apple Pay Merchant Private Key Not Found

The CSR is not valid. Likely a different certificate was provided compared to the one registered on the Apple Pay developer portal. Redo the PEM certificate exchange.

Apple Pay Merchant Public Key Not Found

The CSR is not valid. Likely a different certificate was provided compared to the one registered on the Apple Pay developer portal. Redo the PEM certificate exchange.

Apple Pay Signature Corrupt

There is a signature mismatch; the Apple Pay signature cannot be read.

Missing Certificate For Apple Pay Signature

The signature is empty, or the certificate is missing. Set up the web service user again and configure the Apple Pay token.

Test System Does Not Accept Live Tokens

The test system does not accept Live Apple Pay tokens.

Invalid Google Pay Token

The Google Pay token is incorrect, the merchant account in requestData is wrong, the payment method MID setup is incorrect, or the Android app is not registered with Google.

Google Pay Token Already Expired

The Google Pay token has expired. Troubleshoot with Google; the error maps directly to the Google response.

Google Pay Token Already Used

The Google Pay token has already been used and cannot be reused. Use a new token for each shopper-initiated transaction.

Network Token Suspended Or Deactivated

The network token is suspended or deactivated.

Detokenization Request Declined

Adyen's request to the scheme to fetch the cryptogram for the network token was declined.

Network Token PAN Missing

No Primary Account Number (PAN) was found for the network token.

Network Token Not Active Yet

The network token is not active yet.

Network Token Not Found

No network token was found to complete the payment. The token may have been deleted.

Detokenization Request Timed Out

Adyen's request to the scheme to fetch the cryptogram for the network token timed out.

Network Token Required Fields Missing

One or more required fields for the request are missing. The missing fields are returned in the error message.

Unsupported Variant For Network Tokenization

The variant is not supported for network tokenization.

Tokenization Request Timed Out

The tokenization request timed out.

Operation Not Allowed For Network Token

The attempted action (Delete, Suspend, or Resume) is not allowed for this network token.

Detokenization Request Failed

Adyen's request to the scheme to fetch the cryptogram for the network token failed.

Authorisation

Result of a payment authorization request. `success: true` means the payment was authorised; `success: false` means it was refused.

Authorisation Adjustment

Result of a request to adjust the authorised amount or expiry date of a payment.

Cancellation

Result of a request to cancel an authorised payment before it is captured.

Cancel Or Refund

Result of a request to cancel or refund a payment, whichever is still possible depending on whether the payment has already been captured.

Capture

Result of a request to capture funds on a previously authorised payment.

Capture Failed

A previously successful capture failed after the fact (e.g. the funds could not be settled).

Expire

An authorised payment expired before it could be captured or cancelled (typically 28 days for cards). Always reported with `success: true` since the expiry itself is not a failed operation, but the payment is no longer usable.

Handled Externally

The payment was handled outside of Adyen (e.g. cash) and is registered for bookkeeping purposes only.

Order Opened

A partial-payment order (e.g. gift card + card) was opened.

Order Closed

A partial-payment order was closed. `success: true` means the order was fully paid; `success: false` means it was not completed within the allowed time.

Refund

Result of a request to refund a captured/settled payment.

Refund Failed

A previously accepted refund failed and funds were not returned to the shopper.

Refunded Reversed

A refund that appeared successful was reversed because the shopper did not receive the funds; they were returned to the merchant instead.

Refund With Data

Result of a refund request that included additional data (e.g. for partial-payment methods).

Report Available

Informational notification that a scheduled report is available for download. Not tied to a specific transaction outcome.

Void Pending Refund

A void request was accepted but the payment had already started settlement, so it will be processed as a refund instead.

Chargeback

The shopper (or their issuer) disputed the payment and Adyen has withdrawn the funds.

Chargeback Reversed

A previous chargeback was reversed and funds were returned to the merchant.

Notification Of Chargeback

Early warning that a chargeback is likely to be filed. Informational only; no funds have moved yet.

Information Supplied

Defense documents were successfully supplied for an open dispute.

Notification Of Fraud

The issuer reported the transaction as fraudulent via a TC40/SAFE report. Informational; no funds move on this event alone.

Request For Information

The issuer requested additional information as part of an early dispute/RFI stage.

Second Chargeback

The defense of the first chargeback was not successful and the shopper disputed the payment again. This is a final status for the dispute.

Prearbitration Lost

Adyen lost the pre-arbitration stage of a dispute; the disputed funds remain withdrawn.

Prearbitration Won

Adyen won the pre-arbitration stage of a dispute; the disputed funds are returned to the merchant.

Dispute Defense Period Ended

The window to submit defense documents for an open dispute has ended.

Issuer Response Timeframe Expired

The issuer did not respond to submitted defense documents within the allowed timeframe.

Issuer Comments

The issuer added comments to an open dispute. Informational only.

Payout Expire

A payout request expired before it could be confirmed.

Payout Decline

A payout request was declined by the financial institution.

Payout Third Party

Result of a third-party payout request.

Paid Out Reversed

A completed payout was reversed and funds were returned to the merchant.

Offer Closed

The shopper did not complete an asynchronous payment (e.g. redirect or 3D Secure flow) within the allowed time window, so the offer was closed.

Recurring Contract

Result of a request to store shopper details for recurring/tokenized payments.

Postponed Refund

A refund request was accepted but postponed, typically because the payment has not yet settled.

Authentication

Result of a standalone 3D Secure authentication request.

Manual Review Accept

A payment held for manual risk review was accepted by a reviewer.

Manual Review Reject

A payment held for manual risk review was rejected by a reviewer.

Donation

Result of a request to donate a payment (or part of it) to a charity.

Pending

The payment is pending completion. Used by several async payment methods (bank transfer, Boleto Bancario, direct debit, iDEAL, OXXO, and generic pending notifications).