Adyen

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:

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.

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.

Links

• 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.