ATM & Bank Transfer in Indonesia (Virtual Accounts)

Overview

ATM & Bank Transfer in Indonesia (Virtual Accounts) is the most popular Indonesian alternative payment method that requires the customer to transfer funds to virtual bank account via a banking mobile application, internet banking or physically via ATM. A Virtual Account (VA), 16 digit payment code, is an account created and assigned to each of your paying clients automatically in response to the payment request so that your business would be able to differentiate each payment from the payment source. ECommPay creates a virtual bank account on an interbank network that is unique to the payment. The payments made to the different Virtual Accounts will be automatically aggregated into the merchant's master account.

The customer uses provided information to do a bank transfer into the virtual account before the account expires. A client can perform the bank transfer in the following ways:

  • Physically going to the ATM
  • Mobile banking through bank applications
  • Internet banking

Most (80 %) of transactions in Indonesia occur via bank transfer. ECommPay offers payment processing with major banks in Indonesia—Mandiri, Permata, Danamon, CIMB.

Purchases can be processed by using Payment Page and Gate.

Purchases are processed by using two channels. Refer to your ECommPay key account manager for detail regarding the applicable processing channel.

General information

Payment method type bank transfers
Countries and regions ID
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
  • it is possible to specify additional parameters to preselect the payment method and bank on Payment Page
  • Safari browser may not support the redirection to the provider service. For more information refer to the ECommPay key account manager
Onboarding and access fee refer to your ECommPay key account manager

Interaction diagram

Payment processing by using the ATM & Bank Transfer in Indonesia (Virtual Accounts) payment method requires merchant's web service, one of the interfaces and the payment platform of ECommPay, as well the provider service.



Operations support

  Interfaces Amounts, IDR
Payment Page CMS Plug-ins Gate Dashboard (Old Dashboard) Minimum Maximum
Purchases + + * *

* For the most recent amount limits, contact your ECommPay Key Account Manager.

Processing scenarios

In the ATM & Bank Transfer in Indonesia (Virtual Accounts) method, to perform a purchase operation, you need to redirect a customer to the provider service.

Figure: Purchase by using Payment Page



Figure: Purchase by using Gate



Supported banks

Payments through the ATM & Bank Transfer in Indonesia (Virtual Accounts) method are carried out through banks that are supported by this method. Banks have their own identifiers, which are used to initiate purchases by using Gate, and to display banks on Payment Page when choosing a payment method.

The table below provides information on these banks for informational purposes, it may change without additional notice; for the most recent list of supported banks, contact your ECommPay Key Account Manager or POST the /v2/info/banks/{payment_method}/{operationType}/list request using Gate API: /v2/info/banks/indonesia/sale/list (for the first purchase processing channel) and /v2/info/banks/indonesia-va/sale/list (for the second purchase processing channel).

The request must contain the project and payment IDs, signature, currency, and payment amount, as shown in the example. It is important to specify real payment data, but if the payment has not yet been generated, you can specify a random value for the payment ID in the request.

Figure: Example of requesting a list of banks

{
  "general": {
    "project_id": 200,
    "payment_id": "ORDER_155860015",
    "signature": "K6jllym+PtObocZtr345st...=="
  },
  "payment": {
    "amount": 1000,
    "currency": "IDR"
  }
}
Table 1. Channel 1. List of banks
Bank ID
Bank Permata VA 433
Bank Mandiri VA 434
Bank Danamon VA 435
Bank CIMB VA 436
Table 2. Channel 2. List of banks
Bank ID
Permata Virtual Account 2961
Mandiri Virtual Account 2951
Maybank Virtual Account 2941
BNI Virtual Account 2931

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 ATM & Bank Transfer in Indonesia (Virtual Accounts) method, to perform a purchase by using Payment Page, the merchant web service should 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 ATM & Bank Transfer in Indonesia (Virtual Accounts) methods from the list of other payment methods on Payment Page or have Payment Page opened with the ATM & Bank Transfer in Indonesia (Virtual Accounts) method selected. For more information about preselecting payment methods, see in Preselecting payment method.

