Indonesian Online Banking
Overview
Introduction
Indonesian Online Banking is a payment method which allows to process payments in Indonesian rupiahs by using bank accounts in Indonesia. This method supports purchases and payouts.
This article provides information about working with the Indonesian Online Banking method: general insights are presented in the Overview section, while information about the actions required to process payments and perform other actions is presented in the sections that follow.
General information
Payment method type | bank payments |
---|---|
Payment instruments | bank accounts |
Countries and regions | ID |
Payment currencies | IDR |
Currency conversion | on the ecommpay side |
One-time purchases | + |
Credential-on-file purchases | – |
Full refunds | – |
Partial refunds | – |
Payouts | + |
Chargebacks | – |
Notes |
|
Onboarding and access fee | refer to your ecommpay key account manager; more information is available in the ecommpay shop |
Interaction diagram
Payment processing by using the Indonesian Online Banking method involves the merchant's web service, one of ecommpay interfaces, the ecommpay payment platform, and technical facilities of the bank service.
Operations support
Various platform interfaces can be used to process payments and perform operations using the Indonesian Online Banking 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.
When working with the Indonesian Online Banking the following properties and limitations are applicable.
Amounts, IDR | Times ² | |||
---|---|---|---|---|
minimum | maximum | base | threshold | |
Purchases | 100 000.00 | 25,000 000.00 | * | * |
Payouts | 100 000.00 | 10,000 000.00 | * | * |
- Keep in mind that payment processing times depend on banks, that support purchases by using this payment method.
- The base and threshold times are defined as follows:
- The base time is the average estimated time between the moment a payment is initiated in the payment platform to the moment the payment result is sent to the web service. The base time evaluation is made on the assumption of normal operation of all technical facilities and communication channels and typical customer behaviour (if any input from the customer is required). Use the base time to estimate when to react to the absence of payment result callbacks or when to check payment status (details).
- The threshold time is the maximum possible time between the moment a payment is initiated in the payment platform to the moment the web service receives the callback with the payment result. A payment is automatically assigned the
decline
status if it wasn't processed within the threshold time. For individual customisation of the threshold time limit, contact ecommpay technical support.
Processing scenarios
To perform a purchase by using the Indonesian Online Banking method, you need to redirect customer to the Indonesian Online Banking service, while to initiate a payout, you need to notify the customer via the web service.
The customer payment scenario via Payment Page (in the basic case where the customer chooses the method and bank and is redirected from the final page of the payment form to the web service) looks like this.
General scenarios of processing purchases and payouts can be presented as follows.
At the same time, the specifics of working with the method include the necessity of selecting a bank for each payment. When Payment Page is used for payment processing, the customer usually selects a bank while already in the payment form. When Payment Page is opened with the method and bank preselected as well as when payments are initiated through Gate, the bank must be selected on the side of the web service and the identifier of this bank must be specified in requests. Possible options for bank selection when working with Payment Page are described in Purchases by using Payment Page, ways of using bank identifiers—in the next subsection, Supported banks.
At the same time, different options for selecting a bank are supported for payments by using this method; they are described in the Purchases by using Payment Page section of this article.
Supported banks
The following table lists the names and identifiers of banks supported by the Indonesian Online Banking method. Keep in mind that this list is presented for informational purposes.
Bank | ID | Purchase | Payout |
---|---|---|---|
Bank Artha Graha | 2871 | – | + |
Bank Bukopin | 549 | – | + |
Bank Central Asia | 140 | + | + |
Bank CIMB Niaga | 507 | – | + |
Bank Commonwealth | 567 | – | + |
Bank Danamon Indonesia | 398 | – | + |
Bank HSBC | 513 | – | + |
Bank Mandiri | 143 | + | + |
Bank Maspion | 2891 | – | + |
Bank MayBank Indonesia | 565 | – | + |
Bank Mega | 547 | – | + |
Bank Mestika | 2901 | – | + |
Bank Negara Indonesia | 141 | + | + |
Bank OCBC NISP | 509 | – | + |
Bank Panin | 506 | – | + |
Bank Permata | 396 | – | + |
Bank Rakyat Indonesia | 142 | + | + |
Bank Rakyat Indonesia Syariah | 545 | – | + |
Bank Sinar Mas | 2911 | – | + |
Bank Sumut | 525 | – | + |
Bank Tabungan Pensiunan Nasional /BTPN | 544 | – | + |
Bank UOB Buana Indonesia | 508 | – | + |
OCBC Indonesia | 2921 | – | + |
Since the list of available banks may change over time, it is recommended to send a POST request to the one of the following endpoints: /v2/info/banks/indonesia/sale/list
for purchases and /v2/info/banks/indonesia/payout/list
for payouts to obtain up-to-date information. These endpoints belong to the /v2/info/banks/{payment_method}/{operationType}/list group of the Gate API. The request must contain the project and payment identifiers, signature, currency code, and payment amount, as shown in the example. Specify real payment data if possible. However, random values are also allowed.
If you have any questions about working with banks supported by the Indonesian Online Banking method, refer to your ecommpay account manager.
Purchases by using Payment Page
General information
To process a purchase through Payment Page by using the Indonesian Online Banking 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.
Generally, when a customer confirms their intention to pay on the side of the web service, they are redirected to Payment Page where they select the payment method and, in the case of working with the Indonesian Online Banking method, additionally select one of the available banks. However, in some situations, other options for choosing a payment method and bank may be relevant. For example, upon opening Payment Page, you can immediately redirect the customer to the bank selection page or limit the list of supported banks for a particular payment and display only target bank selection buttons to the customer. The specific option of selecting the payment method and bank is determined depending on the parameters specified in the request for opening Payment Page (details). The following options are available:
- 1—when the payment form is opened, it sequentially displays separate pages for selecting a method and a bank. Then the customer selects the method and the bank (this option is used by default).
- 2—when the payment form is opened, the buttons for selecting other methods and banks supported by this method are displayed on one page. Then the customer selects one of these banks.
- 3—when the payment form is opened, it displays a page with buttons for selecting all available banks for this method. Then the customer selects one of these banks.
- 4—when the payment form is opened, it displays a page with buttons for selecting only specific banks supported by this method. Then the customer selects one of these banks.
- 5—when the payment form is opened, it displays a page requesting confirmation of redirection to the service of the specific bank. Then the customer confirms the redirection.
Information about the formats of requests and callbacks used for processing payments by using the Indonesian Online Banking method via Payment Page is presented further in this section; general information about working with the Payment Page API is presented in Interaction concepts.
Request format
There are several things you need to consider when sending purchase requests by using the Indonesian Online Banking method:
- The following parameters required for any payment must be specified:
project_id
—project identifier obtained from ecommpay during integrationpayment_id
—payment identifier unique within the projectpayment_currency
—payment currency code in the ISO-4217 alpha-3 formatpayment_amount
—payment amount in the smallest currency unitcustomer_id
—customer identifier unique within the project
- The following parameters required for any payment must be specified:
project_id
,payment_id
,payment_currency
,payment_amount
,customer_id
. -
The following are the bank selection options:
- Selecting the method and the bank on Payment Page (1)—the default option, applied if the
force_payment_method
parameter and thepayment_methods_options
object are not used. - Selecting a bank among other methods on Payment Page (2)—for this option in the
payment_methods_options
object specify theonline_indonesian_banks
object containing thesplit_banks
parameter with the valuetrue
:"payment_methods_options": "{\"online_indonesian_banks\": {\"split_banks\": true}}"
- Selecting a bank among all available ones on Payment Page (3)—for this option specify the method code
online-indonesian-banks
in theforce_payment_method
parameter. - Selecting a bank among specific ones on Payment Page (4)—for this option specify the following:
- the online-indonesian-banks code in the
force_payment_method
parameter - the
payment_methods_options
object with theonline_indonesian_banks
object that contains thesplit_banks
parameter with the valuetrue
and abanks_id
object with an array containing the target bank identifiers:"payment_methods_options": "{\"online_indonesian_banks\": {\"split_banks\": true, \"banks_id\": [140, 141]}}"
- the online-indonesian-banks code in the
- Confirming redirection to the service of the specific bank on Payment Page (5)—for this option specify the following:
- the online-indonesian-banks code in the
force_payment_method
parameter - the
payment_methods_options
object with theonline_indonesian_banks
object that contains thesplit_banks
parameter with the valuetrue
and abanks_id
object with an array containing the target bank identifier:"payment_methods_options": "{\"online_indonesian_banks\": {\"split_banks\": true, \"banks_id\": [140]}}"
- the online-indonesian-banks code in the
- Selecting the method and the bank on Payment Page (1)—the default option, applied if the
- Additionally, any other parameters available for working with Payment Page can be used (details).
- After all target parameters are specified, generate a signature (details).
Thus, a correct request for opening the payment form using the Indonesian Online Banking method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier and signature.
At the same time, in case of selecting a bank among specific banks (4), the request for opening Payment Page may contain additional data.
Callback format
The standard format for callbacks is used to deliver purchase results from Indonesian Online Banking. For more information, see Callbacks.
The following is the example of a callback with information about a 200,000.00 IDR
purchase made in the 200
project.
The following is the example of a callback with information about a declined purchase.
Useful links
The following articles can be useful when implementing purchases via Payment Page:
- Interaction concepts—about the interaction with the payment platform by using Payment Page.
- Signature generation and verification—about the procedure of generating and verifying signatures in requests and callbacks.
- Payment models and statuses—about the types, processing models, and possible statuses of supported payments and operations.
- One-time one-step purchase—about processing of one-time one-step purchases by using Payment Page.
- Information of operations performing—about error and response codes that are used in the payment platform to record information about performing of operations.
Purchases by using Gate
General information
To process a purchase through Gate by using the Indonesian Online Banking method, the merchant's web service is required to do the following:
- Send a request with all the required parameters and signature to the ecommpay URL.
- Receive an intermediate callback from the payment platform and redirect the customer to the bank service.
- Receive the final callback from the payment platform.
The full sequence and special aspects of purchase processing are provided below.
Information about the formats of requests and callbacks used for processing payments by using the Indonesian Online Banking method via Gate is presented further in this section. General information about working with the Gate API is presented in Interaction concepts.
Request format
There are several things you need to consider when sending purchase requests by using the Indonesian Online Banking method:
- To initiate each purchase, send a separate POST request to the
/v2/payment/banks/indonesia/sale
endpoint, which belongs to the group /v2/payment/banks/{payment_method}/sale. - 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—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—rounded up integer purchase amount in minor currency units. On the merchant side, customers should be warned about rounding.
- currency—purchase currency in ISO-4217 alpha-3 format
- Object account—customer account information:
- bank_id—bank identifier
- Object general—general purchase information:
- If required, you can also add any other additional parameters Gate supports.
Thus, a correct payment request through the Indonesian Online Banking method must include project, payment, customer, and bank IDs, customer IP-address, signature, currency and amount of the purchase, as shown in the following example:
Formats of the customer redirection data
To redirect a customer from the web service to the bank site, you must receive a callback from the payment platform containing the URL for redirection in the redirect_data.url parameter and data to be sent in the request body in the redirect_data.body parameter, and use these parameters when opening the bank's HTML page using the method specified in the redirect_data.method parameter.
The following is the callback fragment containing the redirection data.
Callback format
In the Indonesian Online Banking method, the callbacks that deliver purchase results use the standard format described in Callbacks.
The following is the example of a callback with information about a 200,000.00 IDR
purchase made in the 200
project.
The following is the example of a callback with information about a declined purchase.
Useful links
The following articles can be useful when implementing purchases via Gate:
- Interaction concepts—about the interaction with the payment platform by using Gate.
- Signature generation and verification—about the procedure of generating and verifying signatures in requests and callbacks.
- Payment models and statuses—about the types, processing models, and possible statuses of supported payments and operations.
- One-time one-step purchase—about processing of one-time one-step purchases by using Payment Page.
- Information of operations performing—about error and response codes that are used in the payment platform to record information about performing of operations.
Payouts by using Gate
General information
To process a payout through Gate by using the Indonesian Online Banking 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.
Information about the formats of requests and callbacks used for processing payouts by using the Indonesian Online Banking method via Gate is presented further in this section. General information about working with the Gate API is presented in Interaction concepts.
Request format
There are several things you need to consider when sending payout requests by using the Indonesian Online Banking method:
- To initiate each payout send a separate POST request to the
/v2/payment/banks/indonesia/payout
endpoint, which belongs to the group /v2/payment/banks/{payment_method}/payout. - Each request must include the following objects and parameters:
- Object
general
—general payout information:project_id
—project identifier obtained from ecommpay during integrationpayment_id
—payment identifier unique within the projectsignature
—request signature generated after all required parameters are specified (details—in the Signature generation and verification) details
- Object
payment
—payment information:amount
—payout amount in the smallest currency unitcurrency
—payout currency code in the ISO-4217 alpha-3 format
- Object
customer
—customer information:id
—customer identifier unique within the projectip_address
—customer IP address relevant for the initiated payout
- Object
account
—customer account information:number
—customer account numberbank_id
—bank identifiercustomer_name
—bank account holder's name
- Object
- Additionally, any other parameters included in the specification can be used.
Thus, a correct payout request by using the Indonesian Online Banking method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer and account information, as well as signature.
Callback format
In the Indonesian Online Banking method, the callbacks that deliver payout results use the standard format described in Callbacks.
The following is the example of a callback with information about a 200,000.00 IDR
payout made in the 200
project.
The following is the example of a callback with information about a declined payout.
Useful links
The following articles can be useful when implementing payouts via Gate:
- Interaction concepts—about the interaction with the payment platform by using Gate.
- Signature generation and verification—about the procedure of generating and verifying signatures in requests and callbacks.
- Payment models and statuses—about the types, processing models, and possible statuses of supported payments and operations.
- Payouts—about processing of payouts by using Gate.
- Information of operations performing—about error and response codes that are used in the payment platform to record information about performing of operations.
Payouts by using Dashboard
When working with Dashboard, you can process single and mass payouts by using the Indonesian Online Banking method.
- To process a single payout, open the payout form, specify all required parameters (including the payment method), send a request and verify that the payout has been processed.
-
To process a mass payout, prepare and upload a file with information about all target payouts, send a batch request, and verify that the payouts have been processed.
Use a CSV file structured according to the requirements presented in the Mass payments data section. The payout parameters must comply with the requirements (you do not have to generate a signature because it is specified by Dashboard).
More information about processing payouts by using Dashboard is presented in a separate section.
Testing
General information
For the Indonesian Online Banking 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 keep in mind that the test project identifier must be indicated in requests, the interfaces of the emulator of Payment Page and Indonesian Online Banking payment forms can differ from the production environment.
Test payments statuses
The final status of test payments and operations is determined by the amount specified in the request.
Test purchases:
40000
or40400
amount to get thedecline
status- any other amount to get the
success
status
Test payouts:
40000
or40400
amount to get thedecline
status- any other amount to get the
success
status
Purchases by using Payment Page
To perform a test purchase by using Payment Page, do the following:
- Send a correct test request for Payment Page opening to the payment platform.
- If the
online-indonesian-banks
method was not specified in the request—select the method on the emulator page. - If multiple banks are available for selection, select a bank; if only one bank is available, click the Pay button.
- Click the Success or Decline button (depending on the amount specified in the request).
- Receive the final callback with information about the payment result.
More information about processing purchases by using the Indonesian Online Banking method via Payment Page is provided in the Purchases by using Payment Page section.
Purchases by using Gate
To perform a test purchase by using Gate, do the following:
- Send a correct test request for purchase to the payment platform (the bank_id parameter must be used in the request, refer to ecommpay technical support for the parameter value).
- Accept a callback with redirection data.
- Go to the received URL and click the Success or Decline button (depending on the amount specified in the request).
- Receive the final callback with information about the payment result.
More information about processing purchases by using the Indonesian Online Banking method via Gate is provided in the Purchases by using Gate section.
Payouts by using Gate
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 Indonesian Online Banking method via Gate is provided in the Payouts by using Gate section.
Analysis of payments results
To analyse information about payments made with the Indonesian Online Banking method and other methods, you can use:
- Dashboard interface toolkit with various lists and analytic panels.
- Reports in CSV file format, available via the Reports section (one-time and periodically).
- Data in JSON format, sent by program requests to a specified URL available by using the Data API interface.
If you have any questions, refer to the documentation (Dashboard and Using Data API) and ecommpay technical support.