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.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:Ways to integrate Nequi
Payrails SDK
Server-to-server integration
Parse Nequi from lookup response
Pass Nequi payment method in request to authorize payment with Payrails
Note on amountsCOP uses 0 decimal places. Amounts should be provided as whole numbers—for example,
100000 for COP 100,000.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
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 🇨🇴