baloto colombia

Via Baloto

Start accepting payment using Via Baloto, a favorite payment method in Colombia.

If you want to use a gateway model for accepting Via Baloto payments, you will need to arrange an agreement with our provider, dLocal, and create merchant details (specifically, x_login and x_trans_key ) and a secret key with them. Share these details with our customer support team and we’ll get you up and running. If you have already been onboarded for one of our other dLocal payment methods, you can use the same credentials.


Via Baloto payments follow a two-step process:

Step 1: Request payment

The POST request


  • Live
  • Sandbox

Header parameters

Body parameters

The table below describes the minimum recommended fields. You can find the full list, as well as complete request and response examples, in our API reference.

Details about the payment source.

The type of payment source. Set this to baloto .

The type of integration. Set this to redirect . This will return a redirect URL. Redirect the customer to this URL to proceed with the payment.

The two-letter code (ISO 3166) of the customer’s country. Should be CO .

Details about the customer.

The full name of the customer.

The email address of the customer.

Request example

The POST response

You should get a 202 response with the status field set to Pending . This means your request has been accepted.

Response example

Step 2: Redirect the customer

To capture and complete the payment, you need to provide the customer with the Via Baloto ticket.

Using the redirection URL returned in the response above via _links.redirect , redirect your customer to the static, hosted Via Baloto ticket page. Once redirected, your customer should save or print the ticket.

Make sure your customer is aware that they will be redirected to the ticket page when they click your Pay now button, and that they should print or save the ticket.

A button on the page will allow them to return to your shop:

  • If the ticket is still valid, they will be redirected to your success URL.
  • If the ticket has expired, they will be redirected to your failure URL.

Your payment confirmation page should make it clear to the customer that their purchase has not yet been completed. Explain that it has been reserved and is pending payment before the order can be completed and the goods/services can be delivered.

Get details about a payment

Using the following endpoint, pass the payment id (for example, pay_hcklpcd45ymepcr7thciirbdaa ) from the payment response to get details about the payment.

The GET request

Use the details below to set up your request.


  • Live
  • Sandbox

Header and path parameters

The GET response

Response examples

  • Payment pending
  • Payment captured

Refunds and chargebacks

Refund a payment

You can refund a Via Baloto payment using our refund API. Partial and multiple – as well as full – refunds are allowed.

The customer will get an email (the email address is taken from the property in the initial payment request) from dLocal asking for their banking details. Once the customer has provided their details, dLocal will transfer the money to the customer’s bank account.

The payment status will update to refunded and you will receive a payment_refunded (or payment_refund_declined , if unsuccessful) webhook notification.

A refund processing fee may apply.


There is no chargeback mechanism for Via Baloto.


Sent when a payment request is successfully initiated.

Sent when the acquirer is in the process of accepting the payment.

Sent when the customer has completed the payment with the ticket.

Sent when the ticket has expired.

Sent when there was a failure in creating the payment.

Sent when a refund is successfully initiated.

Sent when a refund is successfully processed.

Sent when a refund is declined.


To start testing, you’ll need to:

  • create a test account, and
  • contact your Customer Success manager or integrations engineer to activate Via Baloto payments in the sandbox environment.

In your sandbox environment, you can test payment capture and expiration, as well as refund success and failure.

In order to test these actions, pass the string “simulate” as part of the source.description field in the initial payment request.

When you do, you will receive additional hypermedia links in the _links object in the payment response and in the ‘get payment details’ response.

Use the URLs contained in the simulator:payment-succeed , simulator:payment-expire , simulator:refund-succeed and simulator:refund-fail hypermedia objects to simulate the respective action/state change on the test payment. documentation