Contactless delivery system and method

Abstract

A contactless delivery system is provided. The contactless delivery system includes a contactless card that stores a cryptogram including a unique identifier associated with a user account. The contactless card is configured to transmit the cryptogram to a server after entering a communication field. Upon receiving the cryptogram, the server verifies and decrypts the cryptogram to extract the unique identifier. The server can use the unique identifier to query a database for the identity of the user account, generate a digital signature based on the identity of the user account, and transmit a confirmation notice including the identity of the user account and the digital signature.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Patent Application No. 17 / 160,049, filed January 27, 2021, the disclosure of which is incorporated by reference in its entirety into this application. [Technical field]

[0002] The present disclosure relates generally to delivery management, and more particularly, to a contactless delivery system and method. [Background technology]

[0003] Electronic commerce is becoming increasingly widespread and common. Online shopping, where goods are purchased online and shipped to purchasing customers at a residential address, commercial address, or other location, constitutes a large and growing sector of the global economy. As the number and value of goods purchased online and shipped for delivery increases, along with in-store pickup and other forms of goods pickup, it is important to provide efficient, timely, and secure delivery.

[0004] In social distancing scenarios, it is difficult to identify people without close physical personal contact. For example, when a package is delivered to a customer, the customer typically needs to identify themselves to complete the delivery and collect the package. As another example, a customer may arrange to pick up a package from a store and call a phone number to let the store know they have arrived. However, the customer needs to identify themselves to safely collect the package, and presenting identification (such as a driver's license) to store staff is difficult without physical contact or proximity to the store staff. In another example, a package may be delivered to a customer by a delivery person, which may require the customer to identify themselves to the delivery person so that the package can be delivered in a safe manner to the correct recipient. Many of these interactions do not allow for social distancing and the identification and verification process is not efficient.

[0005] These and other drawbacks exist, and therefore there is a need to overcome these drawbacks and provide a system and method for verifying customers in a safe and efficient manner while minimizing physical contact or close person-to-person interaction. Summary of the Invention

[0006] Aspects of the disclosed technology include systems and methods for contactless package delivery.

[0007] An embodiment of the present disclosure provides a contactless delivery system. The contactless delivery system includes a contactless card. The contactless card includes a processor and a memory. The memory stores a cryptogram including a unique identifier associated with a user account. The contactless card is configured to transmit the cryptogram to a server through one or more intermediary devices after entering a communication field. Upon receiving the cryptogram, the server is configured to verify the cryptogram, decrypt the cryptogram to extract the unique identifier, use the unique identifier to query a database for the identity of the user account, generate a digital signature based on the identity of the user account, and transmit a confirmation notice including the identity of the user account and the digital signature.

[0008] An embodiment of the present disclosure provides a contactless delivery system, comprising a server including a processor and a memory, which receives a ciphertext including a unique identifier associated with a user account, verifies the ciphertext, decrypts the ciphertext to extract the unique identifier, queries a database using the unique identifier for an identity of the user account, generates a digital signature based on the identity of the user account, and transmits a confirmation notice including the identity of the user account and the digital signature.

[0009] An embodiment of the present disclosure provides a contactless delivery method that receives a ciphertext including a unique identifier associated with a user account, verifies the ciphertext, decrypts the ciphertext to extract the unique identifier, queries a database using the unique identifier for an identity of the user account, generates a digital signature based on the identity of the user account, and transmits a confirmation notice including the identity of the user account and the digital signature.

[0010] Further features of the disclosed system and method, and advantages offered thereby, will be described in more detail below with reference to specific example embodiments that are illustrated in the accompanying drawings. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram of a system for contactless delivery according to an example embodiment. [Diagram 2] FIG. 1 is a sequence diagram illustrating a method for contactless delivery according to an example embodiment. [Diagram 3] 1 is a flow chart illustrating a method for contactless delivery according to an example embodiment. [Figure 4] 1 is a flow chart illustrating a method for contactless delivery according to an example embodiment. [Diagram 5] FIG. 1 is a diagram of a system for contactless delivery according to an example embodiment. [Figure 6] FIG. 1 is a sequence diagram illustrating a method for contactless delivery according to an example embodiment. [Figure 7] 1 is a flow chart illustrating a method for contactless delivery according to an example embodiment. [Figure 8] 1 is a flow chart illustrating a method for contactless delivery according to an example embodiment. [Figure 9] 1 is a flow chart illustrating a method for contactless delivery according to an example embodiment. [Figure 10] 1 is a flow chart illustrating a method for contactless delivery according to an example embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] The following description of the embodiments provides non-limiting representative examples that refer to symbols to describe features in detail and teach different aspects of the present invention. It is recognized that the described embodiments can be implemented individually or in combination with other embodiments from the description of the embodiments. Those skilled in the art who review the description of the embodiments can know and understand the different described aspects of the present invention. The description of the embodiments promotes understanding of the invention to the extent that other implementations that are not specifically covered but are within the knowledge of those skilled in the art who read the description of the embodiments can be understood to be consistent with the application of the present invention.

[0013] Many customers and merchants are looking to complete transactions efficiently and in a socially distanced manner that does not require employees or other personnel to be in physical proximity to the customer. This is especially true during times such as a pandemic when many people are concerned about the spread of germs. As such, new ways are needed to interact and complete transactions without bringing people into close proximity to one another. This can be challenging because people rely heavily on physical evidence of identity (e.g., driver's license, physical signature, birth certificate, passport, etc.) to verify their identity. Furthermore, common forms of identification such as photo ID and physical signatures are outdated, unreliable, and sometimes not particularly meaningful. In these cases, a digital way may be needed, for example, to sign for a package, present a driver's license when making a purchase, or present a car registration to a police officer.

[0014] Example embodiments of the present disclosure provide systems and methods for contactless delivery. The disclosed systems and methods can also be used beyond contactless package delivery, for example, to keep people safe during a pandemic. A contactless card or other device can be tapped against a device (e.g., a smartphone) to exchange identity over a long distance. Thus, the courier can verify that they are delivering the package to the right person, and the person receiving the package can also verify that the courier who delivered it to them is authorized to deliver. In some embodiments, immunity certificates of both the person receiving the package and the courier can be used to understand the immunity of the person, or company policies around hygiene.

[0015] In some embodiments, when a contactless card or other device is tapped against a person's phone, a certificate signed by an employer (e.g., a courier) can also be transferred, either directly from the contactless card, the person's phone, or indirectly after verifying their identity online.

[0016] In some embodiments, when a contactless card is tapped to a package delivery device, the identity of the person tapping the contactless card may be determined and verified to match the package recipient. This may also be implemented using a host card emulation (HCE) that emulates a contactless card. The address on the package may be a loose address (a stored preference) or may be strictly specified in a digitally signed certificate, or may be scoped to an individual delivery transaction.

[0017] Example embodiments of the present disclosure can facilitate the efficiency and safety of transactions such as package pickup, delivery transactions, and purchases of goods or services that are subject to age restrictions, quantity restrictions, and other restrictions. In addition, identity verification can be performed without the consumer and employee or other personnel being in close proximity to each other. Furthermore, identity verification can be performed quickly without compromising the user experience and without the consumer, employee, or other personnel having to carry identification or other documents. It is understood that example embodiments of the present disclosure can be applied to a wide range of purposes where identity verification is required, such as, but not limited to, package pickup, package delivery, security (e.g., access to buildings or restricted areas), and travel (e.g., purchasing tickets, boarding an airplane or train).

[0018] 1 illustrates a system 100 for contactless package delivery according to an example embodiment. As described below, system 100 may include a contactless card 110, a delivery device 120, a server 130, and a database 140 that communicates using a network 150. Although FIG. 1 illustrates a single entity of components, system 100 may include any number of components.

[0019] The contactless card 110 can be configured to transmit the cryptogram to the delivery device 120 in response to a tap on the delivery device 120. The delivery device 120 can be configured to read the cryptogram from the contactless card 110 after the contactless card 110 enters the communication field of the delivery device 120. The delivery device 120 can then transmit the cryptogram to the server 130. The server 130 can be configured to verify the cryptogram by searching the database 140.

[0020] The contactless card 110 can perform authentication and many other functions that may otherwise require the user to carry a separate physical token in addition to the contactless card 110. By employing a contactless interface, the contactless card 110 can provide a way to interact and communicate between a user device (e.g., a mobile phone or delivery device 120) and the card itself. For example, the Europay, Mastercard, Visa (EMV) protocol that underpins many credit card transactions includes an authentication process that is sufficient for the Android operating system, but presents a challenge to iOS, which is more stringent with respect to Near Field Communication (NFC) applications that can only be used for read-only purposes. The exemplary embodiment of the contactless card 110 described herein utilizes NFC technology.

[0021] The contactless card 110 may include a payment card, such as a credit card, debit card, or gift card, issued by a service provider that is displayed on the front or back of the contactless card 110. In some examples, the contactless card 110 is not related to a payment card and may include, but is not limited to, an identification card, a membership card, and a travel card. In some examples, the contactless card 110 may include a dual interface contactless payment card. The contactless card 110 may include a substrate that may include a single layer or one or more laminates of plastic, metal, and other materials. Exemplary substrate materials include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyester, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In some examples, the contactless card 110 may have physical characteristics that conform to the ID-1 format of the ISO / IEC 7810 standard, and the contactless card 110 may conform to the ISO / IEC 14443 standard. However, it is understood that contactless cards 110 according to the present disclosure may have different characteristics, and the present disclosure does not require that contactless cards 110 be implemented as payment cards.

[0022] The contactless card 110 may also include identification information displayed on the front and / or back of the contactless card 110, and a contact pad. The contact pad may be configured to establish contact with another communication device, such as a user device, a smart phone, a laptop, desktop or tablet computer, etc. The contactless card 110 may also include processing circuitry, an antenna, and other components. These components may be located behind the contact pad or elsewhere on the substrate. The contactless card 110 may also include a magnetic strip or tape, which may be located on the back of the contactless card 110.

[0023] The contact pads of contactless card 110 may include processing circuitry for storing and processing information, the processing circuitry including processor 111 and memory 112. It will be understood that the processing circuitry may include additional components necessary to perform the functions described herein, and that additional components may include processors, memories, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware.

[0024] The memory 112 may be a read-only memory, a write-once read-multiple memory, or a read / write memory, such as RAM, ROM, and EEPROM, and the contactless card 110 may include one or more of these memories. Read-only memory may be factory programmable as read-only or programmable only once. Programmability only once offers the opportunity to write once and then read many times. Write-once read-multiple memory may be programmable at some point after the memory chip leaves the factory. Once programmed, the memory cannot be rewritten, but may be read many times. Read / write memory may be programmed and reprogrammed many times after leaving the factory. Read / write memory may also be read many times.

[0025] The memory 112 may be configured to store one or more applets 113, one or more counters 114, and a unique customer identifier 115. The one or more applets 113 may include one or more software applications configured to run on one or more contactless cards, such as a JavaCard applet. However, it is understood that the one or more applets 113 are not limited to JavaCard applets and may be any software application capable of running on a contactless card or other device having limited memory. The one or more counters 114 may include a numeric counter sufficient to store an integer number. The unique customer identifier 115 may include a unique alphanumeric identifier assigned to a user of the contactless card 110, which identifier may distinguish the user of the contactless card 110 from other contactless card users. In some examples, the customer identifier 115 may identify both a customer and an account assigned to the customer, and may further identify the contactless card 110 associated with the customer's account.

[0026] Although the processor 111 and memory 112 elements of the foregoing exemplary embodiments are described with reference to contact pads, the disclosure is not limited thereto, and it is understood that these elements may be implemented outside of the contact pads, completely separate from the contact pads, or as additional elements in addition to the processor 111 and memory 112 elements located within the contact pads.

[0027] In some examples, contactless card 110 may include one or more antennas. The one or more antennas may be located within contactless card 110 and around the processing circuitry on the contact pads. For example, the one or more antennas may be integral with the processing circuitry, or the one or more antennas may be used with an external booster coil. As another example, the one or more antennas may be external to the contact pads and processing circuitry.

[0028] In one embodiment, the coil of the contactless card 110 may function as the secondary of an air-core transformer. The terminal may communicate with the contactless card 110 by power interruption or amplitude modulation. The contactless card 110 may use the interruption of the power connection of the contactless card to infer data sent from the terminal, which may be kept functional by one or more capacitors. The contactless card 110 may communicate back by load switching or load modulation of the coil of the contactless card. Load modulation may be detected at the terminal coil through interference.

[0029] As described above, the contactless card 110 may be built on a software platform capable of operating on a smart card or other device with limited memory, such as a JavaCard, and one or more applications or applets may be securely executed. An applet may be added to the contactless card to provide a one-time password (OTP) for multi-factor authentication (MFA) in various mobile application-based use cases. The applet may be configured to respond to one or more requests, such as a near field wireless data exchange request, from a reader, such as a mobile NFC reader, and generate an NDEF message that includes the cryptographically secure OTP encoded as an NDEF text tag.

[0030] The delivery device 120 may be a network-enabled computing device. Exemplary network-enabled computing devices may include, but are not limited to, a server, a network appliance, a personal computer, a workstation, a telephone, a handheld personal computer, a personal digital assistant, a thin client, a fat client, an Internet browser, a mobile device, a kiosk, a contactless card, or other computing or communication device. For example, a network-enabled computing device may include an Apple® iPhone®, iPod®, iPad®, or other mobile device running Apple's iOS® operating system, any device running Microsoft's Windows® mobile operating system, any device running Google's Android® operating system, and / or other smartphones, tablets, or similar wearable mobile devices.

[0031] The delivery device 120 may include a processor 121, a memory 122, and an application 123. The processor 121 may be a processor, microprocessor, or other processor, and the delivery device 120 may include one or more of these processors. The processor 121 may include processing circuitry, which may include additional components including additional processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware as necessary to perform the functions described herein.

[0032] The processor 121 may be coupled to the memory 122. The memory 122 may be a read-only memory, a write-once read-multiple memory, or a read / write memory, such as RAM, ROM, and EEPROM, and the delivery device 120 may include one or more of these memories. The read-only memory may be factory programmable as read-only or programmable only once. Programmability only once provides the opportunity to write once and then read many times. The write-once read-multiple memory may be programmable at some point after the memory chip leaves the factory. Once programmed, the memory cannot be rewritten, but may be read many times. The read / write memory may be programmed and reprogrammed many times after leaving the factory, and reprogrammed many times after leaving the factory. The read / write memory may also be read many times. The memory 122 may be configured to store one or more software applications, such as application 123, and other data, such as a user's shopping and financial account information.

[0033] The application 123 may include one or more software applications, such as a parcel delivery application and a contactless card reading application, that include instructions for execution on the delivery device 120. In some examples, the delivery device 120 may execute one or more applications, such as software applications that enable network communication with one or more components of the system 100, transmit and / or receive data, and perform the functions described herein. When executed by the processor 121, the application 123 may provide functionality to execute and perform the functions described herein, in particular the steps and functions of the process flows described below. For example, the parcel delivery application of the application 123 may be executed to perform retrieval of parcel delivery information stored in the database 140. The contactless card reading application of the application 123 may be executed to perform communication with the contactless card 110. Such processes may be implemented in software, such as software modules for execution by a computer or other machine. The application 123 may provide a GUI through which a user may view and interact with other components and devices in the system 100. The GUI may be formatted, for example, as a web page in HyperText Markup Language (HTML), Extensible Markup Language (XML), or other suitable format, for presentation on a display device depending on the application being used by a user to interact with system 100.

[0034] The delivery device 120 may further include a display 124 and an input device 125. The display 124 may be any type of device for presenting visual information, such as a computer monitor, flat panel display, and mobile device screen, including liquid crystal display, light emitting diode display, plasma panel, and cathode ray tube display. The input device 125 may include any device for inputting information into the delivery device 120 available and supported by the delivery device 120, such as a touch screen, keyboard, mouse, cursor control device, touch screen, microphone, digital camera, video recorder, or camcorder. These devices may be used to input information and interact with the software and other devices described herein. For example, the input device 125 may include a card reader. The card reader may be configured to read from and / or communicate with the contactless card 110. In conjunction with the application 123, the card reader may communicate with the contactless card 110 using short-range wireless communication (e.g., NFC).

[0035] Server 130 may be a network-enabled computing device. Exemplary network-enabled computing devices may include, but are not limited to, a server, a network appliance, a personal computer, a workstation, a telephone, a handheld personal computer, a personal digital assistant, a thin client, a fat client, an Internet browser, a mobile device, a kiosk, a contactless card, or other computing or communication device. For example, a network-enabled computing device may include an Apple® iPhone®, iPod®, iPad®, or other mobile device running Apple's iOS® operating system, any device running Microsoft's Windows® mobile operating system, any device running Google's Android® operating system, and / or other smartphones, tablets, or similar wearable mobile devices.

[0036] Server 130 may include processor 131, memory 132, and application 133. Processor 131 may be a processor, microprocessor, or other processor, and server 130 may include one or more of these processors. Processor 131 may include processing circuitry that may include additional components including additional processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware as necessary to perform the functions described herein.

[0037] The processor 131 may be coupled to the memory 132. The memory 132 may be a read-only memory, a write-once read-multiple memory, or a read / write memory, such as RAM, ROM, and EEPROM, and the server 130 may include one or more of these memories. The read-only memory may be factory programmable as read-only or programmable only once. Programmability only once provides the opportunity to write once and then read many times. The write-once read-multiple memory may be programmable at some point after the memory chip leaves the factory. Once programmed, the memory cannot be rewritten, but may be read many times. The read / write memory may be programmed and reprogrammed many times after leaving the factory, and reprogrammed many times after leaving the factory. The read / write memory may also be read many times. The memory 132 may be configured to store one or more software applications, such as application 133, and other data, such as a user's shopping and financial account information.

[0038] The application 133 may include one or more software applications that include instructions for execution on the server 130. In some examples, the server 130 may execute one or more applications, such as software applications that enable network communication with one or more components of the system 100, transmit and / or receive data, and perform the functions described herein. When executed by the processor 131, the application 133 may provide functionality to execute and perform the functions described herein, in particular the steps and functions of the process flows described below. For example, the application 133 may be executed to perform cryptographic verification. Such processes may be implemented in software, such as software modules for execution by a computer or other machine. The application 133 may provide a GUI through which a user may view and interact with other components and devices in the system 100. The GUI may be formatted as, for example, a web page in HyperText Markup Language (HTML), Extensible Markup Language (XML), or other suitable format for presentation on a display device depending on the application used by the user to interact with the system 100.

[0039] Server 130 may further include a display 134 and input devices 135. Display 134 may be any type of device for presenting visual information, such as a computer monitor, flat panel display, and mobile device screen, including liquid crystal displays, light emitting diode displays, plasma panels, and cathode ray tube displays. Input devices 135 may include any device available and supported by server 130 for inputting information to server 130, such as a touch screen, keyboard, mouse, cursor control device, touch screen, microphone, digital camera, video recorder, or camcorder. These devices may be used to input information and interact with the software and other devices described herein.

[0040] Database 140 may be one or more databases configured to store data including, but not limited to, user personal information, user financial accounts, user identities, user transactions, and authenticated and unauthenticated documents. Database 140 may include a relational database, a non-relational database, or other database implementations, including a plurality of relational and non-relational databases, and any combination thereof. In some examples, database 140 may include a desktop database, a mobile database, or an in-memory database. Additionally, database 140 may be hosted internally by server 130 or externally to server 130, such as by a server, a cloud-based platform, or any storage device in data communication with server 130.

[0041] The system 100 may include one or more networks 150. In some examples, the network 150 may be one or more of a wireless network, a wired network, or any combination of wireless and wired networks and may be configured to connect the delivery devices 120, the server 130, and the database 140. For example, the network 150 may include one or more of a fiber optic network, a passive optical network, a cable network, an Internet network, a satellite network, a wireless local area network (LAN), a global system for mobile communications, a personal communication service, a personal area network, a wireless application protocol, a multimedia message service, an enhanced message service, a short message service, a time division multiplexing system, a code division multiple access system, D-AMPS, Wi-Fi, fixed wireless data, IEEE 802.11b, 802.15.1, 802.11n and 802.11g, Bluetooth, NFC, radio frequency identification (RFID), Wi-Fi, and the like.

[0042] Further, network 150 may include a global network such as, but not limited to, telephone lines, fiber optics, IEEE Ethernet 902.3, wide area networks, wireless personal area networks, LANs, or the Internet. Further, network 150 may support an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof. Network 150 may further include one network or any number of the exemplary types of networks described above, operating as a standalone network or in conjunction with one another. Network 150 may utilize one or more protocols of one or more network elements to which they are communicatively coupled. Network 150 may translate to one or more protocols of the network devices or translate from other protocols to one or more protocols of the network devices. Although network 150 is illustrated as a single network, it should be understood that, according to one or more examples, network 150 may comprise multiple interconnected networks, such as, for example, the Internet, a service provider network, a cable television network, an enterprise network (such as a credit card association network), and a home network. Network 150 may further comprise or be configured to form one or more front channels that are publicly accessible and where communications are observable, and one or more secure back channels that are not publicly accessible and where communications are not observable.

[0043] In some examples, communication between the delivery device 120, the server 130, and the database 140 using the network 150 may be performed using one or more front channels and one or more secure back channels. The front channel may be a communication protocol employing a publicly accessible and / or insecure communication channel, whereby communications sent to the delivery device 120, the server 130, and / or the database 140 may be sent from any other device, whether known or unknown to the delivery device 120, the server 130, and / or the database 140, if that device possesses the address (e.g., network address, Internet Protocol (IP) address) of the delivery device 120, the server 130, and / or the database 140. Exemplary front channels may include, but are not limited to, the Internet, open networks, and other publicly accessible communication networks. In some examples, communications sent using the front channel may be subject to unauthorized observation by another device. In some examples, front channel communications may include HyperText Transfer Protocol (HTTP) Secure Sockets Layer (SSL) communications, HTTP Secure (HTTPS) communications, and browser-based communications with servers or other devices.

[0044] A secure backchannel may be a communication protocol that employs a secure and / or non-publicly accessible communication channel. Secure backchannel communications sent to the delivery device 120, the server 130, and / or the database 140 may not be sent from any device, but only from a select number of parties. In some examples, the select number of devices may include known, trusted, or previously approved devices. Exemplary secure backchannels include, but are not limited to, closed networks, private networks, virtual private networks, offline private networks, and other private communication networks. In some examples, communications sent using a secure backchannel may not be subject to unauthorized observation by another device. In some examples, secure backchannel communications may include HyperText Transfer Protocol (HTTP) Secure Sockets Layer (SSL) communications, HTTP Secure (HTTPS) communications, and browser-based communications with a server or other device.

[0045] In some examples, the contactless card 110 can be associated with a user and can be used by the user, e.g., a customer to whom a package is to be delivered. The delivery device 120 can be associated with a person delivering the package and can be operated by the person, e.g., a courier from a courier service. The server 130 can be associated with a financial institution, such as a bank or credit card company, that provides financial services to users of the contactless card 110. The contactless card 110 can be issued by a financial institution. However, it should be understood that the present disclosure is encompassing all entities and is not limited to financial institutions.

[0046] Figure 2 shows a sequence diagram 200 for contactless package delivery according to an example embodiment. Figure 2 may reference components that are the same as or similar to those shown in Figure 1, including contactless cards, delivery devices, servers, databases, and networks.

[0047] In step 210, the contactless card (e.g., contactless card 110) transmits a cryptogram after the contactless card enters a communication field of a delivery device (e.g., delivery device 120). The contactless card may be tapped by a user against the delivery device. The delivery device may be configured with a card reader to read the cryptogram from the contactless card in response to the tap. The card reader may include a communication interface to generate the communication field of the card reader. As used herein, tapping the contactless card against the delivery device may not mean that the contactless card physically contacts the delivery device. Tapping the contactless card against the delivery device may refer to the contactless card entering the communication field of the card reader. The cryptogram may be stored in a memory of the contactless card. The cryptogram may be associated with a unique identifier of a user account.

[0048] In step 215, the delivery device may transmit the cryptogram to a server (e.g., server 130). Upon reading the cryptogram from the contactless card, the delivery device transmits the cryptogram to the server over a network (e.g., network 150). Prior to transmission, the cryptogram may be encrypted by the contactless card.

[0049] In step 220, the server verifies the ciphertext and decrypts the ciphertext to extract the unique identifier. When the server receives the ciphertext, the server may verify the ciphertext and then decrypt it. The server may then extract the unique identifier for the user account.

[0050] In step 225, the server 130 may query the identity of the user account using the unique identifier. In this step, the server communicates with a database (e.g., database 140) to retrieve the identity of the user account. The identity of the user account is stored in the database. The identity of the user account may include the name of the user tapping the contactless card. The user account may include one or more email addresses associated with the user, the user's phone number, the user's postal address, etc. If the identity of the user account matches the unique identifier of the user account, the user of the contactless card is verified.

[0051] In step 230, the server may generate a digital signature based on the identity of the user account. After obtaining and verifying the identity of the user account, the server may be configured to generate a digital signature of the identity. The digital signature may be a signature of the user's name or other signature associated with the user's name.

[0052] In step 235, the server may send a confirmation notice to the delivery device, including the identity and digital signature of the user account. The confirmation notice may indicate that the user of the contactless card has been confirmed, what the identity of the user is, and the digital signature of the identity.

[0053] When the delivery device receives the confirmation, the delivery device may display the confirmation on a display of the delivery device. The delivery device may be configured to sign a package receipt document with a digital signature.

[0054] Figure 3 shows a flow chart of a method 300 of contactless package delivery according to an example embodiment. Figure 3 may reference components that are the same as or similar to those shown in Figures 1 and 2, including contactless cards, delivery devices, servers, databases, and networks. Method 300 may be implemented in system 100 and may include the following steps.

[0055] In step 305, the contactless card transmits the cryptogram to the server via one or more intermediary devices. As used herein, the contactless card may include a payment card such as a credit card, debit card, or gift card issued by a service provider that is displayed on the front or back of the contactless card. In some examples, the contactless card is not associated with a payment card and may include, but is not limited to, an identification card. In some examples, the payment card may include a dual interface contactless payment card. The contactless card may store the cryptogram in its memory and transmit the cryptogram to the server when tapped against one or more intermediary devices. The one or more intermediary devices may include a delivery device (e.g., delivery device 120).

[0056] The cryptogram may include a unique identifier associated with the user / customer account. The cryptogram may further include a counter value and a number of keys, and the contactless card processor is configured to generate the cryptogram using the counter value, the number of keys, and the unique identifier.

[0057] The counter value may be updated by the contactless card for each interaction between the contactless card and one or more intermediary devices.

[0058] For example, the contactless card communicates with one or more intermediary devices that are brought into close proximity to the contactless card. The communication between the one or more intermediary devices and the contactless card may include the contactless card being sufficiently close to a card reader of the one or more intermediary devices to allow for Near Field Communication (NFC) data transfer between the one or more intermediary devices and the contactless card.

[0059] In other embodiments, the contactless card may communicate with the intermediary device through other means, including but not limited to Bluetooth, satellite, Wi-Fi, wired communication, and / or any combination of wireless and wired connections. According to some embodiments, the contactless card may be configured to communicate with a card reader of the intermediary device through NFC when the contactless card is within range of the card reader. In other examples, communication with the contactless card may be achieved through a physical interface, such as, for example, a Universal Serial Bus interface or a card swipe interface.

[0060] In step 310, the server verifies the cryptogram. In some examples, the cryptogram may be a message authentication code (MAC) cryptogram. The MAC cryptogram may be generated from a message that includes the shared secret. The server may generate an additional MAC cryptogram based on the shared secret and compare the additional MAC cryptogram to the MAC cryptogram received from the contactless card. If the additional MAC cryptogram matches the MAC cryptogram received from the contactless card, the MAC cryptogram received from the contactless card is validated.

[0061] In some embodiments, each time the contactless card is read, a counter value is sent to the server. This may be done to determine if the counter value is equal to a counter value maintained by the server for validation and security purposes. The one or more counters may be configured to prevent replay attacks. For example, if a cryptogram is captured and replayed, it is immediately rejected if the counter has been read, used, or otherwise expired. If the counter has not been used, it may be replayed. In some examples, the counter value updated on the contactless card is different from the counter updated for the transaction. In some examples, the contactless card may include a first applet, which may be a transaction applet, and a second applet. Each applet may include a counter.

[0062] In some instances, counters may become out of sync between the contactless card and the server. For example, the contactless card may be activated and the counter updated, and a new communication may be generated by the contactless card, but the communication may not be sent for processing by the server. This may cause the counter of the contactless card and the counter maintained by the server to become out of sync. This may occur unintentionally, including, for example, when the contactless card is stored adjacent to the device (e.g., carried in a pocket with the device) and when the contactless card is read at an angle, which may include the contactless card being activated in the NFC field but not aligned or positioned such that it cannot be read. When the contactless card is near the device, the NFC field of the device may be turned on, powering the contactless card and updating its counter, but the application on the device does not receive the communication.

[0063] To keep the counters synchronized, an application such as a background application may be executed, which may be configured to detect that a read due to detection has occurred and advance the counter when the intermediary device wakes up and synchronizes with the server. Because the contactless card and server counters may become out of sync, the server may be configured to allow the contactless card's counter to be updated a threshold or predetermined number of times before it is read by the server and considered still valid. For example, if the counter is configured to increment (or decrement) by 1 for each event indicating activation of the contactless card, the server may accept any counter value read from the contactless card as valid, or any counter value within a threshold range (e.g., from 1 to 10). Additionally, the server may be configured to request a gesture associated with the contactless card, such as a user tap, if it reads a counter value that has advanced beyond 10 but is below another threshold range value (e.g., 1000). If the counter value is within the desired or acceptable range from the user tap, authentication is successful.

[0064] In step 315, the server decrypts the ciphertext. The ciphertext may be encrypted by the contactless card before being sent to the server. The ciphertext may be encrypted using one or more encryption algorithms including at least one of a symmetric encryption algorithm, a Hash-based Message Authentication Code (HMAC) algorithm, and a Cipher-based Message Authentication Code (CMAC) algorithm. The server may decrypt the ciphertext using the one or more encryption algorithms.

[0065] At step 320, the server extracts the unique identifier from the decrypted ciphertext. The unique identifier may include a unique alphanumeric identifier assigned to the contactless card user. The unique identifier may distinguish the contactless card user from other contactless card users. In some examples, the unique identifier may identify both the customer and the account assigned to the customer, and may further identify the contactless card associated with the customer's account.

[0066] In step 325, the server queries a database for the identity of the user account using the unique identifier. In some embodiments, the cryptographically secure and non-interceptable unique identifier may be transmitted to one or more backend services. The unique identifier may be configured to look up secondary information about the individual. The secondary information may include personally identifiable information about the user (e.g., the user's identity). In some examples, the secondary information may be stored in a contactless card.

[0067] In step 330, the server generates a digital signature based on the identity of the user account. After verifying and obtaining the identity of the user account, the server may use the identity to generate a digital signature for the user. The user's identity may be the user's name. The digital signature may be any suitable form of signature.

[0068] In step 335, the server sends a confirmation notice to the delivery device, including the identity of the user account and the digital signature. The confirmation notice may indicate that the user / customer who tapped the contactless card against the delivery device has been confirmed. Upon receiving the confirmation notice, the delivery device may display the confirmation notice on the display of the delivery device. The delivery device may display the digital signature next to the name of the user / customer to whom the package is being delivered. This digital signature may be considered as authentication and confirmation to release the package to the user.

[0069] Figure 4 shows a flow chart of a method 400 of contactless package delivery according to an example embodiment. Figure 4 may reference components that are the same as or similar to those shown in Figures 1-3, including contactless cards, delivery devices, servers, databases, and networks. Method 400 may include the following steps.

[0070] In some embodiments, in addition to the unique identifier of the user account, one or more authentication factors may be used to verify the identity of the user. The one or more authentication factors may be any suitable factor described below.

[0071] In step 405, the contactless card transmits the cryptogram to the server via one or more intermediary devices. The contactless card may store the cryptogram in its memory and transmit the cryptogram to the server when tapped against one or more intermediary devices. The cryptogram may include a unique identifier associated with the user / customer account. The one or more intermediary devices may include a delivery device (e.g., delivery device 120).

[0072] In step 410, the server verifies the ciphertext. The ciphertext may be a MAC ciphertext. The MAC ciphertext may be generated from a message that includes the shared secret. The server may generate an additional MAC ciphertext based on the shared secret and compare the additional MAC ciphertext with the MAC ciphertext received from the contactless card. If the additional MAC ciphertext matches the MAC ciphertext received from the contactless card, the MAC ciphertext received from the contactless card is validated.

[0073] The server decrypts the ciphertext in step 415. The ciphertext may be encrypted using one or more encryption algorithms before being sent to the server. The server may decrypt the ciphertext using one or more encryption algorithms.

[0074] In step 420, the server extracts the unique identifier. The unique identifier may be used to distinguish the contactless card user from other contactless card users. The unique identifier may identify both the customer and the account assigned to the customer, and may further identify the contactless card associated with the customer's account.

[0075] In step 425, the server queries the database for the identity of the user account using the unique identifier. The unique identifier may be configured to look up secondary information about the person. The secondary information may include personally identifiable information about the user (e.g., the user's identity).

[0076] In step 430, the server receives one or more documents from the database to verify the identity of the user account. The one or more documents may be stored in the database. In another embodiment, the one or more documents may be stored on a contactless card and sent to the server when the contactless card is read on an intermediate device (e.g., a delivery device). In another embodiment, the one or more documents may be stored on a delivery device and sent to the server along with the cryptogram when the contactless card is read on the delivery device.

[0077] The one or more documents may be authenticated documents, such as a certificate signed by an employer (e.g., a courier). The one or more documents may also include information about the delivery package stored on the delivery device, which may be sent by the delivery device to the server as an authentication factor to verify the identity of the user. The information about the delivery package may include the user's name, the user's delivery address, the user's phone number, etc. The one or more documents may also be unauthenticated documents, such as a copy of the user's driver's license. In some embodiments, the one or more documents may include a profile picture of a user account, which may be sent to the server to verify the identity of the user account.

[0078] In step 435, the server generates a digital signature based on the identity of the user account. The identity of the user may be the user's name. The digital signature may be any suitable form of signature.

[0079] In step 440, the server sends a confirmation notice including the identity of the user account and the digital signature. Upon receiving the confirmation notice, the delivery device may display the digital signature next to the name of the user / customer to whom the package is being delivered. This digital signature may be considered as authentication and confirmation to release the package to the user.

[0080] Unlike the system 100 in FIG. 1, in some embodiments, the intermediary device may be a user device other than the delivery device. A contactless card may be tapped against the user device which transmits a cryptogram to a server. The delivery device may receive a confirmation. FIG. 5 illustrates a system 500 for contactless package delivery according to an example embodiment. As described further below, the system 500 may include a contactless card 510, a user device 520, a server 530, a database 540, and a delivery device 550 communicating using a network 560. Although FIG. 5 illustrates a single entity of components, the system 500 may include any number of components.

[0081] The contactless card 510 can be configured to transmit the cryptogram to the user device 520 in response to a tap on the user device 520. The user device 520 may be configured to read the cryptogram from the contactless card 510 after the contactless card 510 is placed in the communication field of the user device 520. The user device 520 may then transmit the cryptogram to the server 530. The server 530 may be configured to verify the cryptogram by searching the database 540. The server 530 may transmit a confirmation notice including the digital signature to the delivery device 550.

[0082] Contactless card 510 may include processing circuitry for storing and processing information, including a microprocessor 511 and a memory 512. Memory 512 may be configured to store one or more applets 513, one or more counters 514, and a unique customer identifier 515. In some examples, contactless card 510 is similar to contactless card 110 in FIG.

[0083] The user device 520 may be a network-enabled computing device. The user device 520 may include a processor 521, a memory 522, and an application 523. The application 523 may include one or more software applications, such as a contactless card reading application, that include instructions for execution on the user device 520. The user device 520 may further include a display 524 and an input device 525.

[0084] The user device 520 may be a network-enabled computing device. Exemplary network-enabled computing devices may include, but are not limited to, a server, a network appliance, a personal computer, a workstation, a telephone, a handheld personal computer, a personal digital assistant, a thin client, a fat client, an Internet browser, a mobile device, a kiosk, a contactless card, or other computing or communication device. For example, a network-enabled computing device may include an Apple® iPhone®, iPod®, iPad®, or other mobile device running Apple's iOS® operating system, any device running Microsoft's Windows® mobile operating system, any device running Google's Android® operating system, and / or other smartphones, tablets, or similar wearable mobile devices.

[0085] The user device 520 may include a processor 521, a memory 522, and an application 523. The processor 521 may be a processor, microprocessor, or other processor, and the user device 520 may include one or more of these processors. The processor 521 may include processing circuitry that may include additional components including additional processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware as necessary to perform the functions described herein.

[0086] The processor 521 may be coupled to the memory 522. The memory 522 may be a read-only memory, a write-once read-multiple memory, or a read / write memory, such as RAM, ROM, and EEPROM, and the user device 520 may include one or more of these memories. The read-only memory may be factory programmable as read-only or programmable only once. Programmability only once provides the opportunity to write once and then read many times. The write-once read-multiple memory may be programmable at some point after the memory chip leaves the factory. Once programmed, the memory cannot be rewritten, but may be read many times. The read / write memory may be programmed and reprogrammed many times after leaving the factory, and reprogrammed many times after leaving the factory. The read / write memory may also be read many times. The memory 522 may be configured to store one or more software applications, such as application 523, and other data, such as the user's shopping and financial account information.

[0087] The applications 523 may include one or more software applications, such as a parcel delivery application and a contactless card reader application, that include instructions for execution on the user device 520. In some examples, the user device 520 may execute one or more applications, such as software applications that enable network communication with one or more components of the system 500, transmit and / or receive data, and perform the functions described herein. When executed by the processor 521, the applications 523 may provide functionality to execute and perform the functions described herein, in particular the steps and functions of the process flows described below. For example, the parcel delivery application of the applications 523 may be executed to execute retrieval of parcel delivery information stored in the database 540. The contactless card reader application of the applications 523 may be executed to execute communication with the contactless card 510. Such processes may be implemented in software, such as software modules for execution by a computer or other machine. The applications 523 may provide a GUI through which a user may view and interact with other components and devices in the system 500. The GUI may be formatted, for example, as a web page in HyperText Markup Language (HTML), Extensible Markup Language (XML), or other suitable format, for presentation on a display device depending on the application being used by a user to interact with system 500.

[0088] The user device 520 may further include a display 524 and input devices 525. The display 524 may be any type of device for presenting visual information, such as a computer monitor, flat panel display, and mobile device screen, including liquid crystal display, light emitting diode display, plasma panel, and cathode ray tube display. The input devices 525 may include any device for inputting information into the user device 520 available and supported by the user device 520, such as a touch screen, keyboard, mouse, cursor control device, touch screen, microphone, digital camera, video recorder, or camcorder. These devices may be used to input information and interact with the software and other devices described herein. For example, the input devices 525 may include a card reader. The card reader may be configured to read from and / or communicate with the contactless card 510. In conjunction with the application 523, the card reader may communicate with the contactless card 510 using short-range wireless communication (e.g., NFC).

[0089] The server 530 may be a network-enabled computing device. The server 530 may include a processor 531, a memory 532, and an application 533. The server 530 may further include a display 534 and an input device 535. In some examples, the server 530 is similar to the server 130 in FIG.

[0090] Database 540 may be one or more databases configured to store data including, but not limited to, user personal information, user financial accounts, user identities, user transactions, and authenticated and unauthenticated documents. In some examples, database 540 is similar to database 140 in FIG.

[0091] The delivery device 550 may be a network-enabled computing device. The delivery device 550 may include a processor 551, a memory 552, and an application 553. The delivery device 550 may further include a display 554 and an input device 555. In some examples, the delivery device 550 is similar to the delivery device 120 in FIG.

[0092] The system 500 may include one or more networks 560. The one or more networks 560 may be similar to the network 150 in FIG.

[0093] In some examples, the contactless card 510 can be associated with a user and can be used by the user, e.g., a customer to whom a package is to be delivered. The user device 520 can be associated with a user who holds the contactless card 510. The server 530 can be associated with a financial institution, such as a bank or credit card company, that provides financial services to a user of the contactless card 510. The contactless card 510 can be issued by the financial institution. The delivery device 550 can be associated with a person delivering a package and can be operated by that person, e.g., a delivery person of a courier service.

[0094] Figure 6 shows a sequence diagram 600 for contactless package delivery according to an example embodiment. Figure 6 may reference components that are the same as or similar to those shown in Figures 1-5, including contactless cards, user devices, delivery devices, servers, databases, and networks.

[0095] In step 610, the contactless card (e.g., contactless card 510) transmits the cryptogram after the contactless card enters a communication field of a user device (e.g., user device 520). The contactless card may be tapped by a user against the user device. The user device may be configured with a card reader to read the cryptogram from the contactless card in response to the tap. The card reader may include a communication interface to generate the communication field of the card reader. As used herein, tapping the contactless card against a user device may not mean that the contactless card physically touches the user device. Tapping the contactless card against a user device may refer to the contactless card entering the communication field of the card reader. The cryptogram may be stored in a memory of the contactless card. The cryptogram may be associated with a unique identifier of a user account.

[0096] In step 615, the user device may transmit the ciphertext to a server (e.g., server 530). Upon reading the ciphertext from the contactless card, the user device transmits the ciphertext to the server over a network (e.g., network 560). Prior to transmission, the ciphertext may be encrypted by the contactless card.

[0097] In step 620, the server verifies the ciphertext and decrypts the ciphertext to extract the unique identifier. When the server receives the ciphertext, the server may verify the ciphertext and then decrypt it. The server may then extract the unique identifier for the user account.

[0098] In step 625, the server may query the identity of the user account using the unique identifier. In this step, the server communicates with a database (e.g., database 540) to retrieve the identity of the user account. The identity of the user account is stored in the database. The identity of the user account may include the name of the user tapping the contactless card. The user account may include one or more email addresses associated with the user, the user's phone number, the user's postal address, etc. If the identity of the user account matches the unique identifier of the user account, the user of the contactless card is verified.

[0099] In step 630, the server may generate a digital signature based on the identity of the user account. After obtaining and verifying the identity of the user account, the server may be configured to generate a digital signature of the identity. The digital signature may be a signature of the user's name or other signature associated with the user's name.

[0100] In step 635, the server may send a confirmation notice to the delivery device, including the identity and digital signature of the user account. The confirmation notice may indicate that the contactless card user has been confirmed, what the user's identity is, and the digital signature of the identity. When the delivery device receives the confirmation notice, the delivery device may display the confirmation notice on a display of the delivery device. The delivery device may be configured to sign the package receipt with the digital signature.

[0101] Figure 7 shows a flow chart of a method 700 of contactless package delivery according to an example embodiment. Figure 7 may reference components that are the same as or similar to those shown in Figures 1-6, including contactless cards, user devices, delivery devices, servers, databases, and networks. Method 700 may be implemented in system 500 and may include the following steps.

[0102] In step 705, the contactless card transmits the cryptogram to the server via an intermediary device. The intermediary device may include a user device (e.g., user device 520). Communication between the user device and the contactless card may include the contactless card being sufficiently close to a card reader of the user device to allow near field communication (NFC) data transfer between the user device and the contactless card.

[0103] In step 710, the server verifies the ciphertext. In step 715, the server decrypts the ciphertext. In step 720, the server extracts the unique identifier from the decrypted ciphertext. In step 725, the server uses the unique identifier to query a database (e.g., database 540) for the identity of the user account. In step 730, the server generates a digital signature based on the identity of the user account. Steps 705-730 are similar to steps 305-330 in FIG. 3. Details of steps 705-730 will not be repeated here.

[0104] In step 735, the server sends a confirmation notice to the delivery device, including the identity of the user account and the digital signature. The confirmation notice may indicate that the user / customer who tapped the contactless card against the user device has been confirmed. Upon receiving the confirmation notice, the delivery device may display the confirmation notice on the display of the delivery device. The delivery device may display the digital signature next to the name of the user / customer to whom the package is being delivered. This digital signature may be considered as authentication and confirmation to release the package to the user.

[0105] In some embodiments, one or more authentication factors may be used to verify the identity of a user / user account in addition to a unique identifier as used in FIG. 7. FIG. 8 shows a flow chart of a method 800 of contactless package delivery according to an example embodiment. In the method of FIG. 8, one or more authentication factors may be used to verify the identity of a user / user account. FIG. 8 may refer to components that are the same as or similar to those shown in FIGS. 1-7, including contactless cards, user devices, delivery devices, servers, databases, and networks. Method 800 may be implemented in system 500 and may include the following steps:

[0106] Method 800 includes: The contactless card sends a ciphertext to a server through an intermediary device (user device 520) (step 805). The server verifies the ciphertext (step 810). The server decrypts the ciphertext (step 815). The server extracts the unique identifier (step 820). The server uses the unique identifier to query a database for the identity of the user account (step 825). The server receives one or more authentication factors from the database to verify the identity of the user account (step 830). The server generates a digital signature based on the identity of the user account (step 835). The server sends a confirmation notice including the identity of the user account and the digital signature (step 840). Steps 805-825 and 835-840 are similar to the corresponding steps 705-725 and 730-735, and their details will not be repeated here.

[0107] In step 830, one or more authentication factors may be provided by the user device 520 and / or the delivery device 550. For example, the user device 520 may send a geo-signature of the user device 520 to the server, and the delivery device 550 may send a geo-signature of the delivery device 550 to the server. The server may compare the geo-signature of the user device to the geo-signature of the delivery device and generate a digital signature based on the results of the comparison.

[0108] The one or more authentication factors may also include at least one selected from the group of a password, a personal identification number (PIN), and a biometric characteristic. The server may verify the identity of the user account based on the one or more authentication factors.

[0109] In some embodiments, the delivery device 550 may send a card tap notification to the user device 520 through a server. For example, when a parcel delivery person is approaching or at a parcel pickup location (e.g., a user's home address / parcel delivery address), the delivery person may operate the delivery device to send a card tap notification to the user device. Upon receiving the card tap notification, the user may tap a contactless card against the user device. FIG. 9 illustrates a method 900 for contactless parcel delivery based on card tap notification, according to an example embodiment. FIG. 9 may reference components that are the same or similar to those illustrated in FIGS. 1-8, including a user device, a server, a database, and a delivery device.

[0110] In step 905, the server receives a card tap notification. The card tap notification may be initiated by the delivery device and sent to the server. Upon receiving the card tap notification, the server may forward / send the card tap notification to the user device, prompting the user to read the contactless card. The user of the user device may then tap the contactless card against the user device in accordance with the card tap notification.

[0111] In step 910, the server may read the contactless card based on the card tap notification. For example, after the contactless card is tapped against the user device, the user device may receive a cryptogram from the contactless card and then transmit the cryptogram to the server.

[0112] In step 915, the server may receive a tap completion notification from the user device. After the contactless card is tapped, the user device generates a card tap completion notification, which is then sent to the server. The server may send a card tap completion notification to the delivery device, which notifies the delivery person that the contactless card has been tapped against the user device.

[0113] In step 920, the server may use the tap completion notification to generate a digital signature of the identity of the user account. For example, as described above, the cryptogram may be verified by the server and the identity of the user account may be obtained by the server. The server may further verify the identity / user of the user account based on the card tap completion notification and then generate a digital signature of the identity of the user.

[0114] In some embodiments, the delivery device 550 may send a universal resource locator (URL) link for card tap to the user device 520 through a server. For example, when a parcel delivery person is approaching or at a parcel pickup location (e.g., a user's home address / parcel delivery address), the delivery person may operate the delivery device to send a URL link for card tap to the user device. Upon receiving the URL link for card tap, the user may tap a contactless card against the user device. FIG. 10 illustrates a method 1000 for contactless parcel delivery based on a URL link for card tap according to an example embodiment. FIG. 10 may refer to components that are the same or similar to those illustrated in FIGS. 1-9, including a user device, a server, a database, and a delivery device.

[0115] In step 1005, the server may receive a URL link for the card tap. The URL link for the card tap may be initiated by the delivery device and sent to the server. Upon receiving the URL link, the server may forward / send the URL link to the user device.

[0116] In step 1010, a user of the user device may open the URL link to display a web page and then tap the contactless card against the user device through the web page.

[0117] In step 1015, the server reads the contactless card. For example, after the contactless card is tapped against the user device through a web page, the user device may receive a cryptogram from the contactless card and then send the cryptogram to the server. For example, the web page may include JavaScript that interacts with the underlying native platform of the web browser to initiate an NFC read. The web page then obtains the content of the NFC read and sends it to the server.

[0118] In step 1020, the server may receive a tap completion notification from the user device. After the contactless card is tapped, the user device may generate a card tap completion notification through a web page, which is then sent to the server. The server may send a card tap completion notification to the delivery device, which notifies the delivery person that the contactless card has been tapped against the user device.

[0119] In step 1025, the server may use the tap completion notification to generate a digital signature of the identity of the user account. For example, as described above, the cryptogram may be verified by the server and the identity of the user account may be obtained by the server. The server may further verify the identity / user of the user account based on the card tap completion notification and then generate a digital signature of the identity of the user.

[0120] In some embodiments, a contactless card may be embodied in a host card emulation. For example, user device 520 in FIG. 5 may emulate a contactless card as opposed to acting as a reader for a contactless card. In this example, user device 520 may act as a contactless card and can be tapped against another device (e.g., delivery device 120 or delivery device 550). Thus, instead of authenticating a user through one or more second factors, the delivery device can communicate with a server to determine and verify the identity of the user in preparation for a scheduled delivery.

[0121] In some examples, a user device emulating a contactless card can also operate anonymously or in an identified manner, but in either case, limiting the disclosure of personal information. The delivery device can contact the server using a request service to verify the user. The server can respond with a decision indicating whether the user has been verified. The delivery device can also submit a package delivery address to the server, which can be used to match the identity to a contactless card identifier on a database.

[0122] In some embodiments, after tapping the contactless card, the user's profile picture may be transmitted. For example, when the user enters or drives to a store, the user can tap their contactless card on a card reader, and the contactless card may transmit the user's profile picture to the store attendant. The store attendant may send the user their picture based on information stored with the user's profile. In this way, the user can recognize the store attendant from one end of the store without physical contact. If a close interaction is required, the user and store attendant are notified of each other and can quickly proceed with the interaction without passing each other or running into other people.

[0123] In some embodiments, the digital signature can be a direct signature or an indirect signature. For example, a direct signature refers to the signature of the known recipient of the delivery package (or a person associated with the account of the known recipient), and an indirect signature refers to the signature of a person other than the known recipient of the delivery package. For example, if a person not listed on the delivery package can tap their contactless card, their name can be applied as an indirect signature. If this indirect signature can satisfy the delivery conditions, a notification can be sent to the known recipient of the delivery package indicating that the person has signed for the package. However, if the delivery requires a direct signature, the system can request a signature from the known recipient, and then the known recipient listed on the delivery package can tap their contactless card.

[0124] In some embodiments, it may be desirable to tap the contactless card multiple times to prevent replay attacks. As used herein, a replay attack may refer to the unauthorized interception of a ciphertext message and duplicating this message for use in signing for a package. For example, the ciphertext message can be read and statically programmed into a writeable NFC tag, which can provide the same ciphertext when read repeatedly (without generating a new counter).

[0125] By tapping the contactless card multiple times (e.g., twice by the user), it is possible to verify that the ciphertext message was authentically generated by the contactless card, even if no second authentication factor was entered, because if the contactless card is tapped multiple times, the server has multiple successive ciphertext messages to compare. In this way, it can be verified that multiple successive ciphertext messages were in fact generated by the card, and not just a static replay of a single ciphertext message.

[0126] This allows for added security in cases where the second authentication factor is not available. For example, if a user taps their random card onto a random person's device, the second authentication factor is not available. In such a situation, multiple taps on the card can be used to verify that the card is the one being used to generate the cryptogram.

[0127] In some embodiments, after recording the digital signature for which this occurred, the actual cryptographic message used to generate that signature may be stored, for example in a database. The stored cryptographic message can be re-verified and therefore can act as an audit mechanism. In a contactless card authentication mechanism, the current cryptographic message being authenticated is within the correct counter range. Thus, verification can prove that the message was once generated by a contactless card.

[0128] In some embodiments, the record of the cryptogram message can serve as a ledger to verify that a package was delivered, for example, if there is a dispute about whether or when a package was delivered and who signed for the package. For example, a customer may claim that they received a package on a particular day within a time frame specified in a return policy. However, by reference to the stored cryptogram message, the merchant who shipped the package can prove that the customer actually received the package the previous day and therefore, the return policy does not apply.

[0129] In some embodiments, the delivery address may be authenticated to serve as a delivery requirement, for example, a package may need to be delivered to an authenticated address (e.g., a digitally signed address, etc.).

[0130] In some embodiments, certain conditions may need to be met before the digital signature can be applied. For example, a product may have restrictions regarding expiration dates, guaranteed delivery dates, and / or the length of time it may be transported. For example, if a product subject to such restrictions (e.g., pharmaceuticals, laboratory samples, perishable goods, etc.) is not delivered within a certain time, the conditions may prevent the consumer from signing for the product.

[0131] In some embodiments, the scope of the signed attestation can be limited to a particular delivery transaction, the terms of operation, and the requirements of the delivery transaction. For example, a merchant can apply requirements that the package be delivered to a particular address, or that there are particular restrictions on the delivery of the package, and the identity of the person signing for the package can be verified against these requirements. For example, a customer seeking a time-sensitive package may contract with a shipping company for a particular delivery date and time, and the customer may not want to pick up the delivery of the package after the specified time. In such an example, the customer can prove that the contract was breached at the time of delivery.

[0132] Although the term merchant is used throughout this disclosure, it is understood that this disclosure is not limited to a particular merchant or type of merchant. Rather, this disclosure includes any type of merchant, distributor, or other entity involved in the activity of selling or providing products or services.

[0133] In some examples, the exemplary procedures according to the present disclosure described herein can be performed by a processing and / or computing arrangement (e.g., a computer hardware arrangement). For example, such a processing / computing arrangement can be, or can include, without limitation, all or part of a computer or processor, including, for example, one or more microprocessors, and capable of using instructions stored in a computer-accessible medium (e.g., RAM, ROM, hard drive, or other storage device). For example, the computer-accessible medium can be part of the memory of the delivery device 120 or 550, the user device 520, the server 130 or 530, and / or the contactless card 110 or 510, or other computer hardware arrangement.

[0134] In some examples, a computer-accessible medium (e.g., a storage device such as a hard disk, floppy disk, memory stick, CD-ROM, RAM, ROM, or a combination thereof, as described herein above) may be provided (e.g., in communication with a processing arrangement). The computer-accessible medium may itself contain executable instructions. Additionally or alternatively, a storage arrangement may be provided separate from the computer-accessible medium, which may provide instructions to the processing arrangement, for example, for configuring the processing arrangement to perform certain example procedures, processes, and methods as described herein.

[0135] Throughout the disclosure, the following terms take at least the meaning expressly associated therewith, unless the context clearly dictates. The term "or" is intended to mean an inclusive "or." Additionally, the terms "a," "an," and "the" are intended to mean one or more, unless otherwise specified or clearly evident from the context as being singular.

[0136] In this description, many specific details are described. However, it should be understood that implementations of the disclosed technology may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail so as not to obscure an understanding of this description. The terms "some examples," "other examples," "one example," "example," "various examples," "one embodiment," "embodiments," "several embodiments," "example embodiments," "various embodiments," "one implementation," "implementation," "example implementation," "various implementations," "several implementations," and the like, mean that implementations of the disclosed technology so described may include certain features, structures, or characteristics, but not all implementations require certain features, structures, or characteristics. Furthermore, repeated use of the phrases "in one example," "in one embodiment," or "in one implementation" may, but do not necessarily, refer to the same example, same embodiment, or same implementation.

[0137] As used herein, unless otherwise indicated, the use of the ordinal adjectives "first," "second," "third," etc. to describe a common object is intended merely to indicate that different instances of a similar object are being referred to, and is not intended to imply that the objects so described must be in a given order in time, space, precedence, or any other manner.

[0138] While particular implementations of the disclosed technology have been described in connection with what are currently considered to be the most practical and versatile implementations, it is to be understood that the disclosed technology is not limited to the disclosed implementations, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0139] This written description uses examples to disclose particular implementations of the disclosed technology, including the best mode, and to enable any person skilled in the art to practice particular implementations of the disclosed technology, including making and using any device or system, and performing the incorporated methods. The patentable scope of particular implementations of the disclosed technology is defined in the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that do not differ insubstantially from the literal language of the claims.

Claims

1. a contactless card including a processor and a memory, the memory storing a cryptogram including a unique identifier associated with a user account; the contactless card is configured to transmit the cryptogram to a server through one or more intermediary devices after entering a communication field; When the server receives the ciphertext, verifying the ciphertext; Decrypting the ciphertext; Extracting the unique identifier from the ciphertext; querying a database using the unique identifier to determine the identity of the user account; Generate a digital signature based on the identity of the user account. It is configured as follows: Contactless delivery system.

2. the one or more intermediary devices include a communication interface configured to generate the communication field; The non-contact delivery system of claim 1.

3. The server is configured to send a confirmation notification including the identity and the digital signature of the user account. The non-contact delivery system of claim 1.

4. The confirmation notification is sent to a user device that stores information regarding the delivery package; the server is configured to receive the information regarding the delivery package as an authentication element for verifying the identity of the user account. The non-contact delivery system of claim 3.

5. the server is configured to transmit the confirmation to a delivery device; the digital signature is displayed on a display of the delivery device; the digital signature is used to sign a package receipt document that is displayed on the display of the delivery device; The non-contact delivery system of claim 4.

6. the memory includes a counter value and a plurality of keys; the processor of the contactless card is configured to generate the cryptogram using the counter value, the plurality of keys, and the unique identifier. The non-contact delivery system of claim 1.

7. the processor of the contactless card is configured to update the counter value; The non-contact delivery system of claim 6.

8. the database includes one or more documents associated with the user account; The one or more documents include a copy of a driver's license; The non-contact delivery system of claim 1.

9. the server is configured to receive the one or more documents from the database to verify the identity of the user account. The non-contact delivery system of claim 8.

10. the contactless card includes a host card emulation device that emulates the contactless card; The non-contact delivery system of claim 1.

11. The server, Retrieving a profile picture for the user account from the database; Sending the profile photo to verify the identity of the user account. It is configured as follows: The non-contact delivery system of claim 1.

12. The server, Retrieving documents for the user account from the database; Sending the document to verify the identity of the user account. It is configured as follows: The non-contact delivery system of claim 1.

13. A server including a processor and a memory, The server, receiving a cryptogram including a unique identifier associated with a user account; verifying the ciphertext; Decrypting the ciphertext; Extracting the unique identifier from the ciphertext; querying a database using the unique identifier to determine the identity of the user account; Generate a digital signature based on the identity of the user account. It is configured as follows: Contactless delivery system.

14. The cryptogram is stored on a contactless card; the server is configured to receive the cryptogram through an intermediary device configured to generate a communication field for data communication with the contactless card; 14. The non-contact delivery system of claim 13.

15. The server is configured to receive a geo-signature of the intermediary device.

15. The non-contact delivery system of claim 14.

16. The server, Receive a geo-signature of the user's device; Comparing the geographic signature of the intermediary device with the geographic signature of the user device; generating the digital signature based on the comparison It is configured as follows:

16. The non-contact delivery system of claim 15.

17. The server configured to send a confirmation notification including the identity and the digital signature of the user account.

14. The non-contact delivery system of claim 13.

18. The server, receiving one or more authentication factors; Verifying the identity of the user account based on the one or more authentication factors. It is configured as follows: the one or more authentication factors include at least one selected from the group consisting of a password, a personal identification number (PIN), and a biometric characteristic; 14. The non-contact delivery system of claim 13.

19. The server, Receive a card tap notification, instructing the device to read a contactless card based on the card tap notification; Receive a notification that the tap is complete, Using the tap completion notification, generate the digital signature of the identity of the user account. It is configured as follows:

14. The non-contact delivery system of claim 13.

20. A method for non-contact delivery performed by a server, comprising: receiving a cryptogram including a unique identifier associated with a user account; verifying the ciphertext; Decrypting the ciphertext; Extracting the unique identifier from the ciphertext; querying a database using the unique identifier to determine the identity of the user account; generating a digital signature based on the identity of the user account; Contactless delivery method.

Images