Professional Documents
Culture Documents
Version 3.0
Date: October 2017
Copyright ©2017 U.S. Payments Forum and Smart Card Alliance. All rights reserved. The U.S. Payments
Forum has used best efforts to ensure, but cannot guarantee, that the information described in this
document is accurate as of the publication date. The U.S. Payments Forum disclaims all warranties as to
the accuracy, completeness or adequacy of information in this document. Comments or
recommendations for edits or additions to this document should be submitted to: transaction-
speed@uspaymentsforum.org.
1 Additional information can be found in Section 7, “Appendix: Faster EMV Questions and Answers.”
2 U.S. Payments Forum, “Merchant Processing during Communications Disruptions,” April 2016, http://www.emv-
connection.com/merchant-processing-during-communications-disruption/
3 Ibid.
4 “DE” is an abbreviation for “Data Element” and is commonly used when referring to fields in an ISO/IEC 8583-based message
format. Thus, “DE4” is the identifier of the fourth data element in an authorization request based on ISO/IEC 8583. “Data
elements” may also be referred to as “fields.” DE4 is defined as the “Transaction Amount;” DE55 Tag 9F02 is defined as
“Amount, Authorized” within the cryptogram data. ISO/IEC 8583 is a common base for payment network messaging;
however other message formats, such as proprietary device-to-server message formats, may be based on other
specifications. Nevertheless, all formats will contain equivalent fields.
POS System
Cardholder Card Reader Terminal Issuer
Start
Start transaction scanning
[Placeholder Amount] goods
Insert Card
(Enter PIN)*
1st Gen AC
* PIN entry is [Placeholder Amount]
conditional
ARQC
ARQC
2nd Gen AC
[Unable to go online, Unable to go online
offline declined]
AAC
EMV Tx Completed
Remove Card
End scanning
goods;
Finalize tx amount
Online Authorization
- DE4[Final Tx Amount]
- DE55[Placeholder
Amount; ARQC]
Authorization
response
Approved Print
receipt
5 Please refer to payment network documentation for variances when performing No CVM transactions.
6 Assuming that the kernel configuration supports PIN.
9 U.S. Payments Forum, “Merchant Processing during Communications Disruptions,” April 2016, http://www.emv-
connection.com/merchant-processing-during-communications-disruption/
10 U.S. Payments Forum, “EMV Testing and Certification White Paper: Current Global Payment Network Requirements for the
U.S. Acquiring Community,” http://www.emv-connection.com/emv-testing-and-certification-white-paper-current-global-
payment-network-requirements-for-the-u-s-acquiring-community/
Two options are available for implementation – T=0 or T=1 – described below; issuers are advised to
consult their card supplier in order to select the appropriate approaches.
The solution implements EMV compliant COLD and WARM ATRs for T = 0 and T = 1 as indicated below:
Contactless Contactless
Indicator Symbol
11 The terminal logic to support the Common AID for the contactless interface is different from the terminal logic to support it
for the contact interface.
12 Merchants are advised to contact the acquirer/processor for additional information.
13 Note that not all CVMs are supported for all AIDs. For network CVM support, contact the acquirer/processor for specific
information.
14 Note that not all CVMs are supported for all AIDs. For network CVM support, contact the acquirer/processor for specific
information.
15 MasterCard, “New MasterCard Advisors Study on Contactless Payments Shows Almost 30% Lift in Total Spend Within First
http://www.smartcardalliance.org/publications-contactless-emv-payments-benefits-for-consumers-merchants-and-issuers/
18 For additional information on PIN bypass, see the U.S. Payments Forum white paper, “PIN Bypass in the U.S. Market,”
http://www.emv-connection.com/pin-bypass-in-the-u-s-market/.
19 Contact the acquirer/processor for additional information on whether cardholder selection of AIDs is required.
20 Application selection processes can be combined to optimize the cardholder experience. For example, the global AID can be
removed from a “debit pair” (global debit AID linked to same source of funding as an associated U.S. Common Debit AID)
before offering cardholder choice (EMV “Cardholder Selection”) between a credit AID and a debit AID.
21 For U.S. debit cards, the U.S. Common Debit AID accesses all networks available on the card for routing purposes; the global
22 Older terminals may not support higher communication speeds, but will process these cards at the highest rate at which they
are capable.
23 http://www.emv-connection.com/recommended-communications-best-practices/
General Questions
Q1. Who are the best candidates to implement Faster EMV?
A. Merchants and deployers will need to determine whether Faster EMV meets their business needs
based on the descriptions and considerations provided in the white paper, “Optimizing
Transaction Speed at the POS.”
Q2. What is the impact of Faster EMV to merchant’s/acquirer’s batch settlement processes? Would
this code change impact settlement certification?
A. Because no Transaction Certificate (TC) was generated, the ARQC and associated data elements
should be used for settlement where chip data is required. This is the same process used when
clearing deferred authorizations. If deferred authorizations are not currently supported, then
changes may be required to the settlement process. No requirements for settlement re-testing
have been announced. Note that the AAC generated by the terminal during Faster EMV
processing is not a “decline” from a business process standpoint. This AAC should not be returned
in clearing, but rather the ARQC (with associated data elements) should be used, as is done when
clearing deferred authorizations.
Q3. Are there implications for chargeback exposure with Faster EMV processes?
A. Faster EMV processing is intended for online-only environments. Faster EMV transactions receive
the same chargeback protection as traditional EMV with online authorization. The same fraud
liability shift applies for Faster EMV transactions; merchants therefore should ensure they obtain
the appropriate CVM to protect themselves from the lost/stolen liability shift.
Q4. Can Faster EMV be used in store-and-forward mode?
A: Faster EMV is a very similar process to Deferred Authorization as discussed in the U.S. Payments
Forum white paper, “Merchant Processing during Communications Disruption,” available at
http://www.emv-connection.com/merchant-processing-during-communications-disruption/.
Cryptograms obtained during a Faster EMV process can be used for a deferred authorization.
24 U.S. Payments Forum, “EMV Testing and Certification White Paper: Current Global Payment Network Requirements for the
U.S. Acquiring Community,” December 2016, http://www.emv-connection.com/emv-testing-and-certification-white-paper-
current-global-payment-network-requirements-for-the-u-s-acquiring-community/
25 Additional information can be found in the white paper, “Merchant Processing during Communications Disruption,” available
at: http://www.emv-connection.com/merchant-processing-during-communications-disruption/.
26 http://www.emv-connection.com/u-s-debit-emv-technical-proposal/
Legal Notices
All answers in this Appendix were prepared and validated by the members of the “Optimizing
Transaction Speed at the POS” white paper project team, including but not limited to representatives of
member acquirers, issuers, payment networks and other stakeholder groups.
While great effort has been made to ensure that the information in this document is accurate and
current as of the publication date, this information does not constitute legal advice and should not be
relied on for any legal purpose, whether statutory, regulatory, contractual or otherwise. Any person
that uses or otherwise relies in any manner on the information set forth herein does so at his or her sole
risk. All warranties of any kind, whether express or implied, relating to this document, the information
set forth or otherwise referenced herein or the use thereof are expressly disclaimed, including but not
limited to all warranties relating to or arising in connection with the use of or reliance on the
information set forth herein, all warranties as to the accuracy, completeness or adequacy of such
information, all implied warranties of merchantability and fitness for a particular purpose, and all
warranties regarding title or non-infringement.
Without limiting the foregoing, it is important to note that the information provided in this document is
limited to the specific approaches, payment networks and other factors as expressly described herein,
and that applicable rules, requirements, configurations and transaction processes may impact or be
impacted by the specific circumstances of a given implementation and related results and/or liabilities.
Additionally, note that specific payment networks and/or acquirers/processors determine their own
respective rules, requirements, policies and procedures for transaction processing, liability and other
matters, all of which are subject to change.
Merchants, issuers, acquirers, processors and others implementing EMV chip technology in the U.S.
therefore are strongly encouraged to consult with their respective payment networks,