Multi-token application functionality for wider availability of digital token processing

Abstract

There are provided systems and methods for multi-token application functionality for wider availability of digital token processing. A user may engage in a transaction with another user, such as a purchase of goods, services, or other items a merchant using a digital wallet, such as through a software application. An online transaction processor may provide a digital account for payment processing, which may include processing through mobile user devices at physical merchant locations using digital tokens and contactless payment terminals. To provide multi-token functionality, an application on a user device may be setup using a software development kit to utilize multiple different digital tokens with different token processor networks. When interacting with a POS device or payment terminal, the application may make each token available with preferences for use so that a primary preferred token may be identified but a fallback token may be used if needed.

Description

MULTI-TOKEN APPLICATION FUNCTIONALITY FOR WIDERAVAILABILITY OF DIGITAL TOKEN PROCESSING Ben Bishop Ludin and Rajvijay GovindarajuTECHNICAL FIELD

[0001] The present application generally relates to mobile application checkout using digital tokens and more particularly to providing mobile applications with multi-token application functionality to enable functionalities with different devices and processors.BACKGROUND

[0002] Users may utilize online transaction processors for processing transactions between different entities through device applications and digital accounts. Further, these online transaction processors may also provide payment options for in-person transaction processing and use at merchant locations, such as through mobile applications on user devices and digital token processing. In this regard, the online transaction processor may also provide transaction processing to merchants, which may be used at merchant locations. For example, merchants may utilize in-person payment terminals, such as point-of-sale (POS) devices that may include components and modules for local wireless exchanges of data and transaction processing, such as through the mobile applications and digital tokens when interacting with user devices. However, digital wallets and mobile software applications may have specific requirements, configurations, and / or specifications for data transfer and interactions with payment terminals for digital token usage and data communication with payment terminals, which may be incompatible with certain data processing schemes.Therefore, if users want to conduct transactions with different payment terminals that are incompatible with certain data processing schemes, users are required to have multiple different digital wallets and / or mobile applications for different data processing schema, hardware of merchants, and the like, which creates vulnerabilities and risk for user financial and personal data and consumes additional device resources for different applications and required data. Further, a single online transaction processor may encounter difficulties in addressing the needs of each customer, merchant, processing schema, and device through a single token processing schema, which may risk loss and poor customer satisfaction. Thus, it is desirable for an onlinetransaction processor to provide multi-token and cross-platform application functionalities with different digital tokens and merchant devices and payment terminals for more coordinated and comprehensive application usage.BRIEF DESCRIPTION OF THE DRAWINGS

[0003] FIG. 1 is a block diagram of a networked system suitable for implementing the processes described herein, according to an embodiment;

[0004] FIGS. 2A and 2B are exemplary system environments for establishing and utilizing operations for multi-token application functionality on user devices and merchant payment terminals, according to an embodiment;

[0005] FIGS. 3A-3C are exemplary diagrams for digital token identification and exchange between user devices and payment terminals when providing multi-token application functionality, according to an embodiment;

[0006] FIG. 4 is a flowchart of an exemplary process for multi-token application functionality for wider availability of digital token processing; and

[0007] FIG. 5 is a block diagram of a computer system suitable for implementing one or more components in FIG. 1 , according to an embodiment.

[0008] Embodiments of the present disclosure and their advantages are best understood by referring to the detailed description that follows. It should be appreciated that like reference numerals are used to identify like elements illustrated in one or more of the figures, wherein showings therein are for purposes of illustrating embodiments of the present disclosure and not for purposes of limiting the same.DETAILED DESCRIPTION

[0009] Provided are methods utilized for multi-token application functionality for wider availability of digital token processing, such as by configuring mobile applications and payment terminals for multi-token data processing through token selectivity during data processing. Systems suitable for practicing methods of the present disclosure are also provided.

[0010] A user may utilize a digital account, payment card, and / or other funding source to conduct transactions, including processing payments through an electronic payment and / or transaction network associated with a backend payment processor or other entity on the network. Users may utilize digital wallets through software applications that allow for electronic transaction processing, such as mobile smartphones that may utilize digital wallets for digital payments through mobile applications with merchant payment terminals and the like. A digital wallet may include payment information (e.g., for credit, debit, or other payment cards, bank accounts, checking accounts and numbers, etc.) and / or be linked to a digital account of the user with an online transaction processor, such as a payment service provider (e.g., PAYPAL®), which may provide electronic transaction processing services to users through the account and one or more websites and / or applications of the online transaction processor or a merchant. The online transaction processor may include a payment network and payment processing channels, processors, and the like, and may further include an integration with the electronic payment network (e.g., for payment cards, tokens, and the like) that allows for data exchange and communications between the two networks. Further, each payment network may provide data communications and backend processing devices that provide for interaction with frontend merchant, POS, and / or payment terminal processing devices that process transactions using data transfers, such as via digital, online, and / or contactless payments including near field communications (NFC), radio frequency identification (RFID) fields and communications, Bluetooth or WiFi communications, infrared scanners and / or communications, EMV chip reader, magnetic stripes and / or emulation readers, and other in-person and / or local data transfers.

[0011] However, to utilize such payment mechanisms and networks, certain data processors and digital token processing protocols may be required. Conventionally, merchants may utilize certain payment terminals, POS devices, and the like, which may be integrated with specific token processor networks for processing of digital tokens in a certain format and / or associated with certain data (e.g., a specific payment card, account, etc.). POS devices and merchant systems may include specific application programming interfaces (APIs) and API integrations for exchanging calls, requests, and responses on payment networks, which may have compatibility with other specific digital wallets, mobile applications, and digital tokens for processing of electronic transactions. In this regard, a service provider may provide APIs, a software development kit (SDK), and software applications that may be configured to and enable user devices of users (e.g., mobile smart phones, wearable devices, and other computing devices) to utilize multiple tokens during checkout and payment processing.

[0012] When a user device utilizing this multi-token functionality in an application is pinged for availability and / or an indication to perform processing of an electronic transaction by a POS device, payment terminal, or the like via short range wireless communications, a list of available tokens and / or token processor networks usable through the user device’ s applications may be returned. A preferred token may be designated for use when available, however, fallback tokens may also be designated and utilized to allow for processing when the preferred token’s processor network is unavailable, incompatible, or unintegrated with the merchant’s devices and systems, such as due to a subsequent failure of a communication or network associated with a selected token and / or token processor network. In some embodiments, the online transaction processor or other service provider may provide the functionality to generate and / or provide the list of available tokens / token processor networks, as well as preferred tokens and fallback tokens, to the user device and / or the POS device when requested. As such, the functionality of the user device’s application may also be, in part or fully, provided server-side at the online transaction processor.

[0013] The POS device or other system of the merchant may identify and / or select a digital token from the list for processing and engage in processing the electronic transaction using such token (e.g., through digital token and secure cryptogram exchange between devices and processing on the token processor network). Further, the POS device functionality to select a digital token may be performed at or with the online transaction processor, such as based on capabilities of the online transaction processor to process transactions electronically using digital tokens on behalf of the POS device. Once the token is selected, the token is encrypted in a secure application cryptogram by the user device and / or online transaction processor (using data from the POS device, such as transaction information and payment terminal qualifiers). This cryptogram allows for payment processing with a token processor network and / or system, such as an online transaction processor, by acting as a financial or payment instrument. A payment may then be made to the corresponding merchant from the user using the user’ s account or other payment instrument associated with the digital token used. As such, the transaction processor and corresponding devices and computing services may provide multi-token functionality through single or limited software applications, digital wallets, and the like.

[0014] In this regard, a user may desire to purchase items via a software application and / or digital account on a mobile device that provides funds, credit, or other value that is accessible to the user from financial instruments and funding sources through an online transaction processor and / or electronic payment network. Selection of one or more items in an in-person transaction at a physical merchant location may require a payment instrument from the user for electronic transaction processing, which may be provided through a token, identifier, data package, or the like that is transmitted to a merchant device at the location, such as via short range wireless communications (e.g., wireless or contactless payments via NFC, RFID, QR code scanning, etc.). A user may pay for one or more transactions using a digital wallet that is set up and configured to utilize payment terminals and devices with a payment network through token exchange, where the digital wallet includes an account with an online service provider or other transaction processor. A digital account with a service provider may be established by providing account details, such as a login, password (or other authentication credential, such as a biometric fingerprint, retinal scan, etc.), and other account creation details. The account creation details may include identification information to establish the account, such as personal information for a user, business or merchant information for an entity, or other types of identification information including a name, address, and / or other information.

[0015] The user may also be required to provide financial information, including digital account (e.g., credit / debit card) information, bank account information, gift card information, benefits / incentives, and / or financial investments, when processing transactions with merchants and / or other users or entities. Account creation may also be used to establish account funds and / or values, such as by transferring money into the account, storing financial information and funding source data with the account, and / or establishing a credit limit and corresponding credit value that is available to the account and / or card. The service provider may also provide for tokenization of data for electronic transaction processing through digital tokens. The application or website of the service provider, such as PAYPAL® or other online payment provider, may provide payments and the other transaction processing services. Moreover, the digital account may be utilized through one or more mobile applications for mobile devices or other software applications.

