DOKU Wallet

Overview

DOKU Wallet is a payment method to process payments by using DOKU Wallet e-wallets. Purchases can be processed by using Payment Page and Gate, payouts by using Gate.

General information

Payment method type E-wallet payments
Countries and regions Indonesia
Payment currencies IDR
Currency conversion on the ECommPay side; refer to your ECommPay key account manager to enable currency conversion
Purchases +
Payouts +
Stored credentials payments
Full refunds contact ECommPay technical support
Partial refunds contact ECommPay technical support
Chargebacks
Notes Safari browser may not support the redirection to a bank service. For the more details, contact ECommPay key account manager
Onboarding and access fee Refer to your key account manager ECommPay

Interaction diagram

Payment processing by using the DOKU Wallet payment method requires merchant's web service, one of ECommPay interfaces, and the ECommPay payment platform, as well as the DOKU Wallet service.

Operations support

Interfaces Amounts, IDR Times**
Payment Page Mobile SDKs CMS Plugins Gate Dashboard 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

* KYC or Know Your Customer is the process that allows organisations to verify clients and prevent frauds.

** The basic and threshold times are defined as follows:
  • The basic 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 initiator. The basic 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 customer is required). Use the basic time to estimate when to react to the absence of payment result notifications or when to check payment status.
  • The threshold time is the maximum possible time between the moment a payment is initiated in the payment platform to the moment the initiator receives the callback with the payment result. A payment is automatically declined, if its waiting time exceeds the threshold time. For individual setting of the threshold time limit, contact ECommPay technical support.

Processing scenarios

In the DOKU Wallet method, purchases and payouts follow different processing procedures. To perform a purchase operation, you need to redirect customer to the DOKU Wallet payment form, while to initiate a payout, you need to notify customer by using merchant's web service.

Figure: Purchase by using Payment Page

Figure: Purchase by using Gate

Figure: Payout by using Gate

The sections that follow provide detailed information about what you need to perform payments and how you can analyse the information on payments and operations.

Purchase by using Payment Page

General information

In the DOKU Wallet method, when processing a purchase by using Payment Page, the merchant web service is required to send a request with all the required parameters and signature to the ECommPay URL and get the callback with the payment result from the payment platform. When opening Payment Page, you can either allow your customer to select the DOKU Wallet method from the list of other payment methods on Payment Page or have Payment Page opened with the DOKU Wallet method selected. For more information about preselecting payment methods, see Preselecting payment method.

The following diagram provides the detailed picture of the payment processing procedure.

Figure: Purchase sequence when using Payment Page

  1. Customer initiates purchase by using the web service.
  2. The merchant web service sends to the specified ECommPay URL the purchase request for processing the purchase by using Payment Page.
  3. The payment platform receives the request for processing the purchase by using Payment Page.
  4. The payment platform performs the initial request processing that involves validation of the required parameters and signature.
  5. Requested Payment Page is generated into the ECommPay payment platform as specified in the project settings and the request parameters.
  6. Payment Page is displayed to the customer.
  7. The customer selects the DOKU Wallet method from the list of other payment methods and agrees to use the method (or accepts the method already selected on Payment Page and agrees).
  8. The payment platform receives the purchase request for payment processing in the DOKU Wallet service.
  9. The payment platform performs the internal purchase request processing and sends it to the DOKU Wallet service.
  10. The purchase request is processed in the DOKU Wallet service.
  11. The DOKU Wallet service generates the data for redirecting the customer to the DOKU Wallet payment form and sends it to the payment platform.
  12. The payment platform sends to Payment Page the data for redirecting the customer to the DOKU Wallet payment form.
  13. The customer is redirected to the DOKU Wallet payment form.
  14. The customer completes all the payment steps required by the DOKU Wallet purchase method.
  15. The payment is processed in the DOKU Wallet service.
  16. The payment result information is displayed to the customer on the DOKU Wallet payment form. The customer initiates redirection to the result waiting page on Payment Page.
  17. The DOKU Wallet service sends the payment result notification to the payment platform.
  18. The payment platform sends the callback to the web service.
  19. The payment platform sends payment results to Payment Page.
  20. A page with the payment result information is displayed to the customer.

