Accept local wallets and QR payments through dLocal
You can now offer seven local payment methods through your existing dLocal connection.
- GCash: wallet payments in the Philippines, in PHP. The customer approves the first payment in GCash, and later recurring payments use that enrollment.
- OVO: wallet payments in Indonesia, in IDR, with the same enrollment flow.
- NuPay: wallet payments in Brazil, in BRL, with the same enrollment flow.
- PicPay: wallet payments in Brazil, in BRL, with the same enrollment flow. Recurring charges are not available in production until dLocal finishes moving PicPay to its enrollment API.
- Mercado Pago: wallet payments in Brazil (BRL), Chile (CLP), Mexico (MXN), and Colombia (COP), with the same enrollment flow.
- Nequi QR: one-time QR payments in Colombia, in COP.
- Thai QR: one-time QR payments in Thailand, in THB.
GCash, OVO, NuPay, PicPay, and Mercado Pago are available in In-App Checkout, Full-Page Checkout, the Chargebee Self-Serve Portal, APIs, and Chargebee.js. A later charge for Nequi QR or Thai QR needs a Pay Now link.
Why is this important?
Offer customers local wallet and QR payment options through your existing dLocal connection, without setting up a separate gateway connection for these methods.
How can you use it?
Prerequisite: Ask dLocal to enable the method on your account, and connect dLocal in Chargebee. Enable that method's currency on your site before you enable the payment method.
- Log in to your Chargebee Billing site.
- Go to Settings > Configure Chargebee > Payment Gateways, and open your dLocal gateway.
- On Configure dLocal, enable the method, and click Apply. Chargebee adds a Smart Routing rule for that currency when none exists yet.
- If a rule already points to another gateway, open Manage Rules under Smart Routing and route the payment method to dLocal.
Chargebee registers the dLocal webhook for you. You do not need to create that endpoint in the dLocal dashboard.