Other Functions
axept® GO now supports several additional integration functions designed to provide integrated applications with maximum flexibility.
Re-Print Last Receipt
To request that axept® GO re-prints the last receipts the below request is required.
EFTServiceLib.reprintTrans(this, <MerchantReceipt>, <CardholderReceipt>);
An example request is shown below that requests both copies to be re-printed is below:
EFTServiceLib.reprintTrans(this, true, true);
The request can be used to re-print the merchant, cardholder or both copies together.
Receipt Data Broadcast
The receipt data is supplied via the broadcast - TRANSACTION_RECEIPT_EVENT. The two receipts are passed as bitmaps and are named ReceiptDataMerchant and ReceiptDataCardholder. These bitmaps can then be printed either on their own or as part of another print when required.
If your integration is suppressing receipt printing, then it is a requirement for this data to be read and printed when required.
The code below shows how this can be achieved;
public void onReceive(Context context, Intent intent) {
if (TRANSACTION_RECEIPT_EVENT.equals(intent.getAction())) {
Bitmap merchant = BitmapFactory.decodeByteArray(intent.getByteArrayExtra("ReceiptDataMerchant"), 0,
intent.getByteArrayExtra("ReceiptDataMerchant").length);
Bitmap cardholder = BitmapFactory.decodeByteArray(intent.getByteArrayExtra("ReceiptDataCardholder"), 0,
intent.getByteArrayExtra("ReceiptDataCardholder").length);
printBitmap(context, merchant);
printBitmap(context, cardholder);
}
Suppress Receipt Printing
There may be scenarios where third-party applications wish to manage all printing themselves and use the receipt data broadcast to receive and then print the data when required. One such example could be where a third-party app wishes to combine the card data receipt with a ticket. Having this option as one which is initiated via integration allows the third-party app to manage its implementation without having to rely upon client configuration, especially useful when the suppression may only be required in specific circumstances. To suppress receipt printing for a specific transaction the below request needs to be sent immediately before requesting the transaction.
EFTServiceLib.suppressPrinting();
Once received the receipt printing will not take place for that specific transaction.
Test Communications
To request that axept® GO performs a communications test to the axept® Platform the below request is required.
EFTServiceLib.runTrans
(
this,
0,
TRANSACTION_TYPE_TESTCONNECT,
"<MerchantDepartmentId>",
"<UserId>",
"<Password>",
"<ReferenceNumber>"
);
An example request is shown below:
EFTServiceLib.runTrans(this, 0, TRANSACTION_TYPE_ TESTCONNECT, "", "", "", "");
The MerchantDepartmentId, UserId, Password and ReferenceNumber fields are not required.
Cancel Transaction on Present Card Screen
axept® GO can wait for a maximum period of 180 seconds for a card to be presented. If during this process the transaction needs to be cancelled the below request can be sent.
EFTServiceLib.cancelTrans(MainActivity.this);
Once received the transaction will be cancelled.
Check Number of Stored Transactions
To confirm the number of transactions currently stored and awaiting submission to the axept® Platform within axept® GO the below request is required.
EFTServiceLib.queryBatchCount(this);
Once received axept® GO will confirm the number of transactions stored.
Submit Stored Transactions
If transactions are stored within axept® GO the upload should take place automatically. However, if the upload is urgently required and needs to be initiated manually this can be done using the below. The upload can either be completed silently (without the axept® GO UI being presented) or interactively with axept® GO showing the upload progress on screen.
EFTServiceLib.submitTrans(this,<Submit Silently>);
An example request is shown below, in this example the transactions will be submitted silently.
EFTServiceLib.submitTrans(this, true);
Once received axept® GO will confirm the number of transactions stored.
Print History Report
To request that axept® GO prints a ‘History Report’ the below request is required.
EFTServiceLib.executeReport(this);
Once received axept® GO will print the ‘History Report’.
Execute & Print X Report
The X report provides the summary totals taken since the last Z report was run. axept® GO allows the integrator to request that the report is printed, the report data is returned via integration or both. To request that axept® GO prints a ‘X Report’ the below request is required.
EFTServiceLib.executeXAndZReports(this, X_REPORT,<PRINT REPORT>,<RETURN X REPORT DATA>);
An example request is shown below, in this example the report will both be printed and returned via integration.
EFTServiceLib.executeXAndZReports(this, X_REPORT, true, true);
Execute & Print Z Report
The X report provides the summary totals taken since the last Z report was run and then re-sets the totals. axept® GO allows the integrator to request that the report is printed, the report data is returned via integration or both. To request that axept® GO prints a ‘Z Report’ the below request is required.
EFTServiceLib.executeXAndZReports(this, Z_REPORT,<PRINT REPORT>,<RETURN X REPORT DATA>);
An example request is shown below, in this example the report will both be printed and returned via integration.
EFTServiceLib.executeXAndZReports(this, Z_REPORT, true, true);
Activation & Deactivation
axept® GO allows the integrated application to manage both the activation and deactivation process.
Activation
An activation can only be performed when axept® GO is in a deactivated state. Once the activation is completed successfully a configuration download will be performed and the device rebooted.
EFTServiceLib.activateTerminal(this,<Merchant Store Id>,,<License ID>,<Merchant Store Key>);
An example request is below.
EFTServiceLib.activateTerminal(this,123456,,3M29JJ4G4X,654321);
Deactivation
A deactivation can only be performed when axept® GO is in an activated state. When deactivation is completed the device will reboot.
EFTServiceLib.deActivateTerminal(this);
The deactivation process clears down the device and removes all data relating to the previous activated state (e.g. reports, receipt history etc.). As a result, a deactivation should only be performed once all required data has been obtained from the device, including any unsubmitted transactions.