Figure: Purchase by using Payment Page



Figure: Purchase sequence by using Payment Page

  1. A customer initiates a purchase on the merchant's web service.
  2. The web service sends the request for Payment Page opening to the specified ECommPay URL.
  3. The request for opening is redirected to the payment platform.
  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 one of the banks from ATM & Bank Transfer in Indonesia (Virtual Accounts) group.
  8. The payment platform receives the purchase request for payment processing.
  9. The payment platform performs the internal purchase request processing and sends it to the provider service.
  10. The purchase request is processed on the provider side.
  11. The provider service generates the data for redirecting the customer to its website form and sends it to the payment platform.
  12. The payment platform sends the customer redirection data to Payment Page.
  13. The customer is redirected to the provider website, where a 16 digit code and payment instructions are displayed to the customer.
  14. In accordance with the payment instructions the customer enters the code on either the bank website, bank mobile application or the ATM, and confirms the purchase.
  15. The payment is processed on the provider side.
  16. The provider service sends the result notification to the payment platform.
  17. The payment platform sends a callback with the payment result to the web service.
  18. The payment platform sends the result to Payment Page.
  19. A page with the payment result information is displayed to the customer on Payment Page.

The sections that follow provide details the request format and the Payment Page parameters to use in the ATM & Bank Transfer in Indonesia (Virtual Accounts) 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.

Channel 1. Request format

There are several things you must consider when performing a purchase through the ATM & Bank Transfer in Indonesia (Virtual Accounts) method:

  1. You must provide values for the basic minimum of parameters. Listed below are the parameters that are mandatory for any payment method:
    • project_id—the project ID obtained from ECommPay
    • payment_id—payment ID unique within the project
    • payment_currency—payment currency in ISO-4217 alpha-3 format
    • payment_amount—purchase amount in minor currency units
    • customer_id—the unique ID of the customer within your project
  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, Submission of additional payment information.
  3. By default Payment Page is opened in English language. To change the language of Payment Page and payment page of the ATM & Bank Transfer in Indonesia (Virtual Accounts) service pass language code in the language_code parameter in the request for opening. The list of supported languages for the ATM & Bank Transfer in Indonesia (Virtual Accounts) payment method is recommended to check with the ECommPay key account manager. For the informational purposes the list of supported languages and their codes are provided below.
    • en—English
    • id—Indonesian
    • ms—Malay
    • my—Burmese
    • th—Thai
    • vi—Vietnamese
    • zh—Chinese
  4. You can customise the selecting payment method page on Payment Page.

    By default the supported banks are grouped in one Online Indonesian banks button on Payment Page, so the selection of a bank is carried out in two steps. First, the ATM & Bank Transfer in Indonesia (Virtual Accounts) method is chosen among others, and then the bank is selected on the next page with the list of banks.

    There are several options for displaying the page with the selecting of payment method on Payment Page:

    • To display grouped in one Online Indonesian banks button on Payment Page in the list of payment methods.
    • To display each bank of the ATM & Bank Transfer in Indonesia (Virtual Accounts) group with a separate buttons, pass split_banks=true in the request for opening in the payment_methods_options string.
      payment_methods_options={"online_indonesian_banks": {"split_banks": true}}
      
    • To preselect ATM & Bank Transfer in Indonesia (Virtual Accounts) as the payment method on Payment Page for customers, pass the code oniline-indonesia-banks in the force_payment_method parameter in the request for opening. The list of the banks from ATM & Bank Transfer in Indonesia (Virtual Accounts) group is displayed to a customer on Payment Page bypassing the page with the payment method selection.
    • To display a button of a specific bank (one or several) from ATM & Bank Transfer in Indonesia (Virtual Accounts) group on Payment Page in the list of payment methods, pass the bank identifier in the banks_id parameter. If it is necessary to display several banks from a group, pass the identifiers of these banks separated by a comma with a space.
      payment_methods_options={"online_indonesian_banks": {"split_banks": true, "banks_id": [433, 434]}}

      Here is the example of a request for opening Payment Page in the Indonesian language with preselecting the Mandiri bank.

      Figure: Example of the request for with preselected payment method and bank

          { payment_id: 'X03936', 
            payment_amount: 20000000, 
            payment_currency: 'IDR', 
            project_id: 120,
            customer_id: '1',
            language_code: 'id',
            force_payment_method: 'oniline-indonesia-banks',
            payment_methods_options={"online_indonesian_banks": {"banks_id": [434]}},
            signature: "kUi2x9dKHAVNU0FYlSCQ9vySO\/RLCvhtT4DqtVUkDJrOcZzUCwX6R\/ekpZhkIQg=="
          }
  5. If required, you can also add any other additional parameters Payment Page supports. For information about all parameters available in the ATM & Bank Transfer in Indonesia (Virtual Accounts) method, see Payment Page invocation parameters.
  6. 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 ATM & Bank Transfer in Indonesia (Virtual Accounts) method must include project, customer and payment IDs, the currency and the amount of a payment, signature and customer data, as shown in the following example:

    { payment_id: 'X03936', 
      payment_amount: 20000000, 
      payment_currency: 'IDR', 
      project_id: 123,
      customer_id: '123',
      customer_first_name: 'Hasan',
      customer_email: 'hasan@example.com',
      signature: "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KURLCvhtT4DqtOcZzUCwX6R\/ekpZhkIQg=="
    }

