PayU Chile

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

API Version

Minimum required API version: 1.2.0

Payment Methods

The following table lists all supported payment methods.

Payment MethodPayment Method Type
American ExpressCards
DINERSCards
MASTERCARDCards
MULTICAJACash
RedcompraDebit Redirect
VISACards

Currencies

CLP

Features

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

FeatureSupported
3DS 1.0 ExternalNo
3DS 1.0 InternalNo
3DS 2.0 ExternalNo
3DS 2.0 InternalNo
InstallmentsYes
Level 2 and 3 DataNo
Retrieve Supported Payment MethodsNo
Statement Soft DescriptorYes
Stored Credentials FlagNo
Transaction Processing without CVVNo

Requests

Note

The PaymentsOS test environment does not support charge and refund requests listed (this is a limitation of the PayU Latam sandbox environment).

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

Supported requests for card transactions.
RequestPartial/MultipleModeNotes
Charge Not ApplicableAsynchronous or SynchronousThe request can be synchronous or asynchronous, depending on your setup.
RefundPartial and multiple are not supportedAsynchronous
Supported requests for debit redirect transactions.
RequestPartial/MultipleMode
Charge Not ApplicableAsynchronous
Supported requests for cash transactions.
RequestPartial/MultipleMode
Charge Not ApplicableAsynchronous

Setup Procedures

Creating a Provider Configuration

When creating a new provider configuration in the PaymentsOS Control Center, select PayU Latam as the provider.

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

ConfigurationRequired/Optional
In the PaymentsOS Control Center, configure the following credentials:
  • apiLogin: The user name supplied by PayU Chile
  • apiKey: The password name supplied by PayU Chile
  • accountId: The identifier of the account in PayU Chile
  • paymentCountry: CHL
  • merchantId: The merchant ID in PayU Chile
When creating a new provider configuration in the PaymentsOS Control Center, select PayU Latam as the provider.
Required
In the PaymentsOS Control Center, register webhooks to be notified when a transaction changes its status.

Note: Some API requests in the payment flow may remain in a pending status for some time.
Required
In your PayU Chile account, enable the validate unique. This will validate that each payment reference sent to the PayU Latam system is unique.Required
Contact PayU Latam Support to get a list of the minimum payment amounts required by the payment methods that you intend to use.

To avoid unnecessary request failures, we recommend that you include some 'minimum value' validation for the transaction payment.amount in your system.
Optional

Integration Procedures

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

Handling the Charge Request Response for Cash Transactions

When you send a post charge request, we will return a charge resource containing a charge.redirection.url, and a status of 'pending'. Redirect your customer to this URL (the MULTICAJA site). Then follow the steps below:

  1. Once your customer finishes their interaction with the MULTICAJA site, we'll redirect your customer's browser back to your site, using the merchant_site_url (that you provided in the post charge request). We've included the following URL parameters in the merchant_site_url, to provide you with the context of the page that you'll need to load: payment_id, charge_id, and status (of the charge).

    Example - Charge request Pending:

     <merchant_site_url>
      ?payment_id=dd1fbe34-4636-4a61-8cb1-27ac8a175284
      &charge_id=aec1c306-e0f7-452b-8fb5-5b34489e9d10
      &status=Pending
    

    The status of your charge request may still be 'pending' when we redirect your customer back to your site (while the provider is processing the request).

    Example - Charge request Failed:

     <merchant_site_url>
      ?payment_id=dd1fbe34-4636-4a61-8cb1-27ac8a175284
      &charge_id=aec1c306-e0f7-452b-8fb5-5b34489e9d10
      &error=provider_error
    
  2. Your customer should choose one of the payment options:

    • Pay at a MULTICAJA office. Your customer should print the "payment coupon", or copy coupon code, and go to any MULTICAJA office to pay for their purchase, before the expiration date.

    • Pay online with an electronic bank transfer. This option is only available in the live environment.

  3. 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:

Card Number
VISA Credit Card 4938590000000017
MASTER Credit Card 5435630000000008
AMEX Credit Card 377825000000005
DINERS Credit Card 36525200000002

results matching ""

    No results matching ""