Skip to main content
dLocal is a global payments platform that helps you accept local payment methods and cards across emerging markets. Pago Efectivo is a payment method in Peru that allows consumers to pay online purchases through cash or bank transfer.

​
Setup

Please follow the common dLocal instructions to get set up with Pago Efectivo. Next, make sure to enable Pago Efectivo as a payment method on the configured account.

​
Features

  • Partial refunds - Refund a portion of the captured amount
  • Refunds - Full refund support
  • Settlement reporting - Access to settlement reports
  • Transaction sync - Automatic transaction status synchronization

​
Supported countries

dLocal supports transactions from buyers in PE.

​
Supported currencies

dLocal supports processing payments in PEN.

​
Limitations

  • Tokenization - Payment method tokenization is not supported
  • Capture - Delayed capture is not supported
  • Void - Transaction void is not supported

​
Integration

For Pago Efectivo, the default integration is through a redirect to a hosted payments page. Start by creating a new transaction with the following required fields. 
var transaction = await client.Transactions.CreateAsync(
    transactionCreate: new TransactionCreate()
    {
        Amount = 1299,
        Currency = "PEN",
        Country = "PE",
        PaymentMethod =
            TransactionCreatePaymentMethod.CreateCheckoutSessionWithUrlPaymentMethodCreate(
                new RedirectPaymentMethodCreate()
                {
                    Method = "pagoefectivo",
                    RedirectUrl = "https://example.com/callback",
                }
            ),
    }
);
After the transaction is created, the API response includes payment_method.approval_url and the status is set to processing. Redirect the buyer to the approval_url so they can complete the payment. After approval the buyer is redirected to the redirect_url you provided when creating the transaction. Do not rely solely on the redirect - either poll the transaction or (recommended) rely on webhooks to detect the final status (for example capture_succeeded or failure states).