The sections that follow discuss in more details the request format and the Payment Page parameters to use in the DOKU Wallet payment method and provide the information on the format of callbacks with payment results. For the general information on how to use the API, see Payment Page API Description.

Request format

There are several things you need to consider when using the DOKU Wallet method:

  1. You must provide values for the basic minimum of parameters. Listed below are the parameters that are mandatory for any payment method:
    • customer_id—the unique ID of the customer within your project
    • project_id—the project ID obtained from ECommPay
    • payment_id—payment ID unique within the project
    • payment_amount—payment amount in minor units
    • payment_currency—payment currency in ISO-4217 alpha-3 format
  2. It is recommended to specify the name and e-mail address of the user in the customer_first_name and customer_email additional parameters. If the request is missing the parameters, on Payment Page the additional fields are displaying to the customer to input missing data. For more details about clarification, see Submission of additional payment information.
  3. If you need to have Payment Page displayed with the DOKU Wallet method selected, set the force_payment_method parameter to doku.
  4. If required, you can also add any other additional parameters Payment Page supports.
  5. After you specify all the parameters you need, you must create the signature for the request. For instructions on how to sign a payment request, see Signature generation and verification.

Thus, a correct payment request in the DOKU Wallet method must include project, customer and payment IDs, amount and currency of a payment in the appropriate currency, first name and email of a customer, and the signature, as shown in the following example:

EPayWidget.run(
    { payment_id: 'ID_183', 
      payment_amount: 1000000, 
      payment_currency: 'IDR', 
      project_id: 238,
      customer_id: '123',
      customer_first_name: 'Hasan',
      customer_email: 'Prasetyo@mail.com',
      signature: "hlhydUV+SmGJYhm6G47NknsqVx2TdMZrnJ9V5Ly
                      O5JuyamXS/BYQ1M2IUgBuVxa93HwzBbEjF9Veg=="
    }
)

For information about all parameters available in the DOKU Wallet method, see Parameters to pass to Payment Page.

Callback format

In the DOKU Wallet method, the callbacks that deliver purchase results use the standard format described in Callbacks.

The following is the example of a callback with an information about successful 1,000.00 IDR purchase made in the 238 project by using the 1189632633 DOKU Wallet e-wallet.

Figure: Example of a successful purchase callback

{
        "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": "026b9dbadeb438abe796132c1db963c9650424fe-a729ea898
                                    99e9ae460d7a86c9667edc9b11eb994",
            "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/D1zXj84lUZVfpbWZol9JAZLnUZoPJKPXRbOqBUpxxa/hOKm2
                            P8XOqydoyeIi7KdqrcxLFd3GxgPgUzIDg=="
    }

The following example of callback is for a payment rejected due to amount or frequency limitation.

Figure: Example of a declined purchase callback

{
        "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": "b12c7232b016305896e2c73d47956b562e131640-44
                                    4c4b88f5f7468d191c0a8ac67b74dd2bc05ac9",
            "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/DG892c1vYILNYttNDkBQJAfC87oDMeySCJ8
                                KQ/CiU02oQvEZUsNbEVDN9uuQTagdL6SYe5iOzSA=="
    }

Related topics

The following topics might be useful when implementing payments by using Payment Page:

Purchase by using Gate

General information

In the DOKU Wallet method, when processing a purchase by using Gate, the merchant web service is required to do the following:

  1. Send a request with all the required parameters and signature to the ECommPay URL.
  2. Perform redirecting customer to the DOKU Wallet payment form.
  3. Get the callback with the payment result from the payment platform.

The following diagram provides the detailed picture of the payment processing procedure.

