Nequi

Introduction

Nequi uses a redirect-based payment flow. When a customer selects Nequi at checkout, they are redirected to Nequi's interface — receiving a push notification on their phone — to authenticate and confirm the payment, then redirected back to your website or app upon completion. Nequi is a single-use payment method where customers must authenticate each payment.

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

Note: Payrails uses the Payrails payment method code nequi for Nequi payments. There is no separate code for Nequi QR.

Pre-requisites

Before you start accepting Nequi 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 Nequi 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 Nequi 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 Nequi checkbox under Payment methods, then save the account.
4. Enable Nequi as a payment option in your workflow.
5. Make sure you're sending the Nequi-specific meta fields in your requests.

Ways to integrate Nequi

Payrails SDK

The simplest way to use Nequi 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 Nequi 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 Nequi by completely managing your own client-side implementation, and using Payrails APIs with a server-to-server integration to process Nequi payments.

Parse Nequi 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 nequi 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": "nequi",
        "description": "Nequi"
      }
    ]
  },
  "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 Nequi payment method in request to authorize payment with Payrails

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

{
  "executionId": "c0fd1c51-e709-47e5-bfd1-5d1c98f7d990",
  "amount": {
    "value": "100000",
    "currency": "COP"
  },
  "paymentComposition": [
    {
      "integrationType": "redirect",
      "paymentMethodCode": "nequi",
      "amount": {
        "value": "100000",
        "currency": "COP"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Jane Doe",
      "email": "[email protected]",
      "phone": {
        "number": "3400100083",
        "countryCode": "57"
      },
      "identityCardNumber": "12345678",
      "country": {
        "code": "CO"
      }
    }
  },
  "returnInfo": {
    "success": "https://mysuccessurl.com",
    "error": "https://myerrorurl.com"
  }
}

Note on amounts: COP uses 0 decimal places. Amounts should be provided as whole numbers — e.g., 100000 for COP 100,000.

Note: Nequi is a redirect-based, single-use payment method. After calling the authorize endpoint, the customer will be redirected to Nequi's interface and receive a push notification on their phone to confirm the payment. The customer has up to 45 minutes to complete the payment. Once confirmed, the customer will be redirected back to the returnInfo.success URL. Make sure to provide valid returnInfo URLs in your authorization request.

Handle the redirect response

After the customer completes the payment on Nequi's side, 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

Nequi via dLocal supports the following presentment currency:

• COP — Colombian Peso

Supported regions / countries

Customer regions

Nequi is available to customers based in:

• Colombia 🇨🇴

Merchant regions

Merchants enabled for Colombia can accept Nequi payments via dLocal.

Supported workflows and services