[0016] In order to pay for the transaction (e.g., a transfer or payment to another user, merchant, or other entity), the user may provide the digital account or funding source information and / or may login to an account with the service provider through authentication information in a software application. When providing in-person payments through NFC, RFID, and similar payment terminals using the user’s mobile or other user device, a digital wallet may be utilized to provide data to the terminal or device wirelessly. In this regard, an identifier and / or digital token or other data may authorize and / or authenticate the user for their digital wallet use and / or a payment instrument in the digital wallet (e.g., the account with the online transaction processor), which may be transmitted to another party for payment processing via wireless communications.

[0017] Generally, digital tokens may correspond to pieces of data, such as identifiers, that may represent other data (e.g., a financial instrument) stored with a backend processor and allow for representing the stored data in a secure manner without proliferating that data when transmitted and exchanged. The data may be stored by and / or transferred using one or more storage mediums and / or wireless transceivers, such as an NFC / RFID component, fob, passive or active antenna, etc., a magnetic stripe or an EMV chip, a displayable code or data, or the like. For example, a POS device and / or card reader may be used to detect, receive, and / or scan digital tokens and other data from mobile smart phones and similar devices that execute applications for digital wallets and digital token usage. This may allow for user payments through the digital wallet through short range wireless communications.

[0018] To properly setup, create, and / or program a mobile application or other software application to provide multi-token functionality with POS devices, payment terminals and the like, the online transaction processor may establish operations, tokens, and token preferences for the application and / or digital wallet accessible via the application. The application may be executable by a user device, such as a mobile smart phone at a merchant location, for processing payments by the user of the device with a merchant at the location. The operations for multi-token functionality may allow a user to store multiple tokens to or with the digital wallet and / or user device (e.g., in a cloud or online storage accessible by the application for the digital wallet or directly on-device in a local memory).

[0019] One or more preferences, a list of preferred tokens and / or token preference rankings, and / or a most preferred token may be set by the user, which may correspondto a particular token processor network, transaction processor, financial institution, payment instrument for the digital token, or the like. For example, the user may designate that they prefer to pay with a PAYPAL® or a VISA® credit card, and a corresponding digital token and / or token processor network may be designated as preferred by the application. As such, the preferences may be used to prioritize the tokens and / or token processor networks and backends (e.g., PAYPAL®) when paying with POS devices. The user may set their preferences that prioritize tokens and token processors in a list, ranking, or the like with an application so that specific tokens may be selected before other tokens for payment processing if the capability to process such tokens is supported by the receiving payment terminal, POS device, or other merchant device. The application may also be configured with a process to interact with POS devices, payment terminals, card or token readers, and the like to make tokens, token preferences, and / or lists of tokens available and further facilitate exchange of a digital token and / or secure application cryptogram for the digital token for transaction processing, as discussed herein. The application may correspond to an application of the online transaction processor, or may be another application (e.g., a merchant application) that integrates processes for the online transaction processor and multi-token functionality in the application.

[0020] The online transaction processor may further create and make available an SDK for configuring merchant-side devices and terminals for use of existing and / or new payment rails, systems, networks, and the like, such as a token processor network for processing a digital token associated with the user’ s account, digital wallet, and / or financial instrument with the online transaction processor. An SDK may also be made available for configuring client-side software applications, such as mobile payment applications, for multi-token functionality and / or the transaction processor may configure their application and / or website for such multi-token functionality. For example, the SDK may include software, data and / or code packages, coded instructions, scripts, and / or other data that may be used to configure operations executed by the merchant’ s device(s) during checkout to allow for payment processing using one or more tokens. The SDK may therefore be provided to merchants for integrating with the transaction processor for payment processing and transaction management services, as well as to software developers for configuring payment applications and interfacing with merchant POS devices and payment terminals. Where the merchant may include POS devices and payment terminals, themerchant may then configured their devices to utilize an available payment network and / or token processor network of the transaction processor using the SDK. In some embodiments, the merchant may also use proprietary software and / or hardware, including POS devices and / or payment terminals, of the service provider that may automatically allow the merchant to use the transaction processors payment and / or token processor network.

[0021] When configuring their devices, the merchant may further onboard with the online transaction processor, link a bank or other financial account and / or payment system for payouts and other payment processing, and the like. Onboarding may include establishing or linking to an account for the merchant with the transaction processor. However, the merchant may not be required to onboard with the transaction processor in all embodiments, and may instead use legacy data processing systems and networks, such as a token processor network. As such, the merchant may instead have POS and / or payment terminals, such as an EMV card and chip reader or other contactless and wireless data transmission mechanism, which may read data from user devices, such as mobile phones, for token processing on a network.

[0022] The user may utilize a mobile and / or resident software application on a computing device and / or a website to utilize a digital account and digital token for processing of an electronic transaction at a merchant’s location. Application interfaces may allow the user to view and / or request processing of transactions and payments based on accessible digital tokens for payment instruments associated with the user. When processing a transaction, a user may open, execute, and / or provide input in the software application on the user’s device. In this regard, a transaction may be processed using the digital accounts ) and / or digital token(s) through the digital wallet and merchant devices (e.g., POS devices, payment terminals, merchant networks and systems, and the like). A merchant device may generate and process transaction data for the transaction on a digital payment and / or token processor network having backend payment and token processors with token service providers (TSPs) for token processing and resolution. The transaction data may be generated and include information, such as identification of one or more items, item costs (e.g., itemizations) and / or a total cost, a transaction time, a corresponding merchant or merchant identifier, other users involved in the transaction, a transaction location, an MCC identifying a particular category for each transaction, and / or other transaction data.

[0023] The merchant may therefore offer transaction processing services to customers, such as the user utilizing the user device with the merchant device, through digital token processing. The online transaction processor may provide electronic transaction and payment processing services used to process the transaction using a digital token for a corresponding account or payment instrument, however, the merchant may also use other payment processors, financial institutions, and the like. In order to receive token data and process the token data on a token processor network, the merchant device may first receive an indication that the user device is ready and available to perform processing of the electronic transaction through an application on the user device and wireless signaling or short-range wireless communications and the like (e.g., NFC / RFID). In response, the merchant device may request a digital token and / or list of available digital tokens. Where configured with the SDK of the online transaction processor, the request may be for the list to determine if a digital token available through the application on the user device is usable with the token processor network for the online transaction processor. However, if not configured and using legacy credit or debit card processors and token processor networks, the merchant device may request the list or a valid token capable of being processing through existing networks and processors.

[0024] The user device may receive the request for the list and / or token, and the application on the user’s device may determine available digital tokens and any preferences for those available digital tokens, such as a preference to use a specific digital token, backend processor or service, payment instrument, and / or token processor network. The list may be generated, retrieved, and / or configured by the application based on the available and / or valid tokens and preferences for token usage. As such, the list may be generated device-side on the user device when requested, or may be generated and / or obtained by the user device from a corresponding online transaction processor (e.g., the transaction processor associated with the mobile application providing the list, such as PAYPAL®). The list may then be returned to the merchant device, which may make a selection from the list based on token availability, availability of supported functionality and / or connectivity with different token processor networks, and the preference(s) for token usage. As such, the merchant device may attempt to process on the preferred token processor network of the user and using the preferred token first, but may default or utilize another network and token where the merchant device is incompatible and / or the preferredtoken processor network is unavailable. While selection of the token and / or token processor network may occur on the POS device, the POS device may also interact with a backend transaction processor to select a token for payment processing based on capabilities and functionalities for payment processing, user preferences, and the like. The mobile device may interact with a nearby or proximate POS or other merchant device and / or terminal through an NFC or RFID transceiver, a reader or scanner for an EMV chip, or the like, that reads data from a local device or data storage mechanism.

[0025] Once the token is selected, the merchant device may interact with the user device to read, from a memory, cache, pathway designated by the application, or the like. This may include requesting and / or retrieving the selected digital token, which may then be transmitted to the merchant device for processing. With providing the digital token, a secure application cryptogram may be generated and provided by the user device, such as a cryptogram that encrypts data associated with processing the token with a time-based factor, encryption key, and the like. The token may be encrypted with data from the POS device, such as transaction information, device / terminal qualifiers, time or session-based identifiers and information, and the like, where the user device and / or online transaction processor may encrypt the token as a cryptogram using private keys for validation by the POS device using corresponding public keys. The user device may provide the cryptogram for the token for payment processing with the online transaction processor or on another token processor network. In this regard, the online transaction processor may utilize an application programming interface (API) to communicate and integrate with one or more APIs of the electronic payment and token processor network. This allows the online transaction processor to detect, receive, and process the transaction data, digital token, and cryptogram. Thereafter, the transaction data may be detected and / or transmitted to the online transaction processor via one or more APIs. This may include receiving and processing the data in real-time, such as when the transactions occur in order to provide per transaction approval and authorization.