Figure: Purchase sequence when using Gate

  1. Customer initiates purchase on the merchant web service by using the DOKU Wallet method.
  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 for processing the purchase by using Gate.
  4. The payment platform performs the initial request processing that includes validation of the required parameters and signature.
  5. The payment platform sends to the web service response with request receipt confirmation and correctness check result. For more information about the response, see Response format.
  6. The payment platform performs the internal payment request processing and sends it to the DOKU Wallet service.
  7. The purchase request is processed in the DOKU Wallet service.
  8. The DOKU Wallet service generates the data for redirecting the customer to the DOKU Wallet form and sends it to the payment platform.
  9. The payment platform sends to the web service the callback that delivers the data for redirecting customer to the DOKU Wallet form.
  10. The customer is redirected to the DOKU Wallet payment form.
  11. The customer completes all the payment steps required by the DOKU Wallet method.
  12. The payment is processed in the DOKU Wallet service.
  13. The payment result information is displayed to the customer on the DOKU Wallet payment form. The customer initiates redirection to the result waiting page on Payment Page.
  14. The DOKU Wallet service sends the payment result notification to the payment platform.
  15. The payment platform sends the callback to the web service.
  16. The customer receives the payment result from the web service.

The sections that follow discuss in more details the request format and the Gate parameters to use in the DOKU Wallet method and provide the information about formats of the data for redirecting customers and the information about the format of callbacks with payment results. For the general information on how to use the API, see API Description.

Request format

There are several things you must consider when using purchase requests in the DOKU Wallet method:

  1. You perform purchases by sending the /v2/payment/wallet/doku/sale request by using POST (HTTP) method. This is an e-wallet payments request group: /v2/payment/wallet/{payment_method}/sale.
  2. The following objects and parameters must be specified in any request:
    • Object general—general request identification information:
      • project_id—the project ID obtained from ECommPay
      • payment_id—payment ID unique within the project
      • signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification.
    • Object customer—customer information:
      • id—the unique ID of the customer within your project
      • ip_address—customer IP address
    • Object payment—payment information:
      • amount—purchase amount in minor units
      • currency—purchase currency in ISO-4217 alpha-3 format
  3. It is recommended to specify the name and e-mail address of the user in the customer_first_name and customer_email additional parameters. If the request is missing the parameters, the list of parameters is sent in the clarification callback. For more details, see Additional payment information submission.
  4. If required, you can also add any other additional parameters Gate supports.

Thus, a correct payment request in the DOKU Wallet method must include project, customer and payment IDs, signature, IP-address, first name and email of the customer, amount and currency of the purchase, as shown in the following example:

{
    "general": {
    "project_id": 125,
    "payment_id": "ID_184",
    "signature": "PJkV8ej\/UG0Di8hTng6JvC7vQsaC6tajQVVLhNN5e7cV+VHq3L
                        wY3T\/pOMeSaRfBaNIipTv+AWoXW\/9MTO8yJA=="
  },
  "customer": {
    "id": "123",
    "ip_address": "114.124.147.207",
    "first_name": "Riza",
    "email": "riza@mail.com"
    },
  "payment": {
    "amount": 100,
    "currency": "IDR"
  }
}

Formats of the customer redirection data

In the DOKU Wallet method, when redirecting customer to the DOKU Wallet payment form, it is required to do the following:

  1. Get a callback with the redirect_data object from the payment platform.
  2. Generate POST request in the format x-www-form-urlencoded by using parameter values contained in the body object.
  3. Open the full redirect URL by using POST method.

The following example of callback code contains the request method, required parameters, and URL.

Figure: Example of customer redirection data

"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@mail.com",
                "BASKET": "Sale,10000.00,1,10000.00",
                "PAYMENTCHANNEL": "41"
            },
            "encrypted": [],
            "url": "https://pay.doku.com/Suite/Receive"
        }

Format of callback with purchase results

In the DOKU Wallet method, the callbacks that deliver purchase results use the standard format described in Callbacks.

The following is the example of a callback with an information about successful 1,000.00 IDR purchase made in the 238 project by using the 1189632633 DOKU Wallet e-wallet.

Figure: Example of a successful purchase callback

