PSE via dLocal

Accept PSE payments from customers in Colombia with dLocal as the payment service provider (PSP). The customer selects PSE, confirms the transfer with their bank and returns to your site.

Supported workflows

Before you begin

Complete these steps before you send your first PSE payment through dLocal:

Set up a dLocal integration in your workspace. Follow the dLocal integration setup guide if you don’t have one yet.
Ask dLocal to enable PSE on your dLocal account.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select PSE under Payment methods, and save.
Add PSE as a payment option in your workflow.

Request fields for dLocal

Send these fields in the authorize request, in addition to the standard authorize fields. Required fields must be present for the payment to succeed. Payrails sends Optional fields to the PSP when you include them.

Field	Status	Description
`amount.currency`	Required	Must be `COP`. Payrails rejects other currencies.
`meta.customer.country`	Required	The customer’s country object. Payrails sends `CO` to dLocal for every PSE payment, whatever `country.code` you send.
`meta.customer.name`	Required	Sent to dLocal as the payer name, together with `meta.customer.lastName`.
`meta.customer.email`	Required	Sent to dLocal as the payer email.
`meta.customer.identityCardNumber`	Required	The customer’s Colombian identity document number, such as a cédula de ciudadanía. Sent to dLocal as the payer document.
`meta.customer.lastName`	Optional	Added to the payer name.
`meta.customer.phone`	Optional	Sent to dLocal as the payer phone number.
`meta.customer.birthDate`	Optional	Sent to dLocal as the payer’s date of birth.
`meta.customer.reference`	Optional	Sent to dLocal as the payer’s user reference.
`meta.order.billingAddress`	Optional	Sent to dLocal as the payer address. `meta.order.deliveryAddress` takes priority when both are present.
`meta.order.description`	Optional	Sent to dLocal as the payment description.
`meta.clientContext.clientType`	Optional	`desktop` or `mobile` sends the device type `WEB`, and `app` sends `APP`.
`meta.clientContext.ipAddress`	Optional	Sent to dLocal as the payer IP address.

Authorize a PSE payment

Call authorize a payment with pse as the paymentMethodCode. The response includes the redirect to the PSE payment page.

Authorize request

{
  "amount": {
    "value": "160000.00",
    "currency": "COP"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "pse",
      "amount": {
        "value": "160000.00",
        "currency": "COP"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Camila",
      "lastName": "Rodríguez",
      "email": "camila.rodriguez@example.com",
      "identityCardNumber": "1012345678",
      "country": {
        "code": "CO"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer confirms the transfer, they return to your success or error URL. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How dLocal handles PSE

dLocal returns a redirect URL to the PSE payment page, where the customer picks their bank and confirms the transfer.
Payrails completes the payment from the dLocal notification.
Payrails captures PSE payments through dLocal immediately, so a successful payment is final. To return funds, refund the payment.
Each PSE payment is a one-time, customer-initiated payment.

Getting Started

Payment Orchestration

Token Vault

Analytics & Reporting

Fraud Management

Chargebacks

Monitoring

Resources

Use Cases

Supported workflows

Before you begin

Request fields for dLocal

Authorize a PSE payment

How dLocal handles PSE

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a PSE payment

​How dLocal handles PSE

Supported workflows

Before you begin

Request fields for dLocal

Authorize a PSE payment

How dLocal handles PSE