> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Napas via dLocal

> Set up Napas domestic card payments through dLocal in Payrails, and see the payer fields dLocal needs on every request.

<picture noZoom>
  ![Napas logo](https://assets.payrails.io/img/logos/napas/logo-full-bleed.svg)
</picture>

<picture noZoom>
  ![dLocal logo](https://assets.payrails.io/img/logos/dlocal/logo-full-bleed.svg)
</picture>

Accept [Napas](https://docs.payrails.com/docs/integrations/payment-methods/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

<table>
  <thead>
    <tr><th>Workflow</th><th>Supported</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td></tr>
  </tbody>
</table>

## Before you begin

Complete these steps before you send your first Napas payment through dLocal:

1. Set up a dLocal integration in your workspace. Follow the [dLocal integration setup guide](https://docs.payrails.com/docs/integrations/payment-providers/dlocal.md) if you don't have one yet.
2. Ask dLocal to enable Napas on your dLocal account for Vietnam.
3. In the Payrails Portal, go to **Settings → Integrations**, open your dLocal integration, select **Napas** under **Payment methods**, and save.
4. Add Napas as a [payment option](https://docs.payrails.com/docs/integrations/payment-methods/set-up-payment-methods.md) in your workflow.

## Request fields for dLocal

Send these fields in the authorize request, in addition to the standard [authorize fields](https://docs.payrails.com/reference/authorizeaction.md). **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](https://docs.payrails.com/reference/authorizeaction.md) with `napas` as the `paymentMethodCode`. The response includes the redirect to the hosted payment page.

```json Authorize request theme={null}
{
  "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](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) 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.


## Related topics

- [Napas](https://docs.payrails.com/docs/integrations/payment-methods/napas.md)
- [Khipu via dLocal](https://docs.payrails.com/docs/integrations/payment-methods/khipu/dlocal.md)
- [BCP via dLocal](https://docs.payrails.com/docs/integrations/payment-methods/bcp/dlocal.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.