PayU Asia Pacific PayU Asia Pacific via PaymentsOS Connection is a gateway that allows you to collect card payments. This guide is intended to help you implement PayU Asia Pacific based on your preferred integration workflow.

Services and compatibility


Supported payment types	Card
Supported transaction types	Sale (saved card token or full card number) ( API ) Auth Only (saved card token or full card number) ( API ) Capture (partial or full) ( API ) Void ( API ) Refund (partial and multiple) ( API )
Supported processing currencies	Support depends on card brand and billing country. For the specific currencies for a card brand, see the Currencies section of the "PayU Asia Pacific" documentation. The following is the complete list of currencies: AED, AUD, BGN, BHD, CAD, CHF, CNY, CZK, DKK, EUR, GBP, HKD, HRK, HUF, IDR, ILS, INR, JPY, KRW, KWD, KZT, MAD, MOP, MVR, MYR, NOK, NZD, OMR, PHP, PLN, QAR, RON, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, VND, ZAR
3D Secure 1.x supported	Yes
3D Secure 2.x supported	Yes
External 3D Secure supported	No
Installments supported	No

Gateway-specific information

PayU Asia Pacific supports sale transactions as well as partial, multiple, or full refunds. Sale transactions can be made with a saved card token or the full card number. PayU Asia Pacific also supports paymentType.

You must support the customer redirect flow for PayU Asia Pacific. For the 3D Secure workflow, see the 3D Secure overview documentation.

The following are not supported with PayU Asia Pacific:

Auth-only transactions do not support partial or multiple
Amount of zero (0) is not supported (this is also known as "zero auth")

Configuration

Work with Integrations Support to add PayU Asia Pacific as a connection. You will need the following credentials from PayU Asia Pacific:

App Id
Public key
Private key

Required fields

In addition to the default required field of data.amount, PayU Asia Pacific requires the following fields to process a transaction with the Run card transaction or Run card transaction with iframe endpoint.

For many of the fields, when included in the Create one-time-use token, Save card token, or Save card token with iframe endpoint. the field is stored in the card token and automatically gets sent with the Run card transaction request without needing to explicitly specify it. For more information about this possibility, see the What data is saved with tokens? topic.

Required Field	Description
`data.amount`	The transaction amount. This must be more than zero.
`data.currency`	The three-character ISO currency code for the transaction. Supported currencies depend on card brand. For the specific currencies for a card brand, see the Currencies section of PaymentsOS's "PayU Asia Pacific" documentation. The following is the complete list of currencies: AED, AUD, BGN, BHD, CAD, CHF, CNY, CZK, DKK, EUR, GBP, HKD, HRK, HUF, IDR, ILS, INR, JPY, KRW, KWD, KZT, MAD, MOP, MVR, MYR, NOK, NZD, OMR, PHP, PLN, QAR, RON, RUB, SAR, SEK, SGD, THB, TRY, TWD, USD, VND, ZAR If you do not include this parameter, the system uses the default of `USD`. Therefore, if your merchant account does not support USD, you will get an error response.
`data.customer.email`	The customer's email address.
`data.customer.billToCountry`	The two-character (Alpha-2) ISO country code.
`data.customer.shipToCountry`	The two-character (Alpha-2) ISO shipping country code.
`processingOptions.paymentType`	A payment type indicates the type of transaction being processed using stored payment credentials. This field is requires in order to properly flag initial and subsequent transactions. For more information about this parameter and when to use each option, see the Payment type (paymentType) reference table.

Testing data

Use the following test card information to test your PayU Asia Pacific configuration. For more information about testing, see Testing for PayU Asia Pacific on the PaymentsOS website.

Brand	Currency	Card number	Expiration date	Security code	Cardholder name	Transaction result
Visa	IDR	4987654321098769	5/21	101	Any	Success. Transaction amount ends with `00` (for example, `10000`)
Visa	IDR	4987654321098760	5/21	101	Any	Decline. Transaction amount ends with `10` (for example, `10010`)
Visa	JPY	4111111111111111	12/23	123	Any	Success
Visa	PHP	4000000000000002	Any	345	Any	Success. Transaction amount is `10.00`
Visa	PHP	4000000000000002	Any	345	Any	Decline. Transaction amount is `4051.00`
Visa	TWD	4111111111111111	12/23	123	Any	Success
Mastercard	Any	5555555555554444	Any	123	Any	Success
Mastercard	Any	5454545454545454	Any	123	Any	Success for 3DS
Mastercard	JPY	5123450131003313	12/22	058	Any	Decline
Mastercard	PHP	5200000000000007	Any	345	Any	Success. Transaction amount is `10.00`
Mastercard	PHP	5200000000000007	Any	345	Any	Decline. Transaction amount is `4051.00`
Mastercard	TWD	5123450131003313	12/22	058	Any	Decline
Discover	Any	6011111111111117	Any	Any	Any	Decline

Status workflows

The status of a successful transaction with PayU Asia Pacific varies, depending on the options you choose.


Sale	When `isAuthOnly` is `false`, successful sale transactions will have the following statuses: pending* or authorized settled
Auth only	When `isAuthOnly` is `true`, successful sale transactions will have the following status: authOnly
Capture	Successful capture transactions will have the following statuses: pending* or authorized settled
Void	Successful void transactions will have the following status: voided
Refund	Successful refund transactions will have the following statuses: pending* or authorized settled

*Pending status displays as "authorized" or "AUTHORIZED" in the Nexio Dashboard; it displays as 10, meaning "authorized", in the response when querying transactions (for more information about transactionStatus, see the appropriate transactionStatus table).

If you have any additional questions or feedback, contact us.