TrueMoney via dLocal

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

Supported workflows

Before you begin

Complete these steps before you send your first TrueMoney 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 TrueMoney on your dLocal account for Thailand.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select TrueMoney under Payment methods, and save.
Add TrueMoney 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. Payrails checks Required fields and returns an error when one is missing. Fields required by the PSP pass the Payrails checks but the PSP can decline the payment without them.

Field	Status	Description
`amount`	Required	Must be in `THB`. Payrails rejects TrueMoney requests to dLocal in any other currency.
`meta.customer.name`	Required	Sent to dLocal as the payer name, together with `meta.customer.lastName` when present.
`meta.customer.email`	Required	Sent to dLocal as the payer email.
`meta.customer.country`	Required	Must be present. Payrails sends `TH` to dLocal for TrueMoney.
`meta.customer.lastName`	Recommended	Added to the payer name.
`meta.customer.identityCardNumber`	Optional	Sent to dLocal as the payer’s document number.
`meta.customer.phone`, `meta.customer.birthDate`	Optional	Sent to dLocal as payer details.
`meta.clientContext.ipAddress`	Optional	Sent to dLocal as the payer’s IP address.
`meta.order.description`	Optional	Sent to dLocal as the payment description.
`meta.order.billingAddress`	Optional	Sent to dLocal as the payer address. `meta.order.deliveryAddress` takes priority when both are present.

Authorize a TrueMoney payment

Call authorize a payment with trueMoney as the paymentMethodCode. The response includes the redirect to TrueMoney.

Authorize request

{
  "amount": {
    "value": "500.00",
    "currency": "THB"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "trueMoney",
      "amount": {
        "value": "500.00",
        "currency": "THB"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Somchai",
      "lastName": "Jaidee",
      "email": "somchai.jaidee@example.com",
      "country": {
        "code": "TH"
      }
    },
    "clientContext": {
      "ipAddress": "203.0.113.10"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer confirms the payment, TrueMoney 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 TrueMoney

Payrails sends TrueMoney to dLocal with Thailand as the payment country, whatever country code the request carries.
Payrails removes digits, punctuation and symbols from the payer name before it sends the name to dLocal.

Merchant regions

Merchants enabled for Thailand on their dLocal account can accept TrueMoney.

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

How dLocal handles TrueMoney

Merchant regions

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a TrueMoney payment

​How dLocal handles TrueMoney

​Merchant regions

Supported workflows

Before you begin

Request fields for dLocal

Authorize a TrueMoney payment

How dLocal handles TrueMoney

Merchant regions