SPEI

Introduction

SPEI uses a redirect-based payment flow. When a customer selects SPEI at checkout, they are redirected to a hosted page showing the recipient bank account details (CLABE number and reference). The customer then logs into their bank's online or mobile banking to execute the transfer. SPEI is a single-use payment method.

This guide explains the process of integrating SPEI into your app or website using Payrails.

Pre-requisites

Before you start accepting SPEI payments with Payrails, there are a few requirements you must meet:

1. Integrate with Payrails using one of our SDKs or our API
2. Configure a new integration account for SPEI via dLocal as a Payment Service Provider. If you do not have a dLocal integration already configured in your workspace, please follow the dLocal integration setup guide first.
3. Enable SPEI as a payment method in your dLocal integration configuration. In the Payrails portal, navigate to Settings → Integrations, select your dLocal integration instance, and enable the SPEI checkbox under Payment methods, then save the account.
4. Enable SPEI as a payment option in your workflow.
5. Make sure you're sending the SPEI-specific meta fields in your requests.

Ways to integrate SPEI

Payrails SDK

The simplest way to use SPEI with Payrails is to use our drop-in in your checkout flow. With this integration type, no additional work is required to accept payments with SPEI except for handling success/failure screens for your users.

For a more flexible implementation using our SDK, you can use our genericRedirectButton element. See special instructions here for your client-side implementation.

Server-to-server integration

You can integrate SPEI by completely managing your own client-side implementation, and using Payrails APIs with a server-to-server integration to process SPEI payments.

Parse SPEI from lookup response

With a server-to-server integration, you can call our lookup payment options endpoint to get available payment options. As shown in the example below, you can see spei returned as an option of the paymentCompositionOptions.

{
  "name": "lookup",
  "actionId": "0bb6413e-cabb-4074-99e6-9e815c69f25b",
  "executedAt": "2026-03-26T12:00:00.000000000Z",
  "data": {
    "paymentCompositionOptions": [
      {
        "integrationType": "redirect",
        "paymentMethodCode": "spei",
        "description": "SPEI"
      }
    ]
  },
  "links": {
    "execution": "https://api.payrails.io/merchant/workflows/payment-acceptance/executions/83c534ac-13b7-43e6-b04b-f3e8b4eb4424",
    "authorize": {
      "method": "POST",
      "href": "https://api.payrails.io/merchant/workflows/payment-acceptance/executions/83c534ac-13b7-43e6-b04b-f3e8b4eb4424/authorize"
    }
  }
}

Pass SPEI payment method in request to authorize payment with Payrails

You can then make a request to our authorize a payment endpoint with spei as the paymentMethodCode. See an example below:

{
  "executionId": "c0fd1c51-e709-47e5-bfd1-5d1c98f7d990",
  "amount": {
    "value": "10000",
    "currency": "MXN"
  },
  "paymentComposition": [
    {
      "integrationType": "redirect",
      "paymentMethodCode": "spei",
      "amount": {
        "value": "10000",
        "currency": "MXN"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Jane Doe",
      "email": "[email protected]",
      "identityCardNumber": "1234567890",
      "country": {
        "code": "MX"
      }
    }
  },
  "returnInfo": {
    "success": "https://mysuccessurl.com",
    "error": "https://myerrorurl.com"
  }
}

Note on amounts: MXN uses 2 decimal places. Amounts should be provided in the smallest currency unit — e.g., 10000 for $100.00 MXN.

Note: SPEI is a redirect-based, single-use payment method. After calling the authorize endpoint, the customer will be redirected to a hosted page with the CLABE number and reference for the transfer. The customer executes the transfer from their bank. Payments expire after 1 day if the transfer is not received. Once confirmed, the customer will be redirected back to the returnInfo.success URL.

Handle the redirect response

After the customer completes the transfer, they will be redirected back to your success or error URL. You should then verify the payment status by checking the workflow execution status via the Payrails API or by listening to webhook notifications.

Supported currencies

SPEI via dLocal supports the following presentment currency:

• MXN — Mexican Peso

Supported regions / countries

Customer regions

SPEI is available to customers based in:

• Mexico 🇲🇽

Merchant regions

Merchants enabled for Mexico can accept SPEI payments via dLocal.

Supported workflows and services