Secure element and portable electronic device for financial transaction

Security element and portable electronic device for financial transaction

SECURE ELEMENT AND PORTABLE ELECTRONIC DEVICE FOR FINANCIAL TRANSACTION

<b>Cross reference to related applications</b>

This application is related to the November 2013 issue of the *** application by Yousuf H. Vaid, George R. Dicker, Ahmer A. Khan, Christopher Sharp, Glenn Steele, Chris Adams and David Haggerty entitled ``Electronic Receipts for NFC- Based Financial Transactions" U.S. Provisional Application No. 61/*** (Agent Case No. APL-P21734USP1), the content of which is incorporated herein by reference.

The described embodiments particularly relate to wireless communication, wireless electronic devices, and techniques for generating identifiers and receipts related to financial transactions conducted by electronic devices via wireless communication.

Many modern electronic devices include a network connection subsystem for wireless communication with other electronic devices. For example, these electronic devices may include a network connection subsystem, which has a cellular network interface (<i>UMTS</i>、<i>LTE</i>Etc.), wireless local area network interface (for example, such as described in the Institute of Electrical and Electronics Engineers (<i>IEEE</i>)802.11 standard or Bluetooth from Kirkland,Washington's Bluetooth Special Interests Group (Bluetooth Special Interests Group)^TMWireless network) and/or another type of wireless interface (such as near Field communication interface). Due to the popularity of these electronic devices and the convenience provided by the wireless communication capabilities, the use of electronic devices for financial transactions has attracted more and more attention.

One method of using cellular phones (and more generally, portable electronic devices) for financial transactions is based on near field communication. In detail, during financial transactions, users can bring their cellular phones close to point-of-sale terminals. When the user does this, financial information (such as information associated with the user's credit card) can be wirelessly communicated to the point-of-sale terminal.

Although a lot of efforts have been devoted to the development of technologies in the field of wireless financial transactions and related fields, other improvements may still be needed.

The described embodiment relates to a portable electronic device that includes: an antenna; an interface circuit that wirelessly communicates with another electronic device (for example, using near field communication); and a security element, which Conduct financial transactions with another electronic device. In addition, after the portable electronic device transmits financial account information to another electronic device during the financial transaction, the secure element determines a unique transaction identifier for the financial transaction based on the financial account information.

For example, the secure element may include a payment applet associated with the financial account information, wherein the payment applet is executed in an environment of the secure element to perform the financial transaction and determine the unique transaction identifier.

In some embodiments, the unique transaction identifier may be calculated independently by one or more other entities associated with the financial transaction based on the financial account information communicated by the portable electronic device. For example, the one or more other entities that can independently calculate the unique transaction identifier include: a counterparty in the financial transaction associated with another electronic device; using one specified by the financial account information A payment network through which a financial account processes payments for the financial transaction; and/or a financial institution associated with the financial account.

Note that the financial account information may include: information associated with a financial account identifier A token, an expiry date of the financial account, and a value corresponding to a number of financial transactions performed by the portable electronic device. In some embodiments, the secure element dynamically generates a dynamic credit card check code for the financial transaction, and the financial account information may include the dynamic credit card check code. In addition, the financial account information can be associated with a credit card.

In addition, the unique transaction identifier can correspond to a secure hash of the financial account information.

In addition, the portable electronic device may include a processor that attaches a time stamp to the unique transaction identifier, wherein the time stamp may correspond to the time when the financial account information is communicated to another electronic device.

In some embodiments, the portable electronic device performs the following operations: receiving a notification associated with the financial transaction from a payment network that processes payment for the financial transaction; Information related to financial transactions; and receiving information including the unique transaction identifier from the payment network. Note that the information may include: a status of the financial transaction, an identifier of the counterparty in the financial transaction, and/or a financial amount of the financial transaction.

Another embodiment provides a computer program product for use with a portable electronic device. The computer program product includes instructions for at least some of the operations performed by the portable electronic device.

Another embodiment provides a method for conducting financial transactions, which can be executed by a processor in a secure element in the portable electronic device. During the method, the portable electronic device can receive information indicating that the financial account information has been transmitted to another electronic device during the financial transaction. Then, the portable electronic device can determine a unique transaction identifier for the financial transaction based on the financial account information, wherein the unique transaction identifier can be determined by one or more other entities associated with the financial transaction based on the The financial account information transmitted by the electronic device is determined without the need for the electronic device to transmit the unique transaction identification symbol.

This [Summary] is provided only for the purpose of summarizing some example embodiments, so as to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it will be understood that the above-mentioned features are only examples and should not be interpreted in any way as narrowing the scope or spirit of the subject matter described herein. Other features, aspects and advantages of the subject matter described in this article will become obvious from the following [implementation], [simple description of drawings] and [applicable patent scope].

<p>110-1Electronic device</p><p>110-2Electronic device</p><p>110-3Electronic device</p><p>112Electronic device</p><p>114-1Radio</p><p>114-2Radio</p><p>116Wireless signal</p><p>118Business</p><p>120Internet</p><p>122Payment Network</p><p>124Financial Institution</p><p>126Internet</p><p>128Receipt Gateway</p><p>130Wireless signal</p><p>210Processing Subsystem</p><p>212Memory Subsystem</p><p>214Network connection subsystem</p><p>216Authentication subsystem</p><p>218Security Subsystem</p><p>220Safe Area Processor</p><p>222Interface circuit</p><p>224antenna</p><p>226Biometric Sensor</p><p>228User Interface Device</p><p>230Safety element</p><p>232Authentication Mini Program</p><p>234Verification completed flag</p><p>236Payment Mini Program</p><p>236-1Payment Mini Program</p><p>236-2Payment Mini Program</p><p>236-3Payment Mini Program</p><p>236-4Payment Mini Program</p><p>238Bus</p><p>240Display Subsystem</p><p>242Safety I/O Subsystem</p><p>244Operating System</p><p>246Program Module</p><p>248Passbook</p><p>400Methods used for financial transactions</p><p>510Third Party</p><p>600Methods used for financial transactions</p><p>710 Merchant Acquiring Bank</p>

FIG. 1 is a block diagram illustrating an electronic device for wireless communication during a financial transaction according to an embodiment of the present invention.

FIG. 2 is a block diagram illustrating one of the electronic devices of FIG. 1 according to an embodiment of the present invention.

FIG. 3 is a block diagram illustrating the security element in the electronic device in FIG. 2 according to an embodiment of the present invention.

4 is a flowchart illustrating a method for performing financial transactions using one of the electronic devices in FIG. 1 according to an embodiment of the present invention.

FIG. 5 is a diagram illustrating communication between the electronic devices of FIG. 1 according to an embodiment of the present invention.

FIG. 6 is a flowchart illustrating a method for performing financial transactions using one of the electronic devices in FIG. 1 according to an embodiment of the present invention.

FIG. 7 is a diagram illustrating communication between the electronic devices of FIG. 1 according to an embodiment of the present invention.

FIG. 8 is a diagram illustrating the provision of notification to one of the electronic devices in FIG. 1 according to an embodiment of the present invention.

FIG. 9 is a diagram illustrating the provision of notification to multiple electronic devices according to an embodiment of the present invention.

FIG. 10 is a diagram illustrating the provision of notification to multiple electronic devices according to an embodiment of the present invention.

FIG. 11 is a diagram illustrating the provision of notification to multiple electronic devices according to an embodiment of the present invention.

Table 1 provides track 1 and track 2 financial account information that can be used to determine a unique transaction identifier according to an embodiment of the present invention.

Table 2 provides first-level information that can be communicated to one of the electronic devices in FIG. 1 according to an embodiment of the present invention.

Table 3 provides second-level information that can be communicated to one of the electronic devices in FIG. 1 according to an embodiment of the present invention.

Note that similar reference numbers refer to corresponding parts throughout the drawings. In addition, multiple examples of the same part are marked with a common prefix separated from the example number by a dash.

In order to facilitate financial transactions via wireless communication between an electronic device (such as a smart phone) and another electronic device (such as a point-of-sale terminal), the electronic device may determine based on the financial account information communicated to the other electronic device The unique transaction identifier used for financial transactions. The financial account information can specify the financial account used to make payments for financial transactions. In addition, it may be able to be carried by one or more other entities associated with a financial transaction (such as a counterparty in a financial transaction associated with another electronic device, or a payment network that processes payment for a financial transaction). The unique transaction identifier is calculated independently based on the financial account information conveyed by the electronic device. The electronic device can associate the receipt information subsequently received from a third party (such as a payment network) with the financial transaction by comparing the determined unique transaction identifier with the calculated unique transaction identifier.

For example, according to a communication protocol such as the Institute of Electrical and Electronics Engineers (<i>IEEE</i>) 802.11 standard, Bluetooth^TM(From Kirkland, Washington's Bluetooth Special Interest Group) and/or such as near field communication standards or specifications (from Wakefield, Another type of wireless interface of the NFC Forum of Massachusetts transmits packets transmitted and received by the radio in the electronic device and another electronic device to conduct financial transactions between the electronic device and another electronic device. In the following discussion, near field communication is used as an illustrative example.

The communication between the electronic device and another electronic device is shown in FIG. 1, which shows a block diagram illustrating the electronic devices 110-1 and 112 for wireless communication. In detail, these electronic devices can communicate wirelessly during financial transactions. For example, a financial transaction may be initiated when the user positions the electronic device 110-1 (such as a cellular phone) close to the electronic device 112 (such as a point-of-sale terminal). Note that the approach may involve physical contact between the electronic devices 110-1 and 112 (such as touching or pressing the electronic device 110-1 on the electronic device 112), or the approach may be contactless (for example, the electronic device 110-1 may be within the radiation field pattern of the antenna in the electronic device 112, such as within a few inches to one foot). This wireless communication may use a radio frequency identification communication protocol (such as near field communication). Therefore, wireless communication may or may not involve establishing a connection between the electronic devices 110-1 and 112, and therefore may or may not involve communication via a wireless network, such as a cellular telephone network.

In response to detecting that the electronic device 110-1 is approaching the electronic device 112, the electronic devices 110-1 and 112 can perform an interaction. During the interaction, the secure element in the electronic device 110-1 (which is further described below with reference to FIG. 2) ) The financial account information can be provided to the electronic device 112 via wireless communication. For example, the financial account information may correspond to the credit card account that the user of the electronic device 110-1 is using to provide payment for items or services purchased during the financial transaction (and more generally, the one associated with the financial account). Financial instruments, such as credit or debit cards).

The financial account information can correspond to or be equivalent to the magnetic stripe data on the credit card. As shown in Table 1, in some embodiments, the financial account information includes so-called "track 1" data and/or "track 2" data, such as the token associated with the financial account identifier and the cardholder name column Bit, the expiry date of the financial account specified by the financial account identifier, corresponding to the Set 110-1 the value of the number of financial transactions, the dynamic credit card check code used for financial transactions (<i>DCVV</i>) And/or additional information.

Since the wireless communication between the electronic devices 110-1 and 112 can (in some cases) communicate "in the clear" (that is, it may not be encrypted), the financial account information can (in some cases) ) Exclude users explicit identifiers to protect their privacy, and dynamically or indirectly specify financial accounts to prevent subsequent fraud or abuse of financial account information (for example, if a malicious party intercepts financial account information during wireless communication). For example, if the financial account is a credit card account, the token can be the device master account (<i>DPAN</i>) Instead of the main financial account (<i>FPAN</i>) Or credit card number, where<i>DPAN</i>Can be thought of as corresponding to/mapping to "real"<i>FPAN</i>"Virtual" credit card number. Similarly, the cardholder name field can include information about the supplier or manufacturer of the designated electronic device 110-1 (for example, Cupertino, Apple Inc., California) and the name used for the user or credit card holder Alternative symbols, such as "APL/Valued Customers". (However, outside the United States, the cardholders name may not be included in the financial account information). In addition, the financial account information may include a truncated counter value (such as the least significant three bits, four bits, or five bits of the two-byte counter value) combined with the dynamic credit card check code. Note that the secure element in the electronic device 110-1 can dynamically generate a dynamic credit card check code for each financial transaction using a cryptographic technique. The cryptographic technique uses<i>DPAN</i>, A counter value, one or more cryptographic keys, and a random number provided by the electronic device 112 during wireless communication. Therefore, a different dynamic credit card check code can be generated for each financial transaction.