[0026] Thus, the online transaction processor may approve the transaction or allow the transaction to be approved on the payment network (e.g., by not declining the transaction or requesting the electronic card network and / or backend credit card processing system to decline the transaction). However, if the transaction violates any risk or limits, then the online transaction processor may decline the transaction byrefusing to process the transaction and / or requesting that the network and / or backend processing system reject or decline the transaction. The online transaction process may also, instead of simply approving or declining the transaction, request additional data from the user and / or the merchant, including additional authentication information or authorization. The user device may include an application having one or more interface options, elements, or graphics that may include an executable option, operation, and / or selectable element to view approvals or declinations of transaction processing, as well as transaction status, balances, transaction and / or merchant information, and the like.

[0027] In this manner, user devices and merchant devices that utilize real-time transaction processing mechanisms may be made compatible with multiple digital tokens. This allows for integration and use of digital tokens with multiple different types of merchant devices, POS devices, payment terminals, and / or data readers. Further, the user’s device and application may provide multi-token functionality, thereby ensuring data processing occurs even in the event of incompatibility with preferred networks and digital tokens / token schema or protocols. Therefore, a system may be coordinated for use of previously incompatible data formats, components, and networks that would otherwise prevent usage and interactions between such platforms.

[0028] FIG. 1 is a block diagram of a networked system 100 suitable for implementing the processes described herein, according to an embodiment. As shown, system 100 may comprise or implement a plurality of devices, servers, and / or software components that operate to perform various methodologies in accordance with the described embodiments. Exemplary devices and servers may include device, stand-alone, and enterprise-class servers, operating an OS such as a MICROSOFT® OS, a UNIX® OS, a LINUX® OS, or another suitable device and / or server-based OS. It can be appreciated that the devices and / or servers illustrated in FIG. 1 may be deployed in other ways and that the operations performed and / or the services provided by such devices and / or servers may be combined or separated for a given embodiment and may be performed by a greater number or fewer number of devices and / or servers. One or more devices and / or servers may be operated and / or maintained by the same or different entities.

[0029] System 100 includes a user device 110, a POS device 130, and a transaction processor 140 in communication over a network 150. User device 110may be used to process a payment for the transaction using different digital tokens and a multi-token capability of user device 110. In this regard, when the transaction is processed, transaction data may be processed by user device 110 interfacing with POS device 130 to exchange a digital token and / or other data for digital token processing. Transaction processor 140 may be used to provide a token processor network and the like for digital token processing with POS device 130, and well as other digital token operations with user device 110.

[0030] User device 110, POS device 130, and transaction processor 140 may each include one or more processors, memories, and other appropriate components for executing instructions such as program code and / or data stored on one or more computer readable mediums to implement the various applications, data, and steps described herein. For example, such instructions may be stored in one or more computer readable media such as memories or data storage devices internal and / or external to various components of system 100, and / or accessible over network 150.

[0031] User device 110 may be implemented using any appropriate hardware and software configured for wired and / or wireless communication with POS device 130 and / or other merchant devices with wireless and contactless payment terminals, as well as transaction processor 140 for processing a transaction using a digital token. User device 110 may correspond to a user that processes payments and sales through an executable software application. In various embodiments, user device 110 may be implemented as a personal computer (PC), a smart phone, laptop / tablet computer, wristwatch with appropriate computer hardware resources, other type of wearable computing device, and / or other types of computing devices capable of transmitting and / or receiving data. Although only one computing device is shown, a plurality of computing devices may function similarly.

[0032] User device 110 of FIG. 1 contains a payment application 120, a database 112, and a network interface component 116. Payment application 120 may correspond to executable processes, procedures, and / or applications with associated hardware. In other embodiments, user device 110 may include additional or different modules having specialized hardware and / or software as required.

[0033] Payment application 120 may correspond to one or more processes to execute software modules and associated components of user device 110 to provide features, services, and other operations to a user of user device 110, which may include payment and transaction processing through multi-token digital tokenfunctionality and compatibility with different physical token processing devices for merchants and the like. In this regard, payment application 120 may correspond to specialized software utilized by a user of user device 110 that provides wider availability and access to payment processing through digital wallets and corresponding tokens for payment instruments and accounts, which may be compatible with different devices, communication and processing protocols, schema, and token processor networks based on token requirements. This may be provided by allowing payment application 120, through a token wallet 122, to use different token services 124 that may require separate tokens and token processor networks by enabling different token reading, transmitting, and the like by POS device 130 and other token processing devices and terminals.

[0034] Payment application 120 may be used to access a website or application (e.g., mobile application, rich Internet application, or resident software application) that may display one or more user interfaces that allow for interaction with the computing services of transaction processor 140, as well as to process transactions with POS device 130. In various embodiments, payment application 120 may correspond to a general browser application configured to retrieve, present, and communicate information over the Internet (e.g., utilize resources on the World Wide Web) or a private network. For example, payment application 120 may provide a web browser, which may send and receive information over network 150, including retrieving website information, presenting the website information to the user, and / or communicating information to the website. However, in other embodiments, payment application 120 may include a dedicated application of a merchant associated with POS device 130, a transaction processor associated with transaction processor 140, or other entity. Payment application 120 may be used to access and utilize a token wallet 122 provided and / or services with POS device 130 using digital tokens 114 for token wallet 122, which may provide digital tokens 114, application cryptograms, and the like for payment processing to different payment and merchant device and terminals.

[0035] Payment application 120 may be associated with account information, user financial information, and / or transaction histories. However, in further embodiments, different services may also be provided via payment application 120, including social networking, media posting or sharing, microblogging, data browsing and searching, online shopping, and other services available through transaction processor 140. Thus, payment application 120 may also correspond to different service applications and thelike. When utilizing payment application 120, a user may request processing of a transaction, such as a payment request, to be processed via a short-range wireless and / or contactless data transfer or other communication of a digital token, such as to POS device for payment processing. Data for the digital token may be provided by token wallet 122 using token services 124 during contactless payments via corresponding protocols, operations, and / or token processing schema. Thereafter, NFC processes 126 may be used for communication of the digital token, a secure application cryptogram, or the like to POS device 130, which may be based on payment services 128 (e.g., NFC / RFID reading, Bluetooth or WiFi communications, etc. with corresponding payment processing operations).

[0036] For example, a payment request for a transaction or other interaction may correspond to utilizing payment application 120 to request, establish, and / or process a transaction for payment using one of digital tokens 114. Payment application 120 may transmit an indication to POS device 130 to transact via short-range wireless communications for token exchange and payment processing via a token processor network, or the indication may be provided device-side for POS device 130, such as by a merchant employee or the like establishing a transaction and initiating a process to receive payment via short-range wireless token exchange and communications. POS device 130 may then receive a request for a digital token and / or list of digital tokens, which may be generated by payment application 120 and provided to POS device 130 for token selection.

[0037] To generate a list of digital tokens 114 available for processing with POS device 130, payment application 120 may access digital tokens 114 and preferences with token wallet 122 for use of digital tokens 114. The preferences may indicate the token processor networks and transaction processors that are preferred for digital tokens 114, such as after onboarding and utilizing an account and / or payment application 120. The list may be generated to request usage of the preferred one of digital tokens 114, but may also default and / or fallback to another digital token in the event that POS device is incapable of processing and / or lacks supported functionalities to process the preferred one of digital tokens 1 14. The list may then be transmitted to POS device 130, such as using NFC processes or other short-range wireless communications corresponding to the one of payment services 128 used for interacting with POS device 130.

[0038] Thereafter, POS device 130 may select the digital token based on capabilities and supported functionalities of POS device 130 for different token processing schema and token processor networks. Payment application 120 may receive the indication of the selection and prepare the digital token for transmission, such as by making available to be read and / or generating the token and a secure application cryptogram as an encrypted value associated with the digital token, a time and / or location-based value, and the like. The token may then be transmitted wirelessly, such as through short range wireless communications for contactless payment protocols, devices, and technology. To do so, NFC processes 126 may determine the requirements for token transfer using payment service 128 for different devices and terminals. In some embodiments, this may include making a record for a digital token or application cryptogram readable and / or transmitting the digital token or application cryptogram to POS device 130. The token record may then be readable and NFC processes 126 may therefore interact with POS device 130 for the token data exchange based on the protocols or operations of payment services 128. Configuring of payment application 120 to utilize token wallet 122 and NFC processes 126 in such a manner for multi-token functionality may be performed using an SDK provided by transaction processor 140. Thereafter, payment application 120 may be used to view the results of transaction processing and the like via one or more interfaces.

[0039] In various embodiments, user device 110 includes other applications as may be desired in particular embodiments to provide features to user device 110. For example, the other applications may include security applications for implementing client-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) over network 150, or other types of applications. The other applications may also include email, texting, voice and IM applications that allow a user to send and receive emails, calls, texts, and other notifications through network 150. In various embodiments, the other applications may include financial applications, such as banking applications. Other applications may include social networking applications, media viewing, and / or merchant applications.

[0040] The other applications may also include location detection applications, which may be used to determine a location for the user, such as a mapping, compass, and / or GPS application, which can include a specialized GPS receiver that determines location information for user device 110. The other applications may include deviceinterface applications and other display modules that may receive input from the user and / or output information to the user. For example, the other applications may contain software programs, executable by a processor, including a graphical user interface (GUI) configured to provide an interface to the user. The other applications may therefore use components of user device 110, such as display devices capable of displaying information to users and other output devices, including speakers.

