# Touch&Go {#pm_touchngo}

**Parent topic:**[Digital wallet payments](en_pm_ewallet.md)

## Overview {#en_pm_touchngo_overview}

An article about the payment method which allows you to process payments in Malaysian ringgits by using e-wallets in Malaysia and supports purchases and payouts.

### Introduction {#section_t5z_rlg_ytb .section}

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 {#section_tbf_2zk_ggb .section}

|Payment method type|digital wallet payments|
|Payment instruments|digital wallets|
|Countries and regions|[MY](references/en/countries/MY.md)|
|Payment currencies|[MYR](references/en/currencies/MYR.md)|
|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 {#section_tsp_gzk_ggb .section}

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.

![](images/pm/en_touchngo_functional.svg)

### Operations support {#section_rnx_4cl_ggb .section}

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.

| |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. Use the base time to estimate when to react to the absence of payment result callbacks or when to check payment status \([details](en_Gate_payment_status_request.md#)\).
    -   *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 {#section_fgt_sdl_ggb .section}

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.

![](images/ecommpay/pm_pp_scenario/en_pp_customer_scenario_touchngo_1.svg "Proceeding to payment")

![](images/ecommpay/pm_pp_scenario/en_pp_customer_scenario_touchngo_2.svg "Selecting method")

![](images/ecommpay/pm_pp_scenario/en_pp_customer_scenario_touchngo_3.svg "Authentication")

![](images/ecommpay/pm_pp_scenario/en_pp_customer_scenario_touchngo_4.svg "Confirming payment")

![](images/ecommpay/pm_pp_scenario/en_pp_customer_scenario_touchngo_5.svg "Redirecting to the payment form")

![](images/ecommpay/pm_pp_scenario/en_pp_customer_scenario_touchngo_6.svg "Redirecting to the web service")

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

![](images/pm/en_touchngo_interfaces_pp.svg "Purchase by using Payment Page")

![](images/pm/en_touchngo_interfaces_gate.svg "Purchase by using Gate")

![](images/pm/en_touchngo_interfaces_gate_payout.svg "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 {#en_pm_touchngo_pp_purchase}

### General information {#section_gtg_vxk_m2b .section}

To process a purchase through Payment Pageby 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.

![](images/pm/en_touchngo_uml_pp.svg)

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](en_pp_interaction_organisation.md#).

### Request format {#section_p5j_fgl_ggb .section}

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.  If you need to have the payment form displayed with the Touch&Go method selected, set the `force_payment_method` parameter to `touchngo\_wallet`.
3.  Additionally, any other parameters available for working with Payment Page can be used \([details](en_PP_Parameters.md)\).
4.  After all target parameters are specified, generate a signature \([details](en_platform_signature.md#)\).

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.

```language-json
{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 50000,
   "payment_currency": "MYR",
   "customer_id": "customer1",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
```

```language-json
{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 50000,
   "payment_currency": "MYR",
   "customer_id": "customer1",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
```

### Callback format {#section_dpx_2hl_ggb .section}

The Touch&Go method uses the standard format for callbacks to deliver purchase results. For more information, see [Handling callbacks](en_platform_callbacks.md#).

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

```language-json
{
    "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.

```language-json
{
    "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 {#section_xpz_thl_ggb .section}

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

-   [Interaction concepts](en_pp_interaction_organisation.md#)—about the interaction with the payment platform by using Payment Page.
-   [Signature generation and verification](en_platform_signature.md#)—about the procedure of generating and verifying signatures in requests and callbacks.
-   [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations.
-   [One-time one-step purchase](en_platform_sms_model.md)—about processing of one-time one-step purchases by using Payment Page.
-   [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations.

## Purchases by using Gate {#en_pm_touchngo_gate_purchase}

### General information {#section_lsx_3jl_ggb .section}

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.

![](images/pm/en_touchngo_uml_gate.svg)

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](en_gate_interaction_organisation.md#)\).
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](en_gate_interaction_organisation.md#).

### Request format {#section_osx_3jl_ggb .section}

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](https://api-developers.ecommpay.com/api-specification/wallet/post-v2-payment-wallet-payment-method-sale).
2.  Each request must include the following objects and parameters:

    -   Object `general`—general purchase information:
        -   `project_id`—project identifierobtained from Ecommpay during integration
        -   `payment_id`—payment identifierunique within the project
        -   `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md#)\)
    -   Object `payment`—payment information:
        -   `amount`—payment amount in the smallest currency unit
        -   `currency`—payment currency codein the ISO-4217 alpha-3 format
    -   Object `customer`—customer information:
        -   `id`—customer identifierunique within the project
        -   `ip_address`—customer IP addressrelevant 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.

```language-json
{
  "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"
  }
}
```

```language-json
{
  "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 {#section_nxg_hmn_zgb .section}

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](en_platform_callbacks.md#)\), 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

Additionally, the `redirect_data` object may include the `encrypted` parameter containing service information.

```language-json
  "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 {#section_dpx_2hl_ggb .section}

The Touch&Go method uses the standard format for callbacks to deliver purchase results. For more information, see [Handling callbacks](en_platform_callbacks.md#).

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

```language-json
{
    "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.

```language-json
{
    "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 {#section_xsx_3jl_ggb .section}

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

-   [Interaction concepts](en_gate_interaction_organisation.md#)—about the interaction with the payment platform by using Gate.
-   [Signature generation and verification](en_platform_signature.md#)—about the procedure of generating and verifying signatures in requests and callbacks.
-   [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations.
-   [One-time one-step purchase](en_platform_sms_model.md)—about processing of one-time one-step purchases by using Gate.
-   [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations.

## Payouts by using Gate {#en_pm_touchngo_gate_payout}

### General information {#section_lsx_3jl_ggb .section}

To process a payout through Gateby 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.

![](images/pm/en_touchngo_uml_gate_payout.svg)

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](en_gate_interaction_organisation.md#)\).
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](en_gate_interaction_organisation.md#).

### Request format {#section_osx_3jl_ggb .section}

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](https://api-developers.ecommpay.com/api-specification/wallet/post-v2-payment-wallet-payment-method-payout).
2.  Each request must include the following objects and parameters:

    -   Object `general`—general payout information:
        -   `project_id`—project identifierobtained from Ecommpay during integration
        -   `payment_id`—payment identifierunique within the project
        -   `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md#)\)
    -   Object `payment`—payment information:
        -   `amount`—payout amount in the smallest currency unit
        -   `currency`—payout currency codein the ISO-4217 alpha-3 format
    -   Object `customer`—customer information:
        -   `id`—customer identifierunique within the project
        -   `ip_address`—customer IP addressrelevant 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.

```language-json
{
  "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"
  }
}
```

```language-json
{
  "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 {#section_dpx_2hl_ggb .section}

The Touch&Go method uses the standard format for callbacks to deliver payout results. For more information, see [Handling callbacks](en_platform_callbacks.md#).

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

```language-json
{
    "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.

```language-json
{
    "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 {#section_xsx_3jl_ggb .section}

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

-   [Interaction concepts](en_gate_interaction_organisation.md#)—about the interaction with the payment platform by using Gate.
-   [Signature generation and verification](en_platform_signature.md#)—about the procedure of generating and verifying signatures in requests and callbacks.
-   [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations.
-   [Payouts](en_Gate_payout.md)—about processing of payouts by using Gate.
-   [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations.

## Payouts by using Dashboard {#en_pm_dash_payout}

When working with Dashboard, you can process *single* and *mass* payoutsby 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](en_dbl_payments.md#) section.The payout parameters must comply with the [requirements](pm_touchngo.md#) \(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](en_dbl_payments.md#).

## Analysis of payments results {#en_pm_touchngo_dash_analysis}

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

-   Dashboardinterface toolkitwith 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 by using the Data API interface.

If you have any questions, refer to the documentation \([Dashboard](en_dbl_about.md) and [Using Data API](en_dbl_api_protocol.md)\) and Ecommpay technical support.