# DOKU Wallet {#pm_doku}

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

## Overview {#en_pm_doku_overview}

An article about the payment method which allows to process payments in Indonesian rupiahs by using e-wallets in Indonesia and supports purchases and payouts.

### Introduction {#section_t5z_rlg_ytb .section}

DOKU Wallet is a payment method which allows to process payments in Indonesian rupiahs by using e-wallets in Indonesia.This method supports purchasesand payouts.

This article provides information about working with the DOKU Wallet 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|[ID](references/en/countries/ID.md)|
|Payment currencies|[IDR](references/en/currencies/IDR.md)|
|Currency conversion|on the Ecommpay side; refer to your Ecommpay key account manager to enable currency conversion|
|One-time purchases|+|
|Credential-on-file purchases|–|
|Full refunds|contact Ecommpay technical support|
|Partial refunds|contact Ecommpay technical support|
|Payouts|+|
|Chargebacks|–|
|Notes|-   In this method all payment amounts in [IDR](references/en/currencies/IDR.md) are integer. If the currency [IDR](references/en/currencies/IDR.md) is specified in the payment request it is necessary to round the payment amount to an integer, otherwise the fractional part is severed during processing on the payment platform side. If another currency is specified in the request, the payment amount is converted to an equivalent amount in the [IDR](references/en/currencies/IDR.md) currency on the Ecommpay side and rounded to 1,000.00 [IDR](references/en/currencies/IDR.md)
-   Safari browser may not support the redirection to a bank service. For the more details, contact your Ecommpay key account manager

|
|Onboarding and access fee|refer to your Ecommpay key account manager, additional information available in the [Ecommpay shop](https://ecommpay.com/shop/payment-methods/doku-wallet/)|

### Interaction diagram {#section_tsp_gzk_ggb .section}

Payment processing by using the DOKU Wallet method involves the merchant's web service, one of Ecommpay interfaces, the Ecommpay payment platform, and technical facilities of the DOKU Wallet service.

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

### Operations support {#section_rnx_4cl_ggb .section}

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

||Amounts, [IDR](references/en/currencies/IDR.md)¹|Times²|
|minimum|maximum|basic|threshold|
|--|:-----------------------------------------------|:-----|
|-------|:------|:----|:--------|
|Purchases|1.00|2,000,000.00 until KYC \*10,000,000.00 since KYC

|Under a minute|Refer to your Ecommpay key account manager|
|Payouts|1.00|10 000 000,00|Under 5 minutes|Refer to your Ecommpay key account manager|

**Note:**

1.  KYC or Know Your Customer is the process that allows organisations to verify clients and prevent frauds.
2.  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 DOKU Wallet method, you need to redirect the customer to the DOKU Wallet service, while to initiate a payout, you need to notify the customer via the web service.

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

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

![](images/pm/eng_doku_interfaces_gate_payout.svg "Payout by using Gate")

## Purchases by using Payment Page {#en_pm_doku_pp}

### General information {#section_gtg_vxk_m2b .section}

To process a purchase through Payment Pageby using the DOKU Wallet 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/eng_doku_uml_pp_wallet.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 DOKU Wallet method.
8.  The payment platform receives the request for processing the payment by using the DOKU Wallet method.
9.  The payment platform processes the request and sends it to the DOKU Wallet service.
10. The request is processed on the DOKU Wallet service side.
11. The data for redirecting the customer to the DOKU Wallet service is sent from the DOKU Wallet service to the payment platform.
12. The data for redirecting the customer is sent from the payment platform to Payment Page.
13. The customer is redirected to the DOKU Wallet service.
14. The customer completes all required payment steps.
15. The purchase is processed in the DOKU Wallet service.
16. The result information is displayed to the customer in the DOKU Wallet service and the customer is redirected to Payment Page.
17. The DOKU Wallet service sends a notification about the result to the payment platform.
18. The payment platform sends the payment result callback to the web service.
19. The payment platform sends the result information to Payment Page.
20. 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 DOKU Wallet 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 using the DOKU Wallet 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
2.  Additionally, it is recommended to specify the first name and email address of the customer in the parameters `customer_first_name` and `customer_email`. If any of these parameters are missing, the payment form may display input fields for entering the missing values \(details are available in [Submission of additional payment information](en_pp_clarification.md)\).
3.  If you need to have the payment form displayed with the DOKU Wallet method selected, set the `force_payment_method` parameter to `doku`.
4.  Additionally, any other parameters available for working with Payment Page can be used \([details](en_PP_Parameters.md)\).
5.  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 DOKU Wallet method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), identifier, first name and email address of the customer, as well as signature.