[0041] User device 1 10 may further include database 112 stored on a transitory and / or non-transitory memory of user device 110, which may store various applications and data and be utilized during execution of various modules of user device 110. Database 112 may include, for example, identifiers such as operating system registry entries, cookies associated with payment application 120 and / or the other applications, identifiers associated with hardware of user device 110, or other appropriate identifiers, such as identifiers used for payment / user / device authentication or identification, which may be communicated as identifying the user / user device 110 to transaction processor 140. Moreover, database 112 may include digital tokens 114 that may be stored locally for payment processing. However, in other embodiments, digital tokens 114 may be generated at the time of transaction processing by payment application 120, such as with transaction processor 140 or POS device 130.

[0042] User device 110 includes at least one network interface component 116 adapted to communicate with POS device 130, transaction processor 140, and / or other devices and servers over network 150. In various embodiments, network interface component 116 may include a DSL (e.g., Digital Subscriber Line) modem, a PSTN (Public Switched Telephone Network) modem, an Ethernet device, a broadband device, a satellite device and / or various other types of wired and / or wireless network communication devices including microwave, radio frequency, infrared, Bluetooth, and near field communication devices.

[0043] POS device 130 may be maintained, for example, by a merchant or other entity that provides items for sale to users at physical merchant locations. POS device 130 may correspond to one or more sales locations where a user may visit in order to shop for items. POS device 130 may further include other platforms, websites, and resources that may allow users to engage in electronic transaction processing, such as those associated with payment processors, transfers of funds, and other payments or purchases that may be used by users and may require payment of a balance due for some product, service, or other item. In some embodiments, POS device 130 may beimplemented as a single or networked personal computers (PCs), servers, a smart phone, laptop computer, wearable computing device, and / or other types of computing devices. In some embodiments, POS device 130 may correspond to a payment terminal and / or transaction processor device provided to a merchant by a transaction processor, such as a PAYPAL® or ZETTLE® payment terminal, payment stand device, or the like. Although only one merchant POS device is shown, a plurality of merchant POS devices may function similarly.

[0044] POS device 130 of FIG. 1 contains an NFC sales application 132 and a communication module 136. NFC sales application 132 may correspond to executable processes, procedures, and / or applications with associated hardware. In other embodiments, POS device 130 may include additional or different software as required.

[0045] NFC sales application 132 may provide and / or process items for sale with user device 110 and / or a user associated with user device 110 (e.g., using payment sources including one of digital tokens 114). NFC sales application 132 may also correspond to a checkout application at a physical merchant location, such as the application(s) of a POS device used to provide sales at physical locations. NFC sales application 132 may be used to establish a transaction once a user / employee associated with POS device 130 has entered one or more items for purchase and / or entered the item(s) to the transaction for processing. Once a payment amount is determined for the item(s) to be purchased by the user, POS device 130 may request payment for the transaction. Payment may be provided using a physical payment instrument (e.g., cash, a payment card, etc.), however, POS device 130 and / or the merchant corresponding to POS device 130 may also be capable of short-range wireless communication via communication module 136 for exchange of data with user device 110 to perform transaction processing. In this regard, payment may be received by using a digital token 134 selected from digital tokens 114 from user device 110. After receipt of one of digital tokens 114, POS device 130 may then process a payment to the merchant associated with POS device 130 using digital token 134.

[0046] To receive digital token 134 for processing, after an indication to process a payment for the transaction through token exchange and short-range wireless communications, NFC sales application 132 may request a token and / or a list of available tokens from user device 110. The list may be generated as previouslydiscussed, and once received, NFC sales application 132 may select digital token 134 based on token preference, supported functionalities and capabilities, such as those to process data on and using a token processor network, and the like. This may include using transaction processor 140 as the processor of digital token 134 over network 150 on the corresponding token processor network. Configuring of POS device 130 and NFC sales application 132 to utilize the token processor network and token processing functionality with transaction processor 140 may be done using an SDK from transaction processor 140. However, where legacy systems and payment processors may be used, such as credit or debit card providers, banks and other financial institutions, and the like, NFC sales application 132 may perform token processing on those networks. After processing, a payment may be effectuated to an account of the merchant from the corresponding account and / or payment instrument of the user.

[0047] POS device 130 includes at least one communication module 136 adapted to communicate with user device 110, transaction processor 140, and / or other devices or servers over network 150. In various embodiments, communication module 136 may include a DSL (e.g., Digital Subscriber Line) modem, a PSTN (Public Switched Telephone Network) modem, an Ethernet device, a broadband device, a satellite device and / or various other types of wired and / or wireless network communication devices including microwave, radio frequency, infrared, Bluetooth, and near field communication devices.

[0048] Transaction processor 140 may be maintained, for example, by an online service provider, which may provide processes to provide account services and process payments, such as using digital tokens 114 that may be exchanged with POS device 130 and / or other devices. In this regard, transaction processor 140 includes one or more processing applications which may be configured to interact with user device 110, POS device 130, and / or another device / server to facilitate communications and transactions between users. Transaction processor 140 may be maintained by or include another type of platform or service provider, for example, a transaction processor such as PAYPAL®, Inc. of San Jose, CA, USA. Although transaction processor 140 and POS device 130 are discussed as separate devices and servers, in some embodiments, one or more of the described processes of may instead be provided by the other device or server, or the same device or server.

[0049] Transaction processor 140 of FIG. 1 includes a transaction processing application 142, a database 146, and a network interface component 148. Transaction processing application 142 may correspond to executable processes, procedures, and / or applications with associated hardware. In other embodiments, transaction processor 140 may include additional or different modules having specialized hardware and / or software as required.

[0050] Transaction processing application 142 may correspond to one or more processes to execute modules and associated specialized hardware of transaction processor 140 to process a transaction for item(s) with user device 110 and one or more merchant or seller devices, which may be based on one or more of digital tokens 114 being registered and established with token wallet 122 for in-person, short range wireless, and / or contactless payments, data transfers, communications, and the like. In this regard, transaction processing application 142 may correspond to specialized hardware and / or software used by users to establish accounts including digital tokens 114 used by user device 110. Accounts may each be created by providing personal and / or financial information to transaction processor 140 and selecting authentication credentials. In various embodiments, the financial information may include payment instrument information, such as account / card numbers and information. The account may be used to purchase items and / or transfer funds. The payment account may be accessed and / or used through a browser application and / or dedicated payment application.

[0051] However, in other embodiments, accounts may be used with POS device 130 for transaction and payment processing through digital wallets provided by POS device 130, such as by using digital wallet protocols and operations through token wallet 122 on user device 110. This may include use of digital tokens 114 through token wallet 122. Transaction processing application 142 may process a payment and may provide a transaction history for transaction authorization, approval, or denial. Computing services of transaction processing application 142 may also or instead correspond to messaging, social networking, media posting or sharing, microblogging, data browsing and searching, online shopping, and other services available through transaction processor 140.

[0052] In some embodiments during transaction processing, transaction processing application 142 may perform token processing 144 to process received tokens and / or application cryptograms for transactions being processed at POSdevices (e.g., POS device 130) by mobile devices (e.g., user device 110). In this regard, token processing 144 may include receiving the transaction data for the transaction with a digital token and / or application cryptogram. The data may be received from POS device 130, and the application cryptogram or other digital token data transmitted to POS device 130 by user device 110 may originate from user device 110. Transaction processing application 142 may then determine a balance, credit limit, and / or other funds available to the digital account of the user, as well as account data used to perform a real-time risk analysis, assessment, and check to approve, decline, or request additional data for the corresponding transaction. In this regard, an Al engine of transaction processing platform may be executed to calculate risk. Using the API calls with the payment and / or token processor network on network 150, devices (e.g., user device 110 and / or merchant, POS, or payment devices) and their corresponding transactions may be processed. Transaction processing application 142 may determine whether the transaction is authorized and then the transaction may be approved. However, if the transaction is not authorized, then transaction processing application 142 may be used to decline transaction processing or instruct a backend credit processor to decline processing of the transaction. Further, transaction processing application 142 may transmit a message to user device 110 and / or another device to notify the user of approval or denial of the transaction.

[0053] In various embodiments, transaction processing application 142 may include other applications as may be desired in particular embodiments to provide features to transaction processor 140. For example, transaction processing application 142 may include security applications for implementing server-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) over network 150, or other types of applications. Transaction processing application 142 may contain software programs, executable by a processor, including a graphical user interface (GUI), configured to provide an interface to the user when accessing transaction processor 140 via one or more of user device 110, where the user or other users may interact with the GUI to view and communicate information more easily. In various embodiments, transaction processing application 142 may include additional connection and / or communication applications, which may be utilized to communicate information to over network 150.

[0054] Additionally, transaction processor 140 includes database 146. Database 146 may store various identifiers associated with user device 110. Database 146 may also store account data, including payment instruments and authentication credentials, as well as transaction processing histories and data for processed transactions. Database 146 may store received data associated with a user, such as transaction data and spending limits on electronic transaction processing. Further, database 146 may be used to store data for accounts, which may be used for generating, storing, and / or transferring identifiers and / or tokens used with digital wallets and processing of transactions.

