Home > Aria6 User Documentation > Processing Payments > Payment Gateways > Supported Payment Gateways > Adyen



Supported Payment Methods and Credit/Debit Cards


  • Credit/Debit Card
  • Tokenized Card
  • iDeal (Netherlands)
  • Boleto Bancario (Brazil)
  • ACH (Electronic Check)
  • Direct Debit
  • SEPA (Single Euro Payments Area)

Alternate Payment Methods

  • Giropay
  • Tokenized Direct Debit
  • Klarna
  • Tokenized Klarna
  • Qiwi
  • Tokenized Qiwi
  • Yandex


  • Recurring payments are supported for all of the above APMs (alternate payment methods) except for Yandex.
  • Refund transactions are supported for all APMs.
  • Please note that the Qiwi and Yandex payment methods are unavailable until further notice.


  • Visa
  • MasterCard
  • American Express
  • Discover
  • Diners Club/Carte Blanche
  • JCB (Japan Credit Bureau)
  • UnionPay ExpressPay

Supported Features

Account Updater

The Adyen Account Updater has been enhanced to support both credit card (pay method = 1) and tokenized credit card (pay method = 13) transactions.

This includes the following status enhancements:

Record Status Pay Method = 1 Pay Method = 13
CardExpiryChanged To update new expiration month and year To update new expiration month and year


(Primary Account Number)

No change – Customer needs to provide the new card info in Aria
  • Clear the existing suffix value.
  • Update new expiration month and year.
There are no changes for the remaining statuses (CloseAccount, NoChange and Error), and those statuses are now also applicable for pay method =13.

Email Template Updates

A new Email template class has been introduced (message class C3) called "Credit Card Update Required." This notifies the account holder that their account number has changed and no longer matches the credit card on file.

For more information on Email template classes, please click here.

Event Notification Updates

Two events have been added in support of the Adyen Account Updater (under the Account Notifications class). They are:

Event Name Description
Account Message Type “Credit Card Update Required” Requires Sending System determination that account message type “Credit Card Update Required” requires sending.
Message Type “Credit Card Update Required” Sent to Account Holder Account message type “Credit Card Update Required” was sent to account holder.

To view events in the Account Notifications class, please click here.

ApplePay Method Support

Adyen now supports Apple payment methods for recurring payments, including the ApplePay payment method (38) and the new Tokenized ApplePay payment method (47). When an ApplePay indirect payment takes place outside of Aria, the payment is recorded using the record_alternative_payment API. Once the external payment is recorded, Aria performs a capture request and receives the respective notification (a more detailed process flow appears below).

You must enter the following input values using the record_alternative_payment API to enable this feature:

Input Description
<acct_no> The Aria account number.
<reference_code> (proc_payment_id) Adyen's pspReference of the external ApplePay authorization response.
<payment_amount> The amount authorized in the ApplePay authorization.
<processor_id> 34 (Adyen processor ID).
  • 38 (ApplePay Indirect – initial transaction).
  • 47 (Tokenized ApplePay – transactions after token generation).
<statement_no> The Aria account statement number.
<payment_auth_received> 1 (indicates that the ApplePay payment is authorized).
<proc_payment_method_id> The shopperReference input used in the ApplePay authorization created outside of Aria (it is recommended that you use the Aria account number in the shopperReferece to Adyen).

To utilize the ApplePay and Tokenized ApplePay payment methods within your Aria integration, you must follow these steps:

  1. Perform an ApplePay authorization only outside of Aria (using a unique shopperReference that should be communicated to Aria using the <proc_payment_method_id> noted above) and record this payment against your Aria account number using the record_alternative_payment API. Aria will then perform a payment capture against the provided pspReference (from Adyen’s authorization response).
  2. When Aria receives the capture Webhook notification, the payment transaction is moved from the authorization stage to the payment approved stage; it is created in Aria and applied against the <statement_no> provided in the record_alternative_payment API.
  3. Once the ApplePay payment is recorded, Aria queries the token details from Adyen using the shopperReference provided in the <proc_payment_method> input field, which is associated with the initial ApplePay payment. A new billing info sequence for the Tokenized ApplePay payment method will be created in Aria using the token details. For subsequent/recurring transactions, use the Tokenized ApplePay payment method.

Note: You must configure Webhook notification in your Adyen payment portal for Aria to receive Adyen’s asynchronous notification, update the proper/final status capture request, and create an Aria payment transaction.

Aria Configuration Fields

  • Adyen Merchant Account: Name that identifies the client to the Adyen server. This name/value is provided by your Adyen support representative.  
  • Adyen User ID: User name for authenticating requests sent to the Adyen server or to log in to the Adyen Customer Area.
  • Adyen Password: Password for authenticating requests sent to the Adyen server or to log in to the Adyen Customer Area.
  • API URL: The client URL where API calls are directed. If you want to use 3D Secure (3DS) authentication 2.0, set this field to  v49. Please contact your payment gateway representative for more information.
  • Notification URL: The client URL where notifications are directed.
  • Notification User ID: User name for HTTP authentications that the client receives.
  • Notification Password: Password for HTTP authentications that the client receives.
  • Notification HMAC: Hash-based Message Authentication Codes (HMAC) can be used as an extra layer of security for data verification and message authentication for notifications. To enable HMAC signing of the Adyen notifications for additional security, use the following steps:
  1. Log in to the Adyen Customer Area (CA) and navigate to Settings > Server Communication.
  2. For standard notification, click Edit & Test.
  3. Expand Additional Settings.
  4. Click Generate New HMAC Key, and copy the key into the Notification HMAC field in Aria to use it for your server configuration.
  • Payer Authentication Settings: If you want to use 3DS 2.0, complete any fields under Payer Authentication Settings. Please contact your payment gateway representative for more information.

Configuration Notes

  • The capture delay in the Adyen environment should be set to “Manual.”
  • Use the Adyen Customer Area for chargeback dispute management.
  • For reconciliation, we recommend building notifications capability to accept Adyen settlement reports.


  • Adyen Customer Area: Log in to your Adyen merchant account.
  • Developer Resources: Documentation of test cards, payment modifications, notifications, live endpoints, libraries, API idempotency, currency codes, refusal reasons, payments with pending status, and response handling.

Regarding Processor/Gateway Integration Certifications

If you previously implemented a custom payment processor/gateway integration, you likely completed a certification process with that processor/gateway. Aria maintains certifications with each of the processors with which it integrates. Though you may wish to certify your Aria-related processor/gateway integration before going live on Aria, this is not necessary and could add significant time and Services costs to your Aria implementation process. Please consult your Aria Implementation representative for more detailed information.

Regarding Processor- and Gateway-specific Information

All Processor- and Gateway-specific information provided on Developer Central exists as publicly accessible information from the respective companies, and is presented here for your convenience. We update this information from time to time as necessary.

Last modified


This page has no custom tags.


This page has no classifications.