Touch&Go

Overview

Introduction

Touch&Go is a payment method which allows you to process payments in Malaysian ringgits by using e-wallets in Malaysia. This method supports purchases and payouts.

This article provides information about working with the Touch&Go method: general insights are presented in the Overview section, while information about the actions required to process payments and perform other actions is presented in the sections that follow.

General information

Payment method type digital wallet payments
Payment instruments digital wallets
Countries and regions MY
Payment currencies MYR
Currency conversion on the ecommpay side
One-time purchases +
Credential-on-file purchases –
Full refunds –
Partial refunds –
Payouts +
Chargebacks –
Notes –
Onboarding and access fee refer to your ecommpay account manager

Interaction diagram

Payment processing by using the Touch&Go method involves the merchant's web service, one of ecommpay interfaces, the ecommpay payment platform, and technical facilities of the provider service.

Operations support

Various platform interfaces can be used to process payments and perform operations using the Touch&Go method. Purchases can be processed by using Payment Page, Gate and Dashboard (using payment links) and payouts—by using Gate. At the same time, regardless of the interfaces used, the following properties and limitations are applicable.

The following properties and limitations apply to the Touch&Go method.

Amounts, MYR Times ¹
minimum maximum base threshold
Purchases 1.00 30,000.00 2 minutes *
Payouts 5.00 20,000.00 2 minutes *

* For information about the threshold time, refer to your account manager.

Note:
  1. The base and threshold times are defined as follows:
    • The base time is the average estimated time between the moment a payment is initiated in the payment platform to the moment the payment result is sent to the web service. The base time evaluation is made on the assumption of normal operation of all technical facilities and communication channels and typical customer behaviour (if any input from the customer is required). Use the base time to estimate when to react to the absence of payment result callbacks or when to check payment status (details).
    • The threshold time is the maximum possible time between the moment a payment is initiated in the payment platform to the moment the web service receives the callback with the payment result. A payment is automatically assigned the decline status if it wasn't processed within the threshold time. For individual customisation of the threshold time limit, contact ecommpay technical support.

Processing scenarios

To perform a purchase by using the Touch&Go method, you need to redirect the customer to the provider service. To initiate a payout, you need to notify the customer via the web service.

The customer payment scenario via Payment Page looks like this.

Figure 1. Proceeding to payment


Figure 2. Selecting method


Figure 3. Authentication


Figure 4. Confirming payment


Figure 5. Redirecting to the payment form


Figure 6. Redirecting to the web service


General scenarios of processing purchases and payouts can be presented as follows.

Figure 7. Purchase by using Payment Page
Figure 8. Purchase by using Gate
Figure 9. Payout by using Gate

Scenarios for performing operations via the main interfaces of the payment platform correspond to those presented in the diagrams. Similarly, when additional features (such as payment links) are used, scenarios for performing operations also correspond to the specifics of those features.

Purchases by using Payment Page

General information

To process a purchase through Payment Page by using the Touch&Go method, the merchant's web service is required to send a request with all required parameters and signature to the ecommpay URL and receive a callback with the result. The full sequence and special aspects of purchase processing are provided below.

Figure 10. Purchase processing by using Payment Page: step-by-step description
  1. A customer initiates a purchase in the web service.
  2. The web service sends the request for opening Payment Page to the specified ecommpay URL.
  3. The request for opening Payment Page is sent to the payment platform.
  4. The payment platform receives the request and validates the required parameters and signature.
  5. Payment Page is generated based on the project and request parameters.
  6. Payment Page is displayed to the customer.
  7. The customer selects the Touch&Go method.
  8. The payment platform receives the request for processing the payment by using the Touch&Go method.
  9. The payment platform processes the request and generates the redirection data.
  10. The data for redirecting the customer is sent from the payment platform to Payment Page.
  11. The customer is redirected to the provider service.
  12. The customer completes all required payment steps.
  13. The purchase is processed in the provider service.
  14. The customer is redirected to Payment Page
  15. The provider service sends a notification about the result to the payment platform.
  16. The payment platform sends the payment result callback to the web service.
  17. The payment platform sends the result information to Payment Page.
  18. The result information is displayed to the customer on Payment Page.

Information about the formats of requests and callbacks used for processing payments by using the Touch&Go method via Payment Page is presented further in this section; general information about working with the Payment Page API is presented in Interaction concepts.

Request format