[0055] In various embodiments, transaction processor 140 includes at least one network interface component 148 adapted to communicate with user device 110, POS device 130, and / or one or more other devices / servers over network 150. In various embodiments, network interface component 148 may comprise a DSL (e.g., Digital Subscriber Line) modem, a PSTN (Public Switched Telephone Network) modem, an Ethernet device, a broadband device, a satellite device and / or various other types of wired and / or wireless network communication devices including microwave, radio frequency (RF), and infrared (IR) communication devices.

[0056] Network 150 may be implemented as a single network or a combination of multiple networks. For example, in various embodiments, network 150 may include the Internet or one or more intranets, landline networks, wireless networks, and / or other appropriate types of networks. Thus, network 150 may correspond to small scale communication networks, such as a private or local area network, or a larger scale network, such as a wide area network or the Internet, accessible by the various components of system 100.

[0057] FIGS. 2A and 2B are exemplary system environments 200a and 200b for establishing and utilizing operations for multi-token application functionality on user devices and merchant payment terminals, according to an embodiment. System environments 200a and 200b of FIGS. 2 A and 2B may correspond to different system environments showing interactions between devices, servers, and / or systems when providing multi-token application functionalities for token provision and processing, such as interactions between user device 110, POS device 130, and / or transaction processor 140 discussed in reference to system 100 of FIG. 1.

[0058] In system environment 200a of FIG. 2A, different interactions between an application 202 and a POS 204 are shown, which may be facilitated over short rangewireless communications and token processor networks 206 for token processing using different network channels, communications, and the like for corresponding processors. Initially, and prior to interfacing with POS 204, application 202 may establish one or more tokens on-device and / or accessible by the device during processing of electronic transactions, such as from an offline token management service 208 that may tokenize data for accounts, payment or financial instruments (e.g., payment cards, bank accounts, checks, etc.), and the like and store on-device for application 202 or with another service for quick access during electronic transaction processing.

[0059] Offline token management service 208 may create tokens and tokenize data with a token service provider (TSP), such as an issuance and tokenization platform 210. Issuance and tokenization platform 210 may correspond to a component of an online transaction processor and / or other payment processor, such as a full wallet platform 212, or may be a third-party TSP associated with such platform. In this regard, issuance and tokenization platform 210 may tokenize and provide card network token or a proprietary network token 214, which may correspond to tokenized data for a corresponding account and / or payment instrument that is to be used by application 202 with payment processing, such as to process an electronic transaction with POS 204. Offline token management service 208 may receive card network token or proprietary network token 214 for management of payment services and token data with application 202.

[0060] Issuance and tokenization platform 210 may generate, such as based on data account or payment instrument data for an account with the transaction processor, a proprietary token that allows processing on one of token processor networks 206 with full wallet platform 212, such as a full digital wallet token for a corresponding digital wallet of the account. Issuance and tokenization platform 210 may also interface with a credit card processor 216 to create a card network token, which allows for processing of such token over another one of token processor networks 206 and credit card processor 216. Thereafter, application 202 may be configured with multi-token processing capabilities with POS 204, such as to process the proprietary token over token processor networks 206 with full wallet platform 212 or process the card token over token processor networks 206 with credit card processor 216.

[0061] An example of the process and steps to establish payment tokens and process a payment, as discussed herein, using the components of system environment 200a is further shown in the numbered interactions of FIG. 2A. For example, offline token management service 208 may, at an interaction 1 , determine the correct tokens to issue to application 202, such as based on the default funding instrument. Offline token management service 208 may further manage token lifecycle, which may include refreshing and generating new tokens when needed. Offline token management service 208 then, at an interaction 2, reaches out over corresponding payment and token processor networks to issue the appropriate network tokens from issuance and tokenization platform 210 for card network token or proprietary network token 214. Further, at an interaction 3, full wallet platform 212 generates and provides an offline token as a representation of the full wallet for partner integrations. The full wallet token may also allow for offline token processing, for example, by providing data that may be validated and trusted by POS 204 without a network connection. At an interaction 4, offline token management service 208 passes both the full wallet token and network token(s) to be securely stored by application 202.

[0062] Thereafter, application 202 is set up for payment processing using digital tokens in a more widely available manner by enabling the functionality of application 202 with multiple tokens, POS devices, payment terminals, and token processor networks. As such, at an interaction 5, when application 202 interactions with POS 204, multiple tokens may be offered and utilized for payment processing. For example, a user may enter a store and use application 202 for a payment to POS 204, which has a designation to use the proprietary network token of PAYPAL® or other payment processor. POS 204 may detect that application 202 has invoked a payment flow for payment processing with POS 204 using a token and request a list of available tokens for application 202. Application 202 may respond with the list of available tokens during interaction 5, which allows POS 204 to select a most preferred token (e.g., the PAYPAL® token when preferred) that is compatible with the functionalities and networks available to POS 204. POS 204 may make this selection from application 202 and then read a digital token or generated application cryptogram of such token (e.g., a cryptogram generated by application 202 to secure pass the token to POS 204 for more secure processing) from application 202.

[0063] In other embodiments, both or all available tokens are passed with the preference for a particular token to POS device 204 in place of the list, allowing POSdevice 204 to select the token instead of reading a token or cryptogram made available by application 202. Further, if another funding source is selected, that may instead be preferred or ranked higher in such list or transmission of tokens to POS 204, and such token may be selected and / or read for processing. Thus, at an interaction 6a, if the POS is capable of processing the proprietary token of full wallet platform 212 (e.g., the full wallet token or the like, such as the PAYPAL® token), POS and corresponding merchant partner may submit the token as an API call to a payment processing platform. For example, during interaction 6a, a retail payments API of full wallet platform 212 may be used to receive the token from POS 204 after the NFC communications between application 202 and POS 204. In some embodiments, the API call may be structured similarly to a retail payment API call for a QR code scan or other in-store payment to a terminal and / or POS 204 connected with full wallet platform 212, however, since done during an NFC session and communications, may have corresponding risk and security protocols.

[0064] However, if another card network token, such as for a credit card is used, at an interaction 6b, the POS 204 processes such token through the card processor network. In such embodiments, an EMV encryption of real and / or stored credit card data (e.g., a credit card number and other information) may be used to pass an encrypted token and / or cryptogram to POS 204. POS 204 may then process the encrypted message as it would with a credit card, in which case full wallet platform 212 may not be invoked and used for payment processing but instead an integration with a payment card network, such as with credit card processor 216, may be used to process the transactions. In some embodiments, full wallet platform 212 may also be used to issue a virtual card first as a representation of a credit card and encrypt the virtual card using EMV encryption and guidelines, which may allow full wallet platform 212 to process the transaction.

[0065] Referring now to FIG. 2B, system environment 200b further shows how application 202, on user device 110, may interact with POS 204 using multi-token application functionality to allow for token processing using different tokens that are compatible and supported by POS 204. User device 110 may execute application 202, which may be used to interface with POS 204 via an NFC controller 222 and short- range wireless communication 224. Application 202 may include various components to generate an indication that application 202 is available for token processing for a payment via short-range wireless communication 224. Initially, application 202 mayinteract with services 228 of transaction processor 140 for token generation and provisioning with application 202. For example, a token SDK may interact with a token service of services 228, which may generate and / or provision tokens. In some embodiments, additional services may be invoked, such as a payment service for payment instrument processing, which may also be used later during issuance of payments.

[0066] Token SDK on application 202 may interact with an NFC SDK to generate and provide an NFC token that may be provided to POS 204 via NFC controller 222 through short-range wireless communications 224. Optionally, application 202 may also include a loyalty SDK or the like to provision loyalty information from a loyalty service or the like of services 228, which may also be used with an NFC SDK or other SDK for short-range wireless communications 224 for token generate and / or provision during processing with POS 204. As such, loyalty cards may also be provided to the NFC SDK, which can be provided to POS 204 in a similar manner to the NFC token. As such, at a time of processing of an electronic transaction, data for the NFC token and the like may be exchanged between application 202 and POS 204, such as a list of available tokens, token usage preferences, and a selected digital token, application cryptogram for such token, or the like. The details for token exchange between application 202 and POS 204 are discussed in further detail below with regard to FIGS. 3A-3C.

[0067] A gateway 226 may receive a digital token, application cryptogram, or the like to process a corresponding transaction. Gateway 226 may correspond to a processing gateway on a payment and / or token processor network, which may route data for processing with a backend and payment issuance. In this regard, where a proprietary token may be used for transaction processor 140, gateway 226 on a corresponding token processor network may provide the proprietary token to transaction processor 140 for processing. For example, the token may be provided to a retail pay service of services 228, which may process the token using received transaction data and a corresponding account or payment instrument. A payment service of services 228 may also be used for payment issuance. However, with a token for a payment card (e.g., credit card) and card processor network that was provided to POS 204 by application 202, gateway 226 may transmit the card token to a processor 230, such as a credit card processor backend or system for other type of payment card. Such card token may correspond to a payment card, such as an EMV and / or magneticstripe credit or debit card. As such, the token may correspond to an EMV card token from reading an EMV chip.