<tables><img he="320" wi="1735" file="twi605397b_d0001.tif" img-content="drawing" img-format="tif" orientation="portrait" inline="no" /></tables>

Related to the performance of financial transactions and/or as part of the performance of financial transactions, the secure element in the electronic device 110-1 can determine the unique transaction identifier for the financial transaction based on the financial account information. As further described below with reference to Figures 4 and 6, this unique transaction identification The token can be used by the electronic device 110-1 to be associated with financial transaction receipt information (such as the status of the financial transaction and/or digital receipt), which uses a wireless connection different from that between the electronic devices 110-1 and 112. The communication channel of the communication (such as a connection in a wireless network (for example, a cellular telephone network or a Wi-Fi network)) is received from a third party (such as a computer system operated by a third party). For example, the third party may be the supplier of the electronic device 110-1 and/or the payment network 122 that uses the financial account specified by the financial account information to process the payment for the financial transaction.

In detail, one or more other entities associated with the financial transaction may be able to independently calculate the unique transaction identifier based on the financial account information communicated by the electronic device 110-1. For example, the one or more other entities may include: counterparties in financial transactions associated with electronic device 112 (such as merchant 118); payment network 122; and/or financial accounts associated with financial accounts Institution 124 (such as a bank). Therefore, the unique transaction identifier can be calculated by a third party without the electronic device 110-1 transmitting the determined unique transaction identifier.

In addition, the receipt information may include the calculated unique transaction identifier, and the electronic device 110-1 may associate the receipt information with the financial transaction by comparing the determined unique transaction identifier with the calculated unique transaction identifier. In this way, without requiring the user to touch the electronic device 110-1 one or more times or bring the electronic device 110-1 close to the electronic device 112, the user can receive information indicating that the financial transaction has been completed and/ Or electronic or digital receipts, so as to significantly improve the user experience and promote the use of the electronic device 110-1 when conducting financial transactions.

Considering this discussion, after receiving the financial account information, the electronic device 112 (or the merchant 118) can use the financial account information to calculate the unique transaction identifier. Then, the merchant 118 can communicate financial account information and additional information associated with the financial transaction (such as the identifier of the counterparty and/or the financial amount of the financial transaction) via the network 120 (such as a wired or wireless network) to Payment network 122 and/or financial institution 124 (such as being used for financial The issuing institution of the credit card or financial instrument used for the payment of the transaction). Note that although entities such as "merchant 118", "payment network 122", and "financial institution 124" are mentioned, this is for ease of description. Merchant 118, payment network 112, etc. mean hardware (server computers and related network connection devices) that perform actions on behalf of these entities under the control of these entities and/or in other ways.

After receiving the financial account information and additional information, the payment network 122 and/or the financial institution 124 can complete the financial transaction. For example, after successful inspection of the financial account and the counterparty, the financial amount can be debited from the financial account and the counterparty can be notified that the payment has been approved. In addition, the payment network 122 and/or the financial institution 124 may calculate a unique transaction identifier based on the financial account information. Alternatively, the merchant 118 may provide the calculated unique transaction identifier to the payment network 122 and/or the financial institution 124.

If the user of the electronic device 110-1 has previously registered with the payment network 122 (which is further described below with reference to FIGS. 2 and 4), the payment network 122 may be connected via a network 126 (such as a cellular telephone network) Or Wi-Fi network) provides the notification to the electronic device 110-1. This notification may indicate that there has been a change associated with the financial account. In response, the electronic device 110-1 may request information (such as receipt information) associated with the financial transaction from the payment network 122. Next, the payment network 122 may provide the requested information, which includes a calculated unique transaction identifier that is subsequently used to associate the information with the financial transaction. Note that the information may include so-called "first-level" information, such as the status of the financial transaction (for example, the financial transaction has been completed), the identifier of the counterparty in the financial transaction, and/or the financial amount of the financial transaction. Alternatively or in addition, the information may include second-level information (e.g., digital receipts), such as: itemized lists of one or more items purchased, links to information associated with products (e.g.,<i>URL</i>), advertisements, discounts for future purchases of at least one item (such as coupons), discounts for future purchases from counterparties in financial transactions, account processing information (which can be used to charge expenses, such as expense reports), sales Tax and/or income tax information (which can be used to determine income tax returns). Table 2 and Table 3 provide the first level of information and the second level Description of the information in the level information (some of which are optional).

<tables><img he="1174" wi="1914" file="twi605397b_d0002.tif" img-content="drawing" img-format="tif" orientation="portrait" inline="no" /></tables>

<tables><img he="1500" wi="1914" file="twi605397b_d0003.tif" img-content="drawing" img-format="tif" orientation="portrait" inline="no" /></tables>

<tables><img he="769" wi="1823" file="twi605397b_d0004.tif" img-content="drawing" img-format="tif" orientation="portrait" inline="no" /></tables>

In some embodiments, the second-level information is provided to the electronic device 110-1 through a merchant payment gateway (such as a receipt gateway 128 associated with a supplier). In detail, the merchant 118 can transfer the calculated unique transaction identifier,<i>DPAN</i>The security hash (such as SHA-256), the first-level information and/or the second-level information are provided to the receipt gateway 128. Then, if the user has previously registered the electronic device 110-1 with the receipt gateway 128 (for example, using the registration process via the network 126 and/or some other network), the receipt gateway 128 can be used via the network 126 provides the notification to the electronic device 110-1. (In detail, the receipt gateway 128 can perform the following operations:<i>DPAN</i>Security hash decision<i>DPAN</i>; Use a lookup table (it can already be in<i>DPAN</i>(Set when deployed to an electronic device)<i>DPAN</i>Map to the secure element identifier in the electronic device 110-1; use the same or another look-up table to map the secure element identifier to the user identifier (such as the identifier of the user account of the supplier of the electronic device); And the push token can be obtained based on the user identifier (such as the address associated with the electronic device, for example,<i>IP</i>Address) so that the receipt gateway 128 can provide the notification to the electronic device 110-1. ) In response, the electronic device 110-1 may request information (such as receipt information) associated with the financial transaction from the receipt gateway 128. Next, the receipt gateway 128 may provide the requested information, which includes a calculated unique transaction identifier for subsequent use in associating the information with the financial transaction.

The wireless communication between the electronic devices 110-1 and 112 may involve the exchange of packets including financial account information. These packets can be included in a frame in one or more wireless channels.

As further described below with reference to FIG. 2, the electronic devices 110-1 and 112 may include subsystems, such as a network connection subsystem, a memory subsystem, a processing subsystem, and a security subsystem. In addition, the electronic devices 110-1 and 112 may include the radio 114 in the network connection subsystem. More generally, the electronic devices 110-1 and 112 may include any electronic devices with network connection subsystems (or may be included in such electronic devices), and the network connection subsystems enable the electronic devices 110-1 and 112 wirelessly communicates with another electronic device. This communication may include transmitting a frame on a wireless channel to enable the electronic device to make an initial contact, and then exchange subsequent data/management frames (such as a connection request to establish a connection), and configure security options (for example,<i>IPSEC</i>), transmit and receive packets or frames, etc.

As can be seen in FIG. 1, a wireless signal 116 (represented by a sawtooth line) is transmitted from the radio 114-1 in the electronic device 110-1. These wireless signals 116 are received by the radio 114-2 in the electronic device 112. (Note that communication via the network 126 may involve the wireless signal 130. However, these wireless signals may involve a different communication protocol than the wireless signal 116.)

In the described embodiment, processing a packet or frame in any one of the electronic devices 110-1 and 112 includes the following operations: receiving a wireless signal 116 with a packet or frame; decoding from the received wireless signal 116 / Extract the packet or frame to obtain the packet or frame; and process the packet or frame to determine the information contained in the packet or frame (such as financial account information).

Although the environment shown in FIG. 1 is described as an example, in alternative embodiments, there may be different numbers or types of electronic devices. For example, some embodiments include more or fewer electronic devices. As another example, in another embodiment, different electronic devices are transmitting and/or receiving packets or frames.

An embodiment of the electronic device will now be described. FIG. 2 provides a block diagram illustrating the electronic device 110-1. This electronic device includes a processing subsystem 210, a memory subsystem 212, a network connection subsystem 214, an authentication subsystem 216, and a security subsystem 218. The processing subsystem 210 includes one or more devices configured to perform computing operations. For example, the processing subsystem 210 may include Including one or more microprocessors, special application integrated circuits (<i>ASIC</i>), microcontroller, programmable logic device and/or one or more digital signal processors (<i>DSP</i>)。

In addition, the processing subsystem 210 may include a secure area (enclave) processor 220 (which is a system-on-a-chip in one or more processors in the processor subsystem 210). Other components perform security services and securely communicate with other subsystems in the electronic device 110-1. The secure zone processor 220 may include one or more processors, secure boot<i>ROM</i>, One or more security peripherals and/or other components. The security peripheral device may be hardware-configured to assist the security services performed by the security zone processor 220. For example, security peripheral devices may include: authentication hardware that implements various authentication technologies, encryption hardware that is configured to perform encryption, and a security interface controller that is configured to communicate with other components via a secure interface. And/or other components. In some embodiments, instructions that can be executed by the secure zone processor 220 are stored in the trust zone assigned to the secure zone processor 220 in the memory subsystem 212, and the secure zone processor 220 fetches the instructions from the trusted zone for execution . The secure area processor 220 can be isolated from the rest of the processing subsystem 210 (except for the strictly controlled interface), thereby forming a secure area for the secure area processor 220 and its components. Since the interface to the secure area processor 220 is strictly controlled, it can prevent direct access to the secure area processor 220 (such as the processor or secure boot<i>ROM</i>) Within the components. In some embodiments, the secure zone processor 220 encrypts and/or decrypts authentication information communicated with the authentication subsystem 216, and encrypts and/or decrypts information (such as tokens) communicated with the security subsystem 218. In addition, the secure zone processor 220 can compare the authentication information with the stored authentication items, and if a match is obtained, it can provide the encrypted token with the authentication completion indicator to the secure element 230.

The memory subsystem 212 includes one or more devices for storing data and/or instructions for the processing subsystem 210, the network connection subsystem 214, the authentication subsystem 216, and/or the security subsystem 218. For example, the memory subsystem 212 may include dynamic random access memory (<i>DRAM</i>), static random access memory (<i>SRAM</i>) And/or other types of memory. exist In some embodiments, the instructions for the processing subsystem 210 in the memory subsystem 212 include: one or more program modules or instruction sets (such as the program module 246, for example, a digital wallet) that can be executed by the processing subsystem 210 , Passbook and/or mobile payment application). Note that one or more computer programs can constitute a computer program mechanism. In addition, the following languages can be used to implement the instructions in the various modules in the memory subsystem 212: high-level procedural language, object-oriented programming language, and/or assembly language or machine language. In addition, the programming language can be compiled or interpreted (eg, configurable or configurable (which can be used interchangeably in this discussion)) for execution by the processing subsystem 210.

