Redsys

This page provides an overview of the payments methods provided by the Redsys adapter in the IXOPAY platform. It also includes a full list of all configuration options available to you when integrating Redsys 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	payment.js	Debit, Preauthorize, Capture, Refund, Void, Register
ApplePay		Payment Token
GooglePay		Payment Token
Bizum	Redirect	Debit

Additional Information

Be aware that there is a format restriction for the required Parameter DS_MERCHANT_ORDER, which represents the given MerchantTransactionId.

Please consult the official Redsys Api Documentation for further information - (https://pagosonline.redsys.es/conexion-rest.html)

Connector Config (Vault Setup) - CreditCard

Key	Required	Type	Description
Terminal Id	true	string	A fixed value given by Redsys for each Merchant
Merchant Id	true	string	A fixed value given by Redsys for each Merchant
Key to perform 3DES Card encryption	conditional	string	A fixed value given by Redsys for each Merchant
Key to sign MerchantParameters	conditional	string	A fixed value given by Redsys for each Merchant
Username to load stored Production Credentials	conditional	string	Username that is given by us in case "Key to perform 3DES Card encryption" is stored internally by us
Password to load stored Production Credentials	conditional	string	Password that is given by us in case "Key to perform 3DES Card encryption" is stored internally by us
Prioritize Description Field over MerchantTransactionId Field	false	boolean	In case that the "Description" Field, send in the Request, should be used instead of the "MerchantTransactionId" Field
Assign Timestamp to empty Description Field	false	boolean	In case that the "Description" Field should be automatically filled with the current Timestamp. Works in conjunction with the "Prioritize Description Field over MerchantTransactionId Field" Option.

Note: If the options Prioritize Description Field over MerchantTransactionId Field & Assign Timestamp to empty Description Field are enabled simultaneously the first 6 characters of the respective Transaction are appended to the timestamp to ensure uniqueness.

Connector Config - Bizum

Key	Required	Type	Description
Terminal Id	true	string	A fixed value given by Redsys for each Merchant
Merchant Id	true	string	A fixed value given by Redsys for each Merchant
ParamsKey	true	string	A fixed value given by Redsys for each Merchant

SideNote: The merchantTransactionId who has to be sent in the Api request, has to be between 4 and 12 Characters long to work for Bizum.