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
POS SAF Processing
Simplify can be configured to support SAF (Store and Forward) processing for timed-out (offline) transactions, using one of the following methods:
POS SAF – Simplify sends a response that allows the transaction to be locally approved or declined by the POS (Stand-in process). If approved, the POS forwards (i.e. resubmits) the transaction (through Simplify or directly to Fusebox) for host approval. POS SAF is described below.
On-Device SAF (version 28 and above) – Simplify performs Stand-in and other SAF processing. On-Device SAF is described separately.
- A transaction is considered to have timed out when: (1) the Fusebox response indicates that the Fusebox request to the authorizer (host) timed out, or (2) Simplify times out before receiving a Fusebox response. (The Simplify timeout interval for a request to Fusebox is defined individually for each request from the POS in the first 3 bytes of Field 11.)
PCI DSS Compliance: For POS SAF only, the response for a timed out transaction contains encrypted customer data. The customer is responsible for making this data unrecoverable after completion of the authorization process (PCI DSS 3.0 Requirement 3.2).
For timed-out EMV transactions, Simplify can be configured to return EMV tags in the response. The POS can include these tags in the resubmitted transaction. Resubmission of EMV Stand-In transactions without EMV tags can cause declines from some issuers. See the EMV section under "EMV API fields" for more information on EMV tags.
SAF support is configured independently for each tender type and applies to the following transaction types:
If Simplify times out waiting for a Fusebox response to one of these three financial transaction types, the outcome at the POS process will depend on whether SAF is enabled. In either case, Inquiry Processing must be performed.
Simplify can be configured to validate transactions for SAF eligibility. If not eligible, the transaction will be declined with a communications error (same as SAF not enabled).
If SAF is enabled and the transaction passes validation (if enabled), the POS process will receive a Stand-in response (Field 1010 = “*SLR STAND-IN.”) containing encrypted account data. This data allows the POS to resubmit locally approved transactions for host approval.
[Notice Note ]“*SLR STAND-IN.” is also returned when Simplify performs Stand-in on a transaction (On-Device SAF). However for On-Device SAF, no PCI-sensitive data is returned.[/notice]
Stand-in Not Enabled
If Stand-in/SAF is not enabled, Simplify will decline the transaction with a communications error (Field 1010 contains "*SLR COMMUNICATIONS ERROR." or "*SLR SWITCH TIMEOUT.").