Access server system and methods for mapping and coupling of digital assets
Patent Information
- Application Number
- HK62026125193
- Authority / Receiving Office
- HK · HK
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-07-24
- Filing Date
- 2026-06-23
- Publication Date
- 2026-09-11
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
(19) State Intellectual Property Office (12) Invention Patent Application (10) Application Publication Number (43) Application Publication Date (21) Application Number 202480046095.2 (22) Application Date 2024.07.18 (30) Priority Data 18 / 225,265 2023.07.24 US (85) PCT International Application Entering National Phase Date 2026.01.08 (86) PCT International Application Application Data PCT / SG2024 / 050461 2024.07.18 (87) PCT International Application Publication Data WO2025 / 023886 EN 2025.01.30 (71) Applicant Mastercard Asia Pacific Pte Ltd Address Singapore (72) Inventors P.A. Ghanapati K. Cheng P.H.L. Lee (74) Patent Agency China Council for the Promotion of International Trade Patent & Trademark Office Co., Ltd. 11038 Patent Attorney Gao Xin (51) Int.Cl. G06F 16 / 27 (2006.01) G06F 21 / 62 (2006.01) G06Q 20 / 36 (2006.01) H04L 9 / 32 (2006.01) (54) Invention Title Access Server System and Method for Mapping and Coupling of Digital Assets (57) Abstract This document discloses various implementations of establishing rights using smart contracts and digital wallets. In one implementation, a card corresponding to a consumer and a blockchain wallet account address can be mapped by an access server, wherein the access server is configured to access mapping service contracts, and wherein the card includes at least one of the consumer's associated Personal Account (PAN) and Electronic Application Identifier (eAid). Claims 2 pages, Description 15 pages, Drawings 22 pages, CN 121488231 A 2026.02.06 CN 1 21 48 82 31 A 1. A method comprising: mapping a card corresponding to a consumer and a blockchain wallet account address by an access server, wherein the access server is configured to access a mapping service contract, and wherein the card includes at least one of a consumer's Personal Account (PAN) and an Electronic Application Identifier (eAid). 2. The method of claim 1, wherein the card mapping is performed prior to a digital asset transaction. 3. The method of claim 2, further comprising: coupling a digital wallet to an issuer's computer system by a consumer device associated with the consumer, wherein the coupling of the digital wallet includes associating the consumer's Personal Account (PAN) with the digital wallet. 4. The method of claim 3, further comprising: generating one or more asset contracts corresponding to a corresponding digital asset on a blockchain by a merchant's computer system.5. The method of claim 4, wherein the corresponding digital asset includes: a non-fungible token (NFT), a semi-fungible token (SFT), or a token. 6. The method of claim 4, further comprising: listing the one or more asset contracts on the blockchain in a digital marketplace by a merchant computer system. 7. The method of claim 6, further comprising: obtaining the one or more asset contracts by a consumer via a consumer device, wherein the one or more assets are configured to be stored on a digital wallet. 8. The method of claim 1, wherein the card mapping is performed concurrently with the digital asset transaction. 9. The method of claim 8, further comprising: providing a blockchain wallet account address to the merchant computer system by a consumer device associated with the consumer to map at least one of the consumer's Personal Account (PAN) and Electronic Application Identifier (eAid) to the merchant computer system. 10. The method of claim 8, further comprising: coupling the card to an asset verifier terminal by the consumer. 11. The method of claim 10, further comprising: processing the Personal Account (PAN) or Electronic Application Identifier (eAid) from the card by the asset verifier terminal; and generating a hashed PAN. 12. The method of claim 11, further comprising: requesting, from an asset verifier terminal, one or more digital assets associated with a hashed PAN or electronic application identifier stored on an access server via a mapping service contract. 13. The method of claim 12, further comprising: searching for the one or more digital assets using a blockchain wallet account address by the access server. 14. The method of claim 13, further comprising: verifying the one or more digital assets by the access server. 15. The method of claim 11, wherein the one or more digital assets include: non-fungible tokens (NFTs), semi-fungible tokens (SFTs), or tokens. 16. The method of claim 15, wherein the one or more digital assets include NFTs or SFTs corresponding to loyalty profiles. 17. The method of claim 1, wherein the card is a chip card corresponding to Europay, Mastercard, or Visa (EMV) cards. Claims 1 / 2 Page 2 CN 121488231 A 18. The method of claim 1, wherein the card is configured for presentation via a mobile device, wearable device, or contactless EMV card. 19. A method comprising: coupling a digital wallet to an issuer computer system via a consumer device associated with a consumer, wherein the coupling of the digital wallet includes associating the consumer’s Personal Account (PAN) or Electronic Application Identifier (eAid) with the digital wallet.20. A method comprising: providing a blockchain wallet account address from a consumer device associated with a consumer to a merchant computer system to map at least one of the consumer's Personal Account (PAN) and Electronic Application Identifier (eAid) to the merchant computer system. Claims 2 / 2 Page 3 CN 121488231 A Access Server System and Method for Mapping and Coupling Digital Assets Background Art
[0001] This section is intended to provide background information to facilitate a better understanding of the various techniques described herein. As the title of this section implies, this is a discussion of related techniques. Such techniques are related and in no way imply that they are prior art. Related techniques may or may not be prior art. Therefore, it should be understood that the statements in this section should be read in this context and should not be considered as an admission of prior art.
[0002] The global pandemic has required a reassessment of how people interact and conduct business. Contactless experiences will become the new normal in the post-COVID world. Current solutions are not entirely end-to-end and use separate tools for identity, payment, and access.
[0003] For example, current ticket verification processes utilize manual checks of images or QR code scans. However, such document verification processes are often error-prone and can be forged. Therefore, there is a need in the art for a system that can provide seamless and secure document or voucher verification, which will prevent scalping and be “copy-proof.” Summary of the Invention
[0004] This document describes various implementations of establishing interests using smart contracts and digital wallets (e.g., crypto wallets). In one implementation, a card (e.g., an EMV card or chip card) corresponding to a consumer and blockchain wallet account address can be mapped by an access server (i.e., an access system) (e.g., Mastercard EZaccess), wherein the access server is configured to securely access a mapping service contract (i.e., a mapping service contract, a smart contract protocol) (e.g., the Mastercard EZaccess NFT protocol), and wherein the card includes at least one of the consumer’s (associated) Personal Account (PAN) (e.g., a payment card number) and Electronic Application Identifier (e.g., Mastercard EzAccess ID).
[0005] In one embodiment, a digital wallet can be coupled to an issuer's computer system via a consumer device associated with the consumer, wherein the coupling of the digital wallet includes associating the consumer's Personal Account (PAN) or Electronic Application Identifier (e.g., Mastercard EzAccess Id) with the digital wallet.
[0006] In one embodiment, a blockchain wallet account address may be provided to a merchant computer system by a consumer device associated with the consumer to map at least one of the consumer's Personal Account (PAN) and Electronic Application Identifier (e.g., Mastercard EzAccess Id) to the merchant computer system.
[0007] The above-referenced Summary section is provided to introduce, in simplified form, a series of concepts further described in the Detailed Description section below. Additional concepts and various other embodiments are also described in the Detailed Description. The Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter or the number of inventions described herein. Furthermore, the claimed subject matter is not limited to embodiments that address any or all of the disadvantages pointed out in any part of this disclosure. Brief Description of the Drawings
[0008] Embodiments of various techniques will be described below with reference to the accompanying drawings. However, it should be understood that the drawings are merely illustrative of the various embodiments described herein and are not intended to limit the scope of the various techniques described herein.
[0009] FIG1 illustrates a system for providing identity, payment, and access services according to embodiments of the various techniques described herein. Specification 1 / 15 Page 4 CN 121488231 A
[0010] Figure 2 illustrates a system having a service provider and an identifier provider according to embodiments of the various technologies described herein.
[0011] Figure 3 illustrates a system for generating a hashed master account (PAN) according to embodiments of the various technologies described herein.
[0012] Figure 4 illustrates a system for mapping and coupling digital assets according to embodiments of the various technologies described herein.
[0013] Figure 5 illustrates an example method that can be implemented using system 400 according to embodiments of the various technologies described herein.
[0014] Figure 6 illustrates an example method that can be implemented using system 400 according to embodiments of the various technologies described herein.
[0015] Figure 7 illustrates a diagram describing the categories of terminal proofs for terminals operating within an identity, payment, and access system according to embodiments of the various technologies described herein.
[0016] Figure 8 illustrates a method for providing identity, payment, and access services according to embodiments of the various technologies described herein.
[0017] FIG9 illustrates a method for providing identity, payment, and access services according to embodiments of the various techniques described herein.
[0018] FIG10 illustrates a system for providing access to events according to embodiments of the various techniques described herein.
[0019] FIG11 illustrates an example software package according to embodiments of the various techniques described herein.
[0020] Figure 12 illustrates an example object of the results of reading EMV card events according to embodiments of the various techniques described herein.
[0021] Figure 13 illustrates a diagram of a system for providing access to a transportation system according to embodiments of the various techniques described herein.
[0022] Figure 14 illustrates a diagram of the hardware architecture of a system for providing identity, payment, and access services according to embodiments of the various techniques described herein.
[0023] Figure 15 illustrates a diagram of an employee registration system using office cubicles according to embodiments of the various techniques described herein.
[0024] Figure 16 illustrates a diagram of an employee registration method using a user's near-field chip (NFC) enabled mobile device according to embodiments of the various techniques described herein.
[0025] Figure 17 illustrates a diagram of a system for providing employee registration and employee access according to embodiments of the various techniques described herein.
[0026] Figure 18 illustrates a diagram of a high-level view of an identity, payment, and access system according to embodiments of the various techniques described herein.
[0027] Figure 19 illustrates a computing system according to embodiments of the various techniques described herein.
[0028] Figure 20 illustrates a category of terminal proofs for terminals operating within an identity, payment, and access system, illustrating implementations of various technologies described herein. Detailed Description
[0029] Advantageously, as described herein, certain inventive aspects incorporate emerging technologies such as smart contracts, blockchain, non-fungible tokens (NFTs), semi-fungible tokens (SFTs), cryptocurrencies, and / or digital wallets, as well as digital assets and / or tokens with inventive identity, payment, and access services. Accordingly, the inventive systems and methods allow for secure and reliable verification of transactions and confirmation of rights using smart contracts.
[0030] In various aspects, the inventive methods provide rights to allow merchants to establish ticketing and / or access to reservation systems while utilizing decentralized public blockchains (i.e., blockchains). According to certain embodiments, referring to Figures 1-4, the inventive asset discovery system (i.e., access system, access server) 400 is based on a mapping (e.g., coupling) between a consumer's card (e.g., 105, 305, 310, 315, 404 as described herein) and a digital wallet 406 address (e.g., a cryptographic wallet 406 address). In some embodiments, the digital wallet 406 may store any number of digital assets 408 and may also include: tokens (e.g., loyalty points), non-fungible tokens (NFTs) (e.g., tickets and / or vouchers), or semi-fungible tokens (SFTs) (e.g., loyalty profiles with vouchers and loyalty points).In this implementation, merchant 420 (i.e., merchant computer system, computer server 420) can issue asset 418 on public blockchain 414 and list such asset 418 for sale on marketplace 416. Once purchased, the digital asset will be stored in the consumer's digital wallet. Furthermore, an asset verifier (e.g., a gate or merchant partner that can handle loyalty rewards, etc.) will be configured to verify the specific type of asset identified by the blockchain, contract, and / or type identifier. The asset verifier will verify ownership of the address by reading the hashed Personal Account Number (PAN) and / or Electronic Application Identifier (e.g., Mastercard EzAccess Id) from the consumer's card and querying a mapping contract (e.g., a smart contract) stored on the public blockchain and securely accessible by access server 410 (e.g., Mastercard EZaccess). In one operation, the access server (via secure access, control, and / or utilization of the mapping contract) will contact a specific contract to retrieve the existence of the asset from the merchant according to the cardholder's (i.e., the consumer's) account address.
[0031] Advantageously, asset verification can be decoupled from asset issuance, thus allowing for better integration of processing flows (e.g., the gate will not need to belong to a specific issuer and will require only minimal configuration to verify tickets from different sellers).
[0032] Figure 1 illustrates a system 100 for providing identity, payment, and access services. Europay, Mastercard, and Visa (EMV) are payment technology standards for providing secure transactions. An EMV card, or chip card, is a device that includes an embedded secure integrated circuit, which may be either a secure microcontroller or an equivalent smart device with internal memory, or simply a secure memory chip. The card connects to a reader via direct physical contact or a remote contactless radio frequency interface (e.g., Near Field Communication (NFC)). Utilizing an embedded microcontroller, chip cards have the unique ability to securely store large amounts of data, perform their own on-card functions (e.g., encryption and mutual authentication), and intelligently interact with the card reader. All EMV cards are chip cards. A chip card can be a plastic or metal card with an embedded chip that transmits information to a payment or automated teller machine (ATM) terminal. Chip cards provide increased security.
[0033] System 100 includes implementations designed to enable cardholders to easily access value-added services (such as identity, loyalty and access) using any EMV contactless card or token in a variety of use cases such as retail, smart cities, tourism and hospitality.
[0034] This system provides an end-to-end implementation of identity 110, loyalty program 115, and access 120 via, for example, contactless cards, tokens, mobile device digital wallets, and wearable devices coupled to mobile devices using EMV standard 105. Examples associated with identity 110 include passports 135, student IDs 130, and user identifiers 125. Examples associated with loyalty 115 include earning points 140 and redeeming points 145. Examples associated with access include office buildings and / or shared workspaces (WeWork) systems 150, hotels and other types of rental properties 155, and attractions 160 (e.g., tourism, sports, or other activities). This system delivers an end-to-end, seamless contactless experience by unlocking the hidden potential in existing contactless cards / tokens. Furthermore, in one example, this system provides seamless and secure ticket or voucher verification, which will prevent ticket scalping and counterfeiting. Specification 3 / 15 pages 6 CN 121488231 A
[0035] Figure 2 illustrates a diagram of a system 200 with a service provider and an identifier provider. Consumer 205 (e.g., consumer device) identifies to service provider 210 or registers with identifier provider 215. In some embodiments, access server 220 (i.e., Mastercard EZaccess) provides service provider 210 with the ability to implement services, such as access control 225, attraction entrance 230, and merchant services 235. Access control 225 system provider may include office lobbies, hotels, door locks. Attraction 230 may include museums, theaters, zoos, or any other type of attraction. Merchant services 235 may include loyalty and analytics programs. Access server 220 enables identifier provider 215 to provide student ID 240, ticketing 245, and loyalty identifier 250 services.
[0036] In some embodiments, when a consumer uses an EMV card, token, or digital wallet with an associated payment card number or master account (PAN), access server 220 is configured to match the consumer's loyalty program identifier with the consumer's PAN. In other words, the access server maps / binds the loyalty program identifier to the consumer's PAN. In other embodiments, as described in later paragraphs, referring to Figures 4-6, access server 220 matches the consumer's blockchain wallet account address with the consumer's PAN or eAid (e.g., Mastercard EzAccess ID).
[0037] Figure 3 illustrates a diagram of system 300 for generating a hashed PAN. Payment card information can be presented in three ways: via mobile device 305, wearable device 310, or contactless EMV card 315. In some embodiments, as described with reference to Figures 4-6, payment card information (as described with reference to Figure 3) is presented as card 404.
[0038] Referring to FIG3, the mobile device 305 may include a near-field communication (NFC) circuitry and digital wallet software. The digital wallet is a software-based system that securely stores the user's payment information and passwords for various payment methods and websites. By using the digital wallet, the user can easily and quickly complete purchases, for example, using NFC technology. The wearable device 310 may also include an NFC circuitry and digital wallet software. In one embodiment, the terminal 320 reads EMV card information from the EMV card 315 or via the digital wallet of the mobile device 305 or the wearable device 310. The terminal 320 determines the PAN from the EMV card or receives the PAN from the digital wallet of the mobile device or the wearable device. In one embodiment, the terminal 320 verifies the authenticity of the card. The terminal 320 generates a hashed PAN and sends the hashed PAN to the access server 330.
[0039] In one embodiment, the hashed PAN or digital account number (DAN) is generated using the following method: A salt is supplied to the terminal 320 by the access server 330. The PAN / DAN is read from the EMV card or token. Salt is random data used as an additional input to a one-way function that hashes data, passwords, or passphrases. Salt is used to protect the PAN / DAN. A new salt is randomly generated for each PAN / DAN. In one implementation, the salt and PAN / DAN (or a version of the PAN / DAN) are concatenated and fed to a cryptographic hash function. The hashed PAN / DAN, for example, the output hash value (instead of the original PAN / DAN), can be stored in local memory or sent to access server 330. If the authentication data repository is compromised, the hash allows for subsequent authentication without storing the PAN / DAN and therefore without risking exposure of the PAN / DAN. In one implementation, the PAN / DAN read by terminal 320 can be 13 to 19 bits. In one implementation, the hashed PAN (PAN|SALT) or hashed DAN (DAN|SALT) can be generated by a SHA256 hash function. For simplicity, wherever PAN-related implementations are described in this disclosure, the same methods described herein can be applied to DANs and / or tokens presented by mobile and / or wearable devices.
[0040] Figure 4 illustrates an asset discovery system 400 that allows for the mapping and coupling of digital assets according to various technical implementations described herein. As can be appreciated, instead of using a proprietary reservation system, tickets / rights can be represented as non-fungible tokens (NFTs), whereby such NFTs can be sold on marketplaces 416 (e.g., NFT platforms or websites with basic Web3 enabled).For example, a mapping contract that can be securely accessed (and controlled and usable) by access server 410 (i.e., access system) (e.g., Mastercard EZaccess) will be configured to represent such tickets as NFTs. In some implementation specifications, page 4 / 15 of CN 121488231 A, access server 410 may be access server 220 or 330 (refer to Figures 2 and 3).
[0041] In one operation, a consumer (via consumer device 402) will first associate their card 404 (e.g., including a Personal Account (PAN) and / or Electronic Application Identifier (e.g., Mastercard EzAccess Id) with a digital wallet 406 (e.g., crypto wallet) account address. Next, the consumer will “tap” their card 404 on a verifier terminal 412 (i.e., asset verifier, gate reader, gate terminal) so that access server 410 can query the blockchain wallet account address (i.e., wallet address). In some implementations, the gate reader / gate terminal 412 may be terminal 320 (refer to FIG. 3). After doing so, the access server 410 (e.g., via the accessed smart contract) can search on the public blockchain 414 to see if the searched wallet address includes an NFT representing a specific note (i.e., equity). For example, in some implementations, while the mapping contract(s) and associated data may be stored on the public blockchain 414, the access server 410 is configured to invoke the functionality of the mapping contract on blockchain 414 to facilitate the lookup.
[0042] In this scenario, advantageously, the mapping service provided by the access server 410 using a smart contract (e.g., based on the use of a standard ERC 721 contract for merchant notes) provides flexibility for the merchant system 420. In various implementations, the smart contract corresponds to a program or transaction protocol written into the blockchain, which may be configured to execute, control, or record events and actions according to the terms of the contract or agreement. As an advantage, in some instances, system 400 will provide merchants with flexibility by using standard ERC 721 contracts for tickets, allowing more gates to directly query a separate blockchain or use the interface of system 400 (e.g., which can be configured for less integration). Advantageously, by using such a smart contract protocol, merchant system 420 is able to create gate smart contracts (i.e., asset contracts, digital assets) 418, as described herein, with capabilities for additional functionality conforming to mapping service contracts (e.g., as the EZaccess NFT protocol accessed, utilized, and / or controlled by access server 410 and stored on public blockchain 414). Therefore, interoperability with merchant 420 or any other involved entity can be improved.
[0043] In a second example, referring to a loyalty implementation, by using an NFT as a representation of a loyalty profile, access server 410 can generate a mapping between an eAid (e.g., Mastercard EzAccess ID) 404 and a loyalty profile (e.g., as described with reference to FIG. 1). For example, when the mapped card 404 is “swipe” to a loyalty terminal (e.g., asset verifier 412), the loyalty terminal 412 can query the user’s wallet 406 address to determine whether the user owns the loyalty profile NFT. In some implementations, such a loyalty terminal 412 may be terminal 320 (refer to FIG. 3). Moreover, in some cases, semi-fungible tokens (SFTs) may be used instead of NFTs as the loyalty profile representation 418 (e.g., digital assets, asset contracts), and have the ability to also store loyalty points balances. In one implementation, SFTs, as defined in the ERC-1155 multi-token standard, allow each token ID to represent a new configurable token type, which may have its own metadata, supply, and other attributes. In doing so, the smart contract (i.e., the asset contract) 418 will be enabled to accept the homogenized portion (e.g., loyalty profile points balance) and the non-homogeneous portion (e.g., the loyalty profile identifier) of the loyalty profile representation.
[0044] Figure 5 illustrates an example method 600 of the asset discovery system 400 according to the first embodiment. In one operation, the mapping of the asset contract 418 (e.g., token, NFT, SFT) by the system 400 is performed prior to purchase. Referring to Figures 4 and 5, at step 510 (S510), at the consumer device 402 (e.g., consumer computer, mobile phone, wearable device), the digital wallet 406 (e.g., crypto wallet, digital asset wallet) can be coupled (connected) to the portal of the issuer 503 (i.e., the issuer computer system, the issuer server) (e.g., the issuer bank portal (website / app) owned by the issuing bank), whereby the master account (PAN) can be associated with the digital wallet 406. At step 520 (S520), the issuer 503 (i.e., the issuer computer system, the issuer server) associates card 404 (e.g., 105) with the wallet account address (i.e., the blockchain address) accessible (and controlled and used) by the access server 410 (e.g., Mastercard EZaccess) through a mapping service contract (e.g., the Mastercard NFT / SFT smart contract).
[0045] In this embodiment, according to the additional steps, at step 530 (S530), merchant 420 (i.e., merchant computer system, merchant computer) can generate (e.g., issue) one or more asset contracts 418 (i.e., assets, smart contracts) (e.g., tokens, NFTs, SFTs) among the asset contracts 418 on the public blockchain 414 (i.e., blockchain). At step 540 (S540), merchant 420 can set up a marketplace (i.e., digital marketplace 416) on the blockchain 414 to list, sell, and / or transfer one or more asset contracts 418. Furthermore, at step 550 (S550), at consumer device 402 (e.g., consumer computer, mobile phone, wearable device), a consumer can obtain (e.g., purchase) one or more asset contracts 418 and store (one or more) asset contracts 418 in a digital wallet 406 account (via blockchain 414).
[0046] FIG6 illustrates an example method 600 of an asset discovery system 400 according to a second embodiment. In one operation, the mapping of asset contract 418 (e.g., token, NFT, SFT) to system 400 is performed upon asset acquisition. Referring to Figures 4 and 6, at step 610 (S610), at consumer device 402 (e.g., consumer computer, mobile phone, wearable device), the consumer can provide a blockchain wallet account address (i.e., blockchain address) to merchant 420 (i.e., merchant server, merchant computer system) to map a PAN (Personal Account) or eAid (Electronic Application Identifier) (e.g., Mastercard EzAccess Id). At step 620 (S620), merchant 420 can associate card 404 (or eAid) with the blockchain address via mapping service contract 410 (i.e., accessed (and controlled and used) by an access server) (e.g., Mastercard EZaccess).
[0047] In this embodiment, according to the additional step, at step 630 (S630), the consumer 402 can “swipe” (i.e., couple) their card 404 on (or near) the verifier terminal 412 (i.e., the asset verifier / authenticator system) (e.g., a gate, terminal system 320 of FIG. 3, a merchant partner that processes loyalty points). By doing so, the verifier terminal 412 will be configured to verify / authenticate the asset or asset type (e.g., as identified by the blockchain 414, contract, and / or type ID).This configuration includes one or more of the following steps: 1) At step 640 (S640), the asset verifier 412 can “read” (e.g., scan, track, process, calculate) a PAN (Personal Account) or eAid (Electronic Application Identifier) (e.g., Mastercard EzAccess Id) from card 404; 2) At step 650 (S650), the asset verifier 412 can query (e.g., request, “call”) digital assets 408, 418 from the mapping contract on access server 410 (e.g., Mastercard EZaccess) using the hashed PAN (e.g., generated as shown by hashed PAN 325 in Figure 3) or eAid from card 404; 3) At step 660 (S660), the mapping contract stored on access server 410 (e.g., Mastercard EZaccess) can be used with the PAN or eAid (e.g., Mastercard EzAccess Id). 4) Query (e.g., search) the associated digital wallet account address of ID 418 or asset 408; and 5) after doing so, at step 670 (S670), asset contract 418 or asset 408 will be verified by the mapping contract on access server 410 for consumer 402. In some implementations, the steps described with reference to method 600 in FIG. 6 can be implemented using system 300 in FIG. 3.
[0048] In other variations and combinations of implementations of the asset discovery system 400, the association of digital assets 408, 418 to card 404 involving access server 410 (i.e., including an accessible mapping contract (i.e., a Mastercard NFT smart contract)) will involve the following initial steps: 1) A consumer associates their card 404 (i.e., a hashed PAN / eaid) with a digital account 406 (i.e., a cryptographic account) via smart contract 410 (e.g., a Mastercard NFT smart contract); 2) The consumer purchases one or more tickets (i.e., NFTs) as digital assets 418 from merchant 420 (i.e., a smart contract from the merchant); 3) The card 404 is coupled (e.g., “swipe”) on gate 412 (e.g., an asset verification terminal).
[0049] However, in the first variation / combination, the additional steps are as follows: 4) the gate 412 will request the access server 410 (e.g., access, control and / or utilize the Mastercard NFT smart contract) to map the NFT ticket to the swipe card 404 by providing the hashed PAN and ticket contract address; 5) the access server 410 (e.g., access, control and / or utilize the Mastercard NFT smart contract) will "call" (e.g., connect to) the NFT contract 418 (i.e., the smart contract from the merchant) to find the (one or more) tickets owned by the wallet address (i.e., the blockchain wallet address); and 6) the access server 410 (e.g., access, control and / or utilize the Mastercard NFT smart contract) will return a list of tickets owned by the cardholder to the gate 412, and the gate 412 will "check" (i.e., confirm, verify) the tickets and allow entry.
[0050] In the second variation / combination, the additional steps are as follows: 4) Gate 412 will map a hashed PAN request to a ticket service contract 418 (i.e., a smart contract from the merchant) for the NFT ticket; 5) The NFT ticket service contract 418 will "call" (e.g., connect to) an access server 410 (i.e., via the Mastercard NFT smart contract) with the hashed PAN to find the mapped wallet address; and 6) The access server 410 (e.g., accessing, controlling, and / or utilizing the Mastercard NFT smart contract) will then find the NFTs owned by the wallet address returned in step 5 and will return a list of tickets owned by the cardholder. After doing so, Gate 412 will "check" (i.e., confirm, verify) the ticket and allow entry.
[0051] In the third variation / combination, the additional steps are as follows: 4) Gate 412 will access server 410 (e.g., via Mastercard NFT smart contract) with a hashed PAN “call” (i.e., request) to find the mapped wallet address(s), and 5) Gate 412 will request the ticket contract 418 of the NFT ticket owned by the wallet address. After doing so, Gate 412 will “check” (i.e., confirm, verify) the ticket and allow access.
[0052] According to some implementations, the interface of the system's contract integrated with the access server 410 (e.g., Mastercard EZaccess) may include:
[0053] pragma solidity ^0.8.17;
[0054] interface MastercardAssetMappingContract {
[0055] / / Asset verifier registration to register the verifier to our Mastercard contract.
[0056] / / This verifier will verify the asset token.
[0057] function registerVerifier(string memory verifierName) external returns (uint256 verifierIdentifier);
[0058] / / When a user registers their card to this program, card-to-account mapping processing occurs.
[0059] / / This contract will automatically create a mapping to the user's account address on the corresponding blockchain where the asset resides.
[0060] function mapCardToAccount(string memory hashedPan , address userAccountAddress) external;
[0061] / / Asset retrieval.
[0062] / / The verifier (gate or any point-of-sale terminal) can send a request directly to this contract to retrieve a list of tokens based on the user-hashable PAN.
[0063] function retrieveAvailableAssets(string memory hashedPan , address assetContract, uint256 chainId) external
[0064] view returns (uint256[ ] memory tokenIds);
[0065] }
[0066] / / MerchantSFT extension ERC1155
[0067] interface MerchantSFT is ERC1155 {
[0068] function getTokensOwnedBy(address userAccountAddress) public view returns (uint256[ ] memory tokenList);
[0069] }
[0070] Figure 7 illustrates four categories of terminal certifications (e.g., terminal 320, asset verification terminal 412, gate 412) that operate within the identity, payment, and access system 100 and the asset discovery system 400. Terminals are categorized based on the type of transaction, credential type, type of solution provided, deployment model version, whether an ATC update is performed, and the type of proof performed. Category 1 terminals provide simple access. Category 2 terminals can be used in free transportation systems. Category 3 terminals can be used to provide secure access, and Category 4 terminals can be used to provide loyalty programs.
[0071] Category 1 terminals provide simple access. The credential type for this type of system is a hashed PAN. In this implementation, combined dynamic data authentication-application password generation (CDA) is not required. In this implementation, the terminal (e.g., terminal 320, asset verification terminal 412, gate 412) reads the PAN and / or user identifier (UID) from an EMV card, mobile device, or wearable device and provides access. Access can be provided by matching the hashed PAN locally or after verification by a remote access server (e.g., access servers 330, 410). The terminal can be provided using a software package (SDK), does not require an application transaction counter (ATC) update, and has low proof requirements. An ATC (Automatic Transmission Counter) is a counter maintained by an EMV card or digital wallet application that provides a sequential reference for each transaction. An ATC is also a sequence counter managed by a contactless card or token, used to ensure that all generated passwords are unique.Duplicate ATCs, ATC reductions, or large jumps in ATC values can indicate data duplication or other fraud to the issuer.
[0072] Category 2 terminals are provided for access and / or transportation systems. Credentials for this type of system are hashed PANs and CDAs. Also known as combined data authentication, CDAs involve including card decisions in data signed by the card's RSA key (public key or asymmetric key algorithm). In this implementation, the terminal (e.g., terminal 320, asset verification terminal 412, gate 412) performs zero-dollar ($0) authorized CDA transactions. The vendor's terminal is an EMV terminal that implements a full EMV access kernel according to the access terminal specification. In this implementation, ATC updates can be deferred and proof requirements are moderate.
[0073] Category 3 terminals are provided for secure access systems. Secure access systems can be targeted at access and / or identification systems. Credentials for this type of system are hashed PANs and CDAs. In this implementation, the terminal (e.g., terminal 320, asset verification terminal 412, gate 412) performs zero-dollar ($0) authorized CDA transactions. The vendor's terminal SDK can be one of two types. The first terminal type used in this implementation is an EMV terminal that implements a full EMV access kernel according to the Access Terminal Specification. The second terminal type is an SDK that communicates with an EMV access kernel implemented in a cloud point-of-sale (POS) server. In this implementation, ATC updates can be deferred or provided in real time and proof requirements are moderate.
[0074] Category 4 terminals are provided for loyalty systems. Loyalty systems can target merchant retail stores and / or payments. Credentials for this type of system are hashed PANs and CDAs. In this implementation, terminals (e.g., terminal 320, asset verification terminal 412, gate 412) execute full EMV transactions from the terminal and / or cloud POS SDK. The vendor's terminal may include a terminal SDK or be hosted by a cloud POS server. In this implementation, ATC updates are provided in real time and full proof is required.
[0075] In one implementation, the terminal reads the PAN number using the SELECT PPSE and READ RECORD commands, for example, for Category 1 transactions. In this implementation, no Get Processing Option (GPO) command is issued. While this implementation is easier to carry out, it is less secure and susceptible to card cloning or emulation.
[0076] In one implementation, the terminal executes CDA with GPO commands, which adds ATC. In this implementation, the access server sends an ATC update to the issuer. This implementation is more secure and ensures the card / token is genuine.
[0077] In one implementation, cloud POS servers can be fully utilized to implement EMV / EA kernels for some use cases to reduce terminal upgrade efforts.
[0078] In one embodiment, the NFC data exchange performed by the terminal can be modified to perform a READ RECORD, followed by a GPO. This embodiment enables a single-click hashed PAN read mode for loyalty systems. Specification 8 / 15 pages 11 CN 121488231 A
[0079] FIG8 illustrates a diagram of a method 800 for providing identity, payment, and access services. Method 800 can be implemented in conjunction with various steps of system 400 (as described with reference to FIG4-6). At block 805, the PAN and / or UID is read by a terminal (e.g., terminal 320, terminal, asset verification terminal 412, gate 412). The PAN and / or UID can be read from a contactless card or via a token provided by a digital wallet present on the mobile device (or accessible via a wearable device communicatively coupled to the mobile device). At block 810, if the PAN is read, the terminal generates a hashed PAN. At box 815, the terminal determines the transaction result based on the hashed PAN. In one embodiment, the transaction result is determined locally. In one embodiment, the transaction result is based on a decision made by an access server (e.g., access servers 330, 410). In one embodiment, the transaction result is determined by performing offline matching of the hashed PAN and / or UID against a locally stored whitelist. In one embodiment, the terminal (e.g., terminal 320, asset verification terminal 412, gate 412) sends the hashed PAN and / or UID to a backend server, such as a server between access servers 330, 410 and the terminal (e.g., terminal 320, asset verification terminal 412, gate 412), so that the backend server determines and provides a decision after matching the received hashed PAN against the whitelist. In one embodiment, a service provider, such as a provider of identity, payment, and / or access services, may optionally (e.g., via a backend server) upload transaction data (including UID, hashed PAN, and / or other relevant data) from the terminal to the access server in real time or as soon as possible.
[0080] For example, a Select Nearest Payment System Environment (PPSE) command can be used to read the card PAN to ensure that the PAN / token from a specific payment processor is read. Once it is verified that the PAN / token from the specific payment processor has been presented, a Read Record command is given to read the PAN / token.The following are examples of SELECT PPSE and READ RECORD commands:
[0081] SELECT PPSE COMMAND: 00B2011400
[0082] READ RECORD COMMAND: 00A4040007A0000000041010
[0083] The proof of the terminal providing method 800 includes testing that the terminal can interact with an EMV card or device (mobile or wearable). The proof also includes testing to verify whether the terminal can determine that the EMV card is enabled and that information flow can be shared. In addition, the proof includes determining whether the terminal and the access server can implement the transactions and data processing described in method 800.
[0084] Figure 9 illustrates a diagram of method 900 for providing identity, payment, and access services. At block 905, a $0 transaction is initiated with an EMV card or token. The EMV card may be a contactless card. Initiating a $0 transaction involves receiving a PAN and other data from the card or token. At block 910, the PAN is determined based on the information received via the $0 transaction. At box 915, the card / token is authenticated. In one implementation, the card / token is authenticated using a CDA. The CDA provides a fast and secure offline card / token authentication protocol and is supported by all contactless cards and tokens. If the CDA is successful, a hashed PAN is generated at box 920. The transaction result is determined at box 925. In one implementation, the transaction result is determined locally. In this implementation, the transaction result is determined by performing an offline match of the hashed PAN against a locally stored whitelist. In another implementation, the transaction result is based on a decision made by a backend server. In this implementation, the hashed PAN is sent to the backend server so that the backend server can make a decision about the transaction by matching the received hashed PAN against the whitelist. In one implementation, the terminal reads ATC data from the EMV card / token and provides this ATC data to the access server.
[0085] The service provider (e.g., via a backend server) uploads transaction data from the terminal (including UID, hashed PAN, and / or other relevant data) to the access server in real time or as quickly as possible. The access server sends an ATC update message to the issuer based on transaction data received from all service providers. Sending an ATC update to the issuer notifies them that the ATC has increased beyond normal levels. Informing the issuer via the ATC update message avoids situations that could lead to unexpected rejection of payment transactions.
[0086] Proof of the terminal providing method 900 includes testing that the terminal can interact with an EMV card or device (mobile or wearable). The proof also includes testing to verify whether the terminal can determine that the EMV card is enabled and that information flow can be shared.Furthermore, the proof includes determining whether the terminal and access server can implement the transactions and data processing described in method 900. In one embodiment, an access kernel is provided. In this embodiment, the proof includes testing to determine whether the access kernel and card / token can transmit the correct information to allow data sharing and allow decision-making on processing at the terminal.
[0087] FIG10 is a diagram of a system 1000 for providing access to an event. In some embodiments, system 1000 may be used in conjunction with system 400 (as described with reference to FIG4-6) (including replaced elements). System 1000 includes an EMV card or token 1005, a gate 1010 including an access kernel 1015 and a gate terminal 1030, a back-end server of a service provider (e.g., a ticketing server 1020), and an access server 1025. At item 1, a visitor purchases a ticket from ticketing server 1020 via a web-based or application-based transaction. At item 2, after purchasing a ticket, the visitor is presented with the option to use their EMV card or token 1005 to obtain access to the event. After selecting the option to use an EMV card or token 1005 for the access event, the user chooses to join the access service and notifies the access server 1025. In one implementation, transaction details and a transaction ID are sent to the user's email address, and the transaction ID is embedded in a link to join the access service. When the link is clicked, a webpage loads along with the transaction ID, and the user can enter additional card details, either from a physical card or from the user's digital wallet. These hashed PANs and transaction IDs are then sent to the access server 1025. At item 3, the ticketing server 1020 downloads a whitelist (e.g., a list of qualified hashed PANs associated with valid ticket reservation references). At item 4, the whitelist is downloaded to the gate 1010. At item 5, when a visitor presents their EMV card / token at the gate 1010, the PAN / token is read by the access kernel 1015. The access kernel 1015 generates a hashed PAN and compares the hashed PAN with the downloaded whitelist.
[0088] Figure 11 illustrates an example SDK 1100. In particular, SDK 1100 can be used to implement terminals 320, 412, etc., and methods 500, 600, 700. Item 1105 describes an application programming interface (API) that can be publicly disclosed for controlling the reading of EMV cards.Specifically, Project 805 describes the following APIs: `EzaSDK.init(Context context)`, `EzaSDK.onNewIntent(Activity activity, Intent intent)`, `EzaSDK.onResume(Activity activity, EzaTransactionListener listener)`, and `EzaSDK.stop()`. The `EzaSDK.init(Context context)` API reads relevant configuration data from a default JavaScript object notation (JSON) file named `AppConfig.ison` in the asset resource folder. The `EzaSDK.onNewIntent(Activity activity, Intent intent)` API specifies that the SDK will begin processing EMV cards when an Android Intent event occurs, such as when a native NFC card is detected or removed. The `EzaSDK.onResume(Activity activity, EzaTransactionListener listener)` API specifies that the SDK activates the NFC module when an Android application starts from the background and becomes active. The `EzaSDK.stop()` API allows the terminal to stop listening for NFC events on the Android device.
[0089] Item 1110 describes the configuration fields supported in AppConfig.json. The fields in Item 1110 describe the options available for access control using the SDK. In one implementation, hashedPanSalt is a random string of a suitable length. The salt value is appended to the PAN and hashed to generate a unique EMV card value across different terminals. The terminalMode field can be one of three values: hashedPan, auth, or fullTransaction. When using hashedPan, the SDK returns the hashed PAN from reading the EMV card. When using auth, the SDK returns the hashed PAN and transaction data from $0 authorization. When using fullTransaction, the SDK requests the transaction amount, performs the full EMV transaction, and returns the result of the transaction. The nfcMode field can have an internal or external value. When setting an internal value, the SDK uses the host Android device's internal NFC module. When setting an external value, the SDK uses an external Universal Serial Bus (USB) NFC driver.
[0090] Figure 12 illustrates an example object 1200 used to read EMV card events.The results of reading EMV card events can be achieved using the EzaTransactionListener on pages 10 / 15 of the instruction manual, CN 121488231 A, based on either success or failure. All transaction information, whether successful or failed, can be retrieved from the TransactionOutcome object.
[0091] Figure 13 is a diagram of system 1300 for providing access to a transportation system. In some embodiments, system 1300 may be used in conjunction with system 400 (as described with reference to Figures 4-6) (including replaced elements). System 1300 includes a transportation key card 1305, a gate / terminal 1310 coupled to one or more fleet terminals 1355 and an access kernel 1350, a terminal backend 1315 of the transportation system provider including a local server 1320, a cloud server 1325 and a PL / SQL server page (PSP), an access server 1335, a payment network 1340, and an issuer 1345.
[0092] In Item 1, the issuer 1345 registers the key card as a hashed PAN to the access server 1335. In Item 2, the supplier (e.g., terminal backend 1315) downloads a list of qualified hashed PANs, such as a whitelist, from the access server 1035. The terminal backend 1315 also uploads transaction records to the access server 1335. In Item 3, when a passenger presents their transit key card at a transportation terminal (e.g., gate 1310 or fleet terminal 1355), entry details are stored in the memory of the gate / terminal 1310, 1355. The gate / terminal 1310, 1355 supports internal and external expandable storage capabilities, such as SD cards. A hashed PAN is generated for the transit key card, and CDA authentication is performed to ensure the card is authentic. In this implementation, the ATC counter is incremented. In Item 4, the hashed PAN is synchronized to the fleet, and historical transaction data is uploaded. At Project 5, Access Server 1335 sends an ATC update to Issuer 1345 via Payment Network 1040.
[0093] The embodiment of Figure 13 illustrates a closed-loop platform where a transportation system access provider can migrate to an open-loop platform. In closed-loop transportation, fares are pre-purchased and stored on non-EMV cards. Fares are synchronized with a local server, for example, at the end of the day. Migrating to open-loop transportation with EMV-enabled gate terminals allows the gate terminals to connect to a cloud server, which in turn connects to a Payment Service Provider (PSP) to allow near real-time (or end-of-day) transactions. Local server 1320 supports gate terminals in closed-loop transportation, and cloud server 1325 supports open-loop transportation.
[0094] In one embodiment, certain hashed PANs are allowed free transportation. These hashed PANs are stored in a whitelist.The whitelist is transmitted from the access server 1335 and stored in the gate terminal 1350. During card swiping at the gate, card transaction data is stored in the gate terminal, but at the end of the day, the card transaction data is synchronized to the backend 1315 and forwarded to the access server 1334.
[0095] Figure 14 is a diagram of the hardware architecture of a system 1400 for providing identity payment and access services. In some embodiments, system 1400 may be used in conjunction with system 400 (as described with reference to Figures 4-6) (including replaced elements). A card or token 1405 (via a mobile and / or wearable device) is presented to terminal 1410. Terminal 1410 may store 1MB of 100 hashed PANs as a whitelist. In addition, terminal 1410 may send Application Protocol Data Unit (APDU) commands via any NFC to read card data. The SHA256 algorithm may be applied to the card data to determine the hashed PAN. The determined hashed PAN may be compared with the whitelist. Terminal 1410 can store card and access details. In one embodiment, terminal 1410 includes a central processing unit (CPU) memory with at least 128 MB of random access memory (RAM) and 256 MB of flash memory. In one embodiment, removable micro-secure digital (µSD) memory is supported. Item 1415 illustrates the hardware integration of terminal 1410 with a turnstile. In this particular embodiment, a sticker may be provided on the turnstile to indicate that only compatible key cards can be swiped. A speaker may be provided to provide feedback to passengers on whether entry is approved or denied. A display may also be provided to provide feedback on whether entry is approved or denied.
[0096] Figure 15 is a diagram of an employee registration system 1500 using office cubicles. In some embodiments, system 1500 may be used in conjunction with system 400 (as described with reference to Figures 4-6), including replaced elements. Self-service registration cubicles may be implemented in the lobby or near the reception area. Staff begin registration processing by swiping their company badge at a card reader 1505 coupled to terminal 1515. Staff will then swipe their contactless physical / digital instruction manual (pages 11 / 15, CN 121488231 A) on the second card reader 1510 to register for access. Once registration is complete, employees can begin accessing the building using their EMV cards, mobile devices, or wearable devices.
[0097] Figure 16 is a diagram of employee registration method 1600 using a user's NFC-enabled mobile device. In some embodiments, method 1600 may be used in conjunction with methods 500, 600 (as described with reference to Figures 5-6) (including replaced elements). At block 1605, the user accesses the employee registration application on their mobile device. At block 1610, the employee ID card is registered when the user's company ID card is placed near the NFC reader of the mobile device.When registration is complete, a notification is provided via a success screen at item 1615. The user is now able to gain access to the site using their mobile device at item 1620.
[0098] Figure 17 is a diagram of a system 1700 for providing employee registration and employee access. In some embodiments, system 1700 may be used in conjunction with system 400 (as described with reference to Figures 4-6) (including replaced elements). System 1700 includes an EMV card 1705, a gate / terminal 1710 having a gate 1715 and one or more terminals 1745, a gate backend 1430, a cloud point-of-sale (POS) server 1720, an access server 1725, a payment network 1735, and an issuer 1740. In one embodiment, one or more terminals 1745 include terminals 1705 and 1715.
[0099] At item 1, the user registers their company ID badge and EMV card with the access server 1725, as described in Figure 12 or Figure 13. At Project 2, the EMV card is presented at gate 1715. At Project 3, cloud POS 1720 initiates a $0 transaction via a secure network. At Project 4, cloud POS 1720 reads the hashed PAN from the EMV card and performs an access rule lookup from access server 1725. At Project 5, access server 1725 requests the gate provider (e.g., gate backend 1730) to generate a gate access response, e.g., authorized or denied. The gate access response is then sent from gate backend 1730 to gate terminal 1710. At Project 6, transaction password data is sent to payment network 1735 to update ATC.
[0100] Figure 18 is a diagram of a high-level view 1800 of an identity, payment, and access system. In some embodiments, system 1800 may be used in conjunction with system 400 (as described with reference to Figures 4-6), including replaced elements. This system uses access ID 1820 to implement various identity, loyalty, and access services. Access ID 1820 is mapped to various items, including but not limited to transaction data 1830, hashed PAN 1810, barcode and / or QR code 1815, program data 1840, and ID 1835. Transaction data 1830, hashed PAN 1810, and barcode / QR code 1815 can be provided by terminal 1805. Various data associated with Access ID 1820 can be provided to issuer 1825. Service provider 1845 can provide rights 1850 and rights mapping 1855 via the use of terminal 1805. Identifier provider 1865 can provide entity ID 1580 mapping 1835 to Access ID 1820 and / or rights 1855.
[0101] This system offers several advantages. QR codes, barcodes, and vendor cards can be easily copied.In some instances, this disclosure provides a system for reading PAN and serial numbers from physical and digital EMV cards. The hardware of this disclosure is inexpensive and uses existing gates and / or USB NFC devices. Implementations of this disclosure build upon existing, highly secure, and proven EMV payment standards, providing a unified digital-first experience for consumers across different domains and offering merchants more data points.
[0102] FIG19 is a block diagram of a hardware configuration 1900 that can be used for device operation in identity, payment, and access system 100 and asset discovery system 400. Hardware configuration 1900 can be used to implement one or more of the elements described with reference to FIG1-18. Hardware configuration 1900 may include a processor 1910, a memory 1920, a storage device 1930, and an input / output device 1940. Each of components 1910, 1920, 1930, and 1940 may be interconnected, for example, using a system bus 1950. Processor 1910 may be able to process instructions for execution within hardware configuration 1900. In one embodiment, processor 1910 may be a single-threaded processor. In another embodiment, processor 1910 may be a multi-threaded processor. Processor 1910 may be able to process instructions stored in memory 1920 or on storage device 1930.
[0103] Memory 1920 may store information within hardware configuration 1900. In one embodiment, memory 1920 may be a computer-readable medium. In one embodiment, memory 1920 may be a volatile memory cell. In another embodiment, memory 1920 may be a non-volatile memory cell.
[0104] In some embodiments, storage device 1930 may be able to provide mass storage for hardware configuration 1900. In one embodiment, storage device 1930 may be a computer-readable medium. In various different embodiments, storage device 1930 may include, for example, a hard disk device / drive, an optical disk device, flash memory, or some other mass storage device. In other embodiments, storage device 1930 may be a device external to hardware configuration 1900. Input / output device 1940 provides input / output operations for hardware configuration 1900.
[0105] Figure 20 illustrates Figure 1200 describing four categories of terminal credentials (in addition to those described in Figure 7) for terminals (e.g., terminal 320, asset verification terminal 412, gate 412) operating within identity, payment, and access system 100 or system 400. Terminals are categorized based on the type of transaction, credential type, type of solution provided, deployment model version, whether an ATC update is performed, and the type of credentials performed. Category 5 terminals provide simple access. Category 6 terminals can be used to provide secure access.Category 7 terminals can be used to provide open transportation and Category 8 terminals can be used to provide retail innovation programs.
[0106] As mentioned above, Category 5 terminals provide simple access. The credential type for this type of system is an access ID or a payment account reference (PAR). In this implementation, combined dynamic data authentication-application password generation (CDA) is not required. Additionally, the terminal (e.g., terminal 320, asset verification terminal 412, gate 412) reads the access ID or PAR from an EMV card, mobile device, or wearable device and provides access. In one implementation, the access ID can be read using third-party data, and the PAR can be read via an EMV card or token. In another implementation, third-party data can be provided via tag 9F6E, and the PAR can be provided via tag 9F24. Access can be provided by matching the access ID or PAR locally or after verification by a remote access server (e.g., access server 330). The terminal can be provided using a software package (SDK), does not require application transaction counter (ATC) updates, and has low authentication requirements. The terminal SDK can be implemented on a computer operating system or on a mobile device operating system, for example, for a telephone, tablet, or similar mobile device.
[0107] As mentioned above, Category 6 terminals are provided for secure access systems. Secure access systems can be for access and / or identification systems. Credentials for this type of system are hashed PANs and CDAs. In this implementation, the terminal (e.g., terminal 320) performs zero-dollar ($0) authorized CDA transactions. The vendor's terminal SDK is an EMV terminal that implements a full EMV access kernel according to the access terminal specification. The complete terminal SDK can be based on a contactless reader SDK or implemented in a mobile device operating system, for example, for a telephone, tablet, or similar mobile device. In this implementation, ATC updates can be deferred or provided in real time and the proof requirement is moderate.
[0108] As mentioned above, Category 7 terminals are provided for access and / or transportation systems. In particular, Category 7 terminals are provided for open transportation systems. Credentials for this type of system are hashed PANs and CDAs. Also known as combined data authentication (CDA), this involves including card decisions in data signed by the card's RSA key (public key or asymmetric key algorithm). In this implementation, a terminal (e.g., terminal 320, asset verification terminal 412, gate 412) executes a zero-dollar ($0) authorized CDA transaction. The vendor's terminal is an EMV terminal that implements a full EMV access kernel according to the access terminal specification. In this implementation, ATC updates can be deferred and require full proof.
[0109] As mentioned above, Category 8 terminals are provided for access and / or payment systems. In particular, Category 8 terminals are provided for retail innovation systems.Retail innovation can target merchant retail stores and / or payments. Credentials used in this type of system are hashed PANs and CDAs. In this implementation, a terminal (e.g., terminal 320, asset verification terminal 412, gate 412) executes a complete EMV transaction from the terminal and / or cloud POS SDK. The vendor's terminal may include a terminal SDK implemented on a mobile device running the operating system described on pages 13 / 15 of the Mobile Device Manual 16 CN 121488231 A or hosted by a cloud POS server. In this implementation, ATC updates are provided in real time and require full proof.
[0110] The subject matter of this disclosure and its components can be implemented by instructions that, upon execution, cause one or more processing devices to perform the aforementioned processing and functions. Such instructions may include, for example, interpreted instructions, such as script instructions, e.g., JavaScript or ECMAScript instructions, or executable code, or other instructions stored in a computer-readable medium.
[0111] Embodiments of the subject matter and functional operations described in this specification may be provided in digital electronic circuit systems, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations thereof. Embodiments of the subject matter described in this specification may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible program carrier for execution by a data processing apparatus or for controlling the operation of a data processing apparatus.
[0112] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the related program, or in multiple coordinated files (e.g., a file storing one or more modules, subroutines, or code portions). Computer programs can be deployed to execute on a single computer, or on multiple computers located at a site or across multiple sites and interconnected by a communication network.
[0113] The processes and logic flows described herein are executed by one or more programmable processors that execute one or more computer programs to perform functions by manipulating input data and generating outputs, thereby binding the processing to a particular machine (e.g., a machine programmed to perform the processes described herein).Processing and logic flows can also be executed by a dedicated logic circuit system, and the apparatus can also be implemented as a dedicated logic circuit system, such as an FPGA (Field Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit).
[0114] Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks (e.g., internal hard disks or removable disks); magneto-optical disks; and CD ROMs and DVD ROMs. Processors and memory can be supplemented or incorporated therein by dedicated logic circuit systems.
[0115] The above discussion is directed to certain specific embodiments. It should be understood that the above discussion is merely to enable those skilled in the art to make and use any subject matter as defined in the patent "claims" of any patent now or hereafter published herein.
[0116] It is particularly intended that the claimed invention is not limited to the embodiments and descriptions contained herein, but includes modified forms of those embodiments, including portions of embodiments and combinations of elements of different embodiments falling within the scope of the following claims. It should be recognized that, in the development of any such practical implementation, as in any engineering or design project, many implementation-specific decisions can be made to achieve the developer’s specific goals, such as compliance with system-related and business-related constraints, which may vary from implementation to implementation. Moreover, it should be recognized that such development efforts can be complex and time-consuming, but this remains a routine practice of design, manufacture, and production for those skilled in the art who benefit from this disclosure. Nothing in this application is considered critical or necessary to the claimed invention unless explicitly indicated as “critical” or “essential.”
[0117] In the foregoing detailed description, numerous specific details have been set forth in order to provide a thorough understanding of this disclosure. However, it will be clear to those skilled in the art that this disclosure can be practiced without these specific details. In other instances, well-known methods, processes, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
[0118] It will also be understood that while the terms first, second, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first object or step may be referred to as a second object or step, and similarly, a second object or step may be referred to as a first object or step, without departing from the scope of the invention. The first object or step and the second object or step are objects or steps, but they should not be regarded as the same object or step.
[0119] The terminology used in the description of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the disclosure. As used in the description of this disclosure and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or,” as used herein, refers to and covers any and all possible combinations of one or more of the associated listed items. It will also be further understood that, when used in this specification, the terms “comprising,” “including,” and / or “containing” specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0120] As used herein, the term “if” may be interpreted, depending on the context, as meaning “when,” “after,” “in response to determining,” or “in response to detecting.” Similarly, the phrases “if determined…” or “if [the condition or event] is detected” can be interpreted, depending on the context, as meaning “after determined…” or “in response to determined…” or “after [the condition or event] is detected” or “in response to the detection of [the condition or event]”. As used herein, the terms “up” and “down”; “above” and “below”; “upward” and “downward”; “below…” and “above…”; and other similar terms indicating relative positions above or below a given point or element may be used in conjunction with some implementations of the various techniques described herein.
[0121] While the foregoing is directed to implementations of the various techniques described herein, other and further implementations may be devised without departing from their basic scope, the scope of which may be determined by the following claims. Although the subject matter has been described in language specific to structural features and / or methodological actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.Instruction manual, page 15 / 15, 18 CN 121488231 A, Figure 1; Instruction manual, Figure 1 / 22, page 19 CN 121488231 A, Figure 2; Instruction manual, Figure 2 / 22, page 20 CN 121488231 A, Figure 3; Instruction manual, Figure 3 / 22, page 21 CN 121488231 A, Figure 4; Instruction manual, Figure 4 / 22, page 22 CN 121488231 A, Figure 5; Instruction manual, Figure 5 / 22, page 23 CN 121488231 A, Figure 6; Instruction manual, Figure 6 / 22, page 24 CN 121488231 A, Figure 7; Instruction manual, Figure 7 / 22, page 25 CN 121488231 A, Figure 8; Instruction manual, Figure 8 / 22, page 26 CN 121488231 A, Figure 9; Instruction manual, Figure 9 / 22, page 27 CN 121488231 A, Figure 10 Instruction Manual Figure 10 / 22, page 28, CN 121488231 A, Figure 11; Instruction Manual Figure 11 / 22, page 29, CN 121488231 A, Figure 11 (continued); Instruction Manual Figure 12 / 22, page 30, CN 121488231 A, Figure 12; Instruction Manual Figure 13 / 22, page 31, CN 121488231 A, Figure 13; Instruction Manual Figure 14 / 22, page 32, CN 121488231 A, Figure 14; Instruction Manual Figure 15 / 22, page 33, CN 121488231 A, Figure 15; Instruction Manual Figure 16 / 22, page 34, CN 121488231 A, Figure 16; Instruction Manual Figure 17 / 22, page 35, CN 121488231 A, Figure 17; Instruction Manual Figure 18 / 22, page 36, CN 121488231 A, Figure 18; Instruction Manual Figure 19 / 22 Page 37 CN 121488231 A Figure 19 Appendix 20 / 22 Page 38 CN 121488231 A Figure 20 Appendix 21 / 22 Page 39 CN 121488231 A Figure 20 (continued) Appendix 22 / 22 Page 40 CN 121488231 A.
Claims
1. A method comprising: The access server maps cards to consumer and blockchain wallet account addresses, wherein the access server is configured as an access mapping service contract, and wherein the card includes at least one of the consumer's Personal Account (PAN) and Electronic Application Identifier (eAid).
2. The method of claim 1, wherein the card mapping is performed prior to the digital asset transaction.
3. The method of claim 2, further comprising: A digital wallet is coupled to the issuer's computer system by a consumer device associated with the consumer, wherein the coupling of the digital wallet includes linking the consumer's Personal Account (PAN) to the digital wallet.
4. The method of claim 3, further comprising: One or more asset contracts are generated by the merchant's computer system and correspond to the corresponding digital assets on the blockchain.
5. The method of claim 4, wherein the corresponding digital asset comprises: Non-fungible tokens (NFTs), semi-fungible tokens (SFTs), or tokens.
6. The method of claim 4, further comprising: The merchant's computer system lists one or more asset contracts on the blockchain in a digital marketplace.
7. The method of claim 6, further comprising: The consumer obtains one or more asset contracts via a consumer device, wherein the one or more assets are configured to be stored on a digital wallet.
8. The method of claim 1, wherein the card mapping is performed concurrently with the digital asset transaction.
9. The method of claim 8, further comprising: Consumer devices associated with consumers provide blockchain wallet account addresses to merchant computer systems to map at least one of the consumer’s Personal Account (PAN) and Electronic Application Identifier (eAid) to the merchant computer systems.
10. The method of claim 8, further comprising: Consumers couple their cards to the asset verification terminal.
11. The method of claim 10, further comprising: The asset verifier terminal processes the Personal Account Number (PAN) or Electronic Application Identifier (eAid) from the card. as well as Generate a hashed PAN.
12. The method of claim 11, further comprising: The asset verifier terminal requests one or more digital assets associated with a hashed PAN or electronic application identifier from a mapping service contract stored on the access server.
13. The method of claim 12, further comprising: The access server uses the blockchain wallet account address to search for the one or more digital assets.
14. The method of claim 13, further comprising: The access server verifies the one or more digital assets.
15. The method of claim 11, wherein the one or more digital assets comprise: Non-fungible tokens (NFTs), semi-fungible tokens (SFTs), or tokens.
16. The method of claim 15, wherein the one or more digital assets include NFTs or SFTs corresponding to loyalty profiles.
17. The method of claim 1, wherein the card is a chip card corresponding to a Europay, Mastercard, or Visa (EMV) card.
18. The method of claim 1, wherein the card is configured to be presented via a mobile device, a wearable device, or a contactless EMV card.
19. A method comprising: A digital wallet is coupled to the issuer's computer system by a consumer device associated with the consumer, wherein the coupling of the digital wallet includes associating the consumer's Personal Account (PAN) or Electronic Application Identifier (eAid) with the digital wallet.
20. A method comprising: Consumer devices associated with consumers provide blockchain wallet account addresses to merchant computer systems to map at least one of the consumer’s Personal Account (PAN) and Electronic Application Identifier (eAid) to the merchant computer systems.
