> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# PSE via dLocal

> Set up PSE bank transfer payments through dLocal in Payrails for customers in Colombia, and see the customer details dLocal needs.

<picture noZoom>
  ![PSE logo](https://assets.payrails.io/img/logos/pse/logo.svg)
</picture>

<picture noZoom>
  ![dLocal logo](https://assets.payrails.io/img/logos/dlocal/logo-full-bleed.svg)
</picture>

Accept [PSE](https://docs.payrails.com/docs/integrations/payment-methods/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

<table>
  <thead>
    <tr><th>Workflow</th><th>Supported</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td></tr>
  </tbody>
</table>

## Before you begin

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

1. Set up a dLocal integration in your workspace. Follow the [dLocal integration setup guide](https://docs.payrails.com/docs/integrations/payment-providers/dlocal.md) if you don't have one yet.
2. Ask dLocal to enable PSE on your dLocal account.
3. In the Payrails Portal, go to **Settings → Integrations**, open your dLocal integration, select **PSE** under **Payment methods**, and save.
4. Add PSE as a [payment option](https://docs.payrails.com/docs/integrations/payment-methods/set-up-payment-methods.md) in your workflow.

## Request fields for dLocal

Send these fields in the authorize request, in addition to the standard [authorize fields](https://docs.payrails.com/reference/authorizeaction.md). **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](https://docs.payrails.com/reference/authorizeaction.md) with `pse` as the `paymentMethodCode`. The response includes the redirect to the PSE payment page.

```json Authorize request theme={null}
{
  "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](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) 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.


## Related topics

- [PSE](https://docs.payrails.com/docs/integrations/payment-methods/pse.md)
- [Khipu via dLocal](https://docs.payrails.com/docs/integrations/payment-methods/khipu/dlocal.md)
- [BCP via dLocal](https://docs.payrails.com/docs/integrations/payment-methods/bcp/dlocal.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.