In addition, the memory subsystem 212 may include mechanisms for controlling access to the memory. In some embodiments, the memory subsystem 212 includes a memory hierarchy that includes one or more cache memories coupled to the memory in the electronic device 110-1. In some of these embodiments, one or more of the cache memory is located in the processing subsystem 210.

In some embodiments, the memory subsystem 212 is coupled to one or more large-capacity large-scale storage devices (not shown). For example, the memory subsystem 212 may be coupled to a magnetic disk drive or optical disk drive, a solid-state disk drive, or another type of mass storage device. In these embodiments, the memory subsystem 212 can be used by the electronic device 110-1 as a quick-access storage for frequently used data, but the mass storage device is used to store less frequently used data.

The network connection subsystem 214 includes one or more devices (that is, to perform network operations) configured to couple to and communicate over wired and/or wireless networks, including interfaces Circuit 222 (such as a near field communication circuit) and antenna 224. For example, the network connection subsystem 214 may include Bluetooth^TMNetwork connection system, cellular network connection system (for example, such as<i>UMTS</i>、<i>LTE</i>5G/4G network), universal serial bus (<i>USB</i>) Network connection system, based on<i>IEEE</i> The standard network connection system described in 802.11 (for example, a Wi-Fi network connection system), an Ethernet connection system and/or another communication system (such as a near field communication system).

The network connection subsystem 214 includes a processor, controller, radio/antenna, socket/plug, and/or for coupling to each supported network connection or communication system, communicating on the system, and processing for the system The data and events of other devices. Note that the mechanisms used to couple to the network for each network system, communicate on that network, and process data and events on that network are sometimes collectively referred to as the "network interface" for the network system . In addition, in some embodiments, the "network" between electronic devices does not yet exist. Therefore, the electronic device 110-1 can use the mechanism in the network connection subsystem 214 to perform simple wireless communication between the electronic devices 110-1 and 112 (FIG. 1), for example, transmitting the advertisement frame and/or as previously described. Or near field communication.

The authentication subsystem 216 may include a device for receiving authentication information from a user of the electronic device 110-1 and for safely communicating the authentication information to the processing subsystem 210 (such as by encrypting the authentication information) Or multiple processors, controllers and devices. For example, the authentication information may include: a biometric identifier obtained by a biometric sensor 226 (such as a fingerprint sensor, a retina sensor, a palm sensor, a signature recognition sensor, etc.); The personal identification code (<i>PIN</i>); and a password received by the user interface device 228 for unlocking at least some of the functionality of the electronic device 110-1.

In addition, the secure subsystem 218 may include a secure element 230, which includes one or more processors and memory. Note that the secure element 230 may be a tamper-proof component used in the electronic device 110-1 to provide security, confidentiality, and multiple application environments required to support various business modes. The security element 230 can exist in one or more of a variety of external dimensions, such as: general integrated circuit card (<i>UICC</i>), embedded secure components (on the circuit board in the electronic device 110-1), smart secure digital (<i>SD</i>) Card, smart micro<i>SD</i>Card etc.

In addition, the secure element 230 may be included in the environment of the secure element 230 (such as One or more small programs or applications executed in the operating system of the full component 230 and/or in the Java runtime environment running on the secure component 230. For example, one or more applets may include an authentication applet 232, which performs the following operations: perform contactless registration services; encrypt/decrypt packets or tokens communicated with the secure zone processor 220; set security One or more software flags in the operating system of the component 230 (such as the authentication completion flag 234); and/or send information to one or more payment applets 236 via a shareable interface object. (Although shareable interface objects are used as illustrative examples in the discussion of the present invention, in other embodiments, different mechanisms may be used, such as global services, remote method calls (<i>RMI</i>)Wait. ) In addition, the one or more applets may include one or more payment applets 236, which are based on one or more software flags and/or when they are activated by the program module 246 When the electronic device 110-1 approaches the electronic device 112 (FIG. 1), a financial transaction is performed with the electronic device 112 (FIG. 1).

The authentication applet 232 may be executed in the main security domain or the card issuer security domain in the secure component 230, and the payment applet 236 may be executed in the supplementary security domain. Different encryption/decryption keys specific to the security domain can be used to encrypt communications between these security domains. In electronic device 110-1 and/or during communication between electronic devices 110-1 and 112 (FIG. 1), encryption/decryption may involve symmetric and/or asymmetric encryption. In addition, the communicated information may also include digital signatures specific to the electronic device 110-1 and/or components in the electronic device 110-1.

The data stored in the secure element 230 is further illustrated in FIG. 3. In detail, for each of the payment applet 236, the secure element 230 can store the following: whether the given payment applet is active (in response to the activation command); and whether the authentication completion flag 234 is given by Set payment applet support/apply to given payment applet. In some embodiments, there are one or more payment applets (such as payment applet 236-4) that have not applied the authentication completion flag 234. In some embodiments, the secure element 230 stores, for at least one of the payment applets 236, information associated with the payment applet<i>PIN</i>(Such as debit card number). For example In other words, as shown in Figure 3, payment applets 236-1 and 236-2 can store related<i>PIN</i>. In addition, one or more of the payment applets can store the associated financial account information.

During the operation of the electronic device 110-1, the user can use the passbook 248 and/or the secure element 230, the interface circuit 222 and the antenna 224 to enable the electronic device 110-1 to register with one or more third parties to receive financial accounts And/or notifications associated with financial transactions. For example, the passbook 248 and/or the secure element 230 may provide the authentication token to one or more third parties. As further described below with reference to FIG. 8, the registration may include the identifier of the user of the electronic device 110-1 (such as a security hash of the user identifier) so that the notification is only used for those who use the electronic device 110-1. Financial transactions. In an exemplary embodiment, the primary cardholder of the credit card allows relatives (such as users) to also use the credit card for financial transactions. In this case, the financial account information of the designated credit card can be provided by different electronic devices at different times for different financial transactions. However, the electronic device 110-1 may only receive notifications of financial transactions conducted using the electronic device 110-1.

Alternatively, as further described below with reference to FIGS. 9 to 11, the registration may include the identifier of the user of the electronic device 110-1 so that the notification is used for financial transactions associated with the financial account specified by the financial account information, and Financial transactions may include their transactions using the electronic device 110-1 and some financial transactions using one or more other electronic devices. For example, the user may be the primary card holder, and he may receive notifications when using the electronic device 110-1 for financial transactions and when one or more relatives use one or more other electronic devices for financial transactions.

The user can also use the passbook 248 to select or activate one or more of the payment applets 236 (such as the payment applets 236-1 and 236-4). If the payment applet 236-1 supports the authentication completion flag 234 (such as the activation or setting instructions for authentication support in the payment applet 236-1), in order to make the payment applet 236-1 and the electronic device 112 (Figure 1) For financial transactions, it may be necessary to activate the payment applet 236-1 and it may be necessary to set or activate the authentication completion flag 234 in the secure element 230 (indicating that the user has been authenticated). In contrast, for those who do not support authentication Completion of the payment applet 236-4 of the flag 234 (as indicated by the disabling of authentication support in the payment applet 236-1), when the payment applet 236-4 is active (that is, without When the authentication completion flag 234 is set or activated in the secure element 230 to gate the operation of the payment applet 236-4), financial transactions can be performed. Although the present invention discusses the use of the global authentication completion flag 234, it should be noted that in some embodiments, there are separate authentication completion flags associated with at least some of the payment applets 236 (that is, there may be use (In the payment applet 236-1, etc., the specific authentication completion flag).

When the interface circuit 222 instructs the electronic device 110-1 to approach the electronic device 112 (FIG. 1), one of the activated and/or authenticated payment applet 236 (such as the payment applet 236-1) can be associated The financial account information is provided to the interface circuit 222. Then, the interface circuit 222 can use the antenna 224 to communicate the financial account information to the electronic device 112 (FIG. 1). In addition, the payment applet 236-1 and/or the secure component 230 can determine the unique transaction identifier based on the financial account information. For example, the payment applet 236-1 and/or the secure component 230 can perform a secure hash (such as SHA-256) on the financial account information, and can use a part (such as the least significant 16-byte) as the unique transaction identification symbol. Next, the secure element 230 can securely communicate the unique transaction identifier to the secure area processor 220.

Since the counter value in the financial account information may be truncated, the different count may look the same in the financial account information. For example, if the counter value is truncated to the least significant three bits, the counter value 999 and 1,999 may appear to be the same. In order to assist the final calculation of the calculated unique transaction identifier for financial transactions (which can then be received from a third party using the interface circuit 222 and the antenna 224) and another determined unique transaction identifier for another financial transaction To eliminate ambiguity, the passbook 248 can precede or append the time stamp when the financial account information is transmitted to the electronic device 112 (FIG. 1) to the unique transaction identifier. (More generally, the time stamp can be associated with the time when the financial transaction occurred.) The modified unique transaction identifier can be safely communicated to the secure element 230 and/or the payment applet 236-1.

If the user and/or electronic device 110-1 is registered to receive the notification, the electronic device 110-1 can use the interface circuit 222 and the antenna 224 to receive notifications of financial transactions from one or more third parties. In response, the secure element 230 and/or the payment applet 236-1 can request information (such as receipt information) associated with the financial transaction, and can receive information from a third party via the interface circuit 222 and the antenna 224. This information can include first-level information and/or second-level information and a calculated unique transaction identifier. The secure element 230 and/or the payment applet 236-1 can compare the determined unique transaction identifier with the calculated unique transaction identifier. If a match is obtained, the secure element 230 and/or the payment applet 236-1 can associate the information received from the third party with the financial transaction. This information (such as a digital receipt) can be presented to the user, for example, using a display in the display subsystem 240.

In some embodiments, the notification and information are processed at least in part by the passbook 248 running on the processing subsystem 210 instead of or in combination with the secure component 230 and/or the payment applet 236-1. For example, the passbook 248 may request information associated with the financial transaction in response to the notification. In addition, the passbook 248 can compare the determined unique transaction identifier with the calculated unique transaction identifier. If a match is obtained, the passbook 248 can associate the information received from the third party with the financial transaction, and the passbook 248 can present the information to the user.

Within the electronic device 110-1, one or more interconnects (such as the bus 238) can be used to connect the processing subsystem 210, the memory subsystem 212, the network connection subsystem 214, the authentication subsystem 216, and the security The subsystems 218 are coupled together. These interconnects may include electrical, optical, and/or electro-optical connections that the subsystems can use to communicate commands and data to each other. Note that different embodiments may include different numbers or configurations of electrical connections, optical connections, and/or electro-optical connections between subsystems. In some embodiments, the electronic device 110-1 can detect tampering by a secure component (such as the secure area processor 220, the secure element 230, and/or the bus 238), and can destroy the encryption/ Decryption key or authentication information (such as stored biometric identifier).

In some embodiments, the electronic device includes a display subsystem 240 for displaying information on a display. The display subsystem may include a display driver and a display (such as a liquid crystal display). Crystal display, multi-touch touch screen, etc.). In addition, in some embodiments, the electronic device includes an electronic device for receiving a user's<i>PIN</i>Safe input/output (<i>I/O</i>) Subsystem 242 (such as a keypad). As mentioned earlier, the display subsystem 240 and/or security<i>I/O</i>The subsystem 242 may be included in the authentication subsystem 216.

The electronic device 110-1 can be any electronic device with at least one network interface (or can be included in it). For example, the electronic device 110-1 may be (or may be included in) each of the following: a desktop computer, a laptop computer, a server, a media player (such as,<i>MP5</i>Players), appliances, mini-laptops/small laptops, tablets, smartphones, cellular phones, a piece of test equipment, network appliances, set-top boxes, personal digital assistants (<i>PDA</i>), toys, controllers, digital signal processors, game consoles, computing engines in appliances, consumer electronic devices, portable computing devices, personal portfolio managers and/or another electronic device.

Although specific components are used to describe the electronic device 110-1, in alternative embodiments, different components and/or subsystems may exist in the electronic device 110-1. For example, the electronic device 110-1 may include one or more additional processing subsystems, memory subsystems, network connection subsystems, authentication subsystems, security subsystems, display subsystems, and/or security<i>I/O</i>Subsystem. In addition, one or more of the subsystems may not exist in the electronic device 110-1. In addition, in some embodiments, the electronic device 110-1 may include one or more additional subsystems not shown in FIG. 2. For example, the electronic device 110-1 may include (but is not limited to) a data collection subsystem, an audio and/or video subsystem, an alarm subsystem, and/or a media processing subsystem. Also, although separate subsystems are shown in FIG. 2, in some embodiments, some or all of the given stator system or components may be integrated into one or more of the other subsystems or components in the electronic device 110-1. In. For example, in some embodiments, the program module 246 is included in the operating system 244. Alternatively or in addition, at least some of the functionality of the program module 246 may be included in the passbook 248.

In addition, any combination of analog circuits and/or digital circuits can be used to implement electronic devices Circuits and components in 110-1, including: bipolar,<i>PMOS</i>And/or<i>NMOS</i>Gate or transistor. In addition, the signals in these embodiments may include digital signals with approximately discrete values and/or analog signals with continuous values. In addition, the components and circuits can be single-ended or differential, and the power supply can be unipolar or bipolar.

The integrated circuit may implement some or all of the functionality of the network connection subsystem 214 (such as a radio), and more generally, implement some or all of the functionality of the electronic device 110-1. In addition, the integrated circuit may include hardware and/or software mechanisms for transmitting wireless signals from the electronic device 110-1 to the electronic device 112 (FIG. 1) and from the electronic device 112 at the electronic device 110-1 Receive wireless signals. Except for the mechanisms described in this article, radio is well known in the art and therefore is not described in detail. Generally speaking, the network connection subsystem 214 and/or the integrated circuit may include any number of radios. Note that the radio in the multi-radio embodiment functions in a similar manner to the radio described in the single-radio embodiment.

In some embodiments, the network connection subsystem 214 and/or integrated circuit includes a configuration mechanism (such as one or more hardware and/or software mechanisms) that configures the radio to operate on a given communication channel (For example, a given carrier frequency) for transmission and/or reception. For example, in some embodiments, the configuration mechanism can be used to switch radio monitoring and/or transmission on a given communication channel to monitoring and/or transmission on a different communication channel. (Note that "monitoring" as used in this article includes receiving signals from other electronic devices and possibly performing one or more processing operations on the received signals, for example, determining whether the received signal contains advertising frames, etc.)

Although as an illustrative example, a communication protocol compatible with near field communication standards or specifications is used, the described embodiments of financial transaction technology can be used in a variety of networks or communication interfaces. In addition, although some of the operations in the previous embodiments are implemented in hardware or software, generally speaking, the operations in the previous embodiments can be implemented in a wide range of configurations and architectures. Therefore, some or all of the operations in the previous embodiment can be in hardware, software, or both Executed.

Although the previous discussion focused on the hardware, software, and functionality in the electronic device 110-1, the merchant 118 (FIG. 1), the payment network 122 (FIG. 1), and/or the receipt gateway 128 (FIG. 1) may have The same or similar hardware (processor, memory, network connection interface, etc.) and/or software are used to support operations performed by such entities, as described below with reference to FIGS. 4-7. In detail, these entities may include one or more computer systems that have processing subsystems that execute one or more program modules stored in the memory subsystem to perform operations, as well as other electronic devices (such as electronic devices). The device 110-1) communicates with one or more network connection interfaces.

An embodiment of the financial transaction technology will now be described. FIG. 4 presents a flowchart illustrating a method 400 for conducting financial transactions, which may be executed by a processor in an electronic device (such as the electronic device 110-1 in FIGS. 1 and 2). During operation, the processor may enable the user and/or the electronic device to register with one or more third parties (operation 408) as appropriate to receive financial transactions, the user (and in particular, the users financial account), and/ Or notifications associated with electronic devices.

In addition, the processor may optionally provide the activation command (operation 410) to the payment via the secure area processor (such as the secure area processor 220 in FIG. 2) and/or the interface circuit (such as the interface circuit 222 in FIG. 2). An applet (such as one of the payment applet 236 in FIG. 2), where the payment applet can perform financial transactions based on the authentication completion indicator after receiving the start command. For example, a user of an electronic device can use a digital wallet/passbook application (such as the passbook 248 in FIG. 2) to select one of the payment applets that corresponds to the credit card or debit card used to pay for financial transactions , Which can cause the activation command to be provided to the selected payment applet. This selection can be made by activating the icon displayed on the touch-sensitive display. Alternatively or in addition, a top-level button in the user interface of the electronic device can be used to make this selection. For example, the user can perform a sliding gesture in the user interface hierarchy or the top user interface in the tree, and then can select a payment applet from a set of possible payment applets displayed.

In response to the start command, the processor may go through the interface circuit and/or the safe area as appropriate The processor receives the activation response from the payment applet (operation 412).

Then, the processor may request authentication information based on the activation response as appropriate (operation 414). For example, the processor may request a biometric sensor (such as the biometric sensor 226 in FIG. 2) to obtain the user's biometric identifier (such as a fingerprint).

In response to the request, the processor may receive authentication information (operation 416). For example, the authentication information may include the biometric identifier received from the biometric sensor.

Next, the processor may use the secure zone processor to compare the authentication information with the stored authentication information (operation 418). Note that the stored authentication information can be stored in the processor or the secure area processor. In some embodiments, the payment applet is associated with<i>PIN</i>Stored in the secure component along with the payment applet (for example, an indicator of the data structure that can exist in the operating system of the secure component). However, in some other embodiments, the user will<i>PIN</i>After providing to the electronic device,<i>PIN</i>Stored in the processor.

In addition, if a match between the authentication information and the stored authentication information is obtained, the processor may provide (operation 420) an authentication completion indicator to the secure element (such as the image) via the secure area processor and/or the interface circuit. 2 in the secure element 230). This communication may involve secure (encrypted) communication between the secure zone processor and the secure element.

For payment applets that support authentication (this can be set during the installation of the payment applet in the secure component), the authentication completion indicator can enable the activated payment applet to conduct financial transactions. For example, the authentication applet in the secure element (such as the authentication applet 232 in FIG. 2) can set an authentication completion flag in the operating system of the secure element based on the received authentication completion indicator. Note that in some embodiments, the authentication completion flag is stored in the random access memory in the secure element. (In some cases, storing the authentication complete flag in the random access memory can save power, and it can also have the effect of clearing the authentication complete flag when the electronic device is powered off.) In addition, as mentioned earlier Then, the authentication applet can use the encryption key to decrypt the encrypted token received from the secure zone processor, and the token can include an authentication completion indicator.

After the payment applet is activated and the authentication completion flag is set based on the authentication completion indicator, the electronic device can perform financial transactions. In detail, after receiving information indicating that the electronic device approaches another electronic device (such as the electronic device 112 in FIG. 1), the electronic device may provide (operation 422) the financial account information to the other electronic device. For example, the authentication completion flag can be set to "true" to enable the activated payment applet when the authentication completion indicator indicates that a match is obtained; otherwise, the authentication completion flag can be set to "false" to enable The activated payment applet supports disabling the payment applet during authentication.

Then, the electronic device may determine a unique transaction identifier based on the financial account information (operation 424). For example, the secure component 230 (FIG. 2) can perform SHA-256 secure hashing on track 1 data and/or track 2 data. The least significant 16-byte output of the 32-byte SHA-256 security hash of the track 1 data and track 2 data can be concatenated as the unique transaction identifier. Note that in the embodiment where the track 1 data or the track 2 data is not available, the corresponding 16-byte groups in the unique transaction identifier may all be zero.

Subsequently, the electronic device may perform one or more additional operations (operation 426). For example, the processing subsystem 210 (FIG. 2) and/or the secure element 230 (FIG. 2) can perform the following operations: receive notifications from a third party; request information associated with financial transactions; receive information (which includes calculated Unique transaction identifier); compare the determined unique transaction identifier with the calculated unique transaction identifier; and/or if a match is obtained, associate the received information with the financial transaction. In an exemplary embodiment, if the portion of the unique transaction identifier associated with the track 1 data or the portion of the unique transaction identifier associated with the track 2 data matches, a match is obtained.

