Skip to main content
Touch ‘n Go is a mobile wallet used by customers in Malaysia. Customers pay from their Touch ‘n Go account and confirm each payment in the Touch ‘n Go app or on the Touch ‘n Go website. Payrails processes Touch ‘n Go through three payment service providers (PSPs). The flow is the same with each one, but the required request fields differ. Pick a PSP below for its setup steps and request examples.

​
How a Touch ‘n Go payment works

Touch ‘n Go is a redirect payment method:
  1. The customer selects Touch ‘n Go at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to Touch ‘n Go.
  3. The customer logs in and confirms the payment in the Touch ‘n Go app or on the Touch ‘n Go website.
  4. Touch ‘n Go sends the customer back to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures Touch ‘n Go payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

Touch ‘n Go supports MYR (Malaysian ringgit) as its only presentment currency. Touch ‘n Go is available to customers based in:
RegionsCountries
Asia Pacific🇲🇾 Malaysia

​
Integrate Touch ‘n Go

Choose the PSP that processes Touch ‘n Go for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

Adyen

Touch ‘n Go via Adyen

Checkout.com

Touch ‘n Go via Checkout.com

dLocal

Touch ‘n Go via dLocal

​
Check PSPs

WorkflowAdyenCheckout.comdLocal
Payrails SDK✔✔✔
Payrails API✔✔✔
Delayed / Manual Capture✖✖✖
Instant Capture✔✔✔
Cancel / Void✖✖✖
Refund / Reverse✔✔✔
Save Instruments✖✖✖
Merchant Initiated Transaction (MIT)✖✖✖
Each Touch ‘n Go payment is a new customer-initiated payment.

​
Ways to integrate Touch ‘n Go

  • Payrails SDK: the Web SDK shows Touch ‘n Go when your workflow returns it as a payment option, and redirects the customer to Touch ‘n Go. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with touchNGo as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 16, 2026