EMVCo Illustrative Wireless Use Cases Disposition of Comments

Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) fEA All UCs EA All UCs Te MINOR Te MINOR Observation: there seem to be a multitude of ways to "pair" the product with the customer who pays. UC1 it may be a QR Code, in UC2 it’s the mobile store app and the connection to the local acceptance system, in UC3 it’s the "link" the store associate’s device provides the customer device (again via QR Code?), in UC4 it’s tapping the phone on a contactless reader, and so on. Do you envision to standardize that "pairing"? All the use cases suggest that the user can choose from his cards; are you thinking of leveraging SRC here (but that would be an e-commerce transaction) or of leveraging mobile wallets on the phone such as HCE NFC wallets or Apple Pay or Google Pay? Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted Acknowledge It is expected that some pairing mechanisms will be more appropriate than others for different use cases. EMVCo is evaluating the scope of any technical work in this area, and the level to which standardised pairing mechanisms are required. Acknowledge The use cases are not intended to imply the use of one particular technology. 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change EA All UCs Te MINOR Most use cases seem to rely on easily and almost seamlessly connecting to a local wifi or BLE; do you already have a vision to make this simple and secure at the same time? Have you thought about manin-the-middle attack possibilities? EA All UCs Te MINOR Slide 20: how do you make sure that the payment methods the user has available (e.g. only Amex) matches the payment methods the merchant offers (e.g. only Visa and Mastercard)? Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted Acknowledge Acknowledge Although not directly addressed within the use cases, any further work will consider security requirements. We are looking at the balance between seamless convenience and the need for the user to explicitly indicate their intent to connect and transact. This is a requirement which would be taken into account in any future specifications. 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA All use all cases ge Merchant always expect a level of confidence or verification that the customer is the authorized cardholder used for the purchase Add to all use cases: "I want to ensure the customer is a buyer authorized to use the payment card used for purchase." Reject Where appropriate, this is an expected part of the payment and has been illustrated in a number of the use cases with the cardholder authenticating for the payment. Whilst not explicitly included in all use cases, methods of assurance, where appropriate, will be taken into account in any further work. EA All use all cases ge Merchant always would prefer to qualify Add to all use cases: "I want to have the Reject for a lower cost of acceptance payment customer submit payment as customer (ie. Card present). present on-site to qualify for a lower cost of acceptance" Providing assurance that the cardholder is in vicinity of the merchant location is in scope for EMVCo ("recognised as a local payment"). However, business pricing is out of scope for EMVCo. Note that the use cases now include the story that the transaction should be recognised as a local transaction. 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA All use all cases ge Merchant always expects to have a choice Add to all use cases: "I want to have a Reject of payment alternatives and priority order choice of payment alternatives and priority in which those alternatives are made order in which those alternatives are made available to the customer available to the customer" The specifics of regional requirements are out of scope for EMVCo; however, any EMV specifications in this area will be flexible enough to meet regional requirements. These may vary from region to region. EA All use all cases Ge Merchants expect to have the ability to route a debit transaction to the debit network of its choice Add to all use cases: "I must have the ability to route a customer’s debit card payment to the debit network of my choice" Reject The fact that a transaction is conducted wirelessly should not affect the routing and authorisation process, and therefore this is out of scope 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA All use All cases EA P16 EA P16 Ge te te Merchants expect to offer customers flexibility of minimal (yet balanced) friction alongside convenience, speed, safety, and efficiency to their customers as part of the payment experience Add some more stories missing Missing story, customer may want to replace food A with food B e.g. I don’t want mushrooms on my pizza I want chilis instead Where not already listed, please add those components missing from each use case. Add new customer stories 1. I want to receive Special offers based on geofencing within a set vicinity 2. I want to have offers that are be timely 3. I want to receive appropriate personalised offers Add new customer story 1. I want to customize the order (eg swap mushrooms for capers) Acknowledge Acknowledge Acknowledge To be taken into account as the illustrative use cases evolve. These are largely the function of the value added service provider. While the specification may provide a framework for the value added services, it is not expected to define this level of detail. Details out of scope of EMV specification 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA P16 EA P16 EA P17 EA P17 EA P17 ge Consider doing research from a Do some first hand research with waiters Acknowledge waiter/tress perspective on common types of requirements ge Consider handling disabilities, eg visually Talk to disability advocate groups and get Acknowledge Implementations to comply with impaired might want the menu to be read advice about how to make the regulations out and voice to pay specification work with these groups. As we work through specification work this will be kept in mind te Missing user story As a customer I want to split the bill with my co-diners Accept Added to use case te Missing user story As a customer I want to see how my bill at any stage of my e.g. dinner. Middle of drinks to know whether to stay and order more drinks or move on Acknowledge Provision of this information is a merchant function. te International customer support in the payment As a customer I want to see local customisation like language, currency, offers Acknowledge This is expected to be a merchant function. 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA P17 EA P18 EA UC1 EA UC1 EA UC1 te te Te MINOR Ge Ge Missing how to handle discrepancies with the bill e.g. item on the bill that you need not purchase. This hasn’t been considered Itemised bill should be provided, missing story Slide 19 mentions scanning a QR Code; As a customer I want to handle errors with the bill As a merchant I want to be able to amend the bill to handle errors As a customer I want to see a full itemised bill An NFC tag may be preferable Acknowledge Acknowledge Acknowledge Slide 20 suggests tip as a percentage amount; Slide 21: is an online checkout rather than sending card credentials to the restaurant’s terminal also a possibility in the WLTF scope? Include absolute amount as an option Acknowledge Accept Provision of this information is a merchant function. Provision of this information is a merchant function. While a QR code is given as an example, this is not intended to exclude the use of NFC tags. Illustrative use cases provided as examples. This reference to the merchant’s local acceptance system has been removed and replaced with the concept of a "local payment" 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA Use Case Slide 25 & ge I am not sure why this statement is Remove the bullet: "I want the payment to Accept 2 & 3 30 required as the Distinguishing Features on be processed by the store’s local slide 11 call out that "Customer’s device acceptance system." interacts over wireless technology with the merchant’s local acceptance system". I don’t know that all merchants would necessarily think this is an expectation for all wireless payments but it is unclear why it is called out in these particular stories. This was provided as an example of a use case that is not an ecommerce transaction. Terminology was changed to indicate it was "local payment". 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA UC2 EA P28 Te MINOR te Slide 27 says customer’s device connects to local acceptance system and that customer chooses a card: is it correct to assume that the user has to download and register with the merchant app prior to going shopping and that the payment cards have been preregistered, i.e. this is a credential-on-file setup and the card or token is sent to the local acceptance system via wifi? (I just realized this is a similar question to the 2nd question further up) The app should be triggered automatically for convenience. Reduces step process and encourages people to use this or expose them to this process Before the ordering stage there is a preordering stage. Add this. Add a story that as a customer I want to get notified when I pass a store, which then easily opens the app. Acknowledge Acknowledge Intention is to allow a separation between any merchant app and the payment functionality. Assumption is that cardholder has a form of wallet on their device. Expectation is that cardholder will not have to register card with specific merchant. Provision of this information is a merchant function. 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA Use Case Slide 30 ge Merchants don’t want to dictate what the Remove the bullet: "I want my customer to Acknowledge Acknowledge that merchants may 3 customer chooses to do or not do to be able to pay without downloading a require or provide a specific engage with the merchant. Many specific app for my store" merchant app. The Use Case is merchants find value in certain apps being highlighting the case where a downloaded by the customer so this merchant app is not required, but is statement is not reflective of all not intended to prevent the use of merchants. In fact, it is used in other use merchant apps. cases. Regardless of the customer choosing or not to use a specific app, the merchant’s desire is to leverage all ways to know your customer and app usage should not be limited in order to enable wireless experiences. EA UC2 Ge Slide 30/31: link from store associate’s Acknowledge The use case is not intended to tablet offers customer’s payment cards, specify the technology used. probably in the mobile browser: is this envisioned to be done by somehow leveraging SRC? (see 2nd question further up) 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change EA UC4 EA UC4 Te MINOR Ge Slide 37: selected goods show up in the app; this can either happen by computer vision (Amazon Go), by self-scanning, or via the new Amazon Dash Cart, correct? Slide 39: after the end-of-trip there’s typically a validation test before the payment verifying that the user has scanned all articles; shall this be part of the scope of WLTF? Also, note that if the user simply walks out and somehow the payment fails the user may already be outside the shop and may be charged with stealing; Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted Acknowledge Yes, but we are not specifying how this occurs. Acknowledge This is out of scope for the WLTF. The card selection at the start of use case would prevent the likelihood, however, the specifics are outside of the scope of the WLTF. 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA UC5 Te MINOR Slide 41: Imagine several cars approaching entry gate 1-3; and further imagine several of those cars lining up at gate 1, others at gate 2 and the rest at gate 3; and finally imagine per car there are several passengers with smartphones; How do you initiate the session with the correct smartphone, so that the owner can confirm the vehicle type and entry? For instance, how to make sure my confirmation opens my gate, not another one; or, how to make sure I’m not opening the gate of the car in front of me who is actually next to pass? Acknowledge The WLTF has reviewed this scenario, but this may be addressed by other technologies such as ultra-wide band. EA UC5 Te MINOR Slide 42/43: is this a pre-registered app with payment cards or a mobile payment page; what does the toll booth wirelessly connect with? The device of the user or the car? How? (see question further up) Acknowledge This could be either a mobile wallet or a specific application. 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13 Draft Specification & Bulletin Industry Feedback Form Company Name: Associates Primary Contact Name: N/A Working Group or Task Force: Wireless Task Force Document: Illustrative Wireless Use Cases Date: September 2020 EA/Sub1 Clause No./ Subclause No. /Annex) Paragraph/ Figure/Tabl e/Note Type of comment2 Comment (justification for change) Proposed change Status (Accept, Reject, Acknowledge, In progress) EMVCo Use Only EMVCo observations on each comment submitted EA P42 EA P42 3rd bullet 2nd bullet te Driver confirmation is not needed for road Remove bullet and confirm button from Acknowledge Use-case being considered was tolls and is not ideal. Make this optional? graphic. User interaction should be where this was a replacement for a Note in some countries holding a phone avoided at low value toll gates. card payment – intent had to be whilst driving is against the law considered, but may not be required for example if the user has pre-allowed payments. Ge Diver does not need to stop at barriers at Driver drives through the toll booth area if Acknowledge It is unlikely that the establishment modern tolls, its just a drive through with barrierless, or stops at the barrier of a connection and payment is later enforcement for non payment likely to happen in the speed of a drivethrough without stopping. While the use case is possible, it may be difficult to meet the performance requirement of such a use case. 1 EA/Sub = EMVCo Associate or Subscriber company (enter a 2-3 letter abbreviation for commenting) 2 Type of comment: ge = general te = technical ed = editorial – For technical comments, please indicate whether your comment is a MAJOR or MINOR technical comment. Completed form should be forwarded to the appropriate Working Group or Task Force. Click on: http://www.emvco.com/subscriber/QueryAdd.aspx to submit feedback. 06-Jan-2021

of 13