When the payment applet can be gated by the activation command and the authentication completion indicator or flag, the secure element may include a second payment applet (such as the other one of the payment applet 236 in FIG. 2). The second payment applet performs the second financial transaction via the interface circuit based on the authentication completion indicator or flag without activation. For example, the second payment applet may include the mass transmission payment applet, which can be used for the second financial transaction before No authentication is required. In fact, when the electronic device approaches another electronic device, the second payment applet can perform financial transactions.

Now describe FIG. 5, which presents a diagram illustrating the communication within the electronic device 110-1 (FIG. 1) and between the electronic devices 110-1 and 112 (FIG. 1) and provides other information about the aforementioned financial transaction technology in FIG. 4 . In detail, the secure element 230 and/or the passbook 248 can enable the user and/or the electronic device to report to one or more third parties (such as the supplier of the electronic device and/or the payment network, and more generally, the first Three parties 510) Register to receive notifications associated with financial transactions.

Then, the passbook 248 can provide the activation command to the authentication applet 232 for one of the payment applets 236 in FIG. 2. In response to the activation command, the passbook 248 can receive the activation response from the payment applet.

Next, the passbook 248 may request biometric authentication (such as a biometric identifier). In response, the secure zone processor 220 may request the biometric sensor 226 to obtain the user's fingerprint. The biometric sensor 226 can provide a fingerprint in response to this request. If the secure zone processor 220 obtains a match with the stored authentication information (such as the stored fingerprint of the user), the secure zone processor 220 may transmit the authentication completion indicator to the authentication applet 232, and the authentication The small program can set the authentication completion flag. In addition, the authentication applet 232 can indicate to the secure zone processor 220 that the payment applet is ready for use, and the secure zone processor can notify the passbook 248 in turn.

Subsequently, when the electronic device approaches the electronic device 112, the electronic device 112 can provide a request for financial account information to the interface circuit 222, and the interface circuit provides the request to the secure element 230. In response to the request, the secure element 230 can provide the financial account information to the interface circuit 222, which wirelessly transmits the financial account information to the electronic device 112. In addition, the secure element 230 can determine a unique transaction identifier based on the financial account information.

Note that the operations illustrated in Figure 5 may include query operations and response operations, which are not shown for clarity. The remaining operations (such as one or more additional operations in operation 426) in method 400 (FIG. 4) are further discussed below with reference to FIG. 6.

In detail, FIG. 6 presents a flowchart illustrating a method 600 for conducting financial transactions, which may be executed by a processor in an electronic device (such as the electronic device 110-1 in FIGS. 1 and 2). During operation, the processor (which may be in the processing subsystem 210 and/or the secure element 230 in FIG. 3) receives notifications associated with financial transactions from a third party (operation 610), where the third party is independent of another The counterparty in a financial transaction associated with an electronic device (such as the electronic device 112 in FIG. 1).

Next, the processor requests receipt information associated with the financial transaction from the third party (operation 612).

In addition, the processor receives receipt information from a third party (operation 614). As mentioned previously, the receipt information may include first-level information and/or second-level information and a calculated unique transaction identifier determined by an entity (which may be different from or the same as a third party) based on financial account information.

In addition, the processor may compare the calculated unique transaction identifier with the determined unique transaction identifier. If the unique transaction identifier received from the third party matches the unique transaction identifier determined by the secure element (operation 616), the processor may associate the receipt information with the determined unique transaction identifier (operation 618) and therefore Associated with financial transactions. Otherwise, the processor may not make this association (operation 620).

FIG. 7 is now described, which presents a diagram illustrating communication between electronic devices (such as electronic devices 110-1 and 112) and provides other information about the aforementioned technology of FIG. 6. During the financial transaction, the electronic device 110-1 can provide financial account information to the electronic device 112 via wireless communication. As previously discussed, this may involve interaction when the electronic devices 110-1 and 112 decide which payment applet to use and provide financial account information.

Then, the electronic device 112 provides the financial account information together with additional information associated with the financial transaction to the merchant 118. In addition, the electronic device 112 and/or the merchant 118 may calculate a unique transaction identifier based on the financial account information.

Next, the merchant 118 can decide whether the financial transaction is from a supplier (such as Apple Inc.) electronic device. For example, the merchant 118 may use an alternative symbol for the name of the user or credit card holder, such as "APL/". In addition, the merchant 118 may request payment from the merchant acquirer 710 (between the merchant 118 and the payment network 122), and the merchant acquirer transmits the request to the payment network 122. If the electronic device 110-1 has been registered with the payment network 122, the payment network 122 may provide a notification associated with the financial transaction to the electronic device 110-1. In response to the notification, the electronic device 110-1 may request receipt information (such as first-level information and/or second-level information), and the payment network 122 may provide the information together with the calculated unique transaction identifier to the electronic device 110-1. By comparing this calculated unique transaction identifier with the unique transaction identifier determined using the secure element 230 (FIG. 2) and/or the processing subsystem 210 (FIG. 2), the calculated unique transaction identifier can be used to make all transactions. The information provided is related to financial transactions. In addition, the electronic device 110-1 can then use the display on the electronic device 110-1 to display the first-level information and/or the second-level information to the user.

Alternatively or additionally, the merchant 118 may send transaction details (including<i>DPAN</i>The security hash, the calculated unique transaction identifier and/or the second-level information) are provided to the merchant payment gateway (such as the receipt gateway 128). In response, the receipt gateway 128 can perform the following operations:<i>DPAN</i>Security hash decision<i>DPAN</i>;based on<i>DPAN</i>Look up the secure element identifier; and obtain the push token based on the secure element identification.

The push token may allow the receipt gateway 128 to provide notifications to the electronic device 110-1. In response to the notification, the electronic device 110-1 may request receipt information (such as second-level information), which may be provided by the receipt gateway 128 to the electronic device 110-1 along with the calculated unique transaction identifier. By comparing this calculated unique transaction identifier with the unique transaction identifier determined using the secure element 230 (FIG. 2) and/or the processing subsystem 210 (FIG. 2), the calculated unique transaction identifier can be used to make all transactions. The second level of information provided is related to financial transactions. In addition, the electronic device 110-1 can then use the display on the electronic device 110-1 to display the first-level information and/or the second-level information to the user.

Note that the communication of the first level information between the payment network 122 and the electronic device 110-1 And the communication of the second-level information between the receipt gateway 128 and the electronic device 110-1 can occur simultaneously or separately. In addition, note that the operations illustrated in FIG. 7 may include query operations and response operations, which are not shown for clarity.

In this way, by providing end-to-end security authentication for the user of the electronic device 110-1 (FIG. 1) and/or by allowing financial transactions to be uniquely associated with the electronic device 110-1 (FIG. 1 and FIG. 2) ) The received information (such as receipt information) is associated (based on a unique transaction identifier), and the electronic device can facilitate financial transactions between the electronic devices 110-1 and 112 (FIGS. 1 and 2).

In some embodiments of method 400 (FIG. 4) and method 600 (FIG. 6), there may be additional or fewer operations. For example, instead of performing operations 410 and 412 in FIG. 4, one of the payment applets can be defined as the default payment applet used in financial transactions, so that unless the user chooses a different payment applet, The default payment applet is always activated. In addition, one or more messages from one or more entities (such as one or more third parties) may be used to convey information (such as receipt information, first-level information, and/or second-level information). In addition, the order of operations may be changed, and/or two or more operations may be combined into a single operation.

