New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates

  • Release Notes

Payment Methods

  • Payment Methods Overview
  • Cards
  • Direct Debit
  • Bank Based Payments
  • Wallets
  • Vouchers
  • Articles and FAQ

Payment Gateways and Configuration

  • Payment Gateways Overview
  • Chargebee Test Gateway
  • Stripe
  • PayPal Payment Services
  • Chargebee Pay
  • Adyen
  • Authorize.net
  • Bambora (formerly Beanstream)
  • Bank of America
  • BluePay
  • BlueSnap
  • Braintree
  • Checkout.com
  • CyberSource
  • dLocal
    • UPI via dLocal
  • EBANX
  • Ecentric
  • Elavon
  • E-xact Direct Integration
  • eWay Rapid
  • Global Payments
  • GoCardless
  • J.P. Morgan Mobility Payment Solutions
  • Metrics Global
  • Mollie
  • Moneris
  • Network Merchants Incorporated (NMI)
  • Nuvei
  • Orbital (Chase Paymentech)
  • Pay.com
  • Paymill
  • Paystack
  • Pin Payments
  • QuickBooks Payments
  • Razorpay
  • Sage Pay
  • Solidgate
  • Twikey
  • Windcave
  • Worldline Online Payments(formerly Ingenico)
  • Worldpay
  • Articles and FAQ

Level 2/3 Data Support

  • Level 2/3 Data Support

Advanced Routing

  • Advanced Routing

Dunning

  • Dunning
  • Articles and FAQ

Offline Checkout

  • Offline Checkout
  • Articles and FAQ

Transaction Sync & Invoice Mapping

  • Transaction Sync and Invoice Mapping

Fraud Management

  • Fraud Management

Error Handling

  • Errors with Root Cause and Troubleshooting

Payment Lifecycle Logs

  • Payment Intents
  • Transactions
  • Gateway Activity Logs
  • Gateway Webhook Logs
  • Articles and FAQ

Others

  • Reach (Merchant of Record)
  • Payment Verification
  • Bulk Deletion of Payment Methods
  • Custom Payment Methods
  • Payment Initiator Parameter
  • PSD2 and Strong Customer Authentication
  • RBI e-Mandate
  • RBI Tokenization Regulations
  • Chargeback Management
  • Transaction Descriptors
  • Payment Preferences
  • Visa Trial Rules
  • Mastercard Trial Rules
  • Co-badged Card Compliance
  • Articles and FAQ
  1. Payments
  3. Payment Gateways and Configuration
  5. dLocal
  6. UPI via dLocal
  1. Payments
  3. Payment Gateways and Configuration
  5. dLocal
  6. UPI via dLocal

UPI via dLocal

This feature is a Private Beta Release. Contact Chargebee Support to enable UPI via dLocal for your live and test sites.

Overview

dLocal supports UPI (Unified Payments Interface) for India, allowing businesses to collect recurring payments via pre-approved UPI mandates. UPI is a pull-based payment method in which the customer authorizes a mandate once, and subsequent debits are pulled automatically without further user action.

This feature is ideal for subscription billing use cases, where reducing payment friction and improving collection success are critical.

This payment method is ideal for:

  • Businesses targeting customers in India who prefer to pay via local methods like UPI, without needing international cards or wallets.
  • Global merchants expanding into India or combining UPI with other local payment methods (LATAM, SE Asia, etc.) via dLocal.

Supported Region

The following are the region categories supported for this integration:

CategoryDetails
Your RegionMerchants onboarded in India and enabled for INR collections.
Payment Collection Region (Your customer’s region)

Payers must have India-issued bank accounts with UPI enabled.

Currency supported: INR

Processing Characteristics

CharacteristicDetails
Payment TypeMandate-based recurring UPI (Autopay mandate)
Mandate ApprovalCustomer authorizes via UPI app or by entering UPI ID
Mandate Rules

Mandate amount ≤ ₹1,00,000

Frequency: daily

Expiry: after 29 years from mandate creation

RefundsFull, partial, and multiple partial refunds are supported

Prerequisites

Ensure the following before configuring UPI payments via dLocal:

  1. A live dLocal merchant account with UPI enabled.
  2. dLocal must be added and configured as a payment gateway in Chargebee.
  3. UPI must be enabled by dLocal for your account. Contact the dLocal support team to activate it for your account.

Required Fields for UPI via dLocal

To collect payments successfully, the following fields must be passed during checkout:

  • First Name, Last Name
  • Email
  • Phone Number
  • Billing Address
  • PAN / Document Number (auto-filled based on currency)

If you're using Chargebee Checkout, go to:

  1. Settings > Configure Chargebee > Checkout & Self-Serve Portal > Fields
  2. Make the following fields mandatory:
    • Under Account Information: First Name, Last Name, Email, Phone Number
    image
    • Under Billing Address: All address fields
    image
    • Ensure PAN / Document Number is set up correctly (auto-handled for INR).

If using a custom checkout using JavaScript, you must explicitly collect and send these fields to Chargebee.

Integration Options

Integration MethodSupported/Not Supported
Chargebee Checkout

In-app layout of Checkout - Supported

Full Page Checkout - Supported

Custom Checkout

Chargebee.js - Supported

Payment Components - Supported

dLocal.js - Not supported

Configuring UPI Payments in Chargebee

Enable UPI via dLocal in your Chargebee site:

  1. Log in to the Chargebee Billing site.
  2. Go to Settings > Configure Chargebee > Payment Gateways > dLocal.
  3. On the Configure dLocal page, enable Unified Payments Interface (UPI) from the list of payment methods.
    image
  4. Click Apply to save changes.
    image

Configure Smart Routing

Follow these steps to configure Smart Routing rules to ensure INR recurring payments for the UPI route to dLocal:

  1. Go to Settings > Configure Chargebee > Payment Gateways.
  2. Select Smart Routing.
  3. Select dLocal as the payment gateway for the INR currency under the For UPI section.
image

Checkout Flow

  1. Customer initiates checkout and selects UPI as the payment method.
  2. Customer enters all mandatory details (e.g., PAN, billing info) and clicks Next.
    image
  3. The customer then reviews the entered information and clicks Pay & Subscribe.
    image
  4. After clicking Pay, the customer is redirected to a processor page or their UPI app.
  5. The customer completes the mandate approval:
    • Enters UPI ID
    • Approves request via app or link
    image
  6. On successful mandate approval:
    • Payment is triggered automatically
    • Subscription moves to In-Progress state
  7. Chargebee updates the status as Successful or Failed based on dLocal’s gateway confirmation.

Was this article helpful?