[0068] FIGS. 3A-3C are exemplary diagrams 300a-300c for digital token identification and exchange between user devices and payment terminals when providing multi-token application functionality, according to an embodiment. In this regard, diagrams 300a-300c demonstrate how the components and systems in system 100 of FIG. 1 may interact to process data. The interactions between user device 110, POS device 130, and transaction processor 140 may be used to provide a digital token through multi-token application functionalities for wireless and contactless payment processing and systems. For example, diagram 300a shows an example of how user device 110 and POS device 130 may interact to exchange calls, messages, requests, and responses for digital token processing through multi-token application functionalities on user device 110.

[0069] In diagram 300a, initially, a user may utilize a software application, such as payment application 120 or other payment card and / or account application for processing electronic transactions, on user device 110 to interact with POS device 130 during an interaction 302. An NFC / RFID component or other transceiver configured for short-range wireless communications and contactless data transfer (e.g., contactless payments via digital tokens) may connect over a short-range wireless communication protocol and signals, where an indication, ping, or the like may be sent to POS device 130 to signal the availability of user device 110 for interacting. This may include POS device 130 detecting that a “card” is available, where the card may correspond to a digital token for an account, payment instrument, or the like that may be read and processed in a similar manner to a payment card payment and processing.

[0070] At an interaction 304, POS device 130 and user device 110 may interact to determine supported “card applications” or digital tokens for payment instruments that may mimic or be created to imitate available payment cards and software applications that process payments using tokens for such payment cards (e.g., a VISA® card application). This request may be setup and optimized using an SDK that provides a directory on POS device 130 that allows POS device 130 to quickly determine what the available tokens or other applications for transaction processing are instead of polling against all known and available tokens / applications. User device 110 may respond to the request with a prioritized list of the digital tokens availablefor processing with user device 110. Further, user device 110 may prioritize the list based on preferences and the like that may be set with the different digital tokens and / or token processor networks for such tokens. This may be used to create a prioritized, ranked, or ordered list to POS device 130 by user device 110. In some embodiments, an online transaction processor providing the token and / or digital wallet service may provide such processes to generate and prioritize the list of tokens for token processing.

[0071] At an interaction 306, POS device 130 may select from the list a particular digital token and / or token processor network. POS device 130 may select a “best match,” where best match may be based on the preferences, processing costs, and / or enabled software processes for an SDK and token processor networks. This may be transmitted by POS device 130 to user device 1 10, which may then determine the selected token from POS device 110. The selection may be based on various parameters, data processing and network capabilities of POS device 130. User device 110 may then respond with a ‘File Control information’ template for the stored and / or available digital tokens, as well as a “Processing Options Data Object List.” The Processing Options Data Object List may correspond to the data and / or data processing requirements of the corresponding digital token, which allows for POS device 130 to proceed with transaction processing by determining required data from user device 110 and POS device 130 for the processing request (e.g., transaction processing request and operations with the token processor network). Thus, POS device 130 may be responsible for (either automatically by the device or manually from user input) selecting the token available from user device 110 for processing.

[0072] At an interaction 308, POS device 130 may proceed with transaction processing, where POS device 130 may obtain processing operations and data object list data from user device 110. User device 110 may respond with a token, application, or other file locator or other information indicating how POS device 130 may read a record for the selected digital token. POS device 130, at an interaction 310, then uses the data to read a record for the digital token from user device 110. This may include requesting to read data from a local data storage or cache, which may be accessible and readable using short-range wireless signaling and an antenna or transceiver on user device 110. The read data may include the token, and at an interaction 312, an application cryptogram and other data is generated, such as by the application on user device 110 using encryption keys, transaction data, and the like, 1which allows an issuer of the digital token to validate the token use and authorization by user device 110 during an authentication process. Thus, the digital token and / or application cryptogram may be used then for transaction processing. The application cryptogram may correspond to a secure encrypted payload that is constructed from a unique identifier for the user device, chosen funding instrument, and other security factors. Such security factors may include a time-based one-time password or other secret, and may be seeded for encryption using optional information for data security and privacy. Further cryptogram seeding may include using an unpredictable number, transaction currency, amount authorized, transaction date, transaction time, merchant identifier, terminal transaction qualifier, or the like.

[0073] Referring now to FIG. 3B, diagram 300b shows how user device 110 may interact with POS device 130 for online token processing 320 with transaction processor 140. The operations and processing flow in diagram 300b for online token processing 320 may occur when POS device 130 has network connectivity with transaction processor 140 at a time of receiving a selected digital token from user device 110. As such, diagram 300b may include operations discussed in reference to diagram 300a for use during network connectivity for online processing of electronic transactions.

[0074] In diagram 300b, user device 110 may initiate operations during a transaction initiation 322 with POS device 130. For example, user device 110 may connect with POS device 110 and / or transmit a ping or other indication over short- range wireless communications to POS device 130. Additionally, or alternatively, a user, such as a merchant or merchant employee, may use POS device 130 to start transaction initiation 322. POS device 130 may respond with a token polling 324 to user device 1 10, during which, POS device 130 may request a list, information for, and / or an indication of one or more digital tokens available from user device 110 for processing with POS device 130. This may include tokens and token processing operations (e.g., available token processor networks) that are usable with an application on user device 110, such as payment application 120. These may include on-device tokens and / or tokens available to user device 110.

[0075] Based on token polling 324, user device 110 may respond with a list and preference 326, which may be previously generated and stored by or on user device 110 and / or generated responsive to POS device 130 performing token polling 324. In this regard, list and preference 326 may include all available digital tokens that maybe used with POS device 130, as well as any preferences, rankings, or order for use of the digital tokens. For example, a user, such as a customer, may select certain digital tokens, payment instruments, and / or associated payment processors or financial institutions that the user prefers to utilize when processing electronic transactions, such as providing in-person payments to POS device 130 via short-range wireless communications. Such preferences may be used to indicate which tokens are to be used and in what order. However, the list for list and preference 326 may further include information for other available tokens so that fallback tokens may be used when a token processor network and / or token processing operations for the preferred token(s) are not available and / or supported with POS device 130.

[0076] In this regard, an SDK of an online transaction processor may be used to configure the application on user device 1 10, such as payment application 120, to facilitate the interactions between the application and POS device 130. The tokens may correspond to a proprietary token of the online transaction processor, such as a single offline payment of a set number of digits (e.g., alphanumeric characters), which may include a unique identifier for user device 110 and a chosen payment instrument so that payment processing may be effectuated using transaction processor 140. Further, the proprietary token may ensure data privacy, and for offline data processing, may further include additional payloads such as an issue certificate, issuer signature, transaction certificate signature, creation timestamp, and the like. The additional payload for a digital token usable in offline processing environments may include such payload to further validate and approve transactions where POS device 130 may not have network connectivity and / or connectivity to transaction processor 140, as discussed in further detail with regard to diagram 300c.

[0077] During a token selection 328, POS device 130 may analyze list and preference 326 to select a token based on the list, preference(s) or the like, and supported functionalities of POS device 130, such as connectable token processor networks and token reading / processing operations for POS device 130. Selection may include requesting the digital token from user device 110, which may result in user device 110 transmitting the digital token to POS device 130 or making the digital token readable from a memory and transceiver of user device 110 (e.g., over short- range wireless communications, such as an NFC / RFID reading of user device 110 by a corresponding component of POS device 130). During or after reading or receiving the digital token, a cryptogram generation 330 may be performed to generate anapplication and / or token cryptogram or the like by user device 110 with POS device 130 that validates use of the digital token and a payment to be made via the digital token when POS device 130 processes the transaction using the digital token with transaction processor 140. As such, the application cryptogram may be seeded and / or generated between user device 110 and POS device 130 using information including an unpredictable number (e.g., a value providing variability and uniqueness to cryptogram generation), a transaction currency, an amount authorized, a transaction date, a transaction time, a merchant identifier, and / or one or more terminal transaction qualifiers.

[0078] During online token processing, POS device 130 may then communicate with transaction processor 140, such as over a network connection and using a token processor network including components and processor for token processing with transaction processor 140, to process a payment request 332. The payment request 332 may include transaction information, a digital token, and / or an application cryptogram for processing and authorization of payment to POS device 130. Transaction processor 140 may respond with a response 334, such as an approval or denial of the transaction or a request for additional data based on the provided data and corresponding funds available for transaction processing using the digital token. Thereafter, POS device 130 may communicate with user device 110 to communicate and process a transaction processing completion 336, which may provide a receipt or other transaction history documenting the transaction processing.

[0079] Referring now to FIG. 3C, diagram 300c shows how user device 110 may interact with POS device 130 for offline token processing with transaction processor 140. The operations and processing flow in diagram 300c for offline token processing may occur when POS device 130 does not have network connectivity with transaction processor 140 at a time of receiving a selected digital token from user device 110. As such, diagram 300c may include operations discussed in reference to diagram 300a for use during asynchronous and offline processing of electronic transactions by validating the digital token without connectivity to transaction processor 140.