```language-json
{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 1000,
   "payment_currency": "IDR",
   "customer_id": "customer1",
   "customer_first_name": "Hasan",
   "customer_email": "prasetyo@example.com",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
```

```language-json
{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 1000,
   "payment_currency": "IDR",
   "customer_id": "customer1",
   "customer_first_name": "Hasan",
   "customer_email": "prasetyo@example.com",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
```

### Callback format {#section_dpx_2hl_ggb .section}

In the DOKU Wallet method, the callbacks that deliver purchase results use the standard format described in [Handling callbacks](en_platform_callbacks.md#).

The following is the example of a callback with information about a `1,000.00 IDR` purchase made in the `238` project.

```language-json
{
        "project_id": 238,
        "payment": {
            "id": "Doku_eWallet_001",
            "type": "purchase",
            "status": "success",
            "date": "2018-12-14T09:21:58+0000",
            "method": "Doku",
            "sum": {
                "amount": 100000,
                "currency": "IDR"
            },
            "description": ""
        },
        "account": {
            "number": "1189632633"
        },
        "operation": {
            "id": 6085000002263,
            "type": "sale",
            "status": "success",
            "date": "2018-12-14T09:21:58+0000",
            "created_date": "2018-12-14T09:20:39+0000",
            "request_id": "026b9dbadeb438abea86c9667edc9b11eb994",
            "sum_initial": {
                "amount": 100000,
                "currency": "IDR"
            },
            "sum_converted": {
                "amount": 100000,
                "currency": "IDR"
            },
            "provider": {
                "id": 1162,
                "payment_id": "342205",
                "date": "2018-12-14T09:21:54+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "XFyr/D1zXj84lUZVfpbWZolLFd3GxgPgUzIDg=="
    }
```

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

```language-json
{
        "project_id": 238,
        "payment": {
            "id": "ECT_TEST_1544793284604",
            "type": "purchase",
            "status": "decline",
            "date": "2018-12-14T13:23:50+0000",
            "method": "Doku",
            "sum": {
                "amount": 2000000000,
                "currency": "IDR"
            },
            "description": ""
        },
        "customer": {
            "id": "1"
        },
        "operation": {
            "id": 19078000002242,
            "type": "sale",
            "status": "decline",
            "date": "2018-12-14T13:23:50+0000",
            "created_date": "2018-12-14T13:20:47+0000",
            "request_id": "b12c7232b016305896e291c0a8ac67b74dd2bc05ac9",
            "sum_initial": {
                "amount": 2000000000,
                "currency": "IDR"
            },
            "sum_converted": {
                "amount": 2000000000,
                "currency": "IDR"
            },
            "provider": {
                "id": 1162,
                "payment_id": "",
                "auth_code": ""
            },
            "code": "20101",
            "message": "Decline due to amount or frequency limit"
        },
        "signature": "5+82BkJhEn/DG892c1vYINbEVDN9uuQTagdL6SYe5iOzSA=="
    }
```

### 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_doku_gate_purchase}

### General information {#section_lsx_3jl_ggb .section}

To process a purchase through Gate by using the DOKU Wallet 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 DOKU Wallet service.
3.  Receive the final callback from the payment platform.

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

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

1.  A customer initiates a purchase by using the DOKU Wallet 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 sends it to the DOKU Wallet service.
7.  The request is processed on the DOKU Wallet service side.
8.  The DOKU Wallet service sends the redirection data to the payment platform.
9.  The payment platform sends the callback with the redirection data to the web service.
10. The customer is redirected to the DOKU Wallet service.
11. The customer completes all required payment steps.
12. The purchase is processed in the DOKU Wallet service.
13. The result is displayed to the customer and the customer is redirected to the web service.
14. The DOKU Wallet service sends the payment result notification to the payment platform.
15. The payment platform sends the payment result callback to the web service.
16. 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 DOKU Wallet 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 must consider when using purchase requests in the DOKU Wallet method:

1.  To initiate each purchase, send a separate POST request to the `/v2/payment/wallet/doku/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
3.  Additionally, it is recommended to specify the following parameters:

    -   Object `customer`—customer information:
        -   `first_name`—first name of the customer
        -   `email`—email address of the customer
    If any of these parameters are missing, the payment platform may send the list of missing parameters in a callback requesting additional information submission \(details are available in [Submission of additional payment information](en_Gate_Clarification.md)\).

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

Thus, a correct purchase request by using the DOKU Wallet method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), identifier, first name, email address and IP address of the customer, as well as signature.

```language-json
{
    "general": {
    "project_id": 125,
    "payment_id": "ID_184",
    "signature": "PJkV8ej\/UG0DiipTv+AWoXW\/9MTO8yJA=="
  },
  "customer": {
    "ip_address": "192.0.2.0",
    "first_name": "Riza",
    "email": "riza@example.com",
    "id": "123"
    },
  "payment": {
    "amount": 100,
    "currency": "IDR"
  }
}
```

```language-json
{
    "general": {
    "project_id": 125,
    "payment_id": "ID_184",
    "signature": "PJkV8ej\/UG0DiipTv+AWoXW\/9MTO8yJA=="
  },
  "customer": {
    "ip_address": "192.0.2.0",
    "first_name": "Riza",
    "email": "riza@example.com",
    "id": "123"
    },
  "payment": {
    "amount": 100,
    "currency": "IDR"
  }
}
```

### Formats of intermediate callbacks for customer redirection {#section_nxg_hmn_zgb .section}

Each payment made with the DOKU Wallet method requires redirection of customers from the merchant's web service to the DOKU Wallet 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": {
                "MALLID": 4038,
                "CHAINMERCHANT": "NA",
                "AMOUNT": "10000.00",
                "PURCHASEAMOUNT": "10000.00",
                "TRANSIDMERCHANT": 1447000002341,
                "PAYMENTTYPE": "SALE",
                "WORDS": "2e2d93c40d5c82f87b555502492222abcdb8c50f",
                "REQUESTDATETIME": "20181218142352",
                "CURRENCY": "360",
                "PURCHASECURRENCY": "360",
                "SESSIONID": "7d28088c",
                "NAME": "Riza",
                "EMAIL": "riza@testpay.com",
                "BASKET": "Sale,10000.00,1,10000.00",
                "PAYMENTCHANNEL": "41"
            },
            "encrypted": [],
            "url": "https://pay.doku.com/Suite/Receive"
        }
```

### Final callback format {#section_dpx_2hl_ggb .section}

In the DOKU Wallet method, the callbacks that deliver purchase results use the standard format described in [Handling callbacks](en_platform_callbacks.md#).

The following is the example of a callback with information about a `1,000.00 IDR` purchase made in the `238` project.

```language-json
{
        "project_id": 238,
        "payment": {
            "id": "Doku_eWallet_001",
            "type": "purchase",
            "status": "success",
            "date": "2018-12-14T09:21:58+0000",
            "method": "Doku",
            "sum": {
                "amount": 100000,
                "currency": "IDR"
            },
            "description": ""
        },
        "account": {
            "number": "1189632633"
        },
        "operation": {
            "id": 6085000002263,
            "type": "sale",
            "status": "success",
            "date": "2018-12-14T09:21:58+0000",
            "created_date": "2018-12-14T09:20:39+0000",
            "request_id": "026b9dbadeb438abea86c9667edc9b11eb994",
            "sum_initial": {
                "amount": 100000,
                "currency": "IDR"
            },
            "sum_converted": {
                "amount": 100000,
                "currency": "IDR"
            },
            "provider": {
                "id": 1162,
                "payment_id": "342205",
                "date": "2018-12-14T09:21:54+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "XFyr/D1zXj84lUZVfpbWZolLFd3GxgPgUzIDg=="
    }
```

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

```language-json
{
        "project_id": 238,
        "payment": {
            "id": "ECT_TEST_1544793284604",
            "type": "purchase",
            "status": "decline",
            "date": "2018-12-14T13:23:50+0000",
            "method": "Doku",
            "sum": {
                "amount": 2000000000,
                "currency": "IDR"
            },
            "description": ""
        },
        "customer": {
            "id": "1"
        },
        "operation": {
            "id": 19078000002242,
            "type": "sale",
            "status": "decline",
            "date": "2018-12-14T13:23:50+0000",
            "created_date": "2018-12-14T13:20:47+0000",
            "request_id": "b12c7232b016305896e291c0a8ac67b74dd2bc05ac9",
            "sum_initial": {
                "amount": 2000000000,
                "currency": "IDR"
            },
            "sum_converted": {
                "amount": 2000000000,
                "currency": "IDR"
            },
            "provider": {
                "id": 1162,
                "payment_id": "",
                "auth_code": ""
            },
            "code": "20101",
            "message": "Decline due to amount or frequency limit"
        },
        "signature": "5+82BkJhEn/DG892c1vYINbEVDN9uuQTagdL6SYe5iOzSA=="
    }
```

### 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_doku_gate_payout}

### General information {#section_lsx_3jl_ggb .section}

To process a payout through Gateby using the DOKU Wallet 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/eng_doku_uml_gate_payout.svg)

1.  A customer initiates a payout by using the DOKU Wallet 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 DOKU Wallet service.
7.  The payout is processed on the side of the DOKU Wallet service.
8.  The DOKU Wallet 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 DOKU Wallet 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 DOKU Wallet method:

1.  To initiate each payout send a separate POST request to the `/v2/payment/wallet/doku/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`—customer e-wallet information:
        -   `number`—customer e-wallet number
        -   `customer_name`—full customer name
3.  Additionally, any other parameters included in the specification can be used.

Thus, a correct payout request by using the DOKU Wallet method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), identifier, e-wallet number, full name and IP address, as well as signature.

