The QuickChip w/ PreRead/ functionality, herein referred to as the QuickChip feature is a "new" capability offered in the Tripos Direct and the Tripos Cloud solutions. It is supported for the following endpoints that communicate with the device to effect payment transactions, sale, refund, authorization, and force credit. Swipe, contact, contactless and manual transactions.The QuickChip solution allows for early removal of the chip card from the terminal (PreRead request stage), while relying on standard EMV processing between the card and terminal. It removes the need for EMV processing to wait for the final transaction amount, authorization response, and post-authorization processing (such as script processing and issuer authentication). QuickChip transactions are always authorized online. This allows the card data to be stored temporarily and the card to be removed before the online response is returned, while the merchant uses the issuer's online response to determine whether the transaction is approved or declined. As with magnetic stripe processing, the cardholder can dip the card at any time during the check-out process. Once the final sale amount is known, the user can be prompted for final approval of that amount. The transaction flow process will then be completed, sending all information out to the card association for approval (QuickChip request stage). QuickChip processing is intended for use at any acceptance point where timeliness (perceived or actual) is critical, such as multi-lane retail, QSR, and Convenience merchants. It is strongly recommended that QuickChip and EMV Contactless are implemented together.
There are five "new" fields introduced for QuickChip, two for configuration and three for
transaction flow operation. The configuration fields are per merchant in the case of Direct
and per lane at registration in the case of Cloud. They are "quickChipEnabled",
indicating that the feature/functionality is enabled/disabled and "quickChipDataLifetime",
indicating the number of seconds the card data will be available before expiration. The QuickChip
request stage (finalization) of the transaction must be performed within this time frame.
The "new" transaction flow operation fields are per transaction for any of the particular
endpoints supported, keeping in mind that for QuickChip, any endpoint transaction is a
two-request process, one endpoint request for the PreRead stage immediately followed by the
same endpoint request for the QuickChip stage. They are, "preRead" set to true to indicate
the request is for PreRead, "quickChip" set to true to indicate the request is for
QuickChip (finalization), and "provisionalAmount", an optional field, used to trigger CVM
behavior (PIN/Signature, etc…) when above CVM limit for various card brands. If this field
is not specified, it defaults to $1.00.. The two fields, "preRead" and "quickChip",
should be mutually exclusive (i.e. - only one should be provided or set to true per request). Please
note that the final amount should be provided at the final (QuickChip request) stage.
{
"laneId": "3",
"preRead": true,
"configuration": {
"provisionalAmount": 30.00
}
}
{
"laneId": "3",
"quickChip": true,
"transactionAmount": 7.31,
"configuration": {
"checkForDuplicateTransactions": false
}
}