{
        "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": "026b9dbadeb438abe796132c1db963c9650424fe-a729ea898
                                    99e9ae460d7a86c9667edc9b11eb994",
            "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/D1zXj84lUZVfpbWZol9JAZLnUZoPJKPXRbOqBUpxxa/hOKm2
                            P8XOqydoyeIi7KdqrcxLFd3GxgPgUzIDg=="
    }

The following example of callback is for a payment rejected due to amount or frequency limitation.

Figure: Example of a declined purchase callback

{
        "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": "b12c7232b016305896e2c73d47956b562e131640-44
                                    4c4b88f5f7468d191c0a8ac67b74dd2bc05ac9",
            "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/DG892c1vYILNYttNDkBQJAfC87oDMeySCJ8
                                KQ/CiU02oQvEZUsNbEVDN9uuQTagdL6SYe5iOzSA=="
    }

Related topics

The following topics might be useful when implementing payments by using Gate:

Payout by using Gate

General information

In the DOKU Wallet method, when processing a payout by using Gate, the merchant web service is required to send a request with all the required parameters and signature to the ECommPay URL and get the callback with the payment result from the payment platform.

The following diagrams provide the detailed picture of the payment processing procedure.

Figure: Payout sequence when using Gate

  1. Customer initiates payout.
  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 for processing the payout by using Gate.
  4. The payment platform performs the initial request processing that includes validation of the required parameters and signature.
  5. The payment platform sends to the web service response with request receipt confirmation and correctness check result. For more information about the response, see Response format.
  6. The payment platform performs the internal payment request processing and sends it to the DOKU Wallet service.
  7. The payment is processed in the DOKU Wallet service.
  8. The DOKU Wallet service sends the payment result notification to the payment platform.
  9. The payment platform sends the callback to the web service.
  10. The customer receives the payment result from the web service.

The sections that follow discuss in more details the request format and the Gate parameters to use in the DOKU Wallet method and provide the information about the format of callbacks with payment results. For the general information on how to use the API, see API Description.

Request format

There are several things you must consider when using payout requests in the DOKU Wallet method:

  1. You perform purchases by sending the /v2/payment/wallet/doku/payout request by using POST (HTTP) method. This is an e-wallet payments request group /v2/payment/wallet/{payment_method}/payout.
  2. The following objects and parameters must be specified in any request:
    • Object general—general request identification information:
      • project_id—the project ID obtained from ECommPay
      • payment_id—payment ID unique within the project
      • signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification.
    • Object customer—customer information:
      • id—the ID of the customer within merchant project
      • first_name—first name
      • last_name—last name
      • ip_address—IP address
      • phone—phone
      • city—city
      • day_of_birth—day of birth
      • country—country in the ISO 3166-1 (alpha-2) format,
      • Object identify—customer identity document information:
        • doc_number—document number
        • doc_type—document type
        • doc_issue_country—an ISO 3166-1 (alpha-2) code of country that issued the document
    • Object account—customer e-wallet information:
      • number—customer e-wallet number
    • Object payment—payout information:
      • amount—payout amount
      • currency—payout currency in the ISO-4217 alpha-3 format
  3. If required, you can also add any other additional parameters Gate supports.

The following example provides a correct payment request with all mandatory parameters:

Figure: Payout request example

{
    "general": {
    "project_id": 2853,
    "payment_id": "test-002",
    "signature": "M1vT4q9c8hA8xCjEwGFSANwbxHShy2TSOI/4sKFk
                        B+9XAaq7vt3/Jkn+aJmGA4jH6bgBOp8DTf8d/XdoV+vd7Q=="
  },
  "customer": {
    "id": "payoutTest",
    "first_name": "Suharto",
    "last_name": "Yudhoyono",
    "ip_address": "114.124.147.206",
    "phone": "02112345678",
    "city": "Jakarta",
    "day_of_birth": "21-09-1983",
    "country": "ID",
    "identify": {
      "doc_number": "2101086512740000",
      "doc_type": "none",
      "doc_issue_country": "ID"
    }
  },
  "account": {
    "number": "654654654"
  },
  "payment": {
    "amount": 10000,
    "currency": "IDR",
    "description": "PayoutTest.49855500 1538564115"
  }
}

