PayU Colombia

Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications in this section to integrate with PayU Colombia.

API Version

Minimum required API version: 1.1.0

The following features require an API version higher than the minimum:

  • 3DS 2.0 External requires API version 1.3.0

Payment Methods

The following table lists all supported payment methods.

Payment MethodPayment Method TypeNotes
American ExpressCards
BANK REFERENCEDCashPayment offices: Davivienda, Banco de Bogotá, Bancolombia.
OTHERS CASHCashLocal name: Matrix (Su Red). Payment offices: PagaTodo, Gana Gana, Gana, Acertemos, Apuestas Cúcuta 75, Su Chance, La Perla, Apuestas Unidas, JER.
PSE Bank TransfersBank Transfer




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

3DS 2.0 ExternalYes
3DS 2.0 PaymentsOS-handledYesSupported flow type: Provider-handled Flow. For more information, see 3DS 2 PaymentsOS-handled Flow.
3DS 2.0 Provider-handledNo
3DS 2.0 Self-handledNo
Level 2 and 3 DataNo
Multi-seller PaymentsNo
Network TokensNo
Payment FacilitatorNo
PayU RiskYes
Retrieve Supported Payment MethodsNo
Retrieve Supported PlansNo
Statement Soft DescriptorYes
Stored Credentials FlagNo
Transaction Processing without CVVYes


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.
AuthorizePartial and multiple are not supportedAsynchronous or Synchronous
CapturePartial and multiple are not supportedAsynchronous or Synchronous
Charge Not ApplicableAsynchronous or SynchronousThe request can be synchronous or asynchronous, depending on your setup.
Refund Partial is supportedAsynchronousPartial refunds require that you send unique partial refund requests.
Supported requests for cash transactions.
Charge Not ApplicableAsynchronous
Supported requests for bank transfer transactions.
Charge Not ApplicableAsynchronous

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.

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

  • Make sure to configure webhook notifications for refunds as well.
  • Some API requests in the payment flow may remain in a pending status for some time.
In your PayU Colombia account, enable the validate unique. This will validate that each payment reference sent to the PayU Latam system is unique.Required
In your PayU Colombia account, enable asynchronous refunds (refunds will initially have a status of pending)Required
In your PayU Colombia account, enable refund notifications. Make sure to include the transaction_type field in the notification (this step is required for PaymentsOS to remain in sync with the refund status).Required
In your PayU Colombia account, enable the 'Process without a cvv2 security code' feature if you intend to use it.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.

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.

Permission to use the PSE Payment Method

PSE Certification

PSE certification is required, before being allowed to use the PSE payment method. To receive certification, you’ll need to conform to the specifications setup by the ACH organization, which is responsible for the PSE payment method.

Creating a PSE Bank Transfer Capture Page

The PSE Bank Transfer Capture page is used by your customer, to capture their PSE Bank Transfer details. Create this page on your site according to the specifications described in the PayU PSE (Colombia) Certification Guide (Download as PDF or Download as HTML.

Redirecting your Customer to Capture the PSE Bank Transfer

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 PSE Bank Transfer Capture page on your site), so that they can capture the bank transfer.

For detail of how to create the PSE Bank Transfer Capture page on your site, and how your customer should capture a PSE bank transfer, see the Permission to use the PSE Payment Method section above.

Once the PSE bank transfer has been captured, 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:


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:


Errors in a Redirection Flow

In a redirection flow, customers finalize a transaction on a third-party site and are then directed back to your web page (the merchant_site_url) where you inform them of the status of their payment. Of course, there’s always a chance of an unexpected error (such as a provider communication timeout) in this process. If an error does occur, we’ll let you know about it by appending the type of error (api_error or provider_error) to the merchant_site_url. If available, we will also include the ID of the original payment request and related transaction request (action).

Here’s an example.



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 Succeed, 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 Authorization request.

Simulating a Request Timeout

To simulate a request timeout, invoke the Create Token request and pass an expiration_date with a format of MM/2022, where MM is the delay in seconds. The month (MM) can be any value between 01 (10 seconds) and 05 (50 seconds).

Test Procedures for Bank Transfers

Use the following test values in the post charge request:

  "bank_transfer_financial_institution_code": "1022",
  "bank_transfer_financial_institution_name": "BANCO UNION COLOMBIANO",
  "user_type": "N",
  "national_identify_number_type": "CC",

Follow a step by step procedure to test PSE bank transfers in the PayU Sandbox environment. For details see the PSE Test Guide (PDF).

Test Cards

You can use the following cards for testing:

Card Number
AMEX Credit Card 377813000000001
DINERS Credit Card 36032400000007
CODENSA Credit Card 5907121111111115
CRM Credit Card 6271800000000002
MASTER Credit Card 5471300000000003
MASTER Credit Card2 2221000000000009
VISA Credit Card 4097440000000004
VISA Debit Card 4509420000000008
Last modified January 2, 2023