PayU Chile

PayU Chile has some special integration requirements. Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications described below.

Creating a Provider Configuration

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

Specifications for Card-based Transactions

The following table lists the integration specifications for PayU Chile.

SpecificationsDetails
Minimum PaymentsOS API Version1.0.0
Requests
  • Charge
  • Refund
Limitations:
  • Partial Refund is not supported.
  • The PaymentsOS test environment does not support the requests listed (this is a limitation of the PayU Latam sandbox environment).
CurrenciesCLP
Payment Methods
  • AMEX
  • DINERS
  • MASTERCARD
  • VISA
Transaction Processing without CVVNot supported
3DS RedirectionNot supported

Specifications for Debit-redirect Transactions

The following table lists the integration specifications for PayU Chile.

SpecificationsDetails
Minimum PaymentsOS API Version1.2.0
RequestsCharge
CurrenciesCLP
Payment MethodsRedcompra

Specifications for Cash-based Transactions

The following table lists the integration specifications for PayU Chile.

SpecificationsDetails
Minimum PaymentsOS API Version1.0.0
RequestsCharge
CurrenciesCLP
Payment MethodsMULTICAJA

Configurations

The following table lists the configurations that are specific to PayU Chile.

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

Sample Requests

Use the bodybuilder to create a sample request body for each request type.

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.

The transaction may be declined with the following responseCode: DECLINED_TEST_MODE_NOT_ALLOWED. For testing, try one of these workarounds:

  • When creating the Token, set the token.holder_name to "APPROVED".

  • Your test account may be configured in "test mode". To disable it, log into your administrative module https://sandbox.secure.payulatam.com/. Then navigate to Settings tab > Settings Accounts, select the account and check off "transaction in test mode". Save your settings when done.

results matching ""

    No results matching ""