Nequi via dLocal

Accept Nequi payments from customers in Colombia with dLocal as the payment service provider (PSP). The customer selects Nequi, confirms the payment in the Nequi app and returns to your site.

Supported workflows

Before you begin

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

Call authorize a payment with nequi as the paymentMethodCode. The response includes the redirect to the Nequi payment page.

Authorize request

{
  "amount": {
    "value": "100000.00",
    "currency": "COP"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "nequi",
      "amount": {
        "value": "100000.00",
        "currency": "COP"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Andrés",
      "lastName": "Gómez",
      "email": "andres.gomez@example.com",
      "identityCardNumber": "1012345678",
      "phone": {
        "countryCode": "57",
        "number": "3001234567"
      },
      "country": {
        "code": "CO"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

The customer confirms the payment in the Nequi app. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How dLocal handles Nequi

dLocal returns a redirect URL to the Nequi payment page, and Nequi sends the customer a push notification to confirm the payment.
The customer has 45 minutes to confirm the payment. Payrails completes the payment from the dLocal notification.
Payrails captures Nequi payments through dLocal immediately, so a successful payment is final. To return funds, refund the payment.
Each Nequi 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 Nequi payment

How dLocal handles Nequi

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a Nequi payment

​How dLocal handles Nequi

Supported workflows

Before you begin

Request fields for dLocal

Authorize a Nequi payment

How dLocal handles Nequi