Managing Transaction Flows

There are many possibilities to execute Payment Transactions, but a few things can be considered before you think of a flow to do it, like:

• The Terminal is operated by a person or is unattended?
• The Card is used at the begin or at the end of the transaction?
• The transaction value is a default value or defined each time?
• Should your cashier work even when it's impossible to process a transaction online?

This and other questions represents challenges to a Merchant's business. The GoChip sdk solution provides a set of flow scenarios to help the Merchant to respond effectively to those situations.

• Default Mode: this mode represents the basic/ default configuration of flows for transactions and considers a payment where Your Application has a online connection with the Payment Gateway and all the transactions should be processed online.
• Offline Mode: allows Your Application to work offline by choice, or based on the connectivity status with the Payment Gateway, proving an later submission for those transactions which couldn't be processed online.
• Polling Mode: allows Your Application to start the flow by making the Card Reader Device wait until a Card is presented. A default transaction value is established when setting this mode, but before submitting the transaction, Your Application needs to set an amount for the Sale.
• Delayed Mode: allows Your Application to start the flow normally, but instead of submitting the Sale Data, asks to present the Card first, and later on, Your Application should just submit the final amount of the transaction.

Now, choose a flow and start implementing to Your Application's needs.