WebPay via dLocal

Accept WebPay payments from customers in Chile with dLocal as the payment service provider (PSP). The customer selects WebPay, pays with their card on the WebPay page and returns to your site.

Supported workflows

Before you begin

Complete these steps before you send your first WebPay 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 WebPay on your dLocal account.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select WebPay under Payment methods, and save.
Add WebPay 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. Payrails checks Required fields and returns an error when one is missing. Fields required by the PSP pass the Payrails checks but the PSP can decline the payment without them.

Field	Status	Description
`amount.currency`	Required	Must be `CLP`. Payrails rejects other currencies.
`meta.customer.country`	Required	The customer’s country object. Payrails sends `CL` to dLocal for every WebPay 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`	Recommended	The customer’s RUT. Sent to dLocal as the payer document.
`meta.customer.lastName`	Recommended	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.ipAddress`	Optional	Sent to dLocal as the payer IP address.

Authorize a WebPay payment

Call authorize a payment with webPay as the paymentMethodCode. The response includes the redirect to the WebPay page.

Authorize request

{
  "amount": {
    "value": "50000",
    "currency": "CLP"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "webPay",
      "amount": {
        "value": "50000",
        "currency": "CLP"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Javiera",
      "lastName": "Muñoz",
      "email": "javiera.munoz@example.com",
      "identityCardNumber": "111111111",
      "country": {
        "code": "CL"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer pays, 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 WebPay

dLocal returns a redirect URL to the WebPay page. The payment stays pending until the customer pays, and Payrails completes it from the dLocal notification.
Payrails captures WebPay payments through dLocal immediately, so a successful payment is final.
Cancel a WebPay payment through dLocal only while it’s still pending, before the customer pays. dLocal can’t cancel a completed 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 WebPay payment

How dLocal handles WebPay

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a WebPay payment

​How dLocal handles WebPay

Supported workflows

Before you begin

Request fields for dLocal

Authorize a WebPay payment

How dLocal handles WebPay