Ingenico Developer Guide 2.03.024-028
Ingenico Download Configuration and Troubleshooting Guide 2.03.024-028
Telium Developer Guide 2.02.021
Verifone Developer Guide 2.19
Verifone Download Configuration and Troubleshooting Guide 2.19
Verifone Guides 2.18
Implementing TLS 1.2 to Simplify
Appendix G - Routing Fusebox Messaging through the POS
Simplify supports routing Simplify-Fusebox messaging via the POS, using the same connection (Ethernet, RS232 etc.) as used for POS-Simplify messaging. The POS forwards the Simplify request to Fusebox and forwards the Fusebox response to Simplify. The POS must manage the certificate for the socket connection to Fusebox.
Note for Link2500: Since the Link2500 cannot communicate directly with Fusebox using WiFi, POS routing (e.g. using an Android tablet connected by USB) provides an indirect way for the device to send Simplify requests to Fusebox.
For requests from Simplify to the POS and responses from the POS to Simplify, a header attached to the message indicates forwarding, FBREQ: for the request and FBRSP: for the response. This header immediately precedes the first message field (no CR/LF). For example:
Exception: If the POS cannot connect to Fusebox, the response from the POS contains the header FBERR: For example:
Points to Consider
Elavon recommends turning off status message 1 (in parm.fil).
The POS can use the request from Simplify as the starting point to wait for a response (before timing out).
If POS Routing is enabled, communication errors on the request from the POS to Fusebox can be handled as follows:
If the POS does not receive a response from Fusebox, it allows Simplify to time out (no response sent to Simplify).
If the POS cannot connect to Fusebox, it echoes the request from Simplify except for the header, which is FBERR:
In either case, further processing is as described under POS SAF Processing (if enabled) and Inquiry Message. (Exception: any required Fusebox messaging uses POS routing.) I.e. if POS SAF is enabled and the transaction is SAF-eligible, Simplify sends a Stand-in Response to the POS (API 1010 = "*SLR STAND-IN.") containing the data needed for the POS to perform Stand-in and SAF processing; else Simplify sends a decline.
The following diagram shows in graphic form how the above rules are used to process offline transactions using POS Routing. This diagram assumes: (1) The POS is mPOS, connected to Simplify by USB. (2) Quick Chip is enabled. (3) The original transaction is a Sale.
Note: This diagram represents the flow only. The exact header values are as described above.