How should I handle transactions requests if I lose internet connectivity. How should I handle a timeout when sending a txn to the cloud?
Users of triPOS Cloud are encouraged to have a transaction processing backup solution in the event of the loss of Internet connectivity. The use of Vantiv's Virtual Terminal on a mobile Internet connected device is one such option. If Internet connectivity loss is expected to be frequent, or the need to seamlessly process transactions when offline is critical, you may want to consider triPOS Distributed and its offline Store and Forward capability.
The procedure for a timeout with triPOS Cloud is the same as the procedure for a timeout with triPOS Distributed or a direct to Express integration. Namely, the attempted transaction should be reversed until a Not Found or Reversed response is received, and then the transaction can be attempted again.
The Vantiv Developer Integrations group can provide more information on this recommended approach.
In the event of a timeout response, the triPOS cloud service does not return the transaction id. This transaction id is REQUIRED in order to issue a Reversal. The TriPOS cloud api does not provide a way to determine this transaction id, and so the only possible way to issue a reversal is to log into the virtual terminal. This is not an acceptable solution, because frontend staff do not have credentials for the virtual terminal (nor should they).
How can this be handled programmatically?
Retrieving data ...