[0080] In diagram 300c, the steps and interactions may proceed similarly to diagram 300b up to cryptogram generation 330, and thus, user device 110 and POS device 130 may, during offline token processing, interact to perform and process transaction initiation 322, token polling 324, exchange of list and preference 326, token selection 328, and cryptogram generation 330. However, after cryptogramgeneration 330, diagram 300c may differ during offline token processing due to the lack of network connectivity of POS device 130 with transaction processor 140. In this regard, POS device 130 may be operating in an offline mode and / or without sufficient network connectivity with transaction processor 140. As such, the token (as well as cryptogram) provided to POS device 130 for transaction processing may be configured to allow for offline data and transaction processing, including being capable of approving or denying the transaction in the offline environment of POS device 130 (e.g., with a connection with the token processor network and transaction processor 140).

[0081] As such, during a transaction processing 342, user device 110 and POS device 130 may interact to negotiate an approval offline of the electronic transaction. This may be based on the offline token, which may include data and parameters to authorize offline transaction processing (e.g., a token / payment instrument validation data object or the like, as well as parameters for approval including time limitations, approval and / or amount limits, and the like). The offline token may also include presigned authorization that enables offline transaction processing. The pre-signed authorization may be signed using an encryption key and may be verified using a downloaded key repository on POS device 130.

[0082] Thereafter, asynchronously from transaction processing 342 (e.g., at a later time, such as when network connectivity is restored and / or transaction processing of stored offline transaction data is performed), an asynchronous token processing 344 between POS device 130 and transaction processor 140 may occur. Asynchronous token processing 344 may include providing the offline digital token, application cryptogram, and / or transaction data to transaction processor 140 to effectuate a payment to POS device 130 and / or corresponding account. Transaction processor 140 may provide a response 346, such as an approval or denial and proof of payment or reason for non-payment. Optionally, POS device 130 may then provide a notification 348, such as an email, text message, or the like to user device 110 to inform the user that the transaction has been approved or denied, as well as proceed with other transaction processing or completion steps.

[0083] FIG. 4 is a flowchart 400 of an exemplary process for multi-token application functionality for wider availability of digital token processing. Note that one or more steps, processes, and methods described herein of flowchart 400 may be omitted, performed in a different sequence, or combined as desired or appropriate.Flowchart 400 of FIG. 4 includes operations the system performs for providing multitoken application functionality with POS devices and payment terminals, as discussed in reference to FIGS. 1-3C above. One or more of steps 402-412 of flowchart 400 may be implemented, at least in part, in the form of executable code stored on non- transitory, tangible, machine-readable media that when run by one or more processors may cause the one or more processors to perform one or more of steps 402-412. In some embodiments, flowchart 400 may be performed by one or more computing devices, servers, and / or components discussed in system 100 of FIG. 1.

[0084] At step 402 of flowchart 400, an indication that a user device is available to process a payment is received at a POS device through short-range wireless or other communications with the POS device. The request may be received via a software application and component (e.g., NFC sales application 1 2) of POS device 130 from user device 110, such as a mobile smart phone, wearable device, portable tablet or laptop, or the like, based on use of token wallet 122 of payment application 120 to process an electronic transaction using one of digital tokens 114. Such processing may be done by application 202 interacting with POS 204 to exchange a card network token or proprietary network token 214 that may be processed by issuance and tokenization platform 210 and / or credit card processor 216. The indication may be transmitted over short-range wireless communications, such as when the user device is brought within a wireless proximity range or distance of the POS device.

[0085] At step 404, a list of available digital tokens for payment processing between the mobile device and the POS device is requested. The list may correspond to an ordering, ranking, or the like of digital tokens 114, such as by token wallet 122 based on preferences for token services 124, which may be requested from and generated by payment application 120 of user device 110. POS device 130 may perform the requesting over short-range wireless communications, such as using NFC sales application 132. For example, in response to pinging or connecting with POS 204 by application 202, POS 204 may respond with the request to application 202, which may then determine the list using on-device and / or server-side data for token availability and / or token preferences.

[0086] At step 406, the list is received at the POS device with a token prioritization of the available digital tokens. In accordance with the above examples, NFC sales application 132 of POS device 130 may receive the list of digital tokens114 from payment application 120 of user device 110, such as over short-range wireless communications. Payment application 120 may generate the list to have an order, ranking, or the like based on preferences for use of different tokens and / or token processors, such as an online transaction processor (e.g., PAYPAL®) for a digital payment account over a physical payment card and card processor gateway, or the list may come with the preference(s) for digital token selection. The list may include all or some available digital tokens for processing. For example, application 202 may respond to POS 204 over short-range wireless communications with data indicating a list of and preferences for card network token or proprietary network token 214. As such, application 202 may provide multiple tokens and their availability to POS 204 so that a preferred token may be provided for use, but a fallback token may also be made available to ensure data processing proceeds where POS 204 is unable to process the preferred token. The processes to generate this list and provide to POS 204 may be configured in application 202 using an SDK provided by an online transaction processor or the like.

[0087] At step 408, a digital token from the available digital tokens is selected based on the token prioritization and supported functionalities for payment processing of tokens at the POS device. NFC sales application 132 may make a selection of digital token 134 from a list of, with preferences for, digital tokens 114 from user device 110. For example, POS 204 may include operations to select a token from the provided list based on the supported functionalities of POS 204, as well as the preferences provided by application 202 with the list. The supported functionalities may include configured SDK processes and capabilities, API integrations for API calls, requests, and responses.

[0088] At step 410, an application cryptogram is generated for the digital token. Payment application 120 may generate the application cryptogram for transfer using NFC processes 126 to POS device 130 based on the selection of digital token 134 using token services 124 and / or payment services 128, as well as required encryption schema and keys. Thus, application 202 may generate the cryptogram for POS 204, where application 202 may generate the cryptogram on device or using an online platform. After generating, the cryptogram may be made available to POS device 130 and / or transmitted to POS device 130. For example, the cryptogram or other data for digital token 134 may be stored in a readable form and component for reading by POS device 130. For example, an NFC / RFID module of network interface component 1 16with a readable memory and transceiver (e.g., a passive or active antenna) may be utilized by user device 110 to allow POS device 130 to read a record, data file, or the like associated with digital token 134 and / or the application cryptogram (e.g., via a file locator). In some embodiments, a bar or QR code may be generated having encoded having the digital token or cryptogram for displaying and reading, or other readable medium may be encoded with or store the cryptogram or other data.

[0089] At step 412, the application cryptogram is processed for the payment. NFC sales application 132 may then process digital token 134, or other data such as an application cryptogram or the like generated for digital token 134, with transaction processor 140 over network 150 or over another token processor network. For example, POS 204 may communicate with full wallet platform 212 or credit card processor 216 over token processor networks 206 for processing of application cryptogram and / or corresponding digital token. Full wallet platform 212 or credit card processor 216 may be selected for processing of the electronic transaction based on the received digital token and token / token processor network preference, which may then lead to an approval or denial of the transaction and corresponding payment, transaction rejection, and transaction history generation.

[0090] As discussed above and further emphasized here, flowchart 400 of FIG. 4 may be performed by / via user device 110 and / or POS device 130 from system 100 when processing digital tokens from multi-token application functionalities with such tokens, which examples should not be used to unduly limit the scope of the claims. One of ordinary skill in the art would recognize many variations, alternatives, and modifications.

[0091] FIG. 5 is a block diagram of a computer system 500 suitable for implementing one or more components in FIG. 1 , according to an embodiment. For example, computer system 500 may correspond to user device 110, POS device 130, and / or one or more servers of transaction processor 140, which may be used for executing steps 402-412 in flowchart 400 of FIG. 4. In various embodiments, computer system 500 may comprise a personal computing device (e.g., smart phone, a computing tablet, a personal computer, laptop, a wearable computing device such as glasses or a watch, Bluetooth device, key FOB, badge, etc.) capable of communicating with the network. A service provider may utilize a network computing device corresponding to computer system 500 (e.g., a network server) capable of communicating with the network. It should be appreciated that each of thedevices utilized by users and service providers may be implemented as computer system 500 in a manner as follows.

[0092] Computer system 500 includes a bus 502 or other communication mechanism for communicating information data, signals, and information between various components of computer system 500. Components include an input / output (I / O) component 504 that processes a user action, such as selecting keys from a keypad / keyboard, selecting one or more buttons, image, or links, and / or moving one or more images, etc., and sends a corresponding signal to bus 502. I / O component 504 may also include an output component, such as a display 511 and a cursor control 513 (such as a keyboard, keypad, mouse, etc.). An optional audio input / output component 505 may also be included to allow a user to use voice for inputting information by converting audio signals. Audio I / O component 505 may allow the user to hear audio. A transceiver or network interface 506 transmits and receives signals between computer system 500 and other devices, such as another communication device, service device, or a service provider server via network 150. In one embodiment, the transmission is wireless, although other transmission mediums and methods may also be suitable. One or more processors 512, which can be a micro-controller, digital signal processor (DSP), or other processing component, processes these various signals, such as for display on computer system 500 or transmission to other devices via a communication link 518. Processor(s) 512 may also control transmission of information, such as cookies or IP addresses, to other devices.

