Skip to main content

PaymentsOS PayU

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

Payment Methods

Payment MethodTransaction FlowsTransaction Types
Credit Cardpayment.js, HPPDebit, Refund, Authorize, Capture
Credit Card (PayU Colombia)payment.js, HPPDebit, Refund
NetbankingFull-Page RedirectDebit, Debit with Register, Refund
UPIFull-Page RedirectDebit, Refund
PhonePeFull-Page RedirectDebit, Refund
PayTMFull-Page RedirectDebit, Refund
PayzappFull-Page RedirectDebit, Refund

Additional Parameters for Debit/Authorize

Creditcard

Extra dataRequiredDescription
customer.emailconditionalRequired for PayU Mexico, Brazil and Colombia
descriptionconditionalRequired for PayU Mexico, Brazil and Colombia
customer.billingCountryconditionalRequired for PayU Russia
extraData.number_of_installmentsconditionalRequired for PayU Peru
customer.nationalIdconditionalRequired for PayU Colombia
customer.extraData.documentTypeconditionalRequired for PayU Colombia. Possible values are - CC, CE, NIT, TI, PP, IDC, CEL, RC, DE

The following parameters are only required for One-off transactions or initial recurring transactions. On recurring transactions the value of the referenced transaction will be used if not explicitly set.

Netbanking

Extra dataRequiredDescription
customer.billingPhonetrue
customer.firstNametrue
customer.lastNametrue
customer.emailtrue
customer.extraData.bank_codetrueThe customers bank code
customer.extraData.account_numberconditionalOnly required for initial recurring transactions
customer.extraData.account_typeconditionalOnly required for initial recurring transactions
customer.extraData.start_dateconditionalOnly required for initial recurring transactions
customer.extraData.end_dateconditionalOnly required for initial recurring transactions

UPI

Extra dataRequiredDescription
customer.billingPhonetrue
customer.firstNametrue
customer.emailtrue
customer.extraData.vpatrueThe customers vpa

PayTM, PhonePe, PayZapp

Extra dataRequiredDescription
customer.billingPhonetrue
customer.firstNametrue
customer.emailtrue

YAPE (ewallet)

Extra dataRequiredDescription
extraData.authorization_codetrueShould be 6 digits long, only numbers are allowed.
extraData.payer_phonefalseIn case null we try to get from Billing phone number. Transaction may fail if the system receives a user phone number that contains white spaces or is not properly separated from the country code.
note

If authorization_code is not provided, then can be submitted in the HPP as a yape_authorization_code

note

If payer_phone is not provided, then can be submitted in the HPP as a yape_payer_phone

PAGOEFECTIVO (cash)

Extra dataRequiredDescription
extraData.cash_payment_method_vendorfalseIn case null the value is "PAGOEFECTIVO". The name of the local card vendor. Vendor names are case-sensitive.