Delayed Auth Mode

The Delayed Mode also changes the normal flow for a Sale Transaction using the GoChip Solution: Initiate the Terminal - Connect the Card Device Reader - Process Sale Data - Present the Card - Submit Transaction Amount - Present the Signature (when required) - Submit the Sale. This Mode is mostly applied to situations where the POS Application is designed to first capture the card’s data before establishing the Sale’s value.

Delayed Auth Mode Flow


  • (1) - Getting Settings: This is the basic initiation of a Terminal. Your Application is going to inform the Terminal credentials and receive the settings of a Terminal.
  • (2) - Configuring Device: This is the connection to the Card Device Reader. Your Application requires the device to be connected, informing the connection type and the parameters for connection (depending on the type of the device). There’s an additional step here regarding the setting of the Delayed Mode when Your Application needs to inform an initial amount to the transactions.
  • (3) - Start Sale – Process Sale: This is the normal Sale execution again. Your Application must send a basic Sale requiring it to be processed. Before actually sending the Sale to the Gateway, Your Application will be able to set the amount to the Sale again.
  • (4) - Start Sale – Present Card: Then, a flow of messages will occur until a card is detected and the required information is provided.
  • (5) - Start Sale – Submit Amount: This part starts when Your Application receives the request to set an amount to the transaction. At this point Your Application needs to set the final amount to the Sale before using the submitAmount() method, once the received CoreSale object, from the OnRequestSetAmount(CoreSale coreSale) method, has amount defined as “0” (zero). But be careful! You need to consider that the onRequestSetAmount(CoreSale coreSale) callback method is going to be called for more than one Mode, so inside the method, when treating the response you received, remember to verify if the Terminal is on Delayed Mode.
  • (6) - Signature: When the transaction method requires a signature, GoChip is going to require that from Your Application. After Your Application submits the captured signature, the GoChip will add it to the Sale Your Application already informed and submit it to the Gateway.
  • (7) - Submit Sale: The last part of the sale transaction is the submission itself and the receiving of the response and, depending on the result, Your Application might need to treat the information and send some feedback to the final user. In case everything goes right, just request the user to remove the card, for example.

This mode can also be used together with the Polling Mode. When together, those two modes also change the normal flow for a Sale Transaction, but it's basically a composition of both: Initiate the Terminal - Connect the Card Device Reader - Present the Card - Submit Transaction Amount - Present the Signature (when required) - Submit the Sale. This configuration is the combination of the Delayed and the Polling Mode, and is usually applied to cases in which the Terminal might be unattended – auto machines to sell stocked items could be an example of use, when there’s a limited number of items, therefore, a limit for the Sale, that can be predefined, in case all the elements are taken.

 Delayed Auth Mode and Polling Mode Resulting Flow


  • (1) - Getting Settings: This is the basic initiation of a Terminal. Your Application is going to inform the Terminal credentials and receive the settings of a Terminal.
  • (2) - Configuring Device: This is the connection to the Card Device Reader. Your Application requires the device to be connected, informing the connection type and the parameters for connection (depending on the type of the device). There’s an additional step here regarding the setting of the Delayed Mode, when Your Application needs to inform an initial amount to the transactions.
  • (3) - Start Sale – Present Card: in this case, the behavior is the same as the Polling Mode, and the card detection comes first.
  • (4) - Start Sale – Submit Amount: in this case, the behavior is the same as the Delayed Mode, and Your Application can set any amount to the Sale before submitting it. But be careful! You need to consider that the onRequestSetAmount(CoreSale coreSale) callback method is going to be called for more than one Mode – Delayed and Polling. And pay attention to the Delayed Mode! This mode is the only one which uses the submitAmount(Coresale coreSale, bool amountConfirmation). So if you are using the Delayed Mode, even if the Polling Mode is enabled, you should use the submitAmount() instead of the processSale().
  • (5) - Signature: When the transaction method requires a signature, GoChip is going to require that from Your Application. After Your Application submits the captured signature, the GoChip will add it to the Sale Your Application already informed and submit it to the Gateway.
  • (6) - Submit Sale: The last part of the sale transaction is the submission itself and the receiving of the response and, depending on the result, Your Application might need to treat the information and send some feedback to the final user. In case everything goes right, just request the user to remove the card, for example.