Supported Functionality

Feature	Supported
Authorization	✅
Capture	✅
Refund	✅
Void	✅
Card Tokenization	✅
Digital Wallet	✅
3D Secure	✅ (passthrough MPI data)
$0 Transactions	✅

Supported Payment Methods

Credit Card
Apple Pay
Google Pay

Adding an Adyen Merchant

To connect a Merchant using the Adyen Gateway,

First add Merchant
Select Adyen as the Gateway
Add Gateway Details as outlined below

Gateway Details	Description
API Key*	Your Adyen API key. Found in the Adyen Customer Area under Developers > API credentials.
Merchant Account*	Your Adyen merchant account name. Found in the Adyen Customer Area under Account > Merchant accounts.
Live Environment	Check this box to use the live Adyen environment instead of the test environment. When enabled, the Company Prefix field becomes required.
Company Prefix (Live Only)**	Your unique company prefix for the live environment (e.g., `1797a841fbb37ca7-AdyenDemo`). Found in the Adyen Customer Area under Developers > API URLs > Prefix. Required when Live Environment is enabled.
Merchant Payment Methods*	The types of payment methods this merchant accepts. This will include digital wallet options — Apple Pay & Google Pay.
Merchant Card Types*	Card types to be accepted on this Merchant
Merchant Default Currency*	Default currency that will be used if currency is not specified
Merchant Currencies*	All currencies accepted on this merchant
Bypass $0 Transaction Authorizations	Adyen accepts $0.00 transactions and will validate the card when processing them. Check this box to bypass the gateway entirely for $0 transactions. This setting only applies to initial transactions — $0 renewals will always bypass the gateway. Learn more

*Required **Required when Live Environment is enabled

Card Tokenization

Adyen automatically tokenizes cards on initial transactions. Vrio stores the token in the format shopperReference|recurringDetailReference, which is used for subsequent transactions (renewals, rebills, etc.) without requiring the customer to re-enter card details.

For recurring/subscription transactions, Vrio sends the shopperInteraction: ContAuth and recurringProcessingModel: Subscription parameters. For initial transactions, shopperInteraction: Ecommerce and recurringProcessingModel: CardOnFile are used.

3D Secure

Adyen supports 3D Secure authentication via passthrough MPI data. When 3DS data is available on the order (e.g., from a third-party 3DS provider), Vrio passes the following fields to Adyen's mpiData object:

Vrio Field	Adyen MPI Field	Description
`order_cardholder_auth`	`authenticationResponse`	Cardholder authentication status (Y, A, N)
`order_eci`	`eci`	Electronic Commerce Indicator
`order_cavv`	`cavv`	Cardholder Authentication Verification Value
`order_xid`	`dsTransID`	Transaction Identifier
`order_3ds_version`	`threeDSVersion`	3DS protocol version
`order_3ds_ds_transaction_id`	`dsTransID`	Directory Server Transaction ID (3DS2)

Declines

When a payment is declined, Adyen returns a refusalReason and refusalReasonCode. Common decline reasons include:

Refused — The transaction was refused by the card issuer
Not Enough Balance — Insufficient funds
Blocked Card — The card has been blocked
Expired Card — The card has expired
Invalid Card Number — The card number is invalid
CVC Declined — The CVC code was incorrect

For a complete list, see the Adyen Refusal Reasons Reference.

Testing

To test Adyen transactions, ensure your merchant is configured with the Live Environment checkbox unchecked. All transactions will be sent to Adyen's test environment (checkout-test.adyen.com).

For Adyen test cards, see the Adyen Test Card Numbers.