UPI via dLocal

Accept UPI payments from customers in India with dLocal as the payment service provider (PSP). The customer goes to a dLocal-hosted page, approves the payment in their UPI app and returns to your site.

Supported workflows

Workflow	Supported
Payrails SDK	✔
Payrails API	✔
Delayed / Manual Capture	✖
Instant Capture	✔
Cancel / Void	✖
Refund / Reverse	✔
Save Instruments	✖
Merchant Initiated Transaction (MIT)	✖

Before you begin

Complete these steps before you send your first UPI 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 UPI on your dLocal merchant account.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select UPI under Payment methods, and save.
Add UPI 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 `INR`. Payrails rejects other currencies.
`meta.customer.name`	Required	The customer’s first name. 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.country.code`	Required	Payrails sends the payment to dLocal with the country `IN`, whatever value you send.
`meta.customer.identityCardNumber`	Required	The customer’s Permanent Account Number (PAN). 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.
`meta.customer.reference`	Optional	Sent to dLocal as the payer’s user reference.
`meta.clientContext.ipAddress`	Optional	Sent to dLocal as the payer’s IP address.
`meta.order.billingAddress`	Optional	Sent to dLocal as the payer address. `meta.order.deliveryAddress` takes priority when you send both.
`meta.order.description`	Optional	Sent to dLocal as the payment description.

Authorize a UPI payment

Call authorize a payment with upi as the paymentMethodCode. The response includes the redirect to the dLocal payment page.

Authorize request

{
  "amount": {
    "value": "500.00",
    "currency": "INR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "upi",
      "amount": {
        "value": "500.00",
        "currency": "INR"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Aarav",
      "lastName": "Sharma",
      "email": "aarav.sharma@example.com",
      "identityCardNumber": "ABCDE1234F",
      "country": {
        "code": "IN"
      }
    },
    "clientContext": {
      "ipAddress": "203.0.113.10"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer approves the payment, dLocal returns them to your success or error URL. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How dLocal handles UPI

Payrails removes digits and punctuation from the payer name before it sends the name to dLocal.
Payrails sends full and partial refunds to dLocal against the original payment.
Each UPI payment is a new 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 UPI payment

How dLocal handles UPI

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a UPI payment

​How dLocal handles UPI

Supported workflows

Before you begin

Request fields for dLocal

Authorize a UPI payment

How dLocal handles UPI