Terminal Application : Payment Eco-system

This picture represent the current PayFacto payment eco-system inside an Android terminal

1. PAX A920
   
2. PAX A80
   
3. PAX IM30 (ECR only)
   

Definitions

List of applications:

1. PayFacto : This is the financial payment application. It is certified for Visa, MC, Interac, Discover, Amex and JCB for Canadian currency code and Canadian country code. It processes the authorizations on the PayFacto Switch
   
2. Gateway PayFacto: This is the application that interfaces with the PayFacto Cloud Gateway and translates the merchant request from the PFCG API to a payment/gift card request.
   
3. DataCandy PayFacto: This application interfaces with the DataCandy servers for gift/promo card processing.
   

1. PayFacto Switch: Provides the processing power for authorizations on all card brands.
   
2. PayFacto Cloud Gateway: Provides an omni-channel experience for the merchant using the latest web technologies. The API can call card-non-present transaction as well as card-present.
   
3. DataCandy: Processes gift cards, promotions and loyalty.
   

Flows

The flow for the Android devices is not that different than the one on the Monitor line. Here is a list of the flow using the whole ecosystem on an Android device.

Standalone payment transactions

From the payment terminal directly, and using any ways to manually type in/input the transaction amount, the merchant processes a payment transaction to the processing host.

Standalone DataCandy transactions

From the payment terminal directly, and using any ways to manually type in/input the transaction amount, the merchant processes a DataCandy transaction to the DataCandy processing host.

ECR through Cloud Gateway API

Please note that using this scenario, you will not be able to switch from the PayFacto payment application to the DataCandy application when reaching the card read screen.

The possible use cases are:

Starting at tag number 5 (see image), the merchant calls the PayFacto Cloud Gateway API to start the required transaction. When the request hits the Cloud Gateway, it will use the open connection to the terminal to start the required transaction. The following description refers to tag number 6 (see image)

·         Payment Transactions

o    If the required transaction is financial, the Gateway PayFacto application will call the PayFacto application to process the transaction

·         DataCandy Transactions

o    If the required transaction if gift/promo card related, the Gateway PayFacto application will call the DataCandy application to process the request.

Using this flow the integrator will require the PayFacto Cloud Gateway API specifications to perform the transactions.  This API description will be provided by the PayFacto integration team.

DataCandy gift redemption/increment through standalone payment transaction

The possible use cases are:

·         From the standalone payment application, the merchant types in the transaction amount. The merchant processes the transaction request.

·         On the card read screen, the customer will have a button to swipe the gift card

o    If the transaction request was a purchase, the Gift card application will be called with a redemption request of the same amount as requested in the payment application

o    If the transaction request was a redemption, the Gift card application will be called with an increment request of the same amount as requested in the payment application

·         The transaction goes through and the receipt is printed as required in the options.

ECR financial payment through the Android intent (third party application)

The possible use cases are:

·         From the third-party application, when required, it will call the PayFacto application to process the required transaction

·         The transaction goes through and the receipt is printed as required in the options.

Using this flow, an Android application developer will require the PayFacto application intent API description to perform actions on the PayFacto application

ECR DataCandy transaction through the Android intent (third party application)

The possible use cases are:

·         From the third-party application, when required, it will call the Gift PayFacto application to process the required transaction

·         The transaction goes through and the receipt is printed as required in the options.

Using this flow, an Android application developer will require the PayFacto application intent API description to perform actions on the PayFacto application