How Emerging Data Elements Can Support Mobile Wallet Use Cases
Publication Date: November 2019
As issuers and merchants implement new and innovative payments technology, consumers can select from a myriad of payment experiences while purchasing goods and services. Consumers have never had so much choice in payment options. Card-present interactions can now be conducted using various device-centric form factors resulting in the need for payment stakeholders to augment existing or create new transaction types. Consumers are empowered with information and payment options at their fingertips and can purchase goods and services by clicking a button or by placing a mobile device or wearable in close proximity to a point-of-sale (POS) device. This ongoing evolution has required the payments industry to introduce new data elements to allow the new form factors to be used in the payment or commerce cycle.
This white paper focuses on card-present transactions, with the following goals:
- Document three specific emerging data elements and how each is supported by the global payment networks today.
- Document use cases in which access, or earlier or broader access, to these three emerging data elements may benefit certain stakeholder groups.
- Provide recommendations regarding access to these three emerging data elements in connection with the identified use cases
The specific emerging data elements discussed in this paper include: token requestor identifier (TRID), wallet identifier (Wallet ID or WID), and Payment Account Reference (PAR). The white paper focuses on access to these emerging data elements for contactless face-to-face transactions.
The information presented in this white paper is intended to provide an overview of the emerging data elements available to the payments ecosystem for face-to-face transactions initiated from non-traditional payment devices. Merchants, payment gateways, and acquirers should consult their payment networks or payment partners for additional details on enabling these data elements to support these use cases.
Please note: The information and materials available on this web page (“Information”) is provided solely for convenience and does not constitute legal or technical advice. All representations or warranties, express or implied, are expressly disclaimed, including without limitation, implied warranties of merchantability or fitness for a particular purpose and all warranties regarding accuracy, completeness, adequacy, results, title and non-infringement. All Information is limited to the scenarios, stakeholders and other matters specified, and should be considered in light of applicable laws, regulations, industry rules and requirements, facts, circumstances and other relevant factors. None of the Information should be interpreted or construed to require or promote the establishment of any solution, practice, configuration, rule, requirement or specification inconsistent with applicable legal requirements, any of which requirements may change over time. The U.S. Payments Forum assumes no responsibility to support, maintain or update the Information, regardless of any such change. Use of or reliance on the Information is at the user’s sole risk, and users are strongly encouraged to consult with their respective payment networks, acquirers, processors, vendors and appropriately qualified technical and legal experts prior to all implementation decisions.