PagoEfectivo via dLocal

Accept PagoEfectivo payments from customers in Peru with dLocal as the payment service provider (PSP). The customer selects PagoEfectivo in your checkout, gets a payment code (CIP) on the dLocal payment page and pays it at a bank, at an agent, or through online banking.

Supported workflows

Before you begin

Complete these steps before you send your first PagoEfectivo 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 PagoEfectivo on your dLocal account.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select PagoEfectivo under Payment methods, and save.
Add PagoEfectivo 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 `PEN`. Payrails rejects other currencies.
`meta.customer.country`	Required	The customer’s country object. Payrails sends `PE` to dLocal for every PagoEfectivo 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 DNI. 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.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`, `mobile` or `app`. Sent to dLocal as the device type.
`meta.clientContext.ipAddress`	Optional	Sent to dLocal as the payer IP address.

Authorize a PagoEfectivo payment

Call authorize a payment with pagoEfectivo as the paymentMethodCode. The response includes the redirect to the dLocal payment page, which shows the payment code.

Authorize request

{
  "amount": {
    "value": "100.00",
    "currency": "PEN"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "pagoEfectivo",
      "amount": {
        "value": "100.00",
        "currency": "PEN"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Carlos",
      "lastName": "Quispe",
      "email": "carlos.quispe@example.com",
      "identityCardNumber": "12345678",
      "country": {
        "code": "PE"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

The payment stays pending until the customer pays the code. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How dLocal handles PagoEfectivo

dLocal returns a redirect URL to its hosted payment page, where the customer gets the PagoEfectivo payment code.
The payment stays pending until the customer pays the code, and Payrails completes it from the dLocal notification.
Payrails captures PagoEfectivo payments through dLocal immediately, so a successful payment is final. To return funds, refund the payment.
Each PagoEfectivo 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 PagoEfectivo payment

How dLocal handles PagoEfectivo

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a PagoEfectivo payment

​How dLocal handles PagoEfectivo

Supported workflows

Before you begin

Request fields for dLocal

Authorize a PagoEfectivo payment

How dLocal handles PagoEfectivo