Convenience stores in Indonesia
Overview
Convenience stores is a payment method that allows to pay at any Alfamart or Indomaret convenience stores around Indonesia with in-store cash payments. A customer orders goods and services online, and completes the payment offline by printing a receipt or taking a reference number to a convenience store to make a cash payment. Convenience stores that support these payment method include "Alfamart" and "Indomaret" making it a convenient way for many Indonesian customers. This is popular due to cash being predominantly used in Indonesia. Purchases can be processed by using Payment Page and Gate.
General information
Payment method type | point of sale payments |
---|---|
Payment instruments | cash |
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 |
|
Onboarding and access fee | Refer to your key account manager ecommpay |
General information
Payment processing by using the Convenience stores payment method requires merchant's web service, one of ecommpay interfaces, and the ecommpay payment platform, as well as the Alfamart or Indomaret convenience stores service.
Operations support
Interfaces | Amounts, IDR | Times* | ||||||
---|---|---|---|---|---|---|---|---|
Payment Page | CMS Plug-ins | Gate | Dashboard | minimum | maximum | basic | threshold | |
Purchases | + | – | + | – | 0.01 | 2, 500,000.00 | 2 hours | 6 hours |
- 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 Convenience stores method, to perform a purchase operation, you need to redirect customer to the page with a payment instruction. Following the instruction customer needs to complete payment at any Alfamart or Indomaret convenience store.
Figure: Payment by using Payment Page
Figure: Payment 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 Convenience stores 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 result information from the payment platform. When opening Payment Page, you can either allow your customer to select the Convenience stores method from the list of other payment methods on Payment Page or have Payment Page opened with Convenience stores method selected. For more information about preselecting payment methods, see Preselecting payment methods.
The full sequence and particularities of the purchase process are provided below.
Figure: Purchase sequence in the Payment Page method:
- Customer initiates purchase by using the web service.
- The merchant web service sends to the specified ecommpay URL the purchase request for processing the purchase by using Payment Page.
- The payment platform receives the request for processing the purchase by using Payment Page.
- The payment platform performs the initial request processing that involves validation of the required parameters and signature.
- Requested Payment Page is generated into the ecommpay payment platform as specified in the project settings and the request parameters.
- Payment Page is displayed to the customer.
- The customer selects on Payment Page the Convenience stores method and agrees to use the method (or accepts the method already selected on Payment Page and agrees).
- The customer is redirected to the page with a payment instruction.
- The customer gets to any Alfamart or Indomaret convenience store and pays in cash.
- The payment is processed on the Alfamart or Indomaret convenience store side.
- The Alfamart or Indomaret service sends the payment result notification to the payment platform.
- The payment platform sends the callback to the web service.
- The payment platform sends payment results to Payment Page.
- 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 Convenience stores 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 Convenience stores method:
- 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_currency—payment currency in ISO-4217 alpha-3 format
- payment_amount—payment amount in minor units
- 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.
- To open Payment Page in the Indonesian language, pass the
id
code in the language_code parameter in the request for opening. For more information, see Interface language support. You can customise the selecting payment method page on Payment Page.
By default, Alfamart and Indomaret are grouped in one Indonesian convenience stores button on Payment Page, so the selection of a convenience store is carried out in two steps. First, the Convenience stores method is chosen among others, and then Alfamart or Indomaret is selected on the next page with the list of the convenience stores.There are several options for displaying the page with the selecting of payment method on Payment Page:
- To display Alfamart and Indomaret convenience stores grouped in one Indonesian convenience stores button on Payment Page in the list of payment methods.
- To display Alfamart and Indomaret with separate buttons in the list of payment methods. You need to pass
true
in the split_banks parameter in the request for opening in the payment_methods_options string."payment_methods_options": "{\"indonesia_cash\": {\"split_banks\": true}}"
- To display only one Indonesian convenience stores button without other payment methods. To preselect Convenience stores as the payment method on Payment Page, pass the code
indonesia-cash
in the force_payment_method parameter. The list of the banks from Convenience stores groupAlfamart and Indomaret with separate buttons are displayed to a customer on Payment Page bypassing the page with the payment method selection. - To display only one button of the Alfamart or Indomaret convenience store on Payment Page. You need to pass the Alfamart or Indomaret ID in the banks_id of the payment_methods_options parameter. The Alfamart ID is
431
, the Indomaret one is432
.payment_methods_options: '{\"indonesia_cash\": {\"banks_id\": [431]}}'
Here is the example of a request for opening Payment Page in the Indonesian language with preselecting the Alfamart convenience store.
Figure: Example of the request with preselecting a convenience store
EPayWidget.run( { payment_id: '580', payment_amount: 20000000, payment_currency: 'IDR', customer_id: '123', project_id: 120, force_payment_method: 'indonesia-cash', payment_methods_options: '{\"indonesia_cash\": {\"banks_id\": [431]}}', language_code: 'id', signature: "XFyr/D1zXj84lUZVfpbWZol9JAZLnUZoPJKPXRbOqBUpxxa/hOKm2 P8XOqydoyeIi7KdqrcxLFd3GxgPgUzIDg== } )
- If required, you can also add any other additional parameters Payment Page supports.
- 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 Convenience stores method must include payment, customer and project IDs, the currency and the amount of a payment in the appropriate currency, as shown in the following example:
EPayWidget.run( { payment_id: '580', payment_amount: 20000000, payment_currency: 'IDR', customer_id: '123', project_id: 120, signature: "XFyr/D1zXj84lUZVfpbWZol9JAZLnUZoPJKPXRbOqBUpxxa/hOKm2 P8XOqydoyeIi7KdqrcxLFd3GxgPgUzIDg==" } )
For information about all parameters available in the Convenience stores method, see Parameters for opening payment form.
Callback format
The Convenience stores method uses the standard format for callbacks to deliver purchase results. 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 8888872800000162
of customer in the 580
project.
Figure: Example of a successful purchase callback
{ "project_id": 580, "payment": { "id": "ECT_TEST_154469827896", "type": "purchase", "status": "success", "date": "2018-12-13T11:04:37+0000", "method": "Indonesia", "sum": { "amount": 20000000, "currency": "IDR" }, "description": "" }, "account": { "number": "8888872800000162" }, "operation": { "id": 4326000002254, "type": "sale", "status": "success", "date": "2018-12-13T11:04:37+0000", "created_date": "2018-12-13T11:03:10+0000", "request_id": "e5c3b50e144a20d166bc13ac388be7bf9297 03ae-46176f275f3311ced91cbb2df953512c17e4f512", "sum_initial": { "amount": 100, "currency": "IDR" }, "sum_converted": { "amount": 100, "currency": "IDR" }, "provider": { "id": 1163, "payment_id": "5044801", "date": "2018-12-13T11:04:35+0000", "auth_code": "" }, "code": "0", "message": "Success" }, "signature": "7Jh1jmn20UFEuuFUCyoPapeKoXauQkO5sapBZ7bnv m+Cl+1nOeyqgz3SOhto2kwe1GS0GCjH5L3rZdV8WXVw7g==" }
The following is the example of a callback for a purchase declined due to time-out.
Figure: Example of a declined purchase callback
{ "project_id": 580, "payment": { "id": "TEST_Indonesia_convenience_stores", "type": "purchase", "status": "decline", "date": "2018-12-13T19:54:35+0000", "method": "Indonesia", "sum": { "amount": 1000000, "currency": "IDR" }, "description": "" }, "account": { "number": "8888887800000022" }, "operation": { "id": 16617000002212, "type": "sale", "status": "decline", "date": "2018-12-13T19:54:35+0000", "created_date": "2018-12-13T13:54:33+0000", "request_id": "12adeb019e5b283f83803845267bd1648e67efb 5-372d87ad3760c628f74cc66d391a0b44fa69b354", "sum_initial": { "amount": 1000000, "currency": "IDR" }, "sum_converted": { "amount": 1000000, "currency": "IDR" }, "provider": { "id": 1163, "payment_id": "", "auth_code": "" }, "code": "20602", "message": "Time-out" }, "signature": "dkURT8W7wV1vvATI/9T1KwepNRSMfyu4AsIpV9Xv78 kQcndRFIlnpHUtMi71Go++SANuH+JOZ454e7FX5uAL0Q==" }
Related topics
The following topics might be useful when implementing payments by using Payment Page:
Analysis of payments results
As with other payment methods ecommpay offers, when using the Convenience stores 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.