```language-json
{
    "general": {
    "project_id": 2853,
    "payment_id": "test-002",
    "signature": "M1vT4q9c8hA8xbgBOp8DTf8d/XdoV+vd7Q=="
  },
  "customer": {
    "id": "payoutTest",
    "ip_address": "192.0.2.0"
  },
  "account": {
    "number": "654654654",
    "customer_name": "John Doe"
  },
  "payment": {
    "amount": 10000,
    "currency": "IDR"
  }
}
```

```language-json
{
    "general": {
    "project_id": 2853,
    "payment_id": "test-002",
    "signature": "M1vT4q9c8hA8xbgBOp8DTf8d/XdoV+vd7Q=="
  },
  "customer": {
    "id": "payoutTest",
    "ip_address": "192.0.2.0"
  },
  "account": {
    "number": "654654654",
    "customer_name": "John Doe"
  },
  "payment": {
    "amount": 10000,
    "currency": "IDR"
  }
}
```

### Callback format {#section_wsx_3jl_ggb .section}

In the DOKU Wallet method, the callbacks that deliver payout results use the standard format described in [Handling callbacks](en_platform_callbacks.md#).

The following is the example of a callback with information about a `1.00 IDR` payout made in the `580` project.

```language-json
{
        "project_id": 580,
        "payment": {
            "id": "ApsViaDoku-040-wallet-1",
            "type": "payout",
            "status": "success",
            "date": "2019-05-07T11:38:24+0000",
            "method": "Doku",
            "sum": {
                "amount": 100,
                "currency": "IDR"
            },
            "description": "ApsViaDokuPayoutTest.49855500 1538564115"
        },
        "account": {
            "number": "1579000479"
        },
        "customer": {
            "id": "1",
            "phone": "623615557444"
        },
        "operation": {
            "id": 31771000001833,
            "type": "payout",
            "status": "success",
            "date": "2019-05-07T11:38:24+0000",
            "created_date": "2019-05-07T11:38:14+0000",
            "request_id": "a6ce8cf365af0c33a3d77cb45e8780793377c9460",
            "sum_initial": {
                "amount": 100,
                "currency": "IDR"
            },
            "sum_converted": {
                "amount": 100,
                "currency": "IDR"
            },
            "provider": {
                "id": 1162,
                "payment_id": "DK06282314",
                "date": "2019-05-07T18:38:19+0000",
                "auth_code": "",
                "endpoint_id": "04"
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "8xwuyUSnpfu4YVMH1qF8ZvMrU3JUTyF8UjZ8qTouKQ=="
    }
```

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

```language-json
{
        "project_id": 439,
        "payment": {
            "id": "ApsViaDoku-129",
            "type": "payout",
            "status": "decline",
            "date": "2019-03-29T09:18:18+0000",
            "method": "Doku",
            "sum": {
                "amount": 1100000000,
                "currency": "IDR"
            },
            "description": "123"
        },
        "account": {
            "number": "1322808400"
        },
        "customer": {
            "id": "payoutTest",
            "phone": "623615557444"
        },
        "operation": {
            "id": 3293088074203,
            "type": "payout",
            "status": "decline",
            "date": "2019-03-29T09:18:18+0000",
            "created_date": "2019-03-29T09:18:14+0000",
            "request_id": "d2b43977e0c6d54ecec408177cfb892f6cf28c07c4",
            "sum_initial": {
                "amount": 1100000000,
                "currency": "IDR"
            },
            "sum_converted": {
                "amount": 1100000000,
                "currency": "IDR"
            },
            "provider": {
                "id": 1274,
                "payment_id": "",
                "auth_code": ""
            },
            "code": "20101",
            "message": "Decline due to amount or frequency limit"
        },
        "signature": "D5SRvrsJaOQMKitsQNJ3hlawe6epQJtfa6uEDwkshnQA=="
    }
```

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

## Testing {#en_pm_doku_testing}

### General information {#section_zqw_xfw_xjb .section}

For the DOKU Wallet method, it is possible to test purchases by using Payment Page and Gate, as well as payouts by using Gate. To enable and disable testing, as well getting assistance with setting up a test project, refer to Ecommpay technical support.

When testing payments and operations keep in mind that the test project identifier must be indicated in requests, only the [IDR](references/en/currencies/IDR.md) currency can be used, the interfaces of the emulator of Payment Page and DOKU Wallet payment forms can differ from the production environment.

### Statuses of test payments and operations {#section_j1z_1s5_zjb .section}

The final status of test payments and operations is determined by the amount specified in the request.

Test purchases:

-   `decline` status with `40000` or `40400` amount
-   `success` status with any other amount

Test payouts:

-   `decline` status with `40000` or `40400` amount
-   `success` status with any other amount

### Purchases by using Payment Page {#section_wlk_dgw_xjb .section}

To perform a test purchase by using Payment Page, do the following:

1.  Send a correct test request for Payment Page opening to the payment platform.
2.  If the `doku` method was not specified in the request—select the method on the emulator page.
3.  Specify a random email address and a random first name in the data entry fields.
4.  Click the **Success** or **Decline** button \(depending on the amount specified in the request\).
5.  Receive the final callback with information about the payment result.

More information about processing purchases by using the DOKU Wallet method via Payment Page is provided in the [Purchases by using Payment Page](pm_doku.md#) section.

### Purchases by using Gate {#section_uvm_ngw_xjb .section}

To perform test purchases by using Gate, it is necessary to submit a URL for redirection to the test purchases confirmation page to Ecommpay technical support \(due to the peculiarities of the DOKU Wallet service one URL is used for payments with `success` and `decline` statuses\), and receive a confirmation about the possibility of testing purchases. After that, do the following for every test purchase:

1.  Send a correct test request for purchase to the payment platform.
2.  Accept a callback with redirection data.
3.  Go to the received URL and click the **Success** or **Decline** button \(depending on the amount specified in the request\).
4.  Make sure that the test purchase confirmation page is displayed.
5.  Receive the final callback with information about the payment result.

More information about processing purchases by using the DOKU Wallet method via Gate is provided in the [Purchases by using Gate](pm_doku.md#) section.

### Payouts by using Gate {#section_wwc_xhw_xjb .section}

o process a test payout by using Gate, send a valid test request for a payout to the payment platform and receive a final callback with information about the payout result. More information about processing payouts by using the DOKU Wallet method via Gate is provided in the [Payouts by using Gate](pm_doku.md#) section.

## Analysis of payments results {#en_pm_doku_dash_analysis}

To analyse information about payments made with the DOKU Wallet 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.