Callback format

In the DOKU Wallet method, the callbacks that deliver payout results use the standard format described in Callbacks.

The following is the example of a callback with the information about a successful 1.00 IDR payout made to DOKU wallet 1579000479 of the 1 customer in the 580 project.

Figure: Example of a successful payout callback

{
        "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": "798454444474"
        },
        "operation": {
            "id": 31771000001833,
            "type": "payout",
            "status": "success",
            "date": "2019-05-07T11:38:24+0000",
            "created_date": "2019-05-07T11:38:14+0000",
            "request_id": "a6ce8cf365af0c33a3d7744bb48b6aac20ecfed
                            8-ea53b2d5ff4ee3dead9dcb45e8780793377c9460",
            "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": "8xwuyUSnpfu4YVMH1qF8Zk2ILnhu21/oE4d1Ue
                7ZlLVdKkMHkUKH51zo76fAVQAiovMrU3JUTyF8UjZ8qTouKQ=="
    }

The following example of callback is for a payout rejected due to amount or frequency limitation.

Figure: Example of a declined payout callback

{
        "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": "b12c7232b016305896e2c73d47956b562e131640-44
                                    4c4b88f5f7468d191c0a8ac67b74dd2bc05ac9",
            "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/DG892c1vYILNYttNDkBQJAfC87oDMeySCJ8
                                KQ/CiU02oQvEZUsNbEVDN9uuQTagdL6SYe5iOzSA=="
    }

Related topics

The following topics might be useful when implementing payments through Gate:

Testing

General information

For the DOKU Wallet method the testing of purchases by using Payment Page and Gate, payouts by using Gate.

Testing can be performed within a test project, to enable and disable the testing availability, contact ECommPay technical support via support@ecommpay.com.

When performing a test payment, take into account that you must specify the identifier of the test project in the requests, the currency can be only IDR, and the interfaces of the payment forms emulator of Payment Page and DOKU Wallet differ from the production environment.

Test payments statuses

When testing purchases, the final payment status is determined by the amount specified in the request:

  • decline status with 40000 or 40400 amount
  • success status with any other amount

When testing payouts, the final payment status is determined by the amount specified in the request:

  • decline status with 40000 or 40400 amount
  • success status with any other amount

Purchases by using Payment Page

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. Accept a callback with information about the payment result.

The full information about purchase process by using DOKU Wallet through Payment Page is provided in the section Purchase by using Payment Page.

Purchases by using Gate

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

  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. Accept a callback with information about the payment result.

While testing purchases by using Gate, after clicking the Success or Decline button, by default the Payment Page result page is used for redirection. In order to change the page used for redirection (for example to a merchant page), contact ECommPay technical support via support@ecommpay.com.

The full information about purchase process by using DOKU Wallet through Gate is provided in the section Purchase by using Gate.

Payouts by using Gate

To perform a test payout by using Gate, send a correct test request to the payment platform and accept a callback with information about the payment result. The full information about payout process by using DOKU Wallet through Gate is provided in the section Payout by using Gate.

Analysis of payments results

As with other payment methods ECommPay offers, when using the DOKU Wallet method, you have several options to analyse the information about payments and operations performed by using the method—alone or in conjunction with other methods.

You can load and analyse all the necessary information in Dashboard, for instance you can use the analytic panels on the Analytics tab to this end.

Also, you can export the information for further analysis by using third party analytical tools. The following options are available:

  • Dashboard allows you to download reports in CSV and XLS formats—by using the tools on the Payments tab. You can perform export as a one-time download to your local computer or have payment data regularly exported and delivered to email addresses you specify.
  • Data API allows you to have payment information exported in JSON format and delivered to a URL you specify. The payment information is exported by using the /operations/get queries.

If you have any further questions regarding payment data analysis, contact ECommPay technical support.