Touch 'n Go via dLocal

Accept Touch ‘n Go payments from customers in Malaysia with dLocal as the payment service provider (PSP). The customer selects Touch ‘n Go, confirms the payment in Touch ‘n Go, and returns to your site.

Supported workflows

Before you begin

Complete these steps before you send your first Touch ‘n Go 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 Touch ‘n Go on your dLocal account for Malaysia.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select TouchNGo under Payment methods, and save.
Add Touch ‘n Go 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 `MYR`. Payrails rejects Touch ‘n Go 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 `MY` to dLocal for Touch ‘n Go.
`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 Touch ‘n Go payment

Call authorize a payment with touchNGo as the paymentMethodCode. The response includes the redirect to Touch ‘n Go.

Authorize request

{
  "amount": {
    "value": "50.00",
    "currency": "MYR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "touchNGo",
      "amount": {
        "value": "50.00",
        "currency": "MYR"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Aisyah",
      "lastName": "Rahman",
      "email": "aisyah.rahman@example.com",
      "country": {
        "code": "MY"
      }
    },
    "clientContext": {
      "ipAddress": "203.0.113.10"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer confirms the payment, Touch ‘n Go 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 Touch ‘n Go

Payrails sends Touch ‘n Go to dLocal with Malaysia 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 Malaysia on their dLocal account can accept Touch ‘n Go.

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 Touch ‘n Go payment

How dLocal handles Touch ‘n Go

Merchant regions

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a Touch ‘n Go payment

​How dLocal handles Touch ‘n Go

​Merchant regions

Supported workflows

Before you begin

Request fields for dLocal

Authorize a Touch ‘n Go payment

How dLocal handles Touch ‘n Go

Merchant regions