PayU Asia Pacific

Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications described below.

API Version
Payment Methods
Currencies
Requests
Setup Procedures
Response Data
Testing

API Version

Minimum required API version: 1.2.0

Payment Methods

The following table lists all supported payment methods.

Payment Method	Payment Method Type
WeChat	eWallet

Currencies

AUD,EUR,GBP,HKD,JPY,SGD,USD

Requests

The following table lists all supported requests for card-based transactions. Use the bodybuilder to create a sample request body for each request type.

Request	Partial/Multiple	Mode
Authorize	Partial and multiple are not supported	Asynchronous
Capture	Partial and multiple are not supported	Asynchronous or Synchronous
Refund	Both partial and multiple are supported	Asynchronous or Synchronous
Void	Not Applicable	Asynchronous or Synchronous

Setup Procedures

The following table lists the setup procedures that are specific to this provider.

Configuration	Required/Optional
In the PaymentsOS Control Center, configure the following credentials: clientId: The client ID provided by PayU Asia Pacific. clientSecret: The client secret provided by PayU Asia Pacific. merchantId: The merchant ID provided by PayU Asia Pacific. accountId: The ID represents the identifier of your account with PayU Asia Pacific. If you do not configure this field for non-card payment methods, then you must pass the accountId in the Create Authorize request. Note: For card payment, if you do not configure this field or pass the accountId in the Create Authorize request, then PayU Asia Pacific will use the BIN number to route the payment to the most optimal payment provider.	Required

Configuration

Required/Optional

In the PaymentsOS Control Center, configure the following credentials:

clientId: The client ID provided by PayU Asia Pacific.
clientSecret: The client secret provided by PayU Asia Pacific.
merchantId: The merchant ID provided by PayU Asia Pacific.
accountId: The ID represents the identifier of your account with PayU Asia Pacific. If you do not configure this field for non-card payment methods, then you must pass the accountId in the Create Authorize request. Note: For card payment, if you do not configure this field or pass the accountId in the Create Authorize request, then PayU Asia Pacific will use the BIN number to route the payment to the most optimal payment provider.

Required

Response Data

The response of the Create Authorize request will include a url field in the redirection object. When using WeChat, this url is a string that references a transaction approval screen in the WeChat app. As a merchant, you must generate a QR code from this string and present the QR code to the user to scan. When scanned, the app will open the transaction approval screen in which the user can approve the transaction. PaymentsOS will then notify you the moment that the transaction has been completed.

Testing

Contact your PayU Asia Pacific Account Manager to obtain test credentials.