Channel 2. Request format

There are several things you must consider when performing a purchase through the ATM & Bank Transfer in Indonesia (Virtual Accounts) method:

  1. You must provide values for the basic minimum of parameters. Listed below are the parameters that are mandatory for any payment method:
    • project_id—the project ID obtained from ECommPay
    • payment_id—payment ID unique within the project
    • payment_currency—payment currency in ISO-4217 alpha-3 format
    • payment_amount—purchase amount in minor currency units
    • customer_id—the unique ID of the customer within your project
  2. You can customise the selecting payment method page on Payment Page.

    By default the supported banks are grouped in one ATM transfer Indonesia button on Payment Page, so the selection of a bank is carried out in two steps. First, the ATM & Bank Transfer in Indonesia (Virtual Accounts) method is chosen among others, and then the bank is selected on the next page with the list of banks.

    There are several options for displaying the page with the selecting of payment method on Payment Page:

    • To display grouped in one ATM transfer Indonesia button on Payment Page in the list of payment methods.
    • To display each bank of the ATM & Bank Transfer in Indonesia (Virtual Accounts) group with a separate buttons, pass split_banks=true in the request for opening in the payment_methods_options string.
      payment_methods_options={"indonesia_va": {"split_banks": true}}
      
    • To preselect ATM & Bank Transfer in Indonesia (Virtual Accounts) as the payment method on Payment Page for customers, pass the code oniline-indonesia-banks in the force_payment_method parameter in the request for opening. The list of the banks from ATM & Bank Transfer in Indonesia (Virtual Accounts) group is displayed to a customer on Payment Page bypassing the page with the payment method selection.
    • To display a button of a specific bank (one or several) from ATM & Bank Transfer in Indonesia (Virtual Accounts) group on Payment Page in the list of payment methods, pass the bank identifier in the banks_id parameter. If it is necessary to display several banks from a group, pass the identifiers of these banks separated by a comma with a space.
      payment_methods_options={"indonesia_va": {"split_banks": true, "banks_id": [2961, 2951]}}

      Here is the example of a request for opening Payment Page in the Indonesian language with preselecting the Mandiri bank.

      Figure: Example of the request for with preselected payment method and bank

      EPayWidget.run(
          { payment_id: 'X03936', 
            payment_amount: 20000000, 
            payment_currency: 'IDR', 
            project_id: 120,
            customer_id: '1',
            force_payment_method: 'indonesian-va',
            payment_methods_options={"indonesia_va": {"banks_id": [2961]}},
            signature: "kUi2x9dKHAVNU0FY...vySO\/RLCvhtT4DqtVUkDJrOcZzUCwX6R\/ekpZhkIQg=="
          }
      )
  3. If required, you can also add any other additional parameters Payment Page supports. For information about all parameters available in the ATM & Bank Transfer in Indonesia (Virtual Accounts) method, see Payment Page invocation parameters.
  4. 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 ATM & Bank Transfer in Indonesia (Virtual Accounts) method must include project, customer and payment IDs, the currency and the amount of a payment, as well as signature, as shown in the following example:

    { payment_id: 'X03936', 
      payment_amount: 20000000, 
      payment_currency: 'IDR', 
      project_id: 123,
      customer_id: 'customer1',
      signature: "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KURLCvhtT4DqtOcZzUCwX6R\/ekpZhkIQg=="
    }

