Napas via dLocal

Accept Napas payments from customers in Vietnam with dLocal as the payment service provider (PSP). The customer selects Napas, confirms the payment with their bank and returns to your site.

Supported workflows

Before you begin

Complete these steps before you send your first Napas 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 Napas on your dLocal account for Vietnam.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select Napas under Payment methods, and save.
Add Napas 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 `VND`. 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 `VN`, whatever value you send.
`meta.customer.lastName`	Optional	Added to the payer name.
`meta.customer.phone`	Optional	Sent to dLocal as the payer phone.
`meta.customer.identityCardNumber`	Optional	Sent to dLocal as the payer document.
`meta.customer.birthDate`	Optional	Sent to dLocal as the payer’s birth date.
`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.clientContext.deviceFingerprint`	Optional	Sent to dLocal as the payer’s device ID.
`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 Napas payment

Call authorize a payment with napas as the paymentMethodCode. The response includes the redirect to the hosted payment page.

Authorize request

{
  "amount": {
    "value": "700000",
    "currency": "VND"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "napas",
      "amount": {
        "value": "700000",
        "currency": "VND"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Minh",
      "lastName": "Nguyen",
      "email": "minh.nguyen@example.com",
      "country": {
        "code": "VN"
      }
    },
    "clientContext": {
      "ipAddress": "203.0.113.10"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer confirms 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 Napas

Payrails sends Napas payments to dLocal with the country VN and checks that the currency is VND.
Payrails collects no card details for Napas. The customer enters them on the hosted payment page.
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.

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 Napas payment

How dLocal handles Napas

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a Napas payment

​How dLocal handles Napas

Supported workflows

Before you begin

Request fields for dLocal

Authorize a Napas payment

How dLocal handles Napas