PayU Argentina

PayU Argentina has some special integration requirements. Follow the standard PaymentsOS integration procedures, 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 Argentina.

Minimum PaymentsOS API Version1.0.0
  • Authorize
  • Capture
  • Charge
  • Refund (including partial)
  • Void
  • Multiple Captures are not supported.
  • Partial refund is only supported for the following payment methods: VISA, MASTERCARD, AMEX, DINERS, Argencard
  • Authorize and Capture are only supported for the local currency, USD is not supported.
  • The PaymentsOS test environment only supports Authorize and Capture requests (this is a limitation of the PayU Latam sandbox environment).
CurrenciesARS, USD
Payment MethodsGlobal credit card vendors:
  • AMEX
  • VISA
Local card vendors:
  • Argencard
  • Cabal
  • Cencosud
  • Naranja
  • Shopping
Transaction Processing without CVVSupported. Not supported with VISA
3DS RedirectionNot supported

Specifications for Cash-based Transactions

The following table lists the integration specifications for PayU Argentina.

Minimum PaymentsOS API Version1.1.0
CurrenciesARS, USD
Payment Methods


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

In the PaymentsOS Control Center, configure the following credentials:
  • apiLogin: The user name supplied by PayU Argentina
  • apiKey: The password name supplied by PayU Argentina
  • accountId: The identifier of the account in PayU Argentina
  • paymentCountry: ARG
  • merchantId: The merchant ID in PayU Argentina
When creating a new provider configuration in the PaymentsOS Control Center, select PayU Latam as the provider.
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.
In your PayU Argentina account, enable the validate unique. This will validate that each payment reference sent to the PayU Latam system is unique.Required
In your PayU Argentina account, enable processing with CVV, if desired.Contact PayU Argentina support for assistance.Optional
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.

Sample Requests

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

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.

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.


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 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 ""