SPEI via dLocal

Accept SPEI payments from customers in Mexico with dLocal as the payment service provider (PSP). The customer selects SPEI in your checkout, gets a CLABE number and a reference on the dLocal payment page and sends the transfer from their bank.

Supported workflows

Before you begin

Complete these steps before you send your first SPEI 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 SPEI on your dLocal account.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select SPEI under Payment methods, and save.
Add SPEI 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 `MXN`. Payrails rejects other currencies.
`meta.customer.country`	Required	The customer’s country object. Payrails sends `MX` to dLocal for every SPEI 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`	Optional	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 SPEI payment

Call authorize a payment with spei as the paymentMethodCode. The response includes the redirect to the dLocal payment page, which shows the transfer details.

Authorize request

{
  "amount": {
    "value": "100.00",
    "currency": "MXN"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "spei",
      "amount": {
        "value": "100.00",
        "currency": "MXN"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Luis",
      "lastName": "García",
      "email": "luis.garcia@example.com",
      "country": {
        "code": "MX"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

The payment stays pending until the transfer arrives. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How dLocal handles SPEI

dLocal returns a redirect URL to its hosted payment page, where the customer gets the CLABE number and reference for the transfer.
The payment stays pending until the transfer arrives, and Payrails completes it from the dLocal notification. The transfer details expire after one day.
Payrails captures SPEI payments through dLocal immediately, so a successful payment is final. To return funds, refund the payment.
Each SPEI 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 SPEI payment

How dLocal handles SPEI

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a SPEI payment

​How dLocal handles SPEI

Supported workflows

Before you begin

Request fields for dLocal

Authorize a SPEI payment

How dLocal handles SPEI