Callback format

The standard format for callbacks is used to deliver purchase results from ATM & Bank Transfer in Indonesia (Virtual Accounts). For more information, see Callbacks.

The following is the example of a callback with an information about successful 200,000.00 IDR purchase made for account 8856113600001045 in the 200 project.

Figure: Example of a successful purchase callback

 {
        "project_id": 200,
        "payment": {
            "id": "9770802",
            "type": "purchase",
            "status": "success",
            "date": "2020-02-22T22:44:46+0000",
            "method": "Indonesian banks",
            "sum": {
                "amount": 20000000,
                "currency": "IDR"
            },
            "description": "test"
        },
        "account": {
            "number": "8856113600001045"
        },
        "customer": {
            "id": "1"
        },
        "operation": {
            "id": 52084000029401,
            "type": "sale",
            "status": "success",
            "date": "2020-02-22T22:44:46+0000",
            "created_date": "2020-02-22T17:30:42+0000",
            "request_id": "59b48b4c2d0a2b6a-00052085",
            "sum_initial": {
                "amount": 20000000,
                "currency": "IDR"
            },
            "sum_converted": {
                "amount": 20000000,
                "currency": "IDR"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 1164,
                "payment_id": "644206",
                "auth_code": "",
                "date": "2020-02-22T22:44:45+0000"
            }
        },
        "signature": "Hekd6+86S592dGuYCHNLADZ8LaBC5/JSKObUxTvkUuCZL4phAiFQA=="
    }

Here is the example of a callback for a purchase rejected due to minimum amount limit exceeding.

Figure: Example of a declined purchase callback

{
        "project_id": 200,
        "payment": {
            "id": "9770802",
            "type": "purchase",
            "status": "decline",
            "date": "2020-02-22T22:44:46+0000",
            "method": "Indonesian banks",
            "sum": {
                "amount": 1000,
                "currency": "IDR"
            },
            "description": "test"
        },
        "account": {
            "number": "8856113600001046"
        },
        "customer": {
            "id": "1"
        },
        "operation": {
            "id": 52084000029401,
            "type": "sale",
            "status": "decline",
            "date": "2020-02-22T22:44:46+0000",
            "created_date": "2020-02-22T17:30:42+0000",
            "request_id": "59b48b4c2d0a2b6a-00052085",
            "sum_initial": {
                "amount": 1000,
                "currency": "IDR"
            },
            "sum_converted": {
                "amount": 1000,
                "currency": "IDR"
            },
            "code": "20101",
            "message": "Decline due to amount or frequency limit",
        },
        "signature": "Hekd6+86S592dGuYCHNLADZ8LaBC5/JSKObUxTvkUuCZL4phAiFQA=="
    }

Related topics

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

Purchase by using Gate

General information

In the ATM & Bank Transfer in Indonesia (Virtual Accounts) 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. Redirect the customer to the page with a payment instructions.
  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 by using Gate



