1. Manuals
  2. Brands
  3. CAN Manuals
  4. Touch terminals
  5. Albert
  6. Integration manual

CAN Albert Integration Manual

Hide thumbs Also See for Albert:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
Albert
POS Integration Guide.
Version 6.0
September 2016

Advertisement

Table of Contents
loading

Related Manuals for CAN Albert

Summary of Contents for CAN Albert

  • Page 1 Albert POS Integration Guide. Version 6.0 September 2016...

  • Page 2: Table Of Contents

    6. Points to Consider 6.1 Security 6.2 Other things to keep in mind 7. Passing the Transaction 8. Test and Submit on App bank 8.1 Testing 8.2 App Submission 9. Billing 10. App Support Commonwealth Bank Albert POS Integration Guide...

  • Page 3: Document Purpose

    2. Introduction to Albert 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 experience, on a single device. Albert has the capability to run Android based apps, managed via a secure portal –...

  • Page 4: Outline Of An Integration

    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.

  • Page 5: Common Pairing Scenarios

    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 responsible for sending and receiving requests to and from the POS. It uses the Albert SDK by Wincor to launch the CommBank Standard Payment app.
  • Page 6 Pros Š Ease and simplicity of implementation Cons Š Connection to POS app defined via static IP by default – if a change is required, IP is manually set on Albert POS Client. Š Addressed in Registry Service example below.

  • Page 7: Direct Connection With Registry Service

    4. Connect 5. Payment Request POS app POS Client 8. Payment Response 7. Payment Response 6. Payment Request CommBank Standard Payment app POS owned and developed CommBank owned and developed POS Terminal Albert Terminal Commonwealth Bank Albert POS Integration Guide...
  • Page 8 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 responsible for sending and receiving requests to and from the POS. It's also responsible for registering itself as an available Payment Terminal with the "Registry...

  • Page 9: Web Based Middleware

    Š Requires a web based Connection Service which is more development and support effort. Š The communication between POS and Albert is direct 1-to-1 and doesn't go via a message broker. This is fine but offers less monitoring or control.
  • Page 10 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 responsible for sending and receiving requests to and from the Publish/ Subscribe Queue.
  • Page 11 The POS sends a message to the MOM over the established connection. The format of this message is left to the POS vendor to decide. It can be extended to support any command recognised by the POS client such as "display advert", "display menu"...

  • Page 12: Web Based Pos

    WebSockets, Long Polling etc. The Albert connection could be a simple TCP/IP socket. The MOM box then becomes a facilitator 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 to a middleware service that will handle all transaction communications.
  • Page 13 POS Client The POS Client is an app or service that runs on Albert that may or may not have an interface. This is responsible for sending and receiving requests to and from the Publish/ Subscribe Queue.
  • Page 14 Request a payment by launching a web page or iFrame. Request an Albert The POS requests an Albert that may be based on: Location, terminal ID, store, features etc. The web page will establish a long running connection with the service using technology such as Long Polling, WebSockets and/or a combination of webhooks.

  • Page 15: Points To Consider

    For certain scenarios, such as pay at table, the terminal will initiate the transaction, rather than the POS. Store and Forward (SAF) When Albert can’t connect to the host, a ‘SAF’ transaction may be initiated. In these instances the STAN for the transaction will be ‘0’.

  • Page 16: Passing The Transaction

    (TransactionReferenceCode code : transactionReferences.getTransactionCodes()) { Log.i(TAG, code.getName() + “ : ” + code.getValue())); break; case Cancelled: // Transaction cancelled break; case Declined: // Transaction Declined break; case Error: // Error break; case Timeout: // Transaction Timeout break; Commonwealth Bank Albert POS Integration Guide...

  • Page 17: Test And Submit On App Bank

    8. Test and Submit on App bank 8.1 Testing Please endeavour to test your device on an Albert as soon as possible. Contact us when you think you are at this stage. You are able to test using the Payment Simulator available within the SDK.

  • Page 18: App Support

    10. App Support As the POS developer, you are responsible for supporting: Š The pairing process between Albert and the target POS. Š Communications to facilitate the pairing process. Š The installation of the POS app on Albert. Support calls to CommBank will be referred on to the POS developer, proving the fault out of the CommBank systems.

Table of Contents