background image

4   

|

   Commonwealth Bank  

Albert POS Integration Guide

 

Š

Albert is SEAndroid Enforcing.

 

Š

Albert is currently running Android 4.0.4.

 

Š

The Merchant Menu Library is required for apps to run on Albert.

 

Š

Firewall restrictions are in place that limit inbound network connectivity.

 

Š

There are no back, home, and recents buttons seen by the end user.

 

Š

The NDK is not supported. C and C++ is not allowed.

 

Š

For hybrid apps, contact us at 

smartterminals&[email protected]

4. Key Considerations for Albert

Building your own integration allows you to use your own POS system to control the merchant interaction. The 
Albert can then act as a customer interaction tool as well as a payment device.

Albert POS Integration

 

The Albert POS application (POS Client), residing on Albert, must establish a connection to the relevant POS 
register (POS Terminal).
The POS register needs to be able to send and receive variables from the POS Client. The POS Client receives the 
variables, and creates an intent to the CommBank Standard Payment app on Albert.
The CommBank Standard Payment app completes the entire transaction where the app takes the customer’s card 
details to process the transaction, prints the merchant and customer receipts and sends the transaction results 
back to the POS Client.
The POS Client then transmits the details back to the POS.

3. Outline of an Integration

Summary of Contents for Albert

Page 1: ...Version 6 0 September 2016 Albert POS Integration Guide...

Page 2: ...mmon Pairing Scenarios 5 5 1 Direct Connection to POS 5 5 2 Direct Connection with Registry Service 7 5 3 Web Based Middleware 9 5 4 Web Based POS 12 6 Points to Consider 14 6 1 Security 14 6 2 Other...

Page 3: ...email SmartTerminals Apps cba com au Albert is an Android based EFTPOS tablet that allows merchants to securely take a payment print a receipt and offer their customers an interactive touch screen exp...

Page 4: ...eraction The Albert can then act as a customer interaction tool as well as a payment device Albert POS Integration The Albert POS application POS Client residing on Albert must establish a connection...

Page 5: ...would be harder as the POS would have to allow connections from the internet POS Client The POS Client is an app or service that runs on Albert that may or may not have an interface This is responsibl...

Page 6: ...The POS Client uses the SDK to make a payment request to the CommBank Payment app 4 Payment Response Once the payment finishes a response is sent back to the POS Client 5 Payment Response The POS Clie...

Page 7: ...multiple locations and multiple terminals that need to be managed off site at a central location head office POS Client queries SDK for Merchant and Terminal ID POS Client connects to a registry servi...

Page 8: ...ister themselves as an available Payment Terminal as well as a way for a POS to request an Albert This would allow management of multiple terminals and POS systems via a central point This would lend...

Page 9: ...e 5 3 Web Based Middleware Similar to the direct connection with registry service approach but taken a step further by completely decoupling Albert and the POS Albert and the POS are not dependant on...

Page 10: ...t allow incoming connections this connection needs to remain in place and needs to be initiated by Albert CommBank Standard Payment app A black box that handles all the payment processing It is launc...

Page 11: ...minal At this point the message can be verified audit logged augmented and finally routed 6 Payment Request The POS Client uses the SDK to make a payment request to the CommBank Payment app 7 Payment...

Page 12: ...cilitator or broker rather than the POS and the Albert Terminal connecting directly If there are multiple POS connections and multiple Alberts it makes sense to be a complete MOM solution POS connects...

Page 13: ...of open sockets to Albert and to the POS as well as web services to register the devices This box could well be broken down further into sub components such as socket server and web service POS Clien...

Page 14: ...e payment request is routed to the correct terminal At this point the message can be verified audit logged augmented and finally routed 7 Payment Request The POS Client uses the SDK to make a payment...

Page 15: ...ation Removing debug and verbose logging may be performed as part of the Application Obfuscation and Protection with tools such as ProGuard At a minimum debug and verbose logging code i e Log d and Lo...

Page 16: ...getInstance AUD Launch the Payment app startActivityForResult payment createIntent 0 Parsing Activity Result Intents Override protected void onActivityResult int requestCode int resultCode Intent dat...

Page 17: ...ng ready at a minimum App launcher icon At least two screenshots of your app Source code ensuring that the code for any private libraries is enclosed as a single zip file Disaster recovery plan The pr...

Page 18: ...epted for publication You are responsible for providing technical support for App users As part of the Development Publication Process You must satisfy CommBank that you have an appropriate support st...

Page 19: ...006 116 030217...

Reviews: