Adyen | IXOPAY

This page provides an overview of the payments methods provided by the Adyen adapter in the IXOPAY platform. It also includes a full list of all configuration options available to you when integrating Adyen within your payments landscape, as well as an overview of the parameters required when submitting a transaction via IXOPAY’s API.

Payment Methods

Payment Method	Transaction Flows	Transaction Types
Creditcard	iFrame Form & payment.js Integration	All
AliPay	Full-Page Redirect	Debit, Refund
Giropay	Full-Page Redirect	Debit, Refund
EPS	Full-Page Redirect	Debit, Refund
DirectDebit	Full-Page Redirect	Debit, Refund
iDeal	Full-Page Redirect	Debit, Refund
Dotpay	Full-Page Redirect	Debit, Refund
DragonPay	Full-Page Redirect	Debit, Refund
Boleto	Full-Page Redirect	Debit, Refund
Bancontact	Full-Page Redirect	Debit, Refund
Qiwi	Full-Page Redirect	Debit, Refund
Sofort	Full-Page Redirect	Debit, Refund
UnionPay	Full-Page Redirect	Debit, Refund
WeChatPay	Full-Page Redirect	Debit, Refund
Blik	Hosted Payment Page	Debit, Refund
Vipps	Full-Page Redirect	All
Online Banking Finland	Full-Page Redirect	Debit, Refund, Partial refund
Swish	Full-Page Redirect	Debit, Refund, Partial refund
PaySafeCard	Full-Page Redirect	Debit, Refund
Riverty	Server-To-Server	Debit, Preauthorize, Capture, Refund
Bizum	Full-Page Redirect	Debit, Refund
MB Way	Hosted Payment Page	Debit, Refund
Multibanco	Full-Page Redirect	Debit
PayPay	Full-Page Redirect	Debit, Preauthorize, Capture, Refund
MobilePay	Full-Page Redirect	Debit, Preauthorize, Capture, Partial Capture, Refund

Additional parameters

Creditcard

Request mapping

For possible values please seeAdyen API documentation

Parameter	Required	Description
extraData.authorisationType	false	`PreAuth` or `FinalAuth`
extraData.requestedTestAcquirerResponseCode	false	To test different responses on Adyen. This data can only be provided within Adyen’s test environment.
extraData.merchantOrderReference	false	Mapped to the field `merchantOrderReference` on the Adyen API.
extraData.installmentsValue	false	Defines the number of installments. Usually, the maximum allowed number of installments is capped. For example, it may not be possible to split a payment in more than 24 installments. The acquirer sets this upper limit, so its value may vary. This value can be zero for Installments processed in Mexico.
extraData.installmentsPlan	false	The installment plan. Possible value - `regular`, `revolving`, or `bonus`. By default, this is set to `regular`.
extraData.splits	false	Splits array must be passed as an encoded JSON string. Mapped to the field `splits` on the Adyen API.
extraData.store	false	Mapped to the field `store` on the Adyen API.
extraData.platformChargebackLogicBehavior	false	Mapped to the field `platformChargebackLogic.behavior` on the Adyen API.
extraData.platformChargebackLogicCostAllocationAccount	false	Mapped to the field `platformChargebackLogic.costAllocationAccount` on the Adyen API.
extraData.platformChargebackLogicTargetAccount	false	Mapped to the field `platformChargebackLogic.targetAccount` on the Adyen API.

Response mapping