There are several things you need to consider when sending purchase requests by using the Touch&Go method:

  1. The following parameters required for any payment must be specified:
    • project_id—project identifier obtained from ecommpay during integration
    • payment_id—payment identifier unique within the project
    • payment_currency—payment currency code in the ISO-4217 alpha-3 format
    • payment_amount—payment amount in the smallest currency unit
    • customer_id—customer identifier unique within the project

    Depending on the payment processing provider, other parameters may be required in the purchase requests.

  2. The following parameters required for any payment must be specified: project_id, payment_id, payment_currency, payment_amount, customer_id.

    Depending on the payment processing provider, other parameters may be required in the purchase requests.

  3. If you need to have the payment form displayed with the Touch&Go method selected, set the force_payment_method parameter to touchngo_wallet.
  4. Additionally, any other parameters available for working with Payment Page can be used (details).
  5. After all target parameters are specified, generate a signature (details).

Thus, a correct request for opening the payment form using the Touch&Go method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier and signature.

{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 50000,
   "payment_currency": "MYR",
   "customer_id": "customer1",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
Figure 11. Example of sufficient data in a purchase request
{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 50000,
   "payment_currency": "MYR",
   "customer_id": "customer1",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}

Callback format

The Touch&Go method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks.

The following is the example of a callback with information about a 500.00 MYR purchase made in the 1234 project.

Figure 12. Example of callback data indicating that the purchase has been processed
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Touchngo Wallet",
        "sum": {
            "amount": 50000,
            "currency": "MYR"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 28,
        "type": "sale",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "created_date": "2022-03-25T11:08:05+0000",
        "request_id": "9e32835fb27907e0e336c5117242b5cf60a4e17839",
        "sum_initial": {
            "amount": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 0000,
            "payment_id": "123abc123-321",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdMaxkUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

The following is the example of a callback with information about a declined purchase.

Figure 13. Example of callback data indicating that the purchase has been declined
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "Touchngo Wallet",
        "sum": {
            "amount": 50000,
            "currency": "MYR"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 31,
        "type": "sale",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "created_date": "2022-03-25T11:19:53+0000",
        "request_id": "fff3d5f8d5d31bc460b68b57dc63f4b482e906eb",
        "sum_initial": {
            "amount": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 0000,
            "payment_id": "0cf4215c-8978",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTCD4HkoMm8C4z258P4VnHANu445/jmY+g=="
}

Useful links

The following articles can be useful when implementing purchases via Payment Page:

Purchases by using Gate

General information

To process a purchase through Gate by using the Touch&Go method, the merchant's web service is required to do the following:

  1. Send a request with all the required parameters and signature to the ecommpay URL.
  2. Receive an intermediate callback from the payment platform and redirect the customer to the provider service.
  3. Receive the final callback from the payment platform.

The full sequence and special aspects of purchase processing are provided below.

Figure 14. Purchase processing by using Gate: step-by-step description
  1. A customer initiates a purchase by using the Touch&Go method in the web service.
  2. The web service sends the request for processing the purchase by using Gate to the specified ecommpay URL.
  3. The payment platform receives the request.
  4. The payment platform validates the required parameters and signature in the request.
  5. The payment platform sends the response to the web service with information about the receipt of the request and its validity (details).
  6. The payment platform performs further processing of the request (with parameter consistency check) and generates the redirection data.
  7. The payment platform sends the callback with the redirection data to the web service.
  8. The customer is redirected to the provider service.
  9. The customer completes all required payment steps.
  10. The purchase is processed in the provider service.
  11. The customer is redirected to the web service.
  12. The provider service sends the payment result notification to the payment platform.
  13. The payment platform sends the payment result callback to the web service.
  14. The customer receives the payment result information from the web service.

Information about the formats of requests and callbacks used for processing payments by using the Touch&Go method via Gate is presented further in this section. General information about working with the Gate API is presented in Interaction concepts.

Request format

There are several things you need to consider when sending purchase requests by using the Touch&Go method:

  1. To initiate each purchase, send a separate POST request to the /v2/payment/wallet/touchngo/sale endpoint. This endpoint belongs to the group /v2/payment/wallet/{payment_method}/sale.
  2. Each request must include the following objects and parameters:
    • Object general—general purchase information:
      • project_id—project identifier obtained from ecommpay during integration
      • payment_id—payment identifier unique within the project
      • signature—request signature generated after all required parameters are specified (details—in the Signature generation and verification) (details)
    • Object payment—payment information:
      • amount—payment amount in the smallest currency unit
      • currency—payment currency code in the ISO-4217 alpha-3 format
    • Object customer—customer information:
      • id—customer identifier unique within the project
      • ip_address—customer IP address relevant for the initiated payment
    • Object return_url—contains the URLs to which customer is redirected while or after payment processing:
      • success—URL to return customer to the web service after a successful payment.

    Depending on the payment processing provider, other parameters may be required in the purchase requests.

  3. Additionally, any other parameters included in the specification can be used.

Thus, a correct purchase request by using the Touch&Go method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier and IP address and the signature.

{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 50000,
    "currency": "MYR"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  }
  "return_url": {
    "success": "http://example.com/success"
  }
}
Figure 15. Example of sufficient data in a purchase request
{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 50000,
    "currency": "MYR"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  }
  "return_url": {
    "success": "http://example.com/success"
  }
}

Formats of intermediate callbacks for customer redirection

Each payment made with the Touch&Go method requires redirection of customers from the merchant's web service to the provider service. To redirect a customer it is necessary to receive an intermediate callback from the payment platform and use the information included in the redirect_data object. The format of such callbacks is standard (details), and the following objects and parameters are included in the redirect_data object:

  • body—object with data to be sent in the request body
  • method—parameter specifying the HTTP method for sending the request (GET or POST)
  • url—parameter containing a link for redirection
Figure 16. redirect_data example
  "redirect_data": {
    "method": "POST",
    "body": {
        "MerchantCode": "M123456",
        "TransNum": "1234567887654321",
        "Currency": "MYR",
        "Amount": "5.00",
        "PaymentDesc": "payment",
        "FirstName": "John Doe",
        "Country": "MYS",
        "TransProvider": "123",
        "Signature": "5dd1b37842380d37ac87d37dea0bf112b3d0c3ac4078d2fbaa692d073a"
    },
    "encrypted": [],
    "url": "https://www.example.com/pay"
}

Final callback format

The Touch&Go method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks.

The following is the example of a callback with information about a 500.00 MYR purchase made in the 1234 project.

Figure 17. Example of callback data indicating that the purchase has been processed
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Touchngo Wallet",
        "sum": {
            "amount": 50000,
            "currency": "MYR"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 28,
        "type": "sale",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "created_date": "2022-03-25T11:08:05+0000",
        "request_id": "9e32835fb27907e0e36c5117242b5cf60a4e17839",
        "sum_initial": {
            "amount": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 0000,
            "payment_id": "123abc123-321",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdMuHp99rHrtaxFvoB3cs9CRd4xeYG2Q=="
}

The following is the example of a callback with information about a declined purchase.

Figure 18. Example of callback data indicating that the purchase has been declined
{
    "project_id": 1234,
    "payment": {
        "id": "payment_47",
        "type": "purchase",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "Touchngo Wallet",
        "sum": {
            "amount": 50000,
            "currency": "MYR"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "operation": {
        "id": 31,
        "type": "sale",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "created_date": "2022-03-25T11:19:53+0000",
        "request_id": "fff3d5f8d5d31bc460b68b57dc63f4b482e906eb",
        "sum_initial": {
            "amount": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 0000,
            "payment_id": "0cf4215c-8978",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTCD4Hko55iFYv58P4VnHANu445/jmY+g=="
}

Useful links

The following articles can be useful when implementing purchases via Gate:

Payouts by using Gate

General information

To process a payout through Gate by using the Touch&Go method, send a request with all required parameters and signature to the ecommpay URL and receive a callback with the result. The full sequence and special aspects of payout processing are provided below.

Figure 19. Payout processing by using Gate: step-by-step description
  1. A customer initiates a payout by using the Touch&Go method in the web service.
  2. The web service sends the request for processing the payout by using Gate to the specified ecommpay URL.
  3. The payment platform receives the request.
  4. The payment platform validates the required parameters and signature in the request.
  5. The payment platform sends the response to the web service with information about the receipt of the request and its validity (details).
  6. The payment platform performs further processing of the request (with parameter consistency check) and sends it to the provider service.
  7. The payout is processed on the side of the provider service.
  8. The provider service sends the result notification to the payment platform.
  9. The payment platform sends the result callback to the web service.
  10. The customer receives the payout result information from the web service.

Information about the formats of requests and callbacks used for processing payouts by using the Touch&Go method via Gate is presented further in this section. General information about working with the Gate API is presented in Interaction concepts.

Request format

There are several things you need to consider when sending payout requests by using the Touch&Go method:

  1. To initiate each payout send a separate POST request to the /v2/payment/wallet/touchngo/payout endpoint. This endpoint belongs to the group: /v2/payment/wallet/{payment_method}/payout.
  2. Each request must include the following objects and parameters:
    • Object general—general payout information:
      • project_id—project identifier obtained from ecommpay during integration
      • payment_id—payment identifier unique within the project
      • signature—request signature generated after all required parameters are specified (details—in the Signature generation and verification) details
    • Object payment—payment information:
      • amount—payout amount in the smallest currency unit
      • currency—payout currency code in the ISO-4217 alpha-3 format
    • Object customer—customer information:
      • id—customer identifier unique within the project
      • ip_address—customer IP address relevant for the initiated payout
    • Object account—account information:
      • number—account number

    Depending on the payment processing provider, other parameters may be required in the purchase requests.

  3. Additionally, any other parameters included in the specification can be used.

Thus, a correct payout request by using the Touch&Go method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier and IP address, as well as account number and signature.

{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 50000,
    "currency": "MYR"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  },
  "account": {
    "number": "00004598"
  }
}
Figure 20. Example of sufficient data in a purchase request
{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 50000,
    "currency": "MYR"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  },
  "account": {
    "number": "00004598"
  }
}

Callback format

The Touch&Go method uses the standard format for callbacks to deliver payout results. For more information, see Callbacks.

The following is the example of a callback with information about a 500.00 MYR payout made in the 1234 project.

Figure 21. Example of callback data indicating that the payout has been processed
{
    "project_id": 1234,
    "payment": {
        "id": "payment_48",
        "type": "payout",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "method": "Touchngo Wallet",
        "sum": {
            "amount": 50000,
            "currency": "MYR"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "account": {
        "number": "123456"
    },
    "operation": {
        "id": 29,
        "type": "payout",
        "status": "success",
        "date": "2022-03-25T11:08:45+0000",
        "created_date": "2022-03-25T11:08:05+0000",
        "request_id": "9e32835fb27900e336c5117242b5cf60a4e17839",
        "sum_initial": {
            "amount": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 0000,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "U7HQO7ToISZhMPKdMaxkUKQtoYzFvoB3cs9CRd4xeYG2Q=="
}

The following is the example of a callback with information about a declined payout.

Figure 22. Example of callback data indicating that the payout has been declined
{
    "project_id": 1234,
    "payment": {
        "id": "payment_48",
        "type": "payout",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "method": "Touchngo Wallet",
        "sum": {
            "amount": 50000,
            "currency": "MYR"
        },
        "description": ""
    },
    "customer": {
        "id": "customer_123"
    },
    "account": {
        "number": "123456"
    },
    "operation": {
        "id": 29,
        "type": "payout",
        "status": "decline",
        "date": "2022-03-25T11:20:30+0000",
        "created_date": "2022-03-25T11:19:53+0000",
        "request_id": "fff3d5f8d5d31bc460b68b57dc63f4b482e906eb",
        "sum_initial": {
            "amount": 50000,
            "currency": "MYR"
        },
        "sum_converted": {
            "amount": 50000,
            "currency": "MYR"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 0000,
            "payment_id": "123abc123-123",
            "auth_code": ""
        }
    },
    "signature": "J7W15rkqrLzTC4m8C4z2iFYv58P4VnHANu445/jmY+g=="
}

Useful links

The following articles can be useful when implementing payouts via Gate:

Payouts by using Dashboard

When working with Dashboard, you can process single and mass payouts by using the Touch&Go method.

  • To process a single payout, open the payout form, specify all required parameters (including the payment method), send a request and verify that the payout has been processed.

  • To process a mass payout, prepare and upload a file with information about all target payouts, send a batch request, and verify that the payouts have been processed.

    Use a CSV file structured according to the requirements presented in the Mass payments data section. The payout parameters must comply with the requirements (you do not have to generate a signature because it is specified by Dashboard).

More information about processing payouts by using Dashboard is presented in a separate section.

Analysis of payments results

To analyse information about payments made with the Touch&Go method and other methods, you can use:

  • Dashboard interface toolkit with various lists and analytic panels.
  • Reports in CSV file format, available via the Reports section (one-time and periodically).
  • Data in JSON format, sent by program requests to a specified URL available by using the Data API interface.

If you have any questions, refer to the documentation (Dashboard and Using Data API) and ecommpay technical support.