PayU Brazil

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

• API Version
• Payment Methods
• Currencies
• Features
• Requests
• Setup Procedures
• Integration Procedures
• Handling the Charge Request Response for Cash Transactions
• Testing

API Version

Minimum required API version: 1.0.0

Payment Methods

The following table lists all supported payment methods.

Currencies

BRL, USD

Features

The following table provides an overview of all supported and non-supported features.

Feature	Supported
3DS 1.0 External	No
3DS 1.0 Internal	No
3DS 2.0 External	No
3DS 2.0 Internal	No
Installments	Yes
Level 2 and 3 Data	No
Retrieve Supported Payment Methods	No
Statement Soft Descriptor	Yes
Stored Credentials Flag	No
Transaction Processing without CVV	Yes

Requests

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

Partial Refund Limitations

While partial refunds are supported, the following limitations apply:

• You can send any amount for the partial refund as long as the value doesn’t exceed the initial or actual amount.

• You can send as many as partial refund request as you require. The sum of the partial refund amounts cannot not exceed the total value of the transaction.

• A partial refund request will always get a status of pending in the response. Partial refunds are processed manually by a PayU representative. The refund may take 2 to 6 calendar days to be processed. Once done, depending on the acquirer, the amount will appear in the extract in the next 1 to 30 days after the partial refund is processed.

• If a partial refund is pending or is being processed, you cannot send a new request until the last one is processed.

Setup Procedures

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

Integration Procedures

The following sections list the integration procedures that are specific to this provider.

Handling the Charge Request Response for Cash Transactions

If the charge request is successful, then the provider will return a charge response containing:

• A status of pending.
• The expiration date of the Payment Receipt.
• A provider_data.document object with href links to the Payment Receipt in HTML format and possibly the Payment Receipt in PDF format.

Note that the provider_data.additional_information field may contain a barcode, for receipt tracking purposes.

Now direct your customer to one, or both of the transaction payment receipts, so that they can print the receipt. Your customer should then take the payment receipt to the relevant Payment Office and pay for their purchase, before the expiration date.

When the provider notifies us that your customer has paid, we will update the transaction status. If no payment notification is received by the expiration date then the transaction will be considered as failed.

Testing

Follow the steps in the PayU integration testing page.

To test requests in the PayU Latam sandbox environment, make sure your account has been configured to operate in test mode. You can then simulate specific response statuses for each request type, as listed below.

For Authorization and Charge Requests:

• To simulate a status of Approved, pass in "holder_name": "APPROVED" in the Create Token request.

• To simulate a status of Pending, pass in "holder_name": "PENDING_TRANSACTION_REVIEW" in the Create Token request.

• To simulate a status of Failed, pass in "holder_name": "REJECTED" in the Create Token request.

For Capture, Refund and Void requests:

• To simulate a successful Capture request, first initiate a successful Authorization request.

• To simulate a successful Refund request, first initiate a successful Charge or Capture request.

• To simulate a successful Void request, first initiate a successful a successful Authorization request request.

Test Cards

You can use the following cards for testing: