Balance Enquiry

📘

Note:

The balance enquiry function is currently only available for Gift Cards.

What is a Balance Enquiry?

A balance enquiry is a way to check the remaining funds available on a card. Since many cards are preloaded or topped up with a set amount, it's useful to verify the current balance before making a transaction.

How Does a Balance Enquiry Work?

Process Description:

Step 1:

The MPOS will initiate a BALANCE_ENQUIRY request, the BALANCE_ENQUIRY request will be sent to the Ecentric Payment App.

Step 2:

The Ecentric Payment App will process the card details and forward the BALANCE_ENQUIRY request to the Ecentric Server.

Step 3:

The Ecentric Server will validate the card bin.

Note: If the card bin is not whitelisted, the Ecentric Server will return and error to the Ecentric Payment App.

Step 4:

Once the card bin has been validated the Ecentric Server will return the BALANCE_ENQUIRY response to the Ecentric Payment App.

Step 5:

The Ecentric Payment App will then forward the BALANCE_ENQUIRY response to the MPOS App.

Step 6:

The MPOS App will then have access to the card details and balance.


Request

Sample Bundle

The following is an example of a BALANCE_ENQUIRY request bundle that the MPOS Application will request.

"authenticationKey": "e27b6ce6-78ba6-4y46-9953-5afr28f7cbeb",
"merchantID": "971234500000003",
"launchType": "BALANCE_ENQUIRY"

Parameters

The following table describes the parameters of the BALANCE_EQUIRY request message.

PARAMETERTYPEDESCRIPTIONEXAMPLE
REQUIRED
launchTypeSTRINGMust be “BALANCE_ENQUIRY”
Used for launching the Ecentric Payment App to perform a card query.
BALANCE_ENQUIRY
merchantIDSTRINGThe merchant ID assigned to the merchant. The merchant ID will always be the same ID for a specific merchant.
To be provided by Ecentric.
776543200000123
authenticationKeySTRINGThe authentication token that was generated by the server on a successful auth call to the Ecentric Payment Appe27b6ce6-78ba6-4y46-9953-5afr28f7cbeb

Sample Code

The following code needs to be implemented by the MPOS Application in order to invoke the Ecentric Payment App to initiate a BALANCE_ENQUIRY request message.

*See Sample Code BALANCE_ENQUIRY Response for the intentLauncher function

private void doBalance_Enquiry() {
   Intent intent = new Intent();
   intent.setClassName("com.ecentric.ecentricpay", "com.ecentric.ecentricpay.MainActivity");
   Bundle dataBundle = new Bundle();
   dataBundle.putString("launchType", "BALANCE_ENQUIRY");
   dataBundle.putString("merchantID", "910100000000001");
 	 dataBundle.putString("authenticationKey", "received_authenticationKey");
   intent.putExtra("ecentricBundle", dataBundle);
   try {
       intentLauncher.launch(intent);
   } catch (Exception e) {
       Log.e(TAG, "Error launching intent: " + e);
   }
}

Response

📘

Note:

Within the Receipt Data two fields will be sent in the response:

  • AVAILABLE_BALANCE_CENTS OR AVAILABLE_BALANCE_FORMATTED: Shows completed transactions (i.e. where the advice message has been sent for that day’s top-ups).
    • Reflects the total amount available on the card, excluding any newly deposited funds
  • CURRENT_BALANCE_CENTS OR CURRENT_BALANCE_FORMATTED: Shows the completed + incomplete transaction values (what the balance will be once the advice messages have been sent).
    • Reflects the total amount available on the card, including any newly deposited funds

Sample Bundle

The following is an example of a BALANCE_ENQUIRY response bundle that the MPOS Application will receive.

"resultDescription": "APPROVED",
"buildInfo": "Ecentric_DEBUG_Ecentric_INT",
"isReceiptDataAvailable": true,
"resultCode": "01",
"receiptBundle": {
    "MERCHANT_REGION_CODE": "09",
    "RC_ALT": "00",
    "CASH_AMOUNT_CENTS": "0",
    "SEQ_NO": "000",
    "STATUS": "APPROVED",
    "BUDGET_PERIOD": "0",
    "CARD_TYPE": "",
    "PAN_WITH_BIN": "478769******5035",
    "MERCHANT_ID": "910100000000001",
    "TIMESTAMP": "1753966909998",
    "EXTERNAL_TRANSACTION_DATETIME": "",
    "PROCESSING_CODE": "0",
    "RC_DESCRIPTION": "Approved",
    "ED_AC_COLLECTION_AMOUNT": "",
    "EXTERNAL_INVOICE_GUID": "",
    "CURRENT_BALANCE_CENTS"= "800000",
    "REPLACEMENT_MERCHANT_ID": "",
    "BATCH_NO": "000",
    "AVAILABLE_BALANCE_FORMATTED" = "R 8000.00",
    "ED_AC_RESPONSE_DESCRIPTION": "",
    "AUTH_PROFILE": "0",
    "ED_AC_DEBTOR_ID": "",
    "INTERCHANGE": "null",
    "ESC_BY_AUTH_CODE": "206 31 SH 514402",
    "TX_TYPE": "49",
    "ACC_TYPE_DESC": "Default",
    "ED_AC_DEBTOR_ID_TYPE": "",
    "TIP_AMOUNT": "",
    "AVAILABLE_BALANCE_CENTS" = "800000",
    "CURRENCY_CODE": "0710",
    "ED_AC_MAC_DATA": "",
    "AUTH_CODE": "514402",
    "RC": "00",
    "AID": "",
    "ATC": "",
    "CRY": "",
    "CVM": "none",
    "PAN": "************5035",
    "RRN": "",
    "APSN": "",
    "DATE": "2025-07-31T13:02:09.017+0000",
    "STAN": "",
    "NAME_ON_CARD": "GROENEWALD/CG.MR",
    "AMOUNT_CENTS": "0",
    "ABS_AMOUNT": "0.00",
    "TOKEN": "",
    "RECEIPT_NUMBER": "",
    "EXTENDED_TRX_TYPE": "",
    "TERMINAL_ID": "91000328",
    "TX_TYPE_DESCRIPTION": "INQUIRY",
    "EXTERNAL_TERMINAL_ID": "",
    "FORMATTED_AMOUNT": "R 0.00",
    "DESCRIPTION": "",
    "BATCH_NUMBER": "0",
    "SETTLEMENT_DATE": "",
    "ED_AC_ACCOUNT_NUMBER": "",
    "SURCHARGE_AMOUNT": "0.00",
    "CURRENT_BALANCE_FORMATTED" = "R 8000.00",
    "ED_AC_CONTRACT_NUMBER": "",
    "EXTERNAL_TRANSACTION_GUID": "",
    "CARD_BIN": "478769",
    "TRANSACTION_INFO": "20631SH514402",
    "REPLACEMENT_TERMINAL_ID": "",
    "POS_ENTRY": "9001",
    "RC_ISO_DESCRIPTION": "Approved or completed successfully",
    "MERCHANT_CITY": "CAPE TOWN",
    "MERCHANT_NAME": "THUMBZUP INT RETAIL",
    "CUSTOMER_NAME": "",
    "APP_VERSION": "",
    "CARD_SEQ_NO": "0",
    "APP_LABEL": "",
    "INVOICE_NUM": "",
    "ED_AC_RESPONSE_CODE": "",
    "MESSAGE_1": "",
    "MESSAGE_2": "",
    "ED_AC_MAX_COLLECTION_AMOUNT": "",
    "CARD_TRANSACTION_TYPE": "MAG",
    "FORMATTED_CASH_AMOUNT": "R 0.00",
    "CASH_AMOUNT": "0.00",
    "RESULT_CODE": "00",
    "MERCHANT_COUNTRY_CODE": "ZA",
    "REPRINT": "false",
    "PAN_HASH": "8fe154743df867956bfd585a16c634e2cd45663a08466eca046e06fd66170533",
    "AMOUNT": "0.00",
    "TIP_LABEL": "",
    "DIGITS": "5035",
    "CVM_ABSA": ""
},
"merchantID": "910100000000001",
"serialNumber": "PC05P2CG10036",
"launchType": "BALANCE_ENQUIRY",
"transactionUuid": "9c638bed-88b1-4a19-ac3c-f143dc2528e8",
"appVersion": "1.9.10",
"transactionAmount": "0",

Parameters

The following table describes the parameters of the BALANCE_ENQUIRY response message.

PARAMETERSTYPEDESCRIPTIONEXAMPLE
launchTypeSTRINGEcho of the launchType used to launch the Ecentric Payment App.BALANCE_ENQUIRY
resultCodeSTRINGRepresents the result status of the intent call to the Ecentric Payment App
● 01: SUCCESSFUL
● 02: DECLINED
● 03: ABORTED
● 04: ERROR
01
resultDescriptionSTRINGA user readable representation of the above resultCode i.e. Approved for resultCode 01.
If the bank or switch approves or declines the transaction, the response description is included in this field.
APPROVED
merchantIDSTRINGEcho of the merchantID used in the request.910100000000001
merchantNameSTRINGThe name of the merchant that requested the transaction as stored at the bank.Merchant A
transactionAmountSTRINGApproved total transactionAmount.1000
transactionDescriptionSTRINGEcho of the transactionDescription used to launch the Ecentric Payment App.3rd party app desc
isReceiptDataAvailableSTRINGBoolean indicating whether a receiptBundle object is available. Will always be included for approved or declined transactions.true
receiptBundleSTRINGConsists of a sub-bundle of server parameters that can be used by the partner application to create a receipt.See Sample ecentricBundle SALE Response.
appVersionSTRINGThe software version currently running on the Ecentric Payment App.1.9.2
externalSTANSTRINGEcho of the systems trace number generated by some 3rd party ERP systems.123456
externalRRNSTRINGEcho of the RRN generated by some 3rd party ERP systems.ABCDEF123456
externalTransactionGUIDSTRINGEcho of the GUID that identifies a specific transaction generated by 3rd party ERP systems.2fdca02f-3cbe-4e8c-82ad-86a1a16b72e8
externalInvoiceGUIDSTRINGEcho of the GUID that identifies a particular invoice that may appear on more than one transaction.2fdca02f-3cbe-4e8c-82ad-86a1a16b72e9
externalTransactionDateTimeSTRINGEcho of the date and time the transaction was generated on the 3rd party ERP systems. Has the format of “yyyy-MM-dd'T'HH:mm:ss”2017-04-28T09:30:00
externalTerminalIdSTRINGEcho of the terminal identifier for device configured on the 3rd party ERP system.98100010
transactionUuidSTRINGEcho of the Unique ID of a transaction.bdf9d0af-17b3-48ca-8a0b-37dc52bf49bc
terminalIdSTRINGThis is an automatically system-assigned terminalID of the payment terminal’s identity number, which can be used to assist with settlement information and is returned in BASE36 format.77012398
latitudeSTRINGEcho of geolocation identifier indicating the latitude position of the device.-28.1619942
longitudeSTRINGEcho of geolocation identifier indicating the longitude position of the device.30.2350981
accuracySTRINGEcho of accuracy indicator of the geolocation.
serialNumberSTRINGThe serial number for the device that was used for the RETAIL_AUTH intent call.PC05P2CG10036

Sample Code

The following code needs to be implemented by the MPOS Application to recover the BALANCE_ENQUIRY transaction outcome and resume the MPOS App flow accordingly.

When the response is returned the calling app needs to override the onActivityResult() method and can be done as follows:

private final ActivityResultLauncher<Intent> intentLauncher = registerForActivityResult(
       new ActivityResultContracts.StartActivityForResult(),
       result -> {
           if (result.getResultCode() == Activity.RESULT_OK) {
               Intent data = result.getData();
               if (data != null) {
                   Bundle responseBundle = new Bundle(data.getBundleExtra("ecentricApplicationResponse"));
                   String launchType = responseBundle.getString("launchType");
                   String resultCode = responseBundle.getString("resultCode");
                 		// Determine if the transaction was successfully executed using returned resultCode
                   Boolean success = false;
                   if (resultCode != null && (resultCode.matches("00") || resultCode.matches("01"))) {
                       success = true;
                   }
                   if (responseBundle.get("errorBundle") != null) {
                       Bundle errorBundle = new Bundle(responseBundle.getBundle("errorBundle"));
                   }
               }
           } else {
               Log.e(TAG, "Received error resultCode: " + result.getResultCode());
           }
       }
);

Error Handling

The following table contains typical errors that might occur and how to handle these errors:

ERROR MESSAGESOLUTION
Incorrect merchantIDEnsure that you have entered the correct merchantID.
authenticationKey is invalidWhen your authenticationKey is invalid, you will receive an error message indicating that the authenticationKey is invalid, a RETAIL_AUTH request needs to be done to obtain a valid authenticationKey.

Sample Bundle

The following is an example of a BALANCE_ENQUIRY ERROR response bundle that the MPOS Application will receive.

"resultDescription": "ERROR",
"errorBundle": {
    "description": "ERROR",
    "reference": "",
    "errorType": "COMMS",
    "message": "Error communicating with server"
},
"buildInfo": "Ecentric_DEBUG_Ecentric_INT",
"resultCode": "0",
"merchantID": "910100000000001",
"serialNumber": "PC05P2CG10036",
"launchType": "BALANCE_ENQUIRY",
"appVersion": "1.9.8"