Adyen MS (Checkout V71) Configuration

Payment Provider	Geographies	Currencies	Payment Methods	Retain Support	Automatic Chargeback Feed	Account Updater	API Version	Microservice?
AdyenMS Payment Provider	Supported Countries Listed Here	Supported Currencies Listed Here	Tokenized Credit Card- Yes	Supported only for Retain merchantsTokenized Credit Card - Yes Detokenize PAN - No Detokenize BIN- No Partial Auth - Yes Forced Deposit - No	Yes	No	Checkout V71	Yes

Required Merchant Information

Name	Expected Value	Description
AdyenMS:merchantAccount		Merchant Account id defined with the processor
AdyenMS:PREFIX		A merchant-specific prefix that serves to create a unique URL.
AdyenMS:merchantAPIKey		A merchant specific Secret key generated at the processor.
Does provider need to whitelist IPs	No
Does merchant need to grant access to Vindicia	No
Chargeback feed	Yes	Webhook
Account Updater	No	No need to update token

Desired Merchant Configuration

Name	Value	Comments
AdyenMS:notificationAuth	Example: “Adyen:Callback”	This is the basic auth username:password for our callback listener (Adyen Callback Listener). The merchant must config their Adyen MS instance with our webhook listener (aka callback listener) and configures basic auth for it. They need to give us this username:password and we add it to the config. For staging, the callback listener is: Adyen Staging Callback Listener
AdyenMS:autoCapture	0/1	Adyen MS can be configured with an immediate or manual capture configuration. With Manual being used we need to issue both an Auth and a separate Capture call to Adyen. When using Immediate we only need to send an Auth as the capture is performed automatically by Adyen. This Delay Capture configuration item needs to be identified with the merchant before the trial can be run so that the correct configuration can be applied to CashBox. When set to “1”, if we get a successful auth, we will set the auth_response_code to ‘Success’. Otherwise we set status to ‘Pending’ and wait for the manual capture request. Recommended value is 1.
AdyenMS:initialSelectTransactionIdForReferenceCode	0/1	If enabled, we will send original failed transaction ID as reference field in the request to Adyen MS. Recommended value is 1.
AdyenMS:auth_response_priority	PMN	The order that authorization response codes are prioritized when deciding to retry Transactions. Supported Authorization Response Codes: Payment Provider Response (P), MAC (M), and Network Response codes (N).
AdyenMS:allowPartialAuth	0/1	This enables partial auth. Use 1 to enable partial authorization. 0 is default

Parent topic:Payment Provider Specific Configuration

Adyen MS Merchant Setup Instructions

The following Instructions are written for Vindicia CTS and services delivery staff. To configure a merchant to use Adyen MS payment provider:

Merchant Payment Providers

In Subscribe Portal 1.0, using your admin account, go to Admin > Merchant Configurations.
Select the relevant Merchant from the drop-down list.
Click Edit Merchant Configurations.
Enter the Jira Ticket # for configuring your merchant payment setup.
Add Adyen to Merchant Payment Providers:
Payment Provider Name Account Number PP Type Active
AdyenMS (1092) <blank> BRD(1) 1
1. Select AdyenMS (1092) as the payment provider and click ADD.
2. Leave Account Number blank.
3. Set PP Type as BRD.
4. Set Active to 1.

Payment Provider Name	Account Number	PP Type	Active
AdyenMS (1092)	<blank>	BRD(1)	1

Routing Rule

Add a Routing Rule for Adyen.
Ordinal Payment Provider Value Rule Method Active
1 AdyenMS (1092) default_method(1) 1
1. Select AdyenMS (1092) as the payment provider and click ADD.
2. Add an Ordinal value of 1.
3. Leave Value blank.
4. Add a Rule Method value of default_method(1).
5. Set Active to 1. Note: If the test payment provider is configured, set its Active value to 0.

Ordinal	Payment Provider	Value	Rule Method	Active
1	AdyenMS (1092)		default_method(1)	1

Note: If a merchant account is set up with several payment providers, the payment provider with highest Ordinal value has priority. If routing will be shared amongst payment providers, see Configuration Method - Payment Providers Routing Rules for examples of possible configurations.

Name/Value Pairs

Add the required configuration details in Name/Value Pairs for the Adyen configuration. Note: The ID is automatically generated and Value for each Name/Value Pair is unique and must be provided by the merchant. The following is an example of Name/Value Pairs for an Adyen configuration.

ID	Name	Value
13022062	AdyenMS:merchantAccount
130022063	AdyenMS:PREFIX
130022064	AdyenMS:merchantAPIKey
130022065	AdyenMS:notificationAuth	Adyen:Callback
130071243	AdyenMS:autoCapture	0/1
130074269	AdyenMS:initialSelectTransactionIdForReferenceCode	0/1
130075551	AdyenMS:auth_response_priority	PMN
130082230	AdyenMS:allowPartialAuth	0,1This enables partial auth. Use 0 to disable partial authorization and 1 if you want to enable partial authorization.
Parent topic:Adyen MS (Checkout V71) Configuration

Adyen MS Detailed Information on Integration

Vindicia supports the following Payment Operations for Adyen MS:

Payment Operation	Yes/No	Notes
Standard Implementation Features
Verification (no Auth)	No
Minimal Authorization ($0) policies, by card type)	No
AVS check with standard result mapping	No
CVV/CVN check with standard result mapping	No
Support real-time authorization (stand-alone Auth)	Yes
Void	Yes
Cancel/reverse authorization	Yes
Conditional deposit (auth and capture combination)	Yes
Capture (stand-alone capture)	Yes
One-time transactions (real-time)	No
Recurring transactions (flagged recurring)	Yes
Refunds - Full	Yes
Refunds - Partial	Yes
3DS	No
CITMIT/Card On File	Yes
Map error/response/result codes to standard actions (Success/Decline/Reject)	Yes
Special Implementation Features
Implemented via Payments Microservice	Yes
Retrieve and store paymentProcessorTransactionId	Yes
Retrieve and store Extended Card/Auth Attributes	No
Support tokenization (for Retain)	Yes
Support BIN/Last-4/Expiry Retrieval from external Token	No
Support detokenization (Subscribe retrieves full PAN/CC details	No
Support Card Type identification (from BIN or API)	No
Support Visa/general “Stored Credential” flags	Yes
Account Updater/Amex Card refresher	No
Automated/manual chargeback feed	Yes
Retain Support
Support token as payment method	Yes
Support detokenization to full PAN	No
Support detokenization to get BIN	No
Support Partial Authorization	Yes	Use merchant NVP `AdyenMS:allowPartialAuth` with value 1.
Support Balance Retrieval	No
Support Forced Deposit	No

Payment Provider Documentation

Link to docs: https://docs.adyen.com/api-explorer/Checkout/71/overview Parent topic:Adyen MS (Checkout V71) Configuration

Home

Guides

APIs

Required Merchant Information

Desired Merchant Configuration

Adyen MS Merchant Setup Instructions

Merchant Payment Providers

Routing Rule

Name/Value Pairs

Adyen MS Detailed Information on Integration

Payment Provider Documentation

​Required Merchant Information

​Desired Merchant Configuration

​Adyen MS Merchant Setup Instructions

​Merchant Payment Providers

​Routing Rule

​Name/Value Pairs

​Adyen MS Detailed Information on Integration

​Payment Provider Documentation

Required Merchant Information

Desired Merchant Configuration

Adyen MS Merchant Setup Instructions

Merchant Payment Providers

Routing Rule

Name/Value Pairs

Adyen MS Detailed Information on Integration

Payment Provider Documentation