> ## 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.

# Touch 'n Go via Checkout.com

> Set up Touch 'n Go payments through Checkout.com in Payrails, and see the order lines and OS type Checkout.com requires.

<picture noZoom>
  ![Touch 'n Go logo](https://assets.payrails.io/img/logos/touchngo/logo-full-bleed.svg)
</picture>

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

Accept [Touch 'n Go](https://docs.payrails.com/docs/integrations/payment-methods/touch-n-go) payments from customers in Malaysia with Checkout.com 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

<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 Touch 'n Go payment through Checkout.com:

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

## Request fields for Checkout.com

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 |
| - | - | - |
| `meta.order.lines` | Required | At least one line item. Each line needs `id`, `name`, `unitPrice` and a `quantity` of one or more. Sent to Checkout.com as the order items. |
| `meta.clientContext.osType` | Required | `ios` or `android`. Payrails rejects Touch 'n Go requests to Checkout.com without one. Sent to Checkout.com as the customer's operating system. |
| `amount` | Required | Must be in `MYR`. |
| `meta.order.description` | Optional | Sent to Checkout.com as the payment description. |
| `meta.clientContext.clientType` | Optional | `app` or `wap` sets the Touch 'n Go terminal type. Any other value, or no value, sends `web`. |
| `meta.customer.name`, `meta.customer.lastName` | Optional | Sent to Checkout.com as the customer name. |
| `meta.customer.email` | Optional | Sent to Checkout.com as the customer email. |
| `meta.customer.country.code` | Optional | Sent to Checkout.com as the customer country. |

## Authorize a Touch 'n Go payment

Call [authorize a payment](https://docs.payrails.com/reference/authorizeaction.md) with `touchNGo` as the `paymentMethodCode`. The response includes the redirect to Touch 'n Go.

```json Authorize request theme={null}
{
  "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"
    },
    "order": {
      "description": "Order 1234",
      "lines": [
        {
          "id": "item-1",
          "name": "Phone case",
          "quantity": 1,
          "unitPrice": {
            "value": "50.00",
            "currency": "MYR"
          }
        }
      ]
    },
    "clientContext": {
      "clientType": "app",
      "osType": "android"
    }
  },
  "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](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status before you fulfill the order.

## How Checkout.com handles Touch 'n Go

* Checkout.com processes Touch 'n Go through the Alipay+ network. Payrails creates a payment setup at Checkout.com and confirms it for Touch 'n Go. The confirmation returns the redirect to Touch 'n Go.
* Touch 'n Go through Checkout.com is an app-based wallet payment, so every request needs the customer's mobile operating system in `meta.clientContext.osType`.
* Payrails sends only order lines of type `lineItem`, or lines with no type. It skips tax, discount and shipping lines, and lines with no unit price or a zero quantity.
* If Checkout.com reports that Touch 'n Go isn't ready on your processing channel, the payment fails before Payrails redirects the customer.


## Related topics

- [Touch 'n Go](https://docs.payrails.com/docs/integrations/payment-methods/touch-n-go.md)
- [Bancontact via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/bancontact/checkout-com.md)
- [Benefit via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/benefit/checkout-com.md)


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