SYSTEM AND METHOD FOR AUTHENTICATED PEER-TO-PEER DATA TRANSFER USING RESOURCE LOCATORS - Patent application

Abstract

The authenticated data transfer system may include generating a link after one or more processors of a transmitting device enter communication range, the link including a near field communication data exchange format uniform resource locator including identifier data and user data, sending the link to a first application including instructions for execution on the first device to initiate the data transfer, authenticating a user associated with the first device by actuating one or more actions based on the link, sending one or more requests for confirmation of quantities and recipient data associated with the data transfer, receiving one or more notifications based on the one or more requests for confirmation of quantities and recipient data associated with the data transfer, and executing one or more login credentials responsive to the one or more notifications to complete the data transfer.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Patent Application No. 17 / 162,783, filed January 29, 2021, the disclosure of which is incorporated herein by reference in its entirety. [Technical field]

[0002] TECHNICAL FIELD The present disclosure relates to peer-to-peer data transfer, and in particular to systems and methods for authenticated peer-to-peer data transfer using resource locators. [Background technology]

[0003] Peer-to-peer data transfers can be cumbersome if the two peer devices are not already connected through an existing network. This is because both peer devices must be registered with and configured to communicate on the same network to accomplish the transfer. Furthermore, setting up and scheduling data transfers can impair the user experience. Security risks also exist, including risks related to data integrity and vulnerability as it traverses between platforms, and misidentification of accounts due to the use of email addresses or other account identifiers. Such risks and shortcomings can reduce user demand for inter-application communication and inhibit the functionality and efficiency of inter-application communication.

[0004] These and other deficiencies exist. Therefore, what is needed is a system and method for peer-to-peer data transfer that provides enhanced security and an improved user experience. Summary of the Invention

[0005] An embodiment of the present disclosure provides an authenticated data transfer system including a contactless card with a processor and a memory. The processor may be configured to dynamically generate a Uniform Resource Locator (URL) after entering a communication range. The URL may include a first set of information including abstracted identifier information. The URL may include a second set of information including user information. The processor may be configured to send the URL to initiate the data transfer. The data transfer may be completed upon verification of the received response and verification of third information related to the data transfer.

[0006] An embodiment of the present disclosure provides a method for authenticating a data transfer. The method may include dynamically generating a link including a near field communication data exchange format uniform resource locator including identifier data and user data after one or more processors of a transmitting device are in communication range. The method may include sending a link to a first application including instructions for execution on the first device to initiate the data transfer. The method may include authenticating a user associated with the first device by actuating one or more actions based on the link. The method may include sending one or more requests for confirmation of a quantity and recipient data associated with the data transfer. The method may include receiving one or more notifications based on the one or more requests for confirmation of a quantity and recipient data associated with the data transfer. The method may include processing one or more login credentials responsive to the one or more notifications to complete the data transfer.

[0007] An embodiment of the present disclosure provides a computer-readable non-transitory medium including computer-executable instructions that, when executed by a processor, perform a processing procedure including the following steps: dynamically generating a link after a contactless card enters a communication range, the link including a first set of information and a second set of information, the first set of information including identifier information and the second set of information including user information; sending a link to a first application including instructions for executing on the first device to initiate a data transfer; identifying a user associated with the first device by actuating one or more actions based on the link, the one or more actions configured to request confirmation of a third set of information associated with the data transfer; and sending one or more responses based on authentication of the third set of information to complete the data transfer. [Brief description of the drawings]

[0008] The various embodiments of the present disclosure, together with further objects and advantages, may best be understood by reference to the following description taken in conjunction with the accompanying drawings, in which:

[0009] [Figure 1] FIG. 1 illustrates an authentication data transfer system according to an exemplary embodiment. [Figure 2A] FIG. 2A is an illustration of a contactless card according to an example embodiment. [Figure 2B] FIG. 2B is an illustration of a contact pad of a contactless card according to an exemplary embodiment. [Diagram 3] FIG. 3 illustrates a method for authorizing a data transfer according to an example embodiment. [Figure 4] FIG. 4 illustrates a method for initiating and authorizing a data transfer according to an example embodiment. [Diagram 5] FIG. 5 illustrates another method for initiating and authorizing a data transfer according to an example embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The following description of the embodiments provides non-limiting representative examples that refer to numbers to particularly explain the features and teachings of different aspects of the present invention. It should be recognized that the described embodiments can be implemented separately from the description of the embodiments or in combination with other embodiments. Those skilled in the art who review the description of the embodiments should be able to learn and understand the different described aspects of the present invention. The description of the embodiments should facilitate understanding of the present invention to the extent that other implementations that are not specifically covered but are within the knowledge of the person skilled in the art who reads the description of the embodiments are understood to be consistent with the application of the present invention.

[0011] As disclosed herein, a user may use their card for seamless identification and initiate data transfer. A resource locator, such as a Uniform Resource Locator (URL), Internet Resource Locator (IRL), Uniform Resource Identifier (URI), Uniform Resource Name (URN), or other resource locator, may include abstracted identity information. Abstracted identity information includes, but is not limited to, a cardholder's account or user identifier that is loaded into the chip when the card is personalized. Abstracted identity information may be generated on a per-transaction basis, such as a dynamically generated URL.

[0012] Without limitation, the identification information may be generated on the card by combining a unique identifier with one or more variables, such as a counter, one or more cryptographic algorithms, and / or any combination thereof. For example, the one or more cryptographic algorithms may include encryption techniques, such as public key encryption or private key encryption, which may also be known by the server for authentication. Without limitation, exemplary symmetric key algorithms include symmetric key encryption, such as Data Encryption Standard (DES), Triple DES, or Advanced Encryption Standard (AES). Without limitation, exemplary asymmetric key algorithms include asymmetric public key encryption, Digital Signature Algorithm, or Rivest-Shamir-Adleman (RSA).

[0013] In some examples, peer-to-peer data transfers may be initiated and authenticated via a website. In other examples, peer-to-peer data transfers may be initiated and authenticated via an application. The systems and methods disclosed herein minimize exposure of identifying information or other private information and provide greater security.

[0014] Exemplary embodiments of the present disclosure provide improvements to limitations in the user experience for setting up and coordinating various types of data transfers, reducing or eliminating security risks such as those associated with platform traversal, misidentification of accounts by email address, authentication of requested data transfers, and validity of device recognition. Thus, the systems and methods disclosed herein address these limitations and improve upon existing implementations by coordinating customized peer-to-peer data transfers that provide enhanced security benefits and an improved user experience.

[0015] 1 illustrates an authenticated data transfer system 100. The authenticated data transfer system 100 may include a sending device 105, a first application 110, a second application 115, a network 120, a server 125, and a database 130. Although FIG. 1 illustrates a single instance of the components of system 100, system 100 may include any number of components.

[0016] The system 100 may include a transmitting device 105. The transmitting device 105 may include a contactless card, a contact card, a network-enabled computer, or other devices described herein. As further described below in FIGS. 2A-2B, the transmitting device 105 may include one or more processors 102, and a memory 104. The memory 104 may include one or more applets 106 and one or more counters 108. The transmitting device 105 may be in data communication with one or more devices 112, 117. For example, the transmitting device may transmit data to the client device 112, 117 over the network 120. In some examples, the transmitting device 105 may be configured to transmit data to the client device 117 over the network 120 after coming into communication range of one or more of the client devices 112, 117. Without limitation, the transmitting device 105 may be configured to transmit data to the client device 112, 117 after one or more entries into a communication range of one or more of the client devices 112, 117. The one or more entries may be associated with a tap, a swipe, a wave, and / or any combination thereof.

[0017] The system 100 may include a first application 110. For example, the first application 110 may include instructions for execution on a first device 112. The first application 110 may communicate with any component of the system 100. For example, the first device 112 may execute one or more applications, such as the first application 110, that enable network and / or data communication with one or more components of the system 100, for example, to transmit and / or receive data. The first device 112 may include one or more processors 113 coupled to a memory 114. For example, the first device 112 may be a network-enabled computer. As referred to herein, a network-enabled computer includes a computing device or a communication device, including, for example, but not limited to, a server, a network appliance, a personal computer, a workstation, a telephone, a handheld PC, a personal digital assistant, a contactless card, a thin client, a fat client, an Internet browser, or other device. The first device 112 may also be a mobile device, which may include, for example, an Apple® iPhone®, iPod®, iPad®, or any 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 any other smartphone, tablet, or similar wearable mobile device.

[0018] The first device 112 may include processing circuitry and may include additional components including processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware necessary to perform the functions described herein. The first device 112 may further include a display and an input device. The display 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 may include any device for inputting information into the user's device that is available and supported by the user's device, such as a touch screen, keyboard, mouse, cursor control device, touch screen, microphone, digital camera, video recorder, camcorder, etc. These devices may be used to input information and interact with the software and other devices described herein. In some examples, the first device 112 may include at least one selected from the group of a mobile device, a wearable device, and a kiosk.

[0019] The system 100 may include a second application 115. The second application 115 may include instructions for execution on a second device 117. The second application 115 may communicate with any component of the system 100. For example, the second device 117 may execute one or more applications, such as the second application 115, that enable network and / or data communication with one or more components of the system 100 and transmit and / or receive data. The second device 117 may include one or more processors 116 coupled to a memory 118. For example, the second device 117 may be a network-enabled computer. As referred to herein, a network-enabled computer may include, but is not limited to, a computing device or a communication device, including, for example, a server, a network appliance, a personal computer, a workstation, a telephone, a handheld PC, a personal digital assistant, a contactless card, a thin client, a fat client, an Internet browser, or other device. The second device 117 may also be a mobile device, which may include, for example, an Apple® iPhone®, iPod®, iPad®, or any 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 any other smartphone, tablet, or similar wearable mobile device.

[0020] The second device 117 may include processing circuitry and may include additional components including processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware necessary to perform the functions described herein. The second device 117 may further include a display and an input device. The display 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 may include any device for inputting information into the user's device that is available and supported by the user's device, such as a touch screen, keyboard, mouse, cursor control device, touch screen, microphone, digital camera, video recorder, camcorder, etc. These devices may be used to input information and interact with the software and other devices described herein. In some examples, the second device 117 may include at least one selected from the group of a mobile device, a wearable device, and a kiosk.

[0021] The system 100 may include a network 120. In some examples, the network 120 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 to any one of the components of the system 100. For example, the client devices 112, 117 may be configured to connect to the server 125 via the network 120. In some examples, the network 120 may include one or more of an optical fiber 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 messaging service, an enhanced messaging service, a short message service, a time division multiplexing based system, a code division multiple access based 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.

[0022] Additionally, network 120 may include, but is not limited to, a telephone line, optical fiber, IEEE Ethernet 902.3, a wide area network, a wireless personal area network, a LAN, or a global network such as the Internet. Additionally, network 120 may support an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof. Network 120 may further include one network, or any number of the exemplary types of networks described above, operating as a standalone network or in cooperation with one another. Network 120 may utilize one or more protocols of one or more network elements to which they are communicatively coupled. Network 120 may translate from other protocols to one or more protocols of the network device, or from other protocols to one or more protocols of the network device. Although network 120 is depicted as a single network, it should be understood that, according to one or more examples, network 120 may include multiple interconnected networks, such as, for example, the Internet, a service provider's network, a cable television network, an enterprise network such as a credit card association network, and a home network.

[0023] The client devices 112, 117 can communicate with one or more servers 125 via one or more networks 120 and can each act as a respective front-end to back-end pair with the server 125. The client devices 112, 117 can send one or more requests to the server 125, for example from a mobile device application 110, 115 executing thereon. The one or more requests may relate to retrieving data from the server 125. The server 125 may receive one or more requests from the client devices 112, 117. Based on the one or more requests from the client application 110, 115, the server 125 may be configured to retrieve the requested data. The server 125 may be configured to send the received data to the client application 110, 115, where the received data is responsive to the one or more requests.

[0024] The system 100 may include one or more servers 125. In some examples, the server 125 may include one or more processors 127 coupled to a memory 129. The server 125 may be configured as a central system, server, or platform for controlling and calling various data at different times to perform multiple workflow operations. The server 125 may be configured to connect to one or more client devices 112, 117. The server 125 may be in data communication with the client applications 110, 115. For example, the server 125 may be in data communication with the client applications 110, 115 via one or more networks 120.

[0025] The system 100 may include one or more databases 130. The database 130 may include a relational database, a non-relational database, or other database implementations, and any combination thereof, including multiple relational and non-relational databases. In some examples, the database 130 may include a desktop database, a mobile database, or an in-memory database. Furthermore, the database 130 may be hosted internally by the device 112, 117, or the database 130 may be hosted externally to the device 112, 117, such as by the server 125, by a cloud-based platform, or in any storage device in data communication with the device 112, 117. In some examples, the database 130 may be in data communication with any number of elements of the system 100. For example, the server 125 may be configured to retrieve requested data from the database 130 transmitted by the application 110, 115. The server 125 may be configured to transmit the data received from the database 130 to the client application 110, 115 over the network 120, where the received data is responsive to one or more transmitted requests. In other examples, the client application 110 , 115 may be configured to send one or more requests for the requested data from the database 130 over the network 120 .

[0026] In some examples, the exemplary processing procedures according to the present disclosure described herein may be performed by a processing arrangement and / or computing device (e.g., computer hardware device). Such a processing / computing device may be, or may include, all or part of a computer / processor, which may include, for example, one or more microprocessors, but is not limited to such a computer / processor, and may use instructions stored on a computer-accessible medium (e.g., RAM, ROM, hard drive, other storage device). For example, the computer-accessible medium may be a portion of memory of the client device 112, 117 and / or the server 125 or other computer hardware device.

[0027] 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 collection thereof, as described hereinabove) may be provided (e.g., in communication with the processing device). The computer-accessible medium may include executable instructions thereon. Additionally or alternatively, a storage arrangement may be provided separate from the computer-accessible medium, which may provide instructions to the processing device, for example, to configure the processing device to perform certain exemplary processing procedures, processes, and methods as described hereinabove.

[0028] In some examples, the sending device 105 may be configured with a contact-based card. For example, the contact-based card may be configured to transmit a link to initiate data transfer after establishing a connection with the device. The link may be configured with, for example, a URL, an IRL, a URI, or a URN. Without limitation, the contact card may be configured to establish physical contact with a card reader (e.g., a chip reader or a magnetic stripe reader) of the client device 112. The card reader may be integral to the client device 112, internal to the client device 112, or external to the client device 112.

[0029] In other examples, the sending device 105 may comprise a contactless card. For example, the contactless card may be configured to send a link to the first application 110 to initiate data transfer after coming into communication range. The link may comprise, for example, a URL, an IRL, a URI, or a URN. In some examples, the contactless card may come into communication range of the client device 112 via one or more gestures selected from the group of a tap, a swipe, a wave, or any combination thereof.

[0030] In some examples, the user may be identified based on a Mobile Network Operator (MNO) lookup. In other examples, the user may be identified based on one or more cookies associated with a previous account login, e.g., an account associated with the sending device, another account associated with the user, and / or logins to another account. The link may comprise a Near Field Communication Data Exchange Format Uniform Resource Locator (NDEF URL) and may be configured to invoke one or more actions or applications. In one example, the link may be configured to invoke a website, which may include causing a browser or other browsing application executing on the client device 112 or another device to access and display the website and / or cause the website to perform one or more actions (e.g., display or submit information). In another example, the link may be configured to invoke an application executing on the client device 112 or another device.

[0031] The link may include a first set of information and a second set of information. For example, the first set of information may include identifier information. The first set of information may include an abstracted username generated by the processor after coming into communication range of the sending device 105. For example, the abstracted identification information may be generated for each transaction in the form of a dynamically generated URL. Without limitation, the identification information may be generated on the card by combining a unique identifier with one or more variables, such as a counter, one or more cryptographic algorithms, and / or any combination thereof. For example, the one or more cryptographic algorithms may include encryption techniques, such as public key encryption or private key encryption, which may also be known by a server, such as the server 125, for authentication purposes. Without limitation, exemplary symmetric key algorithms may include symmetric key encryption, such as DES, triple DES, or AES. Without limitation, exemplary asymmetric key algorithms may include asymmetric public key encryption, digital signature algorithms, or RSA. For example, the second set of information may include user information, such as cardholder information (e.g., account holder name, account number, expiration date, card verification value). The first application 110 may be configured to identify a user associated with the first device 112 by activating one or more actions based on the link. The one or more actions may be configured to request confirmation of a third set of information related to the data transfer. The third set of information may include at least one selected from the group of quantity, digital assets, and recipient information.

[0032] In some examples, the at least one action may include launching a website configured to identify a user associated with the first device 112. The server 125 may be configured to identify a user associated with the first device 112 by at least one selected from the group of device fingerprinting of the first device 112 and cookies stored on the first device 112. Without limitation, the device fingerprinting may be based on at least one selected from the group of device configuration of the first device 112, device memory, device screen size, device operating system version, installed applications, telephone carrier provider, third-party cookies for the website, phone number tracking through Mobile Network Operator (MNO) lookup, browser type, browser language, IP address, and / or any combination thereof. The website may be configured to display the second set of information and the third set of information on the first device 112. After successful identification of the user or owner of the first device 112, the website may be configured to load predefined information including the second set of information. In some examples, the predefined information may include user information such as cardholder information. In some examples, this information may be embedded in and passed via an NDEF URL when the sending device 105 comes into range. The website may be further configured to allow a quantity, including but not limited to a monetary amount, to be specified. The website may be further configured to submit the transfer by selection of a button. Additionally, the website may be further configured to adjust the recipient and / or sender of the data transfer. For example, the direction of the data transfer may be reversed. In some examples, by adjusting the direction of the transfer, such as from sender to recipient or from recipient to sender, a corresponding message, such as a push notification or email, may be generated to indicate confirmation of the desired reversed direction of the transfer.In some examples, the corresponding message may be displayed by the first application 110 and / or the second application 115.

[0033] The second application 115 may be configured to send one or more responses associated with the authentication and verification of the third information to complete the data transfer. In some examples, the second application 115 may be configured to receive a notification from the first application 110, the notification requiring one or more responses associated with the verification of the third set of information. The second application 115 may be configured to perform one or more authentication communications associated with the verification of the third set of information. For example, the data transfer may be completed upon verification of the received response and the verification of the third set of information associated with the data transfer. In some examples, the one or more authentication communications may include at least one selected from the group of a biometric authentication communication and a login communication.

[0034] In other examples, the at least one action may include requesting one or more login credentials by the first application 110. The first application 110 may be configured to deep link to a screen including the second set of information and the third set of information once the requested one or more login credentials are submitted and the one or more login credentials are authenticated. As an example, deep linking as described herein may refer to an NDEF URL being configured to link to a specific, generally searchable or indexed portion of web content on a website, rather than to a homepage of the website. The third set of information may include at least one selected from the group of quantity, digital asset, and recipient information. In some examples, the second application 115 may be configured to receive a notification, the notification requesting one or more responses associated with the verification of the third set of information. The second application 115 may be configured to perform one or more authentication communications associated with the verification of the third set of information. In some examples, the one or more authentication communications may include an authentication input. Exemplary authentication inputs may include, but are not limited to, input of login credentials, account information, security information, biometric information, and combinations thereof (e.g., username, password, account number, security code, one-time passcode, answers to security questions, fingerprint, facial scan, retina scan, voice recognition, logging into an application or website associated with the account or card issuer).

[0035] A device associated with the user of the sending device 105, such as a second application 115 on a second device 117 associated with the cardholder, may be configured to receive a notification, including but not limited to a push notification or email, that serves as a second confirmation of the amount, digital assets, and transfer destination. To confirm the data transfer, the cardholder can select a button to perform an action responsive to the requested authentication communication, such as providing an authentication input. Once the login is authenticated via the received authentication input, the transfer may be confirmed. In this manner, the peer-to-peer transfer is for an authenticated user, as it is forwarded to a known recipient after confirmation.

[0036] In some examples, the peer-to-peer transfer may include the issuance of a credit. The credit may be matched to one or more spending limits. For example, the one or more spending limits may include time limits, amount limits, geographic limits, merchant type, merchant limits, and / or any combination thereof. In some examples, the issuance of the credit may be associated with one or more rewards and / or points. For example, if the credit is used at a particular merchant, such as a restaurant, at a particular time, such as a weekend, rewards and / or points may be issued, which may be credited to a user reward or loyalty points program. For example, the rewards and / or points may be adjusted for each of the transferor and transferee and may be adjusted based on the redemption of the credit. For example, if the credit is used at a particular merchant, such as a restaurant, and / or at a particular time, such as a weekend, rewards and / or points may be issued, which may be credited to a user reward or loyalty points program. The transferor may earn rewards and / or points even if the recipient or transferee uses the credit.

[0037] In another example, the peer-to-peer transfer may include the transfer of one or more digital assets. Without limitation, the digital assets may include images or documents. Without limitation, the format type of the digital assets may include at least one selected from the group of static image files (JPEG, PNG, SVG, etc.), static document files (PDF, PSD, etc.), animation files (GIF, SWF, etc.), and web code (HTML, CSS, JavaScript, etc.). One or more digital assets may be identified for transfer. For example, the digital assets may be securely transferred by launching a website and uploading the digital assets identified for transfer. In another example, the digital assets may be securely transferred by opening an application or launching an email client in which the identified digital assets may be included as an attachment. In another example, the digital assets may be identified as part of a uniform resource locator (URL) that is sent to obtain the identified digital assets.

[0038] In other examples, the peer-to-peer transfer may include a funds transfer, such as a cash transfer. A funds transfer, such as an issuance of credit, may be subject to one or more usage restrictions and / or one or more merchants. For example, a funds transfer may be subject to restrictions based on time restrictions, amount restrictions, geographic restrictions, merchant type, merchant restrictions, and / or any combination thereof. In some examples, a funds transfer may include multiple portions. For example, a first portion of a funds transfer may be sent before a second portion of a funds transfer. Any portion of a funds transfer may be sent at a predetermined time, including but not limited to days, hours, weeks, months, and / or any combination thereof. In this manner, funds transfers may be sent in aggregate until the entire funds transfer is fulfilled.

[0039] In other examples, the peer-to-peer transfer may include the issuance of a virtual gift card. The virtual gift card, like the issuance of a credit, may be subject to one or more spending restrictions and / or one or more merchants. For example, the virtual gift card may be subject to time restrictions, amount restrictions, geographic restrictions, merchant type, merchant restrictions, and / or any combination thereof. In some examples, the peer-to-peer transfer may include multiple portions associated with different amounts of the virtual gift card. For example, a first portion of the peer-to-peer transfer may be sent before a second portion of the peer-to-peer transfer. Any portion of the transfer may be sent at a predetermined time, including but not limited to days, hours, weeks, months, and / or any combination thereof.

[0040] Figure 2A illustrates one or more transmitting devices 200. The transmitting devices 200 may refer to the same or similar components of the transmitting device or contactless card 105, as described above with respect to Figure 1. Although Figures 2A and 2B illustrate a single instance of the components of the transmitting device 200, any number of components may be utilized.

[0041] The transmitting device 200 may be configured to communicate with one or more components of the system 100. The transmitting device 200 may include a contact-based or contactless card, which may include a payment card, such as a credit card, a debit card, or a gift card, issued by a service provider 205 displayed on the front or back of the card 200. In some examples, the contactless card 200 is unrelated to a payment card and may include, but is not limited to, an ID card, a membership card, and a transportation card. In some examples, the payment card may include a dual interface contactless payment card. The contactless card 200 may be comprised of a substrate 210, which may include a single layer or one or more laminates composed of plastic, metal, and other materials. Exemplary substrates include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyester, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In some examples, contactless card 200 may have physical characteristics that conform to the ID-1 format of the ISO / IEC 7810 standard, and contactless cards may conform to the ISO / IEC 14443 standard. However, it is understood that contactless card 200 according to the present disclosure may have different characteristics, and the present disclosure does not require that the contactless card be implemented as a payment card.

[0042] The contactless card 200 may also include identification information 215 displayed on the front and / or back of the card, and a contact pad 220. The contact pad 220 may be configured to establish contact with another communication device, including, but not limited to, a user equipment, a smart phone, a laptop, a desktop, or a tablet computer. The contactless card 200 may also include processing circuitry, an antenna, and other components not shown in FIG. 2A. These components may be located behind the contact pad 220 or elsewhere on the substrate 210. The contactless card 200 may also include a magnetic strip or tape, which may be located on the back of the card (not shown in FIG. 2A).

[0043] As shown in Figure 2B, the contact pad 220 of Figure 2A may include processing circuitry 225 for storing and processing information, including a microprocessor 230 and memory 235. It is understood that the processing circuitry 225 may include additional components including processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware necessary to perform the functions described herein.

[0044] The memory 235 may be a read-only memory, a write-once read multiple memory, or a read / write memory, e.g., RAM, ROM, EEPROM, and the contactless card 200 may include one or more of these memories. A read-only memory may be factory programmable as read-only or may be one-time programmable, which means it is written once and can be read any number of times. A write-once read multiple memory may be programmed at some point after the memory chip leaves the factory. Once programmed, the memory cannot be rewritten, but it can be read any number of times. A read / write memory may be programmed and reprogrammed any number of times after it leaves the factory, and it can be read any number of times.

[0045] The memory 235 may be configured to store one or more applets 240, one or more counters 245, and a customer identifier 250. The one or more applets 240 may comprise one or more software applications configured to run on one or more contactless cards, such as a Java Card applet. However, it is understood that the applet 240 is not limited to a Java Card applet, but may instead be any software application operable on a contactless card or other device having limited memory. The one or more counters 245 may comprise a numeric counter sufficient to store an integer number. The customer identifier 250 may comprise a unique alphanumeric identifier assigned to a user of the contactless card 200, which identifier can distinguish a user of a contactless card from users of other contactless cards. In some examples, the customer identifier 250 may identify both the customer and an account assigned to the customer, and may further identify the contactless card associated with the customer's account.

[0046] Although the processor and memory elements of the foregoing exemplary embodiments are described with reference to contact pads, the disclosure is not limited thereto, and it will be appreciated that these elements may be implemented external to the pads 220, may be completely separate from the pads 220, or may be implemented as additional elements in addition to the processor 230 and memory 235 elements disposed within the contact pads 220.

[0047] In some embodiments, contactless card 200 may include one or more antennas 255. One or more antennas 255 may be disposed within contactless card 200 around processing circuitry 225 of contact pads 220. For example, one or more antennas 255 may be integral with processing circuitry 225, or one or more antennas 255 may be used in conjunction with an external booster coil. As another example, one or more antennas 255 may be external to contact pads 220 and processing circuitry 225.

[0048] In an embodiment, the coil of the contactless card 200 can act as the secondary of an air-core transformer. The terminal can communicate with the contactless card 200 by power disconnection or amplitude modulation. The contactless card 200 can infer data sent from the terminal using gaps in the power connection of the contactless card, which may be kept functional via one or more capacitors. The contactless card 200 may send back communication by switching the load or performing load modulation on the coil of the contactless card. Load modulation may be detected in the terminal coil by interference.

[0049]

[0023] Figure 3 illustrates a method 300 for authorizing a data transfer. Figure 3 may reference the same or similar components of the system 100 and transmitting device 200 of Figures 2A and 2B.

[0050] At block 310, the method 300 may include sending a link to a first application including instructions for execution on the first device after one or more processors of the sending device enter communication range, the link being configured to initiate data transfer, the link including a near field communication data exchange format uniform resource locator including identifier data and cardholder data. In some examples, sending the link may occur after dynamically generating the link. In some examples, the sending device may enter communication range of the client device via one or more gestures selected from the group of a tap, a swipe, a wave, or any combination thereof. In some examples, the user may be identified based on a mobile network operator (MNO) lookup. In other examples, the user may be identified based on one or more cookies associated with previous account logins, e.g., logins to an account associated with the sending device, another account associated with the user, and / or other accounts.

[0051] The link may include a Near Field Communication Data Interchange Format Uniform Resource Locator (NDEF URL). The link may include a first set of information and a second set of information. The first set of information includes identifier information. For example, the first set of information may include an abstracted username generated by the processor after coming into communication range of the transmitting device. For example, the abstracted identification information may be generated per transaction, such as a dynamically generated URL. Without limitation, the identification information may be generated on the card by combining a unique identifier with one or more variables, such as a counter, one or more cryptographic algorithms, and / or any combination thereof. For example, the one or more cryptographic algorithms may include encryption techniques such as public key encryption or private key encryption. Without limitation, exemplary symmetric key algorithms include symmetric key encryption such as DES, triple DES, or AES. Without limitation, exemplary asymmetric key algorithms include asymmetric public key encryption, digital signature algorithms, or RSA. For example, the second set of information may include user information, such as cardholder information. In some examples, the second set of information may include cardholder information (e.g., account holder name, account number, expiration date, card verification value).

[0052] At block 320, the method 300 may include authenticating a user associated with the first device by activating one or more actions based on the link. The one or more actions may be configured to request confirmation of a third set of information related to the data transfer. The third set of information may include at least one selected from the group of quantity, digital assets, and recipient information. In some examples, the at least one action may include launching a website configured to identify a user associated with the first device. In other examples, the at least one action may include requesting, by the first application, one or more login credentials.

[0053] At block 330, the method 300 may include sending one or more requests for confirmation of the quantity, digital assets, and recipient data associated with the data transfer. For example, the first application may be configured to receive input indicating confirmation of the amount, digital assets, and recipient data, such as the recipient, of the peer-to-peer transfer, such as a monetary amount, associated with the third set of information of block 320.

[0054] At block 340, the method 300 may include receiving one or more notifications that are based on one or more requests for confirmation of the quantity, digital assets, and recipient data associated with the data transfer. A device associated with the sending device user, such as a second application on a second device associated with the cardholder, may be configured to receive the notification that serves as a second confirmation of the quantity, digital assets, and transfer destination, but is not limited to a push notification or email.

[0055] At block 350, the method 300 may include performing one or more login credentials in response to the one or more notifications to complete the data transfer. For example, one or more authentication inputs may be received to complete the data transfer. The authentication inputs may be in response to the one or more notifications. To confirm the data transfer, the cardholder may respond to the one or more requests, such as where the requested authentication communication includes the authentication input, and select a button to perform an action based on the one or more notifications. Exemplary authentication inputs include, but are not limited to, input of login credentials, account information, security information, biometric information, and combinations thereof (such as username, password, account number, security code, one-time passcode, answers to security questions, fingerprint, face scan, retina scan, voice recognition, login to an application or website associated with the account or card issuer, etc.). Once the login is authenticated via the received authentication input, the transfer may be confirmed. Additionally, the direction of the data transfer may be reversed. In some examples, by adjusting the directionality of the transfer, such as from the transferor to the recipient or from the recipient to the transferor, a corresponding message, such as a push notification or email, may be generated to indicate confirmation of the desired reversed directionality of the transfer. In some examples, the corresponding message may be displayed by the first application and / or the second application. In this manner, the peer-to-peer transfer, once confirmed, is for an authenticated user since it is a transfer to a known recipient.

[0056] In some examples, the peer-to-peer transfer may include the issuance of credit. The credit may be matched to one or more spending limits. For example, the one or more spending limits may include a time limit, a monetary limit, a geographic limit, a merchant type, a merchant limit, and / or any combination thereof.

[0057] In some examples, a peer-to-peer transfer may be associated with one or more rewards and / or points. For example, the rewards and / or points may be adjusted for each of the transferor and transferee and may be adjusted based on the redemption of the credit. For example, if the credit is used at a particular merchant, such as a restaurant, and / or at a particular time, such as a weekend, rewards and / or points may be issued and thereby credited to a user rewards or loyalty points program. The transferor may earn rewards and / or points even if the recipient or transferee uses the credit. In some examples, a peer-to-peer transfer may include multiple parts. For example, a first part of a peer-to-peer transfer may be sent before a second part of the peer-to-peer transfer. For example, the first part may consist of one or more rewards and the second part may consist of one or more points. Any part of the transfer may be transferred at a predetermined time, including but not limited to days, hours, weeks, months, and / or any combination thereof.

[0058] In another example, the peer-to-peer transfer may include the transfer of one or more digital assets. Without limitation, the digital assets may include images or documents. Without limitation, the format type of the digital assets may include at least one selected from the group of static image files (JPEG, PNG, SVG, etc.), static document files (PDF, PSD, etc.), animation files (GIF, SWF, etc.), and web code (HTML, CSS, JavaScript, etc.). One or more digital assets may be identified for transfer. For example, the digital assets may be securely transferred by launching a website and uploading the digital assets identified for transfer. In another example, the digital assets may be securely transferred by opening an application or launching an email client that may include the identified digital assets as an attachment. In another example, the digital assets may be identified as part of a uniform resource locator (URL) that is transferred to obtain the identified digital assets.

[0059] In other examples, the peer-to-peer transfer may include a funds transfer, such as a cash transfer. A funds transfer, such as an issuance of credit, may be subject to one or more usage restrictions and / or one or more merchants. For example, a funds transfer may be subject to restrictions based on time restrictions, amount restrictions, geographic restrictions, merchant type, merchant restrictions, and / or any combination thereof. In some examples, a funds transfer may include multiple portions. For example, a first portion of a funds transfer may be sent before a second portion of a funds transfer. Any portion of a funds transfer may be sent at a predetermined time, including but not limited to days, hours, weeks, months, and / or any combination thereof. In this manner, funds transfers may be sent in aggregate until the entire funds transfer is fulfilled.

[0060] In other examples, the peer-to-peer transfer may include the issuance of a virtual gift card. The virtual gift card, like the issuance of a credit, may be subject to one or more spending restrictions and / or one or more merchants. For example, the virtual gift card may be subject to time restrictions, amount restrictions, geographic restrictions, merchant type, merchant restrictions, and / or any combination thereof. In some examples, the peer-to-peer transfer may include multiple portions associated with different amounts of the virtual gift card. For example, a first portion of the peer-to-peer transfer may be sent before a second portion of the peer-to-peer transfer. Any portion of the transfer may be sent at a predetermined time, including but not limited to days, hours, weeks, months, and / or any combination thereof.

[0061] Figure 4 illustrates a method of initiating and authenticating a data transfer according to an example embodiment. Figure 4 may refer to the same or similar components of system 100, transmitting device 200 of Figures 2A and 2B, and method 300 of Figure 3. As shown in Figure 4, a peer-to-peer transfer may be initiated by the card coming into range of a user equipment and loading a website.

[0062] At block 405, the method 400 may include the card entering a communication range of the user equipment, including but not limited to via one or more gestures selected from the group of tap, swipe, wave, or any combination thereof. The communication may include but is not limited to NFC. At block 410, the method 400 may include loading a website via an NDEF URL to identify a user of the user equipment after the card enters the communication range of the user equipment. In some examples, the card may be configured to send a link to one or more user equipment client applications to initiate data transfer after entering the communication range of block 405. In some examples, sending the link may occur after dynamically generating the link. In some examples, the client application may be associated with the sending device or the issuer of the card. In other examples, the client application may not be associated with the sending device or the issuer of the card. For example, the client application may be associated with a third party entity or an entity external to the sending device or the issuer of the card.

[0063] In some examples, the NDEF URL may consist of a domain name and an identifier. For example, the link may include abstracted identity information, including but not limited to the cardholder's account or user identifier, that is loaded into the chip when the card is personalized. For example, the URL is encoded into the NDEF file when the card is embossed. The abstracted identity information may be generated per transaction, such as a dynamically generated URL. Without limitation, the identity information may be generated on the card by combining a unique identifier with one or more variables, such as a counter, one or more cryptographic algorithms, and / or any combination thereof. For example, the one or more cryptographic algorithms may include encryption techniques, such as public key encryption or private key encryption, that may also be known by the server for authentication. Without limitation, exemplary symmetric key algorithms include symmetric key encryption, such as DES, triple DES, or AES. Without limitation, exemplary asymmetric key algorithms may include asymmetric public key encryption, digital signature algorithm, or RSA.

[0064] At block 415, the method 400 may include identifying the user via a device fingerprint, which may be based on at least one selected from the group of, but not limited to, device configuration, device memory, device screen size, device operating system version, installed applications, telephone carrier provider, third party cookies on a website, phone number tracking via MNO lookup, browser type, browser language, IP address, and / or any combination thereof of the device.

[0065] At block 420, the method may include prompting a user to log in to identify the user if the website is unable to identify the user via the cookie or device fingerprint. For example, if the website is unable to successfully identify the user via at least one selected from the group of operating system, browser type, browser language, and IP address, the user may receive a server-generated notification indicating that the notification failed and / or be prompted by the application to enter login information in response to the failed notification in order to successfully identify the user.

[0066] At block 425, the method 400 may include loading the predetermined information after identifying the user. In some examples, the predetermined information may be any information related to the cardholder that is already filled in on the website or otherwise provided by embedding directly in the NDEF URL. The website may be further configured to send the transfer by selecting a button. Additionally, the website may be further configured to adjust the recipient and / or the sender of the data transfer. For example, the direction of the data transfer may be reversed. In some examples, by adjusting the direction of the transfer, such as from the sender to the recipient or from the recipient to the sender, a corresponding message, such as a push notification or email, may be generated to indicate confirmation of the desired reversed direction of the transfer. In some examples, the corresponding message may be displayed by the first application and / or the second application.

[0067] At block 430, the method 400 may include inputting a quantity and recipient data for the peer-to-peer transfer prior to sending the transfer. At block 435, the method 400 may include receiving an email or push notification to confirm the peer-to-peer transfer. For example, the cardholder may be associated with a user device. An application on the user device may be configured to receive the notification. At block 440, in response to receiving the notification, the notification may be opened or displayed to prompt the user to log in or request a biometric input to confirm that the user has initiated the transfer. In some examples, the prompt may include a request for one or more authentication inputs. For example, exemplary authentication inputs include, but are not limited to, input of login credentials, account information, security information, biometric information, and combinations thereof (e.g., username, password, account number, security code, one-time passcode, answers to security questions, fingerprint, face scan, retina scan, voice recognition, logging into an application or website associated with the account or card issuer).

[0068] In block 445, after verification of one or more authentication inputs, a peer-to-peer transfer between the cardholder and the second user may be scheduled. In some examples, the peer-to-peer transfer may be scheduled for a predetermined time, such as a predetermined day, hour, week, month, and / or year. In other examples, the peer-to-peer transfer may be scheduled immediately. In this manner, a peer-to-peer transfer may be scheduled or queued for a transaction without a person having to identify or download and sign up for a different application. Additionally, the directionality of the data transfer may be reversed. In some examples, by adjusting the directionality of the transfer, such as from the transferor to the recipient or from the recipient to the transferor, a corresponding message, such as a push notification or email, may be generated to indicate confirmation of the desired reversed directionality of the transfer. In some examples, the corresponding message may be displayed by the first application and / or the second application. In this manner, the peer-to-peer transfer, after confirmation, is for the authenticated user since it is a transfer to a known recipient.

[0069] In some examples, the peer-to-peer transfer may include the issuance of a credit. The credit may be matched to one or more spending limits. For example, the one or more spending limits may include time limits, amount limits, geographic limits, merchant type, merchant limits, and / or any combination thereof. In some examples, the issuance of the credit may be associated with one or more rewards and / or points. For example, if the credit is used at a particular merchant, such as a restaurant, at a particular time, such as a weekend, rewards and / or points may be issued, which may be credited to a user reward or loyalty points program. For example, the rewards and / or points may be adjusted for each of the transferor and transferee and may be adjusted based on the redemption of the credit. For example, if the credit is used at a particular merchant, such as a restaurant, and / or at a particular time, such as a weekend, rewards and / or points may be issued, which may be credited to a user reward or loyalty points program. The transferor may earn rewards and / or points even if the recipient or transferee uses the credit.