Figure: Purchase sequence by using Gate

  1. A customer initiates a purchase through the ATM & Bank Transfer in Indonesia (Virtual Accounts) method on the merchant's web service side.
  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 from Gate.
  4. The payment platform performs the initial request processing that includes validation of the required parameters and signature.
  5. The payment platform sends the response with request receipt confirmation and correctness check result to the web service. For more information, see Response format.
  6. The payment platform performs the internal payment request processing and redirects the request to the provider service.
  7. The request is processed on the provider side.
  8. The provider service sends the data for redirecting the customer to the provider website 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 provider website, where a 16 digit code and payment instructions are displayed to the customer.
  11. In accordance with the payment instructions the customer enters the code on either the bank website, bank mobile application or the ATM, and confirms the purchase.
  12. The payment is processed on the provider side.
  13. The provider service sends the payment result notification to the payment platform.
  14. The ECommPay payment platform sends a callback to the web service.
  15. The customer receives the payment result information from the web service.

The sections that follow discuss in more details the request format and the Gate parameters to use in the ATM & Bank Transfer in Indonesia (Virtual Accounts) payment method and provide the information about formats of the data for redirecting customers and the information about the format of callbacks with payment results. The general information about working with API see in the API Description section.

Channel 1. Request format

There are several things you must consider when using purchase requests in the ATM & Bank Transfer in Indonesia (Virtual Accounts) method:

  1. You perform purchase by sending the /v2/payment/banks/indonesia/sale request by using POST (HTTP) method, which belongs to the following request group: /v2/payment/banks/{payment_method}/sale
  2. The following objects and parameters must be specified in the request:
    • Object general—general purchase information:
      • project_id—the project ID obtained from ECommPay
      • payment_id—the 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—purchase information:
      • amount—purchase amount in minor currency units
      • currency—purchase currency in ISO-4217 alpha-3 format
    • Object account—customer account information:
      • bank_id—bank identifier
  3. It is recommended to specify the 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.

    There is the list of recommended objects and parameters:

    • Object customer—customer information:
      • first_name—first name
      • email—email
  4. If required, you can also add any other additional parameters Gate supports.

Thus, a correct payment request through the ATM & Bank Transfer in Indonesia (Virtual Accounts) method must include project, payment, customer and bank IDs, customer data, signature, currency and amount of the purchase, URL for customer redirection, as shown in the following example:

Figure: Purchase request example

{
    "general": {
      "project_id": 2990,
      "payment_id": payment_id,
      "signature": "PJkV8ej\/UG0Di8hTng6JvC7vQsaC6tajQVVfBaNIipTv+AWoXW\/9MTO8yJA=="
    },
    "payment": {
      "amount": 35000000,
      "currency": "IDR"
      },
    "customer": {
      "id": "123",
      "first_name": "Hasan",
      "email": "hasan@example.com",
      "ip_address": "1.1.1.1"
    },
    "account":{
      "bank_id": 433
    }
 }

Channel 2. Request format

There are several things you must consider when using purchase requests in the ATM & Bank Transfer in Indonesia (Virtual Accounts) method:

  1. You perform purchase by sending the /v2/payment/banks/indonesia-va/sale request by using POST (HTTP) method, which belongs to the following request group: /v2/payment/banks/{payment_method}/sale
  2. The following objects and parameters must be specified in the request:
    • Object general—general purchase information:
      • project_id—the project ID obtained from ECommPay
      • payment_id—the 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—purchase information:
      • amount—purchase amount in minor currency units
      • currency—purchase currency in ISO-4217 alpha-3 format
    • Object account—customer account information:
      • bank_id—bank identifier
  3. If required, you can also add any other additional parameters Gate supports.

Thus, a correct payment request through the ATM & Bank Transfer in Indonesia (Virtual Accounts) method must include project, payment, customer and bank IDs, customer data, signature, currency and amount of the purchase, as shown in the following example:

Figure: Purchase request example

{
    "general": {
      "project_id": 2990,
      "payment_id": payment_id,
      "signature": "PJkV8ej\/UG0Di8hTng6JvC7vQsaC6tajQVVfBaNIipTv+AWoXW\/9MTO8yJA=="
    },
    "payment": {
      "amount": 35000000,
      "currency": "IDR"
      },
    "customer": {
      "id": "12345",
      "ip_address": "1.1.1.1"
    },
    "account":{
      "bank_id": 2961
    }
 }