[0093] Components of computer system 500 also include a system memory component 514 (e.g., RAM), a static storage component 516 (e.g., ROM), and / or a disk drive 517. Computer system 500 performs specific operations by processor(s) 512 and other components by executing one or more sequences of instructions contained in system memory component 514. Logic may be encoded in a computer readable medium, which may refer to any medium that participates in providing instructions to processor(s) 512 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. In various embodiments, non-volatile media includes optical or magnetic disks, volatile media includes dynamic memory, such as system memory component 514, and transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprise bus 502. In one embodiment, the logic is encoded in non-transitory computer readable medium. In one example, transmission media maytake the form of acoustic or light waves, such as those generated during radio wave, optical, and infrared data communications.

[0094] Some common forms of computer readable media includes, for example, floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, CD- ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EEPROM, FLASH- EEPROM, any other memory chip or cartridge, or any other medium from which a computer is adapted to read.

[0095] In various embodiments of the present disclosure, execution of instruction sequences to practice the present disclosure may be performed by computer system 500. In various other embodiments of the present disclosure, a plurality of computer systems 500 coupled by communication link 518 to the network (e.g., such as a LAN, WLAN, PTSN, and / or various other wired or wireless networks, including telecommunications, mobile, and cellular phone networks) may perform instruction sequences to practice the present disclosure in coordination with one another.

[0096] Where applicable, various embodiments provided by the present disclosure may be implemented using hardware, software, or combinations of hardware and software. Also, where applicable, the various hardware components and / or software components set forth herein may be combined into composite components comprising software, hardware, and / or both without departing from the spirit of the present disclosure. Where applicable, the various hardware components and / or software components set forth herein may be separated into sub-components comprising software, hardware, or both without departing from the scope of the present disclosure. In addition, where applicable, it is contemplated that software components may be implemented as hardware components and vice-versa.

[0097] Software, in accordance with the present disclosure, such as program code and / or data, may be stored on one or more computer readable mediums. It is also contemplated that software identified herein may be implemented using one or more general purpose or specific purpose computers and / or computer systems, networked and / or otherwise. Where applicable, the ordering of various steps described herein may be changed, combined into composite steps, and / or separated into sub-steps to provide features described herein.

[0098] The foregoing disclosure is not intended to limit the present disclosure to the precise forms or particular fields of use disclosed. As such, it is contemplated thatvarious alternate embodiments and / or modifications to the present disclosure, whether explicitly described or implied herein, are possible in light of the disclosure. Having thus described embodiments of the present disclosure, persons of ordinary skill in the art will recognize that changes may be made in form and detail without departing from the scope of the present disclosure. Thus, the present disclosure is limited only by the claims.

Claims

CLAIMSWHAT IS CLAIMED IS:

1. A system comprising: a non- transitory memory; and one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising: receiving an indication to perform a processing of an electronic transaction with an application on a user device through short-range wireless communications; requesting, via the short-range wireless communications, a list of available digital tokens for the processing of the electronic transaction using the application on the user device; receiving, via the short-range wireless communications, the list from the user device with a preference associated with one or more of the available digital tokens in the list, wherein the preference prioritizes a first token processor network of at least two token processor networks for the one or more of the available digital tokens over a second token processor network; selecting a digital token from the list of the available digital tokens based on a supported functionality of the system and the preference, wherein the supported functionality indicates one or more of the at least two token processor networks is connectable with the system for the processing of the electronic transaction; reading, via the short-range wireless communications, a token record for the digital token from the application on the user device; and receiving, via the short-range wireless communications based on the reading, an application cryptogram from the application for the processing of the electronic transaction using the digital token.

2. The system of claim 1 , wherein the receiving the list comprises receiving a prioritized designation of a plurality of payment card applications corresponding to the available digital tokens, and wherein the selecting the digital token is performedbased on the prioritized designations and the supported functionality indicating the one or more of the at least two token processor networks connectable to the system.

3. The system of claim 1 , wherein the system corresponds to or includes a point- of-sale (POS) device, and wherein the operations further comprise: processing the electronic transaction using the application cryptogram with an online transaction processor.

4. The system of claim 3, wherein the processing is performed asynchronously and the application cryptogram is generated in an offline mode of the system, wherein the application cryptogram includes the digital token with a pre-signed authorization from the online transaction processor associated with processing the digital token for at least the electronic transaction, and wherein the operations further comprise: verifying the pre-signed authorization.

5. The system of claim 1 , wherein, prior to the receiving the indication, the operations further comprise: performing a setup of the system with an online transaction processor for processing the digital token using a software development kit (SDK) provided by the online transaction processor, wherein the performing includes: establishing, using the SDK, a connection with a token processor network for the online transaction processor, and establishing, using the SDK, a process to recognize the digital token and the preference for processing with the online transaction processor.

6. The system of claim 1 , wherein the preference selects an online transaction processor on the first token processor network for processing the digital token in place of a payment card token.

7. The system of claim 1, wherein the digital token is associated with the first token processor network and an account of a user corresponding to the user device with an online transaction processor, and wherein the first token processor network includes the online transaction processor that provides digital payments using the account of the user.

8. The system of claim 1 , wherein the second token processor network comprises a payment card network for tokenized payment card data.

9. The system of claim 1 , wherein the application cryptogram comprises transaction data and the digital token signed using a key associated with an online transaction processor on the first token processor network, and wherein the operations further comprise: exchanging the application cryptogram on one of the at least two token processor networks for the processing of the electronic transaction.

10. The system of claim 1 , wherein the first token processor network is selected with the digital token in response to the supported functionality indicating an SDK established process for the processing of the electronic transaction using the application cryptogram.

11. A user device system comprising: a non- transitory memory; and one or more hardware processors coupled to the non- transitory memory and configured to read instructions from the non-transitory memory to cause the user device system to perform operations comprising: transmitting, via short-range wireless communications, an indication to perform a processing of an electronic transaction with an application on the user device system with a point-of-sale (POS) device; receiving, via the short-range wireless communications, a request for payment data for the processing of the electronic transaction through the application; determining, from the application, a preference for a use of a first token processor network for the processing of the electronic transaction; determining a list of at least two digital tokens for the processing of the electronic transaction on a corresponding one of at least two token processor networks via the application, wherein the list prioritizes a digital token of the at least two digital tokens that corresponds to the first token processor network based on the preference;transmitting, responsive to the request for the payment data via the short-range wireless communications, the list to the POS device; in response to the POS device selecting the digital token based on a supported functionality of the POS device and the preference, providing a file locator for a token record associated with the digital token to the POS device; and generating an application cryptogram for the processing of the electronic transaction by the POS based on the digital token and the electronic transaction.

12. The user device system of claim 11 , wherein the transmitting comprises returning a list comprising a plurality of available digital tokens with the application and prioritization of the plurality of available digital tokens in the list for the processing of the electronic transaction, wherein the prioritization selects the digital token over other digital token in the list for use with an online transaction processor providing a digital payment account associated with the digital token, and wherein the preference is based on the prioritization.

13. The user device system of claim 12, wherein, prior to the transmitting, the operations further comprise: establishing the digital token for the digital payment account with the application and the prioritization in the application.

14. The user device system of claim 11 , wherein the digital token is provisioned for an offline mode of at least the POS device, and wherein the digital token is preloaded on the user device system prior to the electronic transaction.

15. The user device system of claim 14, wherein the generating comprises providing a pre-signed authorization for the processing of the electronic transaction using the digital token, wherein the pre-signed authorization is loaded on the user device system prior to the electronic transaction, and wherein the pre-signed authorization is verifiable using a key repository available to the POS device in the offline mode.

16. The user device system of claim 11 , wherein the preference designates the use of the first token processor network corresponding to an online transaction processor for the processing of the electronic transaction using a digital payment account identified by the digital token.

17. The user device system of claim 16, wherein the preference prioritizes the online transaction processor over a card processor corresponding to a second token processor network.

18. A non-transitory machine-readable medium having stored thereon machine- readable instructions executable to cause a machine to perform operations comprising: generating, by a point-of-sale (POS) device, an electronic transaction for processing with a user device; requesting, via short-range wireless communications with the user device, that a digital token be provided from an application on the user device for processing of the electronic transaction; receiving, via the short-range wireless communications, a list from the user device, wherein the list indicates at least two digital tokens available from the application for processing on a corresponding one of at least two token processor networks, and wherein the list includes a preference for one of the at least two token processor networks for processing the electronic transaction; determining, by the POS device, a supported functionality with the one of the at least two token processor networks based on the preference, wherein the supported functionality indicates the one of the at least two token processor networks is connectable to the POS device; determining one of the at least two digital tokens for processing of the electronic transaction on the one of the at least two token processor networks; selecting the one of the at least two digital tokens from the list of the available digital tokens based on the supported functionality and the preference; reading, via the short-range wireless communications, a token record for the one of the at least two digital tokens from the application on the user device; and receiving, via the short-range wireless communications, an application cryptogram from the application for the processing the electronic transaction using the one of the at least two digital tokens.

19. The non- transitory machine-readable medium of claim 18, wherein the supported functionality is based on an onboarding of the POS device with an online transaction processor using a software development kit (SDK) for token processing operations on the POS device and account establishment of a merchant digital account for the POS device with the online transaction processor.

20. The non- transitory machine-readable medium of claim 18, wherein the one of the at least two digital tokens is associated with a user digital account of a user corresponding to the user device with an online transaction processor instead of card tokenized data for a payment card.

Images