Gateway parameter	Adyen parameter	Type	Description
`extraData.additionalPspResponse`	`additionalData`	`string`	All the additional response data provided by Adyen, json encoded.
This can be configured in Adyen’s Customer Area
`returnData.merchantAdviceCode`	`additionalData.merchantAdviceCode`	`string`	The raw merchantAdviceCode provided by Adyen if available. (AdyenPci & AdyenCheckoutPci only)
`returnData.avsResult`	`additionalData.avsResultRaw`	`string`	For possible values see Adyen AVS Mapping Table. (AdyenCheckoutPci only)
`extraData.avs_result`	`additionalData.avsResult`	`string`	For possible values see Adyen AVS Mapping Table. Only available when `Enable AVS Support` in Connector Config (Vault Setup) is active. (AdyenCheckoutPci only)
`extraData.cvv_result`	`additionalData.cvcResult`	`string`	For possible values see Adyen CVC/CVV Result Codes. Only available when `Include CVV Result in Responses` in Connector Config (Vault Setup) is active. (AdyenCheckoutPci only)

Blik

Parameter	Required	Description
extraData.blikCode	false	The code the customer got from Blik

If blikCode is not provided, the customer gets redirected to a hosted payment page where the blikCode can be entered.

Riverty

Parameter	Required	Description
customer.birthDate	true	The customer’s birth date in ISO 8601 format. eg. 1970-07-10
customer.gender	true	The customer’s gender. (“MALE"
customer.shippingFirstName	true	The customer’s first name and any middle names
customer.shippingLastName	true	The customer’s last name
customer.shippingAddress1	true	Street name of the shipping address
customer.shippingAddress2	true	Street number of the shipping address
customer.shippingCity	true	City name of the shipping address
customer.shippingPostcode	true	ZIP or postal code of the shipping address
customer.shippingCountry	true	Two characters Code of the shipping country (“NL”/“BE”)
customer.billingFirstName	false	If not sent, customer.shippingFirstName will be used
customer.billingLastName	false	If not sent, customer.shippingLastName will be used
customer.billingAddress1	conditional*	If not sent, customer.shippingAddress1 will be used
customer.billingAddress2	conditional	If not sent, customer.shippingAddress2 will be used
customer.billingCity	conditional	If not sent, customer.shippingCity will be used
customer.billingPostcode	conditional	If not sent, customer.shippingPostcode will be used
customer.billingCountry	conditional	If not sent, customer.shippingCountry will be used
customer.shippingPhone	true	eq. “+31612345678”
customer.ipAddress	true	The shopper’s IP address. Riverty uses this for risk checks.
customer.email	true	The customer’s email address
items	true	Array of line-items
item.identification	true	An item unique item id
item.description	true	Description of the item
item.quantity	true	Item quantity eq. “2”
item.price	true	Item price (exclusive tax)
item.l2l3Data.taxDetails.type	true	Item tax type information
item.l2l3Data.taxDetails.amount	true	Item tax amount
item.l2l3Data.taxDetails.rate	true	Item tax rate in percentages

Note : If customer.billingAddress1 is sent, following parameters should also be sent:
- customer.billingAddress2
- customer.billingCity
- customer.billingPostcode
- customer.billingCountry

If any of these parameters are missing, the shipping data will be used as billing data.

MB Way

Parameter	Required	Description
customer.billingPhone	true	Has to be a valid Portuguese phone number. eq. “+351234567890”
customer.billingCountry	true	ISO 3166-1 alpha-2 country code. Has to be “PT”.

The term “item” refers to an object within the items array. There must be at least one “item,” but there is no maximum limit on the number of items allowed.

Multibanco

Parameter	Required	Description
customer.billingCountry	true	customer.shippingCountry should be PL
currency	true	EUR

PayPay

Parameter	Required	Description
currency	true	JPY

Pay-Easy Online Banking

Request mapping

For more details see Adyen Documentation

Parameter	Required	Description
currency	true	JPY
successUrl	true	Adyen requires this field, but the customer will not be redirected back to the merchant upon success.
customer.firstName	true	The customer’s first name, including any middle names
customer.lastName	true	The customer’s last name.
customer.email	true	The customer’s email address.
customer.billingPhone	true	Must be a valid Japanese phone number (10–11 digits).
extraData.shopperLocale	true	Language and country code to be used in the payment. Should usually be `ja-JP`.