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 Cash 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
  • You can customise the selecting payment method page on Payment Page
  • Safari browser may not support the redirection to a bank service. For the more details, contact ECommPay key account manager
  • Indomaret requires your local entity to be registered within their system to activate Indomaret payment option for your web service
  • Alfamart is available for international merchants without local incorporation in Indonesia
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 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 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 method.

The full sequence and particularities of the purchase process are provided below.



Figure: Purchase sequence in the Payment Page method:

  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 on Payment Page the Convenience stores method and agrees to use the method (or accepts the method already selected on Payment Page and agrees).
  8. The customer is redirected to the page with a payment instruction.
  9. The customer gets to any Alfamart or Indomaret convenience store and pays in cash.
  10. The payment is processed on the Alfamart or Indomaret convenience store side.
  11. The Alfamart or Indomaret service sends the payment result notification to the payment platform.
  12. The payment platform sends the callback to the web service.
  13. The payment platform sends payment results to Payment Page.
  14. 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:

  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_currency—payment currency in ISO-4217 alpha-3 format
    • payment_amount—payment amount in minor units
  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. 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.
  4. 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 is 432.
      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==
          }
      )
  5. If required, you can also add any other additional parameters Payment Page supports.
  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 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 Payment Page invocation parameters.

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:

Purchase by using Gate

General information

In the Convenience stores 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 page with a payment instruction.
  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 in the Payment Page method:

  1. Customer initiates purchase on the merchant web service by using the Convenience stores method to pay in cash at the Alfamart or Indomaret convenience store
  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, see Response format.
  6. The payment platform sends to the web service the callback that delivers the data for redirecting customer to the page with a payment instruction. The redirect_data object has the required data.
  7. The customer is redirected to the page with a payment instruction.
  8. The customer gets to any Alfamart or Indomaret convenience store and pays in cash.
  9. The payment is processed on the Alfamart or Indomaret convenience store side.
  10. The Alfamart or Indomaret service sends the payment result notification to the payment platform.
  11. The payment platform sends the callback to the web service.
  12. 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 Convenience stores payment method and provide the information on the format of callbacks with purchase results.

Request format

There are several things you must consider when using purchase requests in the Convenience stores method:
  1. You perform purchase by sending the /v2/payment/cash/indonesia/sale request by using POST (HTTP) method. This is an cash payment request group: /v2/payment/cash/{payment_method}/sale.
  2. The following objects and parameters must be specified in any 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 account—customer account information:
      • number—customer account number
    • Object payment—purchase information:
      • amount—purchase amount
      • currency—purchase currency in the ISO-4217 alpha-3 format
  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
    • Object account—convenience store information:
      • bank_id—convenience store ID. The Alfamart ID is 431, the Indomaret one is 432.
  4. If required, you can also add any other additional parameters Gate supports.

Thus, a correct payment request in the Convenience stores method must include project, customer and payment IDs, signature, amount and currency of the purchase and customer IP address, as well as the request may include recommended parameters such as first name and email of the customer and the convenience store ID, as shown in the following example:

Figure: Example of a purchase request

{
    "general": {
      "project_id": 580,
      "payment_id": payment_id,
      "signature": "PJkV8ej\/UG0Di8hTng6JvC7vQs
                    aC6tajQVVfBaNIipTv+AWoXW\/9MTO8yJA=="
    },
    "payment": {
      "amount": 35000000,
      "currency": "IDR"
      },
    "customer": {
      "id": "123",
      "ip_address": "248.121.176",
      "first_name": "Riza",
      "email": "riza@testpay.com"
    },
    "account":{
      "bank_id": 431
    }
}

Formats of the customer redirection data

In the Convenience stores methods, when redirecting customer to the page with a payment instruction, it is required to do the following:

  • 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": "10000.00",
                        "PURCHASEAMOUNT": "10000.00",
                        "TRANSIDMERCHANT": 16617000002212,
                        "PAYMENTTYPE": "SALE",
                        "WORDS": "4d1a2cdbc8a1fe972c3437953fc8c844cfeafa90",
                        "REQUESTDATETIME": "20181213205434",
                        "CURRENCY": "360",
                        "PURCHASECURRENCY": "360",
                        "SESSIONID": "6ac463c1",
                        "NAME": "ROMAN",
                        "EMAIL": "test@test.ru",
                        "BASKET": "Sale,10000.00,1,10000.00",
                        "PAYMENTCHANNEL": "35"
                    },
                    "method": "POST",
                    "url": "https://pay.com/Suite/Receive"
                },

Format of callback with purchase results

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.

 {
        "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": "12adeb019e5b283f83803845267bd1648e67efb5-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:

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