As previously discussed, after the registration process, one or more third parties can provide notifications to the electronic device 110-1 (FIGS. 1 and 2). Registration may involve the user providing the user's identifier to one or more third parties. For example, as shown in FIG. 8 showing a diagram illustrating the provision of notification to one of the electronic devices in FIG. 1, after registration, a financial transaction report using the electronic device 110-1 (via Notification) to the electronic device 110-1. In addition, financial transactions performed using financial instruments (such as credit cards) may be reported to the electronic device 110-1 as appropriate. In this case, the credit card can represent<i>FPAN</i>And the electronic device 110-1 can be used<i>DPAN</i> 1. Therefore, note that financial transactions originating from two locations can be reported to one electronic device.

The change of this scenario is shown in FIG. 9, which presents a diagram illustrating the provision of notifications to multiple electronic devices. In this embodiment, the user may have more than one electronic device ( For example, electronic devices 110-1 and 110-2). In addition, credit cards can indicate<i>FPAN</i>, The electronic device 110-1 can be used<i>DPAN</i> 1. The electronic device 110-2 can be used<i>DPAN</i> 2. Depending on the user's choice (such as using the user interface associated with the passbook 248 in FIG. 2), the so-called<i>DPAN</i>Notifications associated with financial transactions (that is, their transactions conducted using electronic device 110-1 and/or 110-2): Provided to the originating electronic device (that is, financial transactions conducted using electronic device 110-1 The notification provided to the electronic device 110-1, and the notification of the financial transaction using the electronic device 110-2 can be provided to the electronic device 110-2); or to both the electronic devices 110-1 and 110-2; Financial transactions originating from the electronic device 110-1 are provided to the electronic device 110-1; and financial transactions originating from the electronic device 110-2 are provided to both the electronic devices 110-1 and 110-2. In addition, the so-called<i>FPAN</i>The notification of the financial transaction is reported to one or both of the electronic devices 110-1 and 110-2. Note that financial transactions originating from three locations can be reported to a maximum of two electronic devices.

In another embodiment, for the financial instrument, there is a<i>FPAN</i>, And three<i>DPAN</i>(<i>DPAN</i> 1、<i>DPAN</i> 2、<i>DPAN</i> 3) Propagate to three electronic devices with two associated user identifiers (such as user account identifiers for suppliers of electronic devices). FIG. 10 presents a diagram illustrating the provision of notifications to the electronic devices 110-1, 110-2, and 110-3. Depending on the users choice, it can be compared with the so-called<i>DPAN</i>Notifications related to financial transactions: provided to the originating electronic device; provided to electronic devices 110-1 and 110-2, which share a common user identifier; or provided to electronic devices 110-1, 110-2, and 110-3, these electronic devices share the same<i>FPAN</i>. In addition, the so-called<i>FPAN</i>The notification of the financial transaction is reported to one, many, or all of the electronic devices 110-1, 110-2, and 110-3. Note that financial transactions originating from four locations can be reported to a maximum of three electronic devices.

In an exemplary embodiment, under default conditions,<i>DPAN</i> 1 and<i>DPAN</i> 2 receive notifications from each other, and<i>DPAN</i> 3 receive only<i>DPAN</i> 3 of the notice. If received by default<i>DPAN</i> 1 notice and<i>DPAN</i> 2 User selection of the notified electronic device 110-1<i>FPAN</i>Notice, call Sub-device 110-1 can be unregistered<i>DPAN</i> 1 notification and registration<i>FPAN</i>notify.

In another embodiment, for two financial instruments (such as a spouses credit card), there are two<i>FPAN</i>, And three<i>DPAN</i>(<i>DPAN</i> 1、<i>DPAN</i> 2、<i>DPAN</i> 3) Propagate to three electronic devices with two associated user identifiers (such as user account identifiers for suppliers of electronic devices). FIG. 11 presents a diagram illustrating the provision of notifications to the electronic devices 110-1, 110-2, and 110-3. Depending on the users choice, it can be compared with the so-called<i>DPAN</i>Notifications associated with financial transactions: provided to the originating electronic device; provided to the electronic devices 110-1 and 110-2 sharing a common user identifier; provided to the same<i>FPAN</i>All electronic devices (such as electronic devices 110-1 and 110-2 or electronic device 110-3); or all electronic devices (such as electronic devices 110-1, 110-2, and 110) that share a common financial account -3). In addition, the so-called<i>FPAN</i>The notification of the financial transaction is reported to one, many, or all of the electronic devices 110-1, 110-2, and 110-3. Note that financial transactions originating from five locations can be reported to a maximum of three electronic devices.

In the previous embodiment, in<i>FPAN</i>After registering one or more user identifiers with the payment network 122 and/or the receipt gateway 128, the notification can be provided to one or more electronic devices. This registration allows<i>FPAN</i>And one or more user identifiers and one or more of one or more electronic devices<i>DPAN</i>Associated. Then, after receiving the information indicating the occurrence of a financial transaction, the payment network 122 and/or the receipt gateway 128 can access the associated lookup table, and can use information such as push tokens to provide notifications to one or more Designations<i>DPAN</i>。

Although the previous embodiment illustrates the static selection of the electronic device that receives the notification, in other embodiments, the notification associated with the financial transaction may be provided to multiple electronic devices only once (for example, for a financial transaction). Only notifications associated with subsequent financial transactions can be provided to the originating electronic device.

In some embodiments, touching the electronic device 110-1 (FIG. 1) or bringing the electronic device 110-1 close to the electronic device 112 (FIG. 1) allows the establishment of a direct-channel inter-level wireless connection (with rich data communication). For example, near field communication may allow communication between electronic devices 110-1 and 112 Exchange encryption/decryption keys. Subsequently, the wireless communication between the electronic devices 110-1 and 112 (such as via Wi-Fi or Bluetooth) can be encrypted/decrypted.^TM)。

In some embodiments, the communication technology is modified to accommodate the use of loyalty programs and/or electronic or digital coupons. For example, when the electronic devices 110-1 and 112 (FIG. 1) are close to each other, loyalty card information (such as a loyalty card account) can be communicated from the electronic device 110-1 (FIG. 1 and FIG. 2) to the electronic device 112 (figure 1). In detail, you can use barcodes or by<i>DPAN</i>The link is provided to the electronic device 112 (FIG. 1) to convey the loyalty card information. Subsequently, the receipt information (and, in detail, the second-level information) may include a user interface object that allows the user to choose to join the merchant 118's loyalty program (FIG. 2). Since the user has previously opted in, the opt-in procedure will be executed once the time interval has expired or the procedure will be executed after the time interval has expired.

In the previous description, "some embodiments" were mentioned. Note that "some embodiments" describe a subset of all possible embodiments, but do not always specify the same subset of embodiments.

The foregoing description is intended to enable anyone familiar with the art to make and use the present invention, and is provided in the context of a specific application and its requirements. In addition, the foregoing description of the embodiments of the present invention has been presented for the purpose of illustration and description only. The description is not intended to be exhaustive or to limit the invention to the form disclosed. Therefore, many modifications and changes will be obvious to those skilled in the art, and the general principles defined herein can be applied to other embodiments and applications without departing from the spirit and scope of the present invention. In addition, the discussion of the previous embodiments is not intended to limit the present invention. Therefore, the present invention is not intended to be limited to the illustrated embodiments, but should conform to the broadest scope consistent with the principles and features disclosed herein.