Supported Functionality

Feature	Supported
Authorization	✅
Capture	✅
Refund	✅
Void	✅ Authorization only
Card Tokenization	✅
Dynamic Merchant Descriptors	❌
3D Secure	✅ Pass your own
$0 Transactions	✅

Setup

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 — credit card and digital wallets.
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

Supported Payment Methods

Credit Card
Apple Pay
Google Pay

Void

Voiding an uncaptured authorization cancels it at Adyen.
Once the charge has been captured the same request becomes a full refund of the original charge.

Card Tokenization

Charges made with card data ask Adyen to save the card. Vrio stores the returned payment method id and reuses it for every renewal.

Dynamic Merchant Descriptors

Vrio does not send a descriptor to Adyen with the charge, so the customer's statement shows whatever is configured on your Adyen account.

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)

See Third Party 3DS Providers for the full parameter reference.

Testing

Note : Placing test orders with an Adyen sandbox account or using Adyen test cards will not automatically set the order as a test in Vrio. Be sure to flag the order as a test using the is_test flag after the order is processed. For more details on placing test orders, click here.

For Adyen test cards, check here.