[0070] In another example, the peer-to-peer transfer may include the transfer of one or more digital assets. Without limitation, the digital assets may include images or documents. Without limitation, the format type of the digital assets may include at least one selected from the group of static image files (JPEG, PNG, SVG, etc.), static document files (PDF, PSD, etc.), animation files (GIF, SWF, etc.), and web code (HTML, CSS, JavaScript, etc.). One or more digital assets may be identified for transfer. For example, the digital assets may be securely transferred by launching a website and uploading the digital assets identified for transfer. In another example, the digital assets may be securely transferred by opening an application or launching an email client that may include the identified digital assets as an attachment. In another example, the digital assets may be identified as part of a uniform resource locator (URL) that is transferred to locate the identified digital assets.

[0071] In other examples, the peer-to-peer transfer may include a funds transfer, such as a cash transfer. A funds transfer, such as an issuance of credit, may be subject to one or more usage restrictions and / or one or more merchants. For example, a funds transfer may be subject to restrictions based on time restrictions, amount restrictions, geographic restrictions, merchant type, merchant restrictions, and / or any combination thereof. In some examples, a funds transfer may include multiple portions. For example, a first portion of a funds transfer may be sent before a second portion of a funds transfer. Any portion of a funds transfer may be sent at a predetermined time, including but not limited to days, hours, weeks, months, and / or any combination thereof. In this manner, funds transfers may be sent in aggregate until the entirety of the funds transfer is fulfilled.

[0072] In other examples, the peer-to-peer transfer may include the issuance of a virtual gift card. The virtual gift card, like the issuance of a credit, may be subject to one or more spending restrictions and / or one or more merchants. For example, the virtual gift card may be subject to time restrictions, amount restrictions, geographic restrictions, merchant type, merchant restrictions, and / or any combination thereof. In some examples, the peer-to-peer transfer may include multiple portions associated with different amounts of the virtual gift card. For example, a first portion of the peer-to-peer transfer may be sent before a second portion of the peer-to-peer transfer. Any portion of the transfer may be sent at a predetermined time, including but not limited to days, hours, weeks, months, and / or any combination thereof.

[0073]

[0023] Figure 5 illustrates another method for initiating and authenticating a data transfer according to an exemplary embodiment. Figure 5 may refer to the same or similar components of system 100, transmitting device 200 of Figures 2A and 2B, method 300 of Figure 3, and method 400 of Figure 4. As shown in Figure 5, a peer-to-peer transfer may be initiated by the card coming into range of the user equipment and deep linking to an application.

[0074] At block 505, the method may include the card entering a communication range of the user equipment, including, but not limited to, via one or more gestures selected from the group of tap, swipe, wave, or any combination thereof. The communication may include, but is not limited to, near field communication (NFC). At block 510, the method may include launching an application on the user equipment via a near field communication data exchange format (NDEF URL) after the card enters a communication range of the user equipment. In some examples, the sending of the NDEF URL occurs after dynamically generating the NDEF URL. In some examples, the application may be associated with an issuer of the sending device. In other examples, the application may not be associated with an issuer of the sending device. For example, the application may be associated with a third party entity or an entity external to the issuer of the sending device. At block 515, the method may include deep linking by the application to a peer-to-peer transfer screen that includes the predetermined information. In some examples, the predetermined information may be any information already filled in or otherwise associated with the cardholder via being directly embedded in the NDEF URL. In some examples, the application may be configured to prompt the user to log in before deep linking. In other examples, the application is configured to prompt the user to log in after deep linking. In some examples, the login before deep linking may be the same or different as the login required after deep linking. Additionally, example authentication inputs may include, but are not limited to, input of login credentials, account information, security information, biometric information, and combinations thereof (e.g., username, password, account number, security code, one-time passcode, answers to security questions, fingerprint, face scan, retina scan, voice recognition, and login to an application or website associated with the account or card issuer).At block 520, the method may include entering quantity and recipient data for the peer-to-peer transfer before the transfer is sent. At block 525, the method may include receiving an email or push notification to confirm the peer-to-peer transfer. For example, the cardholder may be associated with a user device. The user device or an application thereof may be configured to receive the notification. At block 530, in response to receiving the notification, the notification may be opened or displayed to prompt for authentication input to confirm that the user has initiated the transfer. At block 535, after verification, the peer-to-peer transfer between the cardholder and the second user may be scheduled. In some examples, the peer-to-peer transfer may be scheduled for a predetermined time, such as a predetermined day, hour, week, month, and / or year. In other examples, the peer-to-peer transfer may be scheduled immediately. In this manner, peer-to-peer transfers may be scheduled or queued for a transaction without identifying an individual or downloading and signing up for a different application. Additionally, the direction of the data transfer may be reversed. In some examples, by adjusting the directionality of the transfer, such as from the transferor to the recipient or from the recipient to the transferor, a corresponding message, such as a push notification or email, may be generated to indicate confirmation of the desired reversed directionality of the transfer. In some examples, the corresponding message may be displayed by the first application and / or the second application. In this manner, the peer-to-peer transfer, once confirmed, is for an authenticated user since it is a transfer to a known recipient.

[0075] In some examples, the peer-to-peer transfer may include the issuance of a credit. The credit may be matched to one or more spending limits. For example, the one or more spending limits may include time limits, amount limits, geographic limits, merchant types, merchant limits, and / or any combination thereof. In some examples, the issuance of the credit may be associated with one or more rewards and / or points. For example, if the credit is used at a particular merchant, such as a restaurant, at a particular time, such as a weekend, rewards and / or points may be issued, which may be credited to a user reward or loyalty points program. For example, the rewards and / or points may be adjusted for each of the transferor and transferee and may be adjusted based on the redemption of the credit. For example, if the credit is used at a particular merchant, such as a restaurant, and / or at a particular time, such as a weekend, rewards and / or points may be issued, which may be credited to a user reward or loyalty points program. The transferor may earn rewards and / or points even if the recipient or transferee uses the credit.

[0076] In another example, the peer-to-peer transfer may include the transfer of one or more digital assets. Without limitation, the digital assets may include images or documents. Without limitation, the format type of the digital assets may include at least one selected from the group of static image files (JPEG, PNG, SVG, etc.), static document files (PDF, PSD, etc.), animation files (GIF, SWF, etc.), and web code (HTML, CSS, JavaScript, etc.). One or more digital assets may be identified for transfer. For example, the digital assets may be securely transferred by launching a website and uploading the digital assets identified for transfer. In another example, the digital assets may be securely transferred by opening an application or launching an email client that may include the identified digital assets as an attachment. In another example, the digital assets may be identified as part of a uniform resource locator (URL) that is transferred to locate the identified digital assets.

[0077] In other examples, the peer-to-peer transfer may include a funds transfer, such as a cash transfer. A funds transfer, such as an issuance of credit, may be subject to one or more usage restrictions and / or one or more merchants. For example, a funds transfer may be subject to restrictions based on time restrictions, amount restrictions, geographic restrictions, merchant type, merchant restrictions, and / or any combination thereof. In some examples, a funds transfer may include multiple portions. For example, a first portion of a funds transfer may be sent before a second portion of a funds transfer. Any portion of a funds transfer may be sent at a predetermined time, including but not limited to days, hours, weeks, months, and / or any combination thereof. In this manner, funds transfers may be sent in aggregate until the entire funds transfer is satisfied.

[0078] In other examples, the peer-to-peer transfer may include the issuance of a virtual gift card. The virtual gift card, like the issuance of a credit, may be subject to one or more spending restrictions and / or one or more merchants. For example, the virtual gift card may be subject to time restrictions, amount restrictions, geographic restrictions, merchant type, merchant restrictions, and / or any combination thereof. In some examples, the peer-to-peer transfer may include multiple portions associated with different amounts of the virtual gift card. For example, a first portion of the peer-to-peer transfer may be sent before a second portion of the peer-to-peer transfer. Any portion of the transfer may be sent at a predetermined time, including but not limited to days, hours, weeks, months, and / or any combination thereof.

[0079] References are made herein to types of resource locators, such as URL, NDEF URL, IRL, URI, and URN, although it should be understood that these references are exemplary and that the present disclosure includes, but is not limited to, the types of resource locators referenced.

[0080] It is further noted that the systems and methods described herein can be tangibly implemented in one of, but not limited to, a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a hard drive, a read-only memory (ROM), a random access memory (RAM), and other physical media capable of storing data. For example, data storage devices include random access memory (RAM) and read-only memory (ROM), which can be configured to access and store data and information as well as computer program instructions. For example, RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, flash drive, any type of tangible and non-transitory storage medium) in which an operating system, application programs including, for example, a web browser application, an email application and / or other applications, and files constituting data files are stored. Data storage in a network-enabled computer system may include electronic information, files, and documents stored in a variety of ways including, for example, flat files, indexed files, hierarchical databases, relational databases, databases created and maintained with software such as Oracle® Corporation, Microsoft® Excel files, Microsoft® Access files, solid-state storage devices which may include flash arrays, hybrid arrays, or server-side products, enterprise storage which may include online or cloud storage, or any other storage mechanism. Additionally, the diagram illustrates various components (e.g., servers, computers, processors, etc.) separately.The functions described as being performed by various components may be performed by other components, the various components may be combined or separated, and other variations are possible.

[0081] In the preceding specification, various embodiments have been described with reference to the accompanying drawings. It will be apparent, however, that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as defined in the claims which follow. The specification and drawings are therefore to be regarded in an illustrative rather than a restrictive sense.

Claims

1. 1. A secure peer-to-peer data transfer system, comprising: a contactless card including a processor and a memory and associated with a cardholder; the processor is configured to generate a link after the contactless card comes into communication range associated with a communication device of a recipient user different from the card owner; the link functions to initiate a secure peer-to-peer data transfer involving the receiving user and the cardholder; The link is: a first set of information including one or more abstracted identification information that uniquely identifies the contactless card and a particular peer-to-peer data transfer session; a second set of information including information associated with the card owner that is loaded onto the contactless card when the contactless card is personalized; one or more data fields for specifying one or more data transfer parameters; A secure peer-to-peer data transfer system.

2. The one or more data transfer parameters include a peer-to-peer data transfer directionality.

2. The secure peer-to-peer data transfer system of claim 1.

3. the link includes a Near Field Communications Data Exchange Format Uniform Resource Locator (NDEF URL); The processor is further configured to transmit the NDEF URL via near field communication.

2. The secure peer-to-peer data transfer system of claim 1.

4. The processor is further configured to transmit the link to the communication device to initiate a data transfer associated with a third set of information.

2. The secure peer-to-peer data transfer system of claim 1.

5. the third set of information includes at least one selected from the group of quantity, digital assets, and recipient information; The processor is further configured to initiate the data transfer in response to verifying the third set of information via an authentication response from the cardholder.

5. A secure peer-to-peer data transfer system according to claim 4.

6. the link is operable to initiate the data transfer session by launching a website on the communication device; The website functions to initiate the secure peer-to-peer data transfer.

2. The secure peer-to-peer data transfer system of claim 1.

7. A third set of information is entered into the website based on one or more inputs provided by the recipient user.

7. A secure peer-to-peer data transfer system according to claim 6.

8. The one or more actions based on the link are configured to identify a user.

7. A secure peer-to-peer data transfer system according to claim 6.

9. At least one of the one or more actions includes launching a website, the website configured to initiate a data transfer upon receiving one or more valid authentication inputs from the communication device associated with the recipient user and an authentication confirmation from a computing device associated with the cardholder.

9. A secure peer-to-peer data transfer system according to claim 8.

10. The recipient user associated with the communication device is identified by at least one selected from the group of a device fingerprint and a cookie.

2. The secure peer-to-peer data transfer system of claim 1.

11. 1. A method for implementing secure peer-to-peer data transfer, comprising: generating a link after a processor of the contactless card comes into communication range of a first device associated with the recipient, said link including abstracted identifier information and one or more account and identification information associated with the cardholder; sending the link to a first application running on the first device, the link operable to initiate the secure peer-to-peer data transfer according to one or more transfer parameters; A method comprising:

12. and authenticating a user associated with the first device by activating one or more actions based on the link. The method of claim 11.

13. The one or more actions include at least one selected from the group of: requesting confirmation of a third set of information associated with the secure peer-to-peer data transfer, launching a second website configured to identify the user associated with the first device, and requesting one or more login credentials. The method of claim 12.

14. the link is operable to initiate a data transfer by launching a website on the first device that displays one or more identification information associated with the cardholder; The website includes one or more data fields for specifying the one or more transfer parameters. The method of claim 11.

15. the abstracted identifier information is generated using a unique identifier and a cryptographic algorithm; The method of claim 11.

16. The abstracted identifier information is generated using a unique identifier, a counter, and a cryptographic algorithm. The method of claim 11.

17. The secure peer-to-peer data transfer is scheduled at a predetermined time. The method of claim 11.

18. A non-transitory computer-readable medium containing computer-executable instructions that, when executed by a processor, generating a link after a processor of the contactless card comes into communication range of a first device associated with the recipient, said link including abstracted identifier information and one or more account and identification information associated with the cardholder; sending the link to a first application running on the first device, the link functioning to initiate a secure peer-to-peer connection according to one or more transfer parameters; A non-transitory computer-readable medium for carrying out processing steps including:

19. the link is operable to initiate a data transfer by launching a website on the first device that displays one or more identification information associated with the cardholder; The website includes a data field for specifying the one or more transfer parameters.

20. The non-transitory computer-readable medium of claim 18.

20. The process further includes authenticating a user associated with the first device by activating one or more actions based on the link; The one or more actions are configured to include at least one selected from the group of: requesting confirmation of a third set of information associated with the secure peer-to-peer data, launching a second website configured to identify the user associated with the first device, and requesting one or more login credentials.

20. The non-transitory computer-readable medium of claim 18.

Images