Formats of the customer redirection data

  • Get a callback with the redirect_data object from the payment platform.
  • Generate POST request in the format x-www-form-urlencoded by using parameter values contained in the body object.
  • Open the redirect URL by using POST (HTTP) method.

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

"redirect_data": {
                    "body": {
                        "MALLID": 4038,
                        "CHAINMERCHANT": "NA",
                        "AMOUNT": "20000.00",
                        "PURCHASEAMOUNT": "20000.00",
                        "TRANSIDMERCHANT": 16617000002000,
                        "PAYMENTTYPE": "SALE",
                        "WORDS": "4d1a2cdbc8a1fe972c3444cfeafa90",
                        "REQUESTDATETIME": "20191313706435",
                        "CURRENCY": "360",
                        "PURCHASECURRENCY": "360",
                        "SESSIONID": "6ac463c1",
                        "NAME": "HASAN",
                        "EMAIL": "test@example.com",
                        "BASKET": "Sale,20000.00,1,20000.00",
                        "PAYMENTCHANNEL": "35"
                    },
                    "method": "POST",
                    "url": "https://example.com/Suite/Receive"
                },

Callback format

In the ATM & Bank Transfer in Indonesia (Virtual Accounts) 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 200,000.00 IDR purchase made for account 8856113600001045 in the 200 project.

Figure: Example of a successful purchase callback

 {
        "project_id": 200,
        "payment": {
            "id": "9770802",
            "type": "purchase",
            "status": "success",
            "date": "2020-02-22T22:44:46+0000",
            "method": "Indonesian banks",
            "sum": {
                "amount": 20000000,
                "currency": "IDR"
            },
            "description": "test"
        },
        "account": {
            "number": "8856113600001045"
        },
        "customer": {
            "id": "1"
        },
        "operation": {
            "id": 52084000029401,
            "type": "sale",
            "status": "success",
            "date": "2020-02-22T22:44:46+0000",
            "created_date": "2020-02-22T17:30:42+0000",
            "request_id": "59b48b4c2d0a2b6a-00052085",
            "sum_initial": {
                "amount": 20000000,
                "currency": "IDR"
            },
            "sum_converted": {
                "amount": 20000000,
                "currency": "IDR"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 1164,
                "payment_id": "644206",
                "auth_code": "",
                "date": "2020-02-22T22:44:45+0000"
            }
        },
        "signature": "Hekd6+86S592dGuYCHNLADZ8LaBC5/JSKObUxTvkUuCZL4phAiFQA=="
    }

The following is the example of a callback for a purchase rejected due to the exceeded amount limit.

Figure: Example of a declined purchase callback

{
        "project_id": 200,
        "payment": {
            "id": "9770802",
            "type": "purchase",
            "status": "decline",
            "date": "2020-02-22T22:44:46+0000",
            "method": "Indonesian banks",
            "sum": {
                "amount": 1000,
                "currency": "IDR"
            },
            "description": "test"
        },
        "account": {
            "number": "8856113600001046"
        },
        "customer": {
            "id": "1"
        },
        "operation": {
            "id": 52084000029401,
            "type": "sale",
            "status": "decline",
            "date": "2020-02-22T22:44:46+0000",
            "created_date": "2020-02-22T17:30:42+0000",
            "request_id": "59b48b4c2d0a2b6a-00052085",
            "sum_initial": {
                "amount": 1000,
                "currency": "IDR"
            },
            "sum_converted": {
                "amount": 1000,
                "currency": "IDR"
            },
            "code": "20101",
            "message": "Decline due to amount or frequency limit",
        },
        "signature": "Hekd6+86S592dGuYCHNLADZ8LaBC5/JSKObUxTvkUuCZL4phAiFQA=="
    }

Related topics

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

Analysis of payments results

As with other payment methods ECommPay offers, when using the ATM & Bank Transfer in Indonesia (Virtual Accounts) 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.