ES2749625T3 - Methods and systems to provide payment credentials - Google Patents

Abstract

A method of providing a digital wallet application on a mobile device (112, 212, 316, 931) with payment credentials that the digital wallet application lacked prior to provisioning, the payment credentials being usable by the mobile device ( 112, 212, 316, 931) in making a contactless payment, the method being performed in a provisioning system (140, 240, 340, 901) and comprising the steps of: receiving (402, 422, 704) credentials payment from a point of sale or ATM device (120, 222, 320, 920) in a financial transaction message, having obtained the payment credentials by the point of sale or ATM device (120, 222, 320, 920 ) from a portable payment device (114, 214, 314, 905) through a communication interface with or without contact of the point of sale or ATM device (120, 222, 320, 920) presenting the portable payment device (114, 214, 314, 905) by a consumer at the point of v ent or ATM device (120, 222, 320, 920); reception (404, 424, 704), from the point of sale or ATM device (120, 222, 320, 920), of an identifier entered by the consumer in the financial transaction message; identification (406, 430, 705) of a mobile device (112, 212, 316, 931) or a secure element (113) in the mobile device (112, 212, 316, 931) that corresponds to the identifier; and communication (410, 432, 707) of the payment credentials to the identified mobile device (112, 212, 316, 931) or the secure element (113) on the mobile device (112, 212, 316, 931), causing payment credentials are securely stored in the secure element (113) of the mobile device (112, 212, 316, 931), the secure element (113) being one of the group of: a secure element (113) provided in the mobile device (112, 212, 316, 931), a secure element (113) embedded in a layer (318) that is located between a communication component (317) of the mobile device (112, 212, 316, 931) and a communication component interface of the mobile device (112, 212, 316, 931), and a secure element (113) provided in a communication component (317) of the mobile device (112, 212, 316, 931).

Description

DESCRIPTION

Methods and systems to provide payment credentials

Field of the Invention

This request refers to the field of provision of payment credentials usable by a mobile device.

Background

As more merchants are adopting point-of-sale terminals that are capable of transacting with mobile devices, consumers are much more likely to replace their physical wallets with digital wallet applications running on their mobile devices (eg, mobile phones). . Transactions with digital wallet applications running on a mobile device may be contactless, for example, using the near field communication (NFC) capabilities of the mobile device.

Contactless payment transactions provide significant convenience to consumers by allowing consumers to shop faster and more comfortably than in a contact-based environment. In a contactless payment transaction, a consumer carries a contactless capable user portable payment device (CPPD) such as a contactless smart card or a mobile phone in close proximity to an acceptance terminal. Information such as payment credentials is exchanged between the contactless CPPD and the accepting terminal in a wireless manner to effect the payment transaction without requiring direct physical contact between the contactless CPPD and the accepting terminal. In some cases, the contactless CPPD and the acceptance terminal are not co-located, but may be in different locations, for example, in different cities or countries. In such a case the information is transmitted between the contactless CPPD and the accepting terminal via, for example, the Internet.

A mobile device that is used as a contactless CPPD is often required by various standards or compliance authorities to contain a secure element. Such a secure element is no different than a secure integrated circuit used in conventional CPPDs, such as cards with a secure integrated circuit. Secure elements that are in communication with mobile devices typically provide secure memory and secure processor that are separate from mobile device memory and processor and can only be accessed by trusted applications, often only after a number has been entered correctly. specified personal identification (PIN). Mobile devices in which such secure elements are arranged or embedded are often equipped with proximity communication interfaces such as, for example, near field communications (NFC).

It is in this secure memory that information, such as payment credentials, can be stored. In some cases, the provision of such payment credentials to the secure memory of the mobile device may be through over the air communications (OTA) methods originating from a trusted service manager (TSM). Such TSMs are typically operated from secure data centers in such a way that the process complies with security standards imposed by relevant standards or compliance authorities.

Providing digital wallet applications on mobile devices can be a complicated task. For example, to provision a mobile device with credentials for contactless transactions such as contactless payment transactions, users may be required to access a contactless transaction service provider from their mobile device to perform a provisioning process. from OTA. The OTA process may require the user to manually enter user credentials such as account numbers. Since most consumers probably have many credential storage instruments such as credit / debit cards from different banks that the user would like to include in the digital wallet application, enter this information for all of a user's credential storage instruments It can be a time consuming process. Additionally, the OTA provision process may generate unwanted charges for the use of wireless data for the user.

Embodiments of the invention are intended to address these and other problems individually and collectively, at least to some extent.

Brief summary

In accordance with a first aspect of the present invention there is provided a method of providing payment credentials usable by a mobile device in making a payment as defined in claim 1.

The method may additionally include: encrypting the received payment credentials, the encrypted payment credentials having a unique decryption key. Payment credentials can be communicated in encrypted form with the unique decryption key being stored in the provisioning system. In one example, reporting a derivation of Payment credentials communicates the unique decryption key, and encrypted payment credentials are stored in the provisioning system. In the case where the unique decryption key is communicated, the unique decryption key can be purged from the provisioning system.

In method embodiments, the provisioning system is a remotely accessible server from an issuing authority, a trusted security gateway or service manager, and on which to communicate payment credentials or a derivation of payment credentials to Identified mobile device or secure element uses a secure communication channel.

In alternative embodiments of the method, the provisioning system is a kiosk having a processor local to the receiving device, and wherein the method includes: establishing a communication channel between the kiosk and the mobile device to communicate the payment credentials or a derivation of payment credentials. The kiosk can act as a broker for a remotely accessible server and the method can include using the received identifier to identify and / or verify a user or account on a remotely accessible server. The method may include: requesting authorization from a trusted service manager to access a secure element; and receive a security key to access the secure element.

The method may additionally include: communicating additional credentials to the identified mobile device or secure item to be stored securely in association with the mobile device, in which the additional credentials are required in use in addition to the payment credentials or derivation of the credentials of payment that carry out a transaction. In one embodiment, the additional credentials can be card verification values. In another embodiment, the additional credentials may be in the form of a dynamic verification algorithm or application to generate dynamic verification values. The method may include obtaining additional credentials from a remotely accessible server using the identifier and forwarding the additional credentials to the mobile device.

The receiving device may be one of the group of: a card reader associated with a kiosk, a point of sale device, an ATM, a merchant point of sale terminal, or a personal PIN entry device (PPED) .

The portable payment device can be one of the group of: a magnetic stripe debit or credit card, a debit or credit card with an integrated security circuit, a bank card, a contactless bank card, a credit card, a existing payment credential stored on a mobile device.

Payment credentials received may include receiving one or more of track 1 data, track 2 data, track 3 data and equivalent track 2 data. Received payment credentials may include one or more of the group of: track data , an account number, account holder name and / or date of birth, a bank identification number (BIN), a primary account number (PAN), a service code, an expiration date, card verification values (CVV1 or CVV2), personal details of an account holder, a PIN block or range, a bank account number, a branch code, an account number or loyalty identifier, credit card number information, and / or or debit, account balance information.

The identifier may be one or more of the group of: an international mobile station subscriber directory number (MSISDN), an email address, a social network identifier, a predefined consumer name, a consumer account number.

The step of receiving payment credentials and the stage of receiving an identifier may include receiving a single secure transaction message containing the payment credentials and the identifier. The secure transaction message can be one of the group of: a payment processing network message, a financial transaction message, a financial transaction message in the form of an ISO 8583 message, a financial transaction message containing a transaction code server routing. The server routing code can be used to route the financial transaction message to the remotely accessible server via a payment processing network.

Identifying a mobile device or secure element that corresponds to the identifier may include: determining whether or not a mobile device or secure element that corresponds to the identifier has been registered with a remotely accessible server, and whether the mobile device has been registered, identify a corresponding communication address of the mobile device and / or secure element.

Additional features provide the step of identifying a mobile device that corresponds to the identifier to include the step of using the identifier to query a database to obtain a communication address of the mobile associated device with the identifier. Additional features provide the step of communicating payment credentials to the mobile device to include communicating payment credentials to the mobile device using the communication address.

Communicating payment credentials or a derivation of payment credentials to the identified mobile device to be stored securely in association with the mobile device, may include: communicating payment credentials or a derivation of payment credentials to the mobile device to store in a secure element, wherein the secure element is one of the group of: a secure element provided in the mobile device, a secure element embedded in a layer that is located between a communication component of the mobile device and a component interface of mobile device communication, a secure element provided in a mobile device communication component, a cloud-based secure element associated with the mobile device. In one embodiment, the secure element may be embedded in a label, card, or board and located between a communication component of the mobile device and a communication component interface of the mobile device,

The method can be repeated for multiple payment credentials to be stored securely in association with a single mobile device.

The method can be used to transfer payment credentials to a second mobile device from its existing secure storage on a first mobile device, wherein the portable payment device is an existing payment credential stored securely on the first mobile device.

In accordance with a second aspect of the present invention there is provided a method for providing payment credentials usable by a mobile device in making a payment, the method being performed on a point of sale device and comprising the steps as defined in the claim 10.

In accordance with a third aspect of the present invention there is provided a system for providing payment credentials usable by a mobile device in making a payment, including a provisioning system as defined in claim 11.

The provisioning system may include: an encryption component to encrypt the received payment credentials, the encrypted payment credentials having a unique decryption key; and in which communicating a derivation of the payment credentials communicates the unique decryption key.

In system examples, the provisioning system is a remotely accessible server from an issuing authority, a security gateway, or a trusted service manager, and on which the communication module to communicate payment credentials or a referral of the payment credentials to the identified mobile device or the secure element uses a secure communication channel.

In alternative embodiments, the provisioning system is a kiosk having a processor local to the receiving device, and in which the kiosk includes the communication module to establish a communication channel between the kiosk and the mobile device to communicate the credentials of payment or a derivation of payment credentials. The kiosk can act as an intermediary for a remotely accessible server and the system includes a communication module server to use the received identifier to identify and / or verify a user or account on the remotely accessible server.

The provisioning system may additionally include: an authorization component to request authorization from a trusted service manager to access a secure element and receive a security key to access the secure element.

The provisioning system may additionally include: an additional credential component to communicate additional credentials to the identified mobile device or the secure item to be securely stored in association with the mobile device, wherein the additional credentials are required in use in addition to the payment credentials or derivation of payment credentials that make a transaction. In one embodiment, the additional credentials can be card verification values. In another embodiment, the additional credentials may be in the form of a dynamic verification algorithm or application to generate dynamic verification values. The method may include obtaining additional credentials from a remotely accessible server using the identifier and forwarding the additional credentials to the mobile device.

The identification component for identifying a mobile device that corresponds to the identifier may include functionality to determine whether or not a mobile device or a secure element that corresponds to the identifier has been registered with a remotely accessible server and, if the mobile device has been registered, identify a corresponding communication address of the mobile device or secure element.

The communication module for communicating payment credentials or a derivation of payment credentials to the identified mobile device to be stored securely in association with the mobile device, includes functionality to communicate payment credentials or a derivation of payment credentials. to the mobile device to be stored in a secure element, in which the secure element is one of the group of: a secure element provided in the mobile device, a secure element embedded in a layer that is located between a communication component of the mobile device and a communication component interface of the mobile device, a secure element provided in a communication component of the mobile device, a cloud-based secure element associated with the mobile device.

In further embodiments, the system may include: a point of sale device comprising: a payment credential obtaining component for obtaining payment credentials from a portable payment device presented by a consumer at the receiving device; an identifier receiver for receiving an identifier entered by the consumer in the point of sale device; a communication module to communicate the payment credentials and identifier to a remotely accessible server for additional communication of the payment credentials or a bypass of the payment credentials to a mobile device to be stored securely in association with the mobile device .

In a further aspect of the present invention, a kiosk is provided to allow a user to provide a mobile device with credentials from the user's credential storage instruments also referred to as portable payment devices. The kiosk includes a credential storage instrument reader to retrieve credentials from a credential storage instrument. The kiosk also includes a mobile device interface to establish a communication channel with a mobile device, and to upload credentials from the credential storage instrument to the mobile device through the communication channel.

In accordance with a fourth aspect of the present invention, a computer program product is provided to provide payment credentials usable by a mobile device in making a payment, the computer program product comprising a computer readable medium that has stored Computer readable program for performing the steps of the first aspect of the present invention and one or more additionally defined features listed above.

In accordance with a fifth aspect of the present invention a computer program product is provided to provide payment credentials usable by a mobile device in making a payment, the computer program product comprising a computer readable medium that has stored code computer readable program for performing the steps of the second aspect of the present invention and one or more further defined features listed above.

Additional features of the invention provide that the computer readable medium is a non-transient computer readable medium and that the computer readable program code is executable by a processing circuit.

For the invention to be more fully understood, implementations thereof will now be described with reference to the accompanying drawings.

Brief description of the drawings

Figure 1 is a schematic diagram of a first embodiment of a system according to the present invention;

Figure 2 is a schematic diagram showing variations of the first embodiment of Figure 1;

Figure 3 is a schematic diagram of showing variations of the first embodiment of Figure 1;

Figure 4A is a flow chart of a method performed on a delivery system in accordance with the present invention;

Figure 4B is a flow chart of one embodiment of the method of Figure 4A;

Figure 5 is a flow chart of a method performed on a point of sale device in accordance with the present invention;

Figure 6A is a block diagram of one aspect of a system in accordance with the present invention;

Figure 6B is a block diagram of one aspect of a system in accordance with the present invention;

Figure 7 is a lane diagram of an example of a method according to the present invention;

Figure 8 is a lane diagram of another example of a method according to the present invention;

Figure 9A illustrates a second embodiment of a system in accordance with the present invention;

Figure 9B is a block diagram of a kiosk of the embodiment of the system of Figure 9A;

Figure 9C is a schematic diagram of a system of the embodiment of Figure 9A;

Figure 9D is a flow chart of a method of the embodiment of Figure 9A;

Figure 10 is a lane diagram of the embodiment of Figure 9A;

Figure 11 illustrates a block diagram of a computing device in which various aspects of the invention can be implemented; Y

Figure 12 illustrates a block diagram of a communication device that can be used in various embodiments of the invention.

Detailed description

In the following detailed description, numerous specific details are set forth to provide a complete understanding of the invention. However, it will be understood by those skilled in the art that the present invention can be practiced without these specific details. In other cases, well known methods, procedures and components have not been described in detail so as not to hinder the present invention.

Methods and systems are described for providing payment credentials or derivations of payment credentials usable by a mobile device in making a contactless payment.

Embodiments of the invention include a method performed on a remotely accessible server for providing payment credentials or derivations thereof to a mobile device through a receiving device into which a portable payment device or storage instrument can be inserted. of credentials such as a payment card. The receiving device may be, for example, a point of sale device, an ATM or other intermediary device.

Payment credentials can be securely provided to the mobile device from the server remotely accessible via channels to a secure item associated with the mobile device.

Payment credentials can be provided to the mobile device or, alternatively, payment credentials can be stored on the remotely accessible server in an encrypted form and a unique decryption key can be provided to the mobile device.

Other embodiments of the invention provide a kiosk to allow a user to provide a mobile device with credentials from the user's credential storage instruments. By providing a kiosk as an interface between the user's mobile device and the user's credential storage instruments, manual entry of the credentials can be avoided because such credentials can be read directly from the user's credential storage instruments. Additionally, the kiosk can act as a communication intermediary between the mobile device and entities involved in the provisioning process such as a trusted service issuer or manager to prevent use of wireless data on the mobile device during the provisioning process. Therefore, embodiments of the present invention provide a convenient and cost-effective way to enable mobile devices with digital wallet applications for use in contactless transactions.

These additional embodiments and embodiments are now described in detail.

Figure 1 illustrates a block diagram of an illustrative system (100) according to embodiments of the invention. The system includes a mobile device (112) and a portable payment device (114) from a consumer (102). The system further includes a receiving device for the portable payment device (114) and, in this embodiment, the receiving device is in the form of a point of sale device (120). The system further includes a remotely accessible server (140) which, in the illustrative system (100), is in communication with the point of sale device (120) through a payment processing network (130). While the figure only shows a consumer (102), a mobile device (112), a portable payment device (114) and a point of sale device (120), it will be appreciated that this is purely for illustration purposes and that the Invention provides for one or more of each.

The mobile device 112 can be any suitable mobile device having a secure element 113. The secure element (113) can be embedded in the mobile device, arranged within a mini secure digital card (SD) form factor or the like that is located in a mini SD card slot of the mobile device (112).

As an alternative, the secure element 113 can be arranged within a communication component of the mobile device, such as a universal integrated circuit card (UICC). It is also envisaged that in some embodiments the secure element 113 can be arranged in an expansion device can be connected to a mobile device or alternatively be disposed within it, for example a tag, plate or card which is then placed between a UICC and a UICC interface of the mobile device in such a way that the secure element can properly intercept and process any communication sent between the UICC and the mobile device and consequently between the mobile device and a mobile communication network.

It is further envisaged that the secure element (113) may be a cloud-based secure element using system card emulation (HCE) which enables external network accessible storage to the mobile device (112) with an application on the mobile device (112 ) configured to emulate card functions.

Illustrative mobile devices include smartphones, basic phones, tablet computers, personal digital assistants, or the like. The mobile device 112 is in data communication with the server remotely accessible through, for example, a mobile data or mobile communication network, and is configured to at least securely receive, store, launch and transmit payment credentials or derivations of payment credentials. For example, mobile device 112 may be any such device that complies with payment or financial scheme standards, such as, for example, the Global Platform Card Specification. Embodiments of the invention provide that an appropriate mobile software application is resident in the mobile device 112 that allows a user thereof to interact with, or associate with, the secure element 113. architecture based on the cloud, and that can also facilitate communications between the mobile device (112) and the secure element (113).

The software application can provide: a user interface to facilitate entering an access key in the mobile device (112) to be compared with an interval stored in the secure element (113); a list from which users can select payment credentials to use; notifications of receipt or use or payment credentials or similar. The user interface may include a menu from which at least some of these communications can be initiated. Examples of the invention further provide that such an interface is provided by a SIM application toolkit protocol implementation (commonly referred to as the STK protocol) or the like.

The portable payment device 114 in the illustrated embodiment is a security integrated circuit bank card. Such cards are also known as 'chip and pin' cards or 'EMV smart cards'. The portable payment device 114 has payment credentials, which can be track 2 information and / or track 2 equivalent (such as EMV tag data 57), stored therein. Track 2 and / or track 2 equivalent information may include a bank identification number (BIN), a primary account number (PAN), an expiration date, a service code, discretionary data such as card verification values (CVV) as well as any checks for space and redundancy. In addition to this, examples of the invention provide that the portable payment device (114) contains payment credentials that may include any one or more of a customer name and / or date of birth, a BIN, a PAN, a service, an expiration date, CVV1 or CVV2 numbers, a PIN block or range, a bank account number, a branch code, an account number or loyalty identifier, credit and / or debit card number information , account balance information and / or other consumer information. In other examples of the invention, the payment credentials may include track 1 and / or track 3 information.

The point of sale device 120 can be any suitable device configured to obtain payment credentials from appropriate portable payment devices and to communicate these payment credentials to a payment processing network or financial institution network. The point of sale device (120) can be configured to obtain payment credentials from portable payment devices through any appropriate contact or non-contact communication interface which can be, for example, ISO / IEC 7813, ISO / IEC 7816 standards. or ISO / IEC 14443 where applicable.

The point of sale device (120) may include one or more of various means for retrieving information from a portable payment device that includes the user placing the portable payment device (114) in physical contact with the point of sale device. (120), for example, sliding or inserting a magnetic stripe card into a magnetic stripe reader, or inserting a chip card into a chip card reader slot, or the user locating the portable payment device (114) in close proximity to the point of sale device (120), for example, by placing a contactless card in close proximity to a contactless card reader, or by placing a printed medium, for example, with a barcode or rapid response (QR) in front of an infrared scanner.

In the illustrated illustrative system 100, the point of sale device 120 is a hand held point of sale device. In addition to this, the point of sale device (120) is configured to receive an identifier entered by a consumer through, for example, a numeric keypad of the point of sale device (120).

The point of sale device (120) is further configured to format the payment credentials as well as the identifier in a financial transaction message and to communicate this message to the payment processing network (130). The financial transaction message may be, for example, an ISO 8583 message. Additionally, the point of sale device (120) is configured to insert a routing code of server in the financial transaction message such that the financial transaction message is routed to the remotely accessible server (140) via the payment processing network (130) using the server routing code. The server routing code can be placed in the 'BIN' field of the financial transaction message.

The payment processing network 130 is a network of financial entities and payment processing entities and is configured to route financial transaction messages between, for example, merchants, acquirers and issuers, among others. An example of such a payment processing network is VisaNet ™ which has a plurality of acquiring financial entities and issuers that are a part of the network.

The remotely accessible server 140 may be any appropriate server computer or distributed server computer system and has a database 142 stored in digital memory therein and also has secure memory which, in one embodiment Preferred is within a remotely accessible server hardware security module 144. The remotely accessible server (140) is configured to receive payment credentials from a point of sale device (for example 120), in which the payment credentials have been obtained from a portable payment device (for example 114) presented by a consumer (for example 102) at the point of sale device (120).

The remotely accessible server can be configured to encrypt payment credentials, with encrypted payment credentials having a unique decryption key. Encryption can be done in hardware security module (144). In one example, the key to decrypt the payment credentials is kept by the remotely accessible server (140) and the encrypted payment credentials are sent to the mobile device (112) for storage in the secure element (114) associated with the mobile device (112). In another example, the encrypted payment credentials are stored in the remotely accessible server hardware security module 144 (140) and the decryption key is sent to the mobile device (112) for storage in the secure element ( 113) associated with the mobile device (112).

In addition to this, the remotely accessible server (140) is configured to receive an identifier from the point of sale device (120) that is entered by the consumer (102) in the point of sale device (120). The remotely accessible server (140) is configured to then identify a mobile device (for example 112), or a secure element (113) associated with a mobile device (112), which corresponds to the identifier and to communicate the credentials of payment to the mobile device (112) to be stored in a secure element (113) associated with the mobile device (112).

This can be done using the identifier to query the database 142 to obtain a communication address of the mobile device 112 associated with the identifier. The payment credentials can then be sent to the mobile device 112 using the communication address. The identifier received by the remotely accessible server may be, for example, any one or more than one mobile station international subscriber directory number (MSISDN), an email address, a social network identifier, a predefined consumer, a consumer account number, or the like. The communication address of the mobile device may similarly be, for example, any one or more of an MSISDN, an email address, a social network identifier, a predefined consumer name, a consumer account number, or the like. The identifier and communication address can be the same.

Embodiments of the invention provide that the remotely accessible server is configured to associate one or more of the group of: the identifier; decryption key; encrypted payment credentials; and communication address with a user profile in the database.

In some embodiments of the invention the function performed by the remotely accessible server (140) can be similar to that of a trusted service manager (TSM) and therefore can meet any requirements for security or data identity imposed by standards relevant payment and financial schemes, such as the Global Platform card specification.

In use, a consumer (102) may wish to provide their payment credentials or a derivation thereof to a secure item (113) on their mobile device (112) such that the mobile device (112) can be used to make payment no contacts at physical merchants or online merchants.

To do this, the consumer, who has already registered his mobile device (112) with the remotely accessible server (140) and associated it with an identifier and communication address, visits, for example, a physical merchant and presents the merchant your portable payment device (114). The portable payment device (114) interfaces with a merchant's point of sale device (120) and, for example, a 'credential transfer' menu option is selected on the point of sale device (120). The consumer 102 may be prompted to enter a PIN that he or she enters into the point of sale device 120, after which the consumer 102 may be prompted to enter their identifier. The consumer (102) enters their default identifier, which has been registered with the remotely accessible server (140), at the point of sale device (120).

Having received the consumer's PIN, the point of sale device (120) is able to extract payment credentials from the portable payment device (114). The point of sale device (120) formats the payment credentials in a financial transaction message. The point of sale device 120 can also include the identifier in the financial transaction message as well as a server routing code. The server routing code can be similar to a BIN and ensures that the financial transaction message is routed to the remotely accessible server (140) via the payment processing network (130).

The financial transaction message is received at the remotely accessible server (140). The remotely accessible server uses the identifier contained in the financial transaction message to identify a communication address of an associated mobile device (112). The remotely accessible server (140) uses the communication address to communicate the payment credentials or a derivation of the payment credentials to the mobile device (112) for storage in the secure element (113) associated therewith.

Payment credentials are then received by the mobile device (112) and stored securely in the secure element (113) of the mobile device (112). The user can be notified for a PIN before the payment credentials are stored in the secure element. In some examples the payment credentials are provided to the mobile device 112 from the remotely accessible server 140 and stored in the secure element 113 through provision during communication (OTA). This accordingly can enable the user to make contactless payment using their mobile device (112) as a contactless portable payment device, in which the credentials provided by the mobile device (112) to the appropriately configured point of sale device of the merchant are those of the user's portable payment device (114).

In some examples, the remotely accessible server (140) can encrypt the payment credentials, and a unique decryption key can be associated with the payment credentials. One of the encrypted payment credentials or decryption key can then be stored in secure memory, such as a remotely accessible server hardware security module 144. The other of the encrypted payment credentials or the decryption key can be sent to the secure element (113) associated with the mobile device (112). Payment credentials can be encrypted using any appropriate encryption algorithm such that, once encrypted, payment credentials can only be decrypted using the unique decryption key. If the decryption key is sent to mobile device 112 for storage in secure element 113, this decryption key is not stored on the remotely accessible server or its hardware security module.

The encrypted payment credentials or decryption key received by the mobile device (112) are stored securely in the secure element (113) of the mobile device (112). The user can be notified for a PIN before encrypted payment credentials or decryption keys are stored in the secure item. In some key decryption examples they are provided to the mobile device (112) from the remotely accessible server (140) and stored in the secure element (113) through provision during air communication (OTA).

In the scenario of derivation of payment credentials in the form of a decryption key is stored in the secure element (113) associated with the mobile device (112), a user can present the identifier to a merchant as a payment method in conducting a transaction. The merchant can request payment credentials from the remotely accessible server (140) and, in conjunction, communicate the identifier to the remotely accessible server (140). The remotely accessible server (140) can use the received identifier to identify a mobile device (112) and request a decryption key from the identified mobile device (112). The mobile device (112), upon receiving this request, can then notify the user for a PIN, password or password before communicating a relevant decryption key to the remotely accessible server (140) so that corresponding credentials of Encrypted payment can be decrypted and communicated to the merchant and / or the merchant's acquirer and / or the payment processing network so that the transaction can be completed.

Figure 2 illustrates an illustrative system (200) in accordance with a second embodiment of the invention. The system is similar to that illustrated in Figure 1 and similar reference numbers refer to similar systems, entities, or devices. The system (200) in Figure 2 differs from that in Figure 1 in that the point of sale device in this embodiment is an automated teller machine (ATM) (222). ATM (222) can be any suitable ATM and is configured to obtain payment credentials from a consumer's portable payment device (214) (202) and to communicate these payment credentials to a payment processing network (230) or financial institution network. The ATM (222) can be configured to obtain payment credentials from the portable payment device (214) through any appropriate communication interface with or without contact, for example a card reader or near field communication interface (NFC) .

The ATM (222) in the illustrated embodiment is configured to receive an identifier entered by a consumer (202) through, for example, an ATM numeric keypad (222). The ATM (222) is further configured to format the payment credentials as well as the identifier in a financial transaction message and to communicate this message to the payment processing network (230). The financial transaction message may, for example, be an ISO 8583 message. Additionally, ATM (222) is configured to insert a transaction code. server routing in the financial transaction message such that the financial transaction message is routed to the remotely accessible server (240) via the payment processing network (230) using the server routing code. The server routing code can be placed in the 'BIN' field of the financial transaction message.

Once the payment credentials are received on the remotely accessible server, they can communicate or a derivation of the payment credentials can be communicated to the mobile device for storage in a secure element thereof as described in the description above.

The system (200) can be put into use by a user (202) in a similar way to the system of Figure 1. The user (202) presents his portable payment device (214) to a portable payment device interface of the ATM (222). The user may be prompted for a PIN, in response to a correct entry of which, the user (202) selects a 'credential transfer' option from a menu displayed on an ATM screen (222). The user (202) will also be notified for an identifier, which he or she enters into the ATM (222) through the numeric keypad of the ATM (222). The ATM (222) obtains payment credentials from the portable payment device (214) and formats the payment credentials, identifier, as well as the server routing code in a financial transaction message that is then sent to the payment processing (230) and routes from there to the remotely accessible server (240). Similar to the scenario in use of Figure 1, the payment credentials are then communicated to the user's mobile device (926) to be stored in a secure element thereof.

Figure 3 illustrates yet another illustrative system (300) in accordance with a third example of the invention. System 300 is similar to that illustrated in Figures 1 and 2, and similar reference numbers refer to similar systems, entities, or devices. The system (300) of Figure 3 differs from that of Figures 1 and 2 in that the mobile device (316) does not have an embedded secure element. Instead, the mobile device (316) has a cryptographic expansion tag (318) on which a secure element is provided. The cryptographic expansion tag (318) has electrical contacts arranged on an upper side and a lower side thereof that interacts with a communication component (317) and a communication component interface of the mobile device (316) respectively. The cryptographic expansion tag (318) can then be affixed to the communication component (317) which is inserted into a communication port of the mobile device (316) such that the secure element can properly intercept and process any communication sent between the communication component (317) and mobile device (316) and, accordingly, between mobile device (316) and a mobile communication network. In the illustrated example, the communication component is a universal integrated circuit card (UICC).

Figure 4A illustrates a flow diagram of a method according to an embodiment of an aspect of the invention. The method is performed in a provisioning system which can be a remotely accessible server, similar to those described in the previous description with reference to Figures 1 to 3, or a specialized kiosk as described further below in relation to Figures 9A to 9D.

The method includes a series of steps, a first one (402) of which is the step of receiving payment credentials from a receiving device which may be a point of sale device, incorporated in or used in association with a payment device. point of sale, as described with reference to Figures 1 to 3, or a kiosk credential storage instrument reader with reference to Figures 9A to 9D, or other form of receiving device for receiving payment credentials. The point of sale device may be, for example, an ATM machine, a merchant point of sale terminal, or a personal PIN input device (PPED).

Payment credentials received from the point of sale device are obtained from a portable payment device (also referred to below in connection with the embodiment of Figures 9A to 9D as a credential storage instrument) presented by a consumer on the receiving device. The portable payment device may be a credit or debit card, which may be any one of a magnetic stripe bank card, an integrated security circuit bank card, or a contactless bank card. Payment credentials can be track 1 data, track 2 data, track 3 data or equivalent track 2 data (such as EMV tag 57 data). Additionally, payment credentials may include an account holder name and / or date of birth, a bank identification number (BIN), a primary account number (PAN), a service code, an expiration date, values Card Verification (CVV1 or CVV2), a PIN block or range, a bank account number, a branch code, an account number or loyalty identifier, credit and / or debit card number information, information account balance and / or consumer information such as name, date of birth. Payment credentials can be received by the server remotely accessible through a payment processing network.

The method includes a step (404) of receiving an identifier from the receiving device, eg, the point of sale device, or kiosk user input interface. The identifier can be any one or more of a mobile station international subscriber directory number (MSISDN), an email address, a social network identifier, a predefined consumer name, or a consumer account number. In a preferred embodiment of the invention, the payment and identifier credentials are received at the server remotely accessible in a financial transaction message, which may be, for example, an ISO 8583 message. Additionally, the financial transaction message can be communicated from the point of sale device to the remotely accessible server through a payment processing network. The financial transaction message may therefore include a server routing code such that the payment processing network is able to route the financial transaction message to the remotely accessible server.

The method includes a next step (406) of identifying a mobile device and / or a secure element of a mobile device that corresponds to the identifier. This step may include the step of determining whether or not a mobile device and / or secure element corresponding to the identifier has been registered with the remotely accessible server and, if a mobile device and / or secure element has been registered, identify a corresponding communication address of the mobile device and / or secure element. This can be done using the identifier to query a remotely accessible server database to obtain the communication address of the mobile device and / or secure element associated with the identifier.

As an optional additional step 408, a registration or activation request can be sent to a trusted management service (TSM) that manages security keys or tokens that are used to access a secure element. The request may include the identifier. The TSM can authorize the unlocking of a secure item associated with the mobile device. TSM can be provided on the remotely accessible server or via a remote service provided on a separate remotely accessible server.

The method includes a step (410) of communicating the payment credentials to the mobile device to be stored in a secure element associated with the mobile device. This may include communicating payment credentials to the mobile device using the communication address. This may also include communicating payment credentials to the secure element associated with the mobile device using a secure element identification code to configure a secure channel of communication with the secure element that can be through the mobile device. In some examples as further described in relation to Figure 4B, a derivation of payment credentials is communicated to the mobile device or secure element, for example, the derivation of payment credentials may be a decryption key corresponding to credentials Remotely stored encrypted payment methods.

As an additional optional step (412), additional credentials can be requested by or supplied by the remotely accessible server. The additional credentials can be credentials that cannot be automatically read from a portable payment device such as a printed card verification value (eg CVV2 number) that is human readable from the portable payment device. In this case, additional credentials can be requested by the remotely accessible server and obtained from the consumer through the point of sale device.

Additional credentials can also include Dynamic Card Verification Value (dCVV) software that is used to generate a dCVV for individual transactions. Such additional credentials can be identified using the identifier and supplied by the remotely accessible server or by a separate remotely accessible server during the provisioning process. Additional credentials can be communicated to the secure item associated with the mobile device. These can be communicated separately to the payment credentials or derivation of the payment credentials.

The secure element of the mobile device may, in accordance with some examples of the invention, be embedded in a label, card or plate as described above in the following description. Before communicating the payment credentials to the mobile device, the remotely accessible server can encrypt the payment credentials using any one of a number of encryption algorithms. Illustrative encryption algorithms include Advanced Encryption Standard (AES), Data Encryption Standard (DES), Triple Data Encryption Standard / Algorithm (TDES / TDEA), Secure Socket Layer (SSL), Blowfish, Serpent, Twofish, International Data Encryption Algorithm (IDEA), Rivest, Shamir and Adleman (RSA), Digital Signature Algorithm (DSA), Tiny Encryption Algorithm (TEA), Extended TEA (XTEA), and / or other encryption algorithms or protocols . In some examples, the decryption key, also called the private key, is stored in a secure memory of the remotely accessible server in association with the identifier, such that only the remotely accessible server, or a module of Hardware security of the same, you can decrypt payment credentials before submission to, for example, a merchant. In this example, the payment credentials are stored in encrypted form on the secure element of the mobile device.

Figure 4B illustrates a flow diagram of a method according to another embodiment of an aspect of the invention. The method is performed on a remotely accessible server, such as that of Figures 1 to 3. The method includes a series of steps, a first one (422) of which is the receipt of payment credentials from a receiving device such as as a point-of-sale device similar to that of step (402) of Figure 4A.

The method includes a next step (424) of receiving an identifier from the receiving device such as a point of sale device similar to that of step (404) of Figure 4A.

The method includes a next step (426) of encrypting the payment credentials. Payment credentials can be encrypted with any appropriate algorithm and once encrypted, have a unique decryption key. Illustrative encryption algorithms include, but are not limited to, Advanced Encryption Standard (AES), Data Encryption Standard (DES), Triple Data Encryption Standard / Algorithm (TDES / TDEA), Secure Socket Layer (SSL), Blowfish , Serpent, Twofish, International Data Encryption Algorithm (IDEA), Rivest, Shamiry Adleman (RSA), Digital Signature Algorithm (DSA), Tiny Encryption Algorithm (TEA), Extended TEA (XTEA) and / or other algorithms or encryption protocols.

Since the decryption key is unique to those payment credentials, only that decryption key can be used to decrypt those payment credentials. The unique decryption key, which in some embodiments may be a private key, is not stored in the same location as the encrypted payment credentials.

The method includes a next step (428) of storing one of the encrypted payment credentials or the decryption key in a remotely accessible server secure memory, which in a preferred embodiment is a hardware security module. Encrypted payment credentials or unique decryption key, communication address, and identifier can be associated with a user profile stored in a remotely accessible server database. After receiving, for example, a unique decryption key, the corresponding payment credentials can be identified, stored in the hardware security module. The method includes a next step (430) of identifying a mobile device and / or a secure element corresponding to the identifier. This step is similar to step (406) in Figure 4A.

The method includes a final step (432) of communicating the other of the encrypted payment credentials and the unique decryption key to the mobile device to be stored in a secure element associated with the mobile device. This may include communicating to the mobile device using the communication address. The secure element of the mobile device can, according to some examples of the invention, be embedded in a label, card or plate as described above in the description above.

Since only one of the encrypted payment credentials and the decryption key is stored only in the secure element of the mobile device, the encrypted payment credentials cannot be decrypted and therefore cannot be used.

In the scenario where encrypted payment credentials are stored on the remotely accessible server and the unique decryption key is transmitted to the secure element of the mobile device, the unique decryption key is purged and is not stored in the remotely accessible server hardware security.

This scenario, which can be considered an inverse of one in which payment credentials are stored in the secure element of the mobile device, is advantageous in that if the secure element of the mobile device is compromised, only the decryption keys can be obtained encrypted payment credentials. Additionally, in the event that the secure element is compromised, the decryption keys stored in it can be simply revoked, without having to issue payment credentials again.

Figure 5 illustrates a flow diagram of a method according to another aspect of the invention. The method is performed on a suitable modified point of sale device, such as any of those described in the description above with reference to Figures 1 to 3.

The method includes a first step 502 of obtaining payment credentials from a portable payment device presented by a consumer at the point of sale device. This can be done in a similar way to conventional payment credential access operations, such as through an ISO 7816 or ISO / IEC 14443 communication protocol or the like. The obtained payment credentials could be considered as 'card present' payment credentials in that they provide enough information for a subsequent transaction using the payment credentials to be considered a card present transaction. The payment credentials can then, for example, be track 1 data, track 2 data, track 3 data or equivalent track 2 data (such as EMV tag data 57). Additionally, payment credentials may include an account holder name and / or date of birth, a bank identification number (BIN), a primary account number (PAN), a service code, an expiration date, values Card Verification (CVV1 or CVV2), a PIN block or range, a bank account number, a branch code, an account number or loyalty identifier, credit and / or debit card number information, information account balance or consumer information such as name, date of birth.

The method includes a next step (504) of receiving an identifier entered by the consumer in the point of sale device. The identifier may be any one or more of one or more of an International Mobile Station Subscriber Directory (MSISDN) number, an email address, a social network identifier, a predefined consumer name, or a customer account number. consumer.

The method further includes a next step (506) of communicating the payment credentials and identifier to a remotely accessible server for additional communication to a secure item associated with a consumer mobile device. This stage may include formatting the payment credentials and identifier in a financial transaction message. The financial transaction message may, for example, be an ISO 8583 financial transaction message. The point of sale device may additionally be configured to insert a server routing code into the financial transaction message such that the Financial transaction is routed to the remotely accessible server via a payment processing network and not, for example, an issuing bank as indicated by the BIN originally included in the payment credentials.

If requested, the consumer can enter additional credentials at the point of sale device and they can communicate to the remotely accessible server, for example, card verification values that are not machine-readable (for example, CVV2 data).

Figure 6A illustrates a remotely accessible server for providing payment credentials, such as the one in Figures 1, 2, and 3. The remotely accessible server (140) has a payment credential receiver (602). to receive payment credentials. Payment credentials can be received from a point of sale device where payment credentials may have been obtained from a portable payment device presented by a consumer. The remotely accessible server (140) has an identifier receiver (604) to receive, from the point of sale device, an identifier entered by the consumer. In some examples, the payment credential receiver 602 and the identifier receiver 604 can be provided in a single receiver that can be configured to receive payment credentials and an identifier in a financial transaction message. In some examples, the financial transaction message may be an ISO 8583 message. The remotely accessible server 140 may include an encryption component 606 to encrypt the received payment credentials, the encrypted payment credentials having a key single decryption. The remotely accessible server (140) may have secure memory (608) incorporated therein or associated with the remotely accessible server (140) to store one of the encrypted payment credentials or the unique decryption key. In the illustrated embodiment, the secure memory (608) and the encryption component (606) are contained within a remotely accessible server hardware security module (644) (140).

The remotely accessible server 140 may include an identification component 610 to identify a mobile device and / or secure element that corresponds to the identifier. In the illustrated embodiment, the identification component (610) is part of a remotely accessible server database (642) (140) in which one or more of the group of: an identifier; decryption key; encrypted payment credentials; and communication address can be associated with a user profile.

The remotely accessible server (140) further includes a communication module (612) to communicate to the identified mobile device or the secure element associated with the mobile device. The communication module can communicate with the mobile device through any appropriate mobile data or mobile communication network. The communication module (612) can configure a secure communication channel with the secure element through the mobile device for communication of one of the encrypted payment credentials or the unique decryption key.

The remotely accessible server (140) may optionally include an authorization component (646) to send a registration or activation request to a trusted management service (TSM) that manages security keys or tokens that are used to access a safe item.

The remotely accessible server (140) may optionally include an additional credential component (648) to request or supply additional credentials to communicate to the mobile device or secure element. The additional credentials component (648) can request additional credentials from a consumer through a point of sale device, for example, human readable card verification values, which are forwarded for storage in the secure item associated with the mobile device. Alternatively or additionally, the additional credentials component (648) may supply additional credentials stored on the remotely accessible server or a related remote server, for example in the form of dynamic card verification value (dCVV) software used to generate a dCVV for individual transactions. The supplied additional credentials can be forwarded for storage on the secure item associated with the mobile device.

Figure 6B illustrates a point of sale device for providing payment credentials, such as that of Figures 1, 2 and 3.

The point of sale device (120) may include a payment credential obtaining component (652) which may be in the form of a card reader or scanner as described above. The point of sale device (120) can also include an identifier receiver (654) to receive an identifier as input by a consumer.

The point of sale device (120) can include a communication module (656) for communication with a remotely accessible server. The communication module 656 can communicate with the remotely accessible server securely using financial transaction messages.

In some examples, the point of sale device 120 may include an authorization component 658 to send a registration or activation request to a trusted management service (TSM) that manages security keys or tokens that are used to access a secure item.

In further examples, the point of sale device (120) may include an additional credential receiver (659) to receive additional credentials from a customer, for example, in the form of a printed card verification value that is not obtainable from the component for obtaining payment credentials (652).

Figure 7 shows a lane flow diagram illustrating the flow between a mobile device (112), a point of sale device (120) and a remotely accessible server (140) according to examples. The remotely accessible server 140 may be provided by a financial institution or service provider. In one example, the remotely accessible server 140 is part of a payment processing network.

A consumer may present (701) their portable payment device (eg, a payment card) at the point of sale device that can extract payment credentials from the portable payment device. The consumer may also provide (702) an identifier. For example, the consumer may present a payment card to a merchant that can be inserted into a point of sale device and a “credential transfer” transaction may be requested. The consumer can be notified for their payment card PIN which can be entered into the point of sale device through a numeric keypad. The point of sale device can also alert the consumer to an "alias" that is used as an identifier for the consumer and their mobile device.

The point of sale device can format (703) the extracted payment credentials and identifier in a transaction message, for example, an ISO 8583 message. This message is similar to a normal point of sale transaction message with the addition the provided identifier. The BIN field can be populated with a payment processing network BIN so that the message is routed to a payment processing gateway instead of a sender. The consumer's BIN remains provided in the message.

The remotely accessible server receives (704) the transaction message and extracts the payment credentials and identifier. The identifier is used to identify (705) one or more of: a consumer who has a registered mobile device and / or secure item; an account that has a registered mobile device and / or secure element; or own the mobile device and / or secure element.

The remotely accessible server can encrypt (706) the payment credentials and a specific unique decryption key can be generated for the payment credentials. One of the encrypted payment credentials and the unique decryption key can be securely communicated (707) to the secure item associated with the mobile device, while the other of the encrypted payment credentials and the unique decryption key can be stored (708 ) on the remotely accessible server.

The secure element associated with the mobile device can receive (709) either the encrypted payment credentials or the unique decryption key and can alert the user to a PIN (710), the interval of which is stored in association with the credentials or the decryption key in such a way that the payment credentials will be released only by the secure element in case the correct PIN is entered.

Figure 8 is a lane diagram illustrating the flow between a mobile device (112), a point of sale device (120) and a remotely accessible server (140) in accordance with an embodiment of the described method in which the decryption key for payment credentials is provided to the secure item associated with the mobile device.

A consumer may present (801) an identifier to a merchant as a method of payment in the conduct of a transaction. The merchant can request (802) payment credentials from the remotely accessible server by sending the identifier with the request.

The remotely accessible server can use the received identifier to identify (803) a mobile device associated with a secure element in which a decryption key is stored. The remotely accessible server can request (804) the decryption key through secure communication with the secure element, which can be through the mobile device.

The mobile device upon receipt of the request can notify (805) the consumer for a PIN before communicating (806) the decryption key to the remotely accessible server.

The remotely accessible server can retrieve (807) encrypted payment credentials from its storage and decrypt (808) payment credentials using the decryption key. The payment credentials can then be transmitted (809) and received (810) at a point of sale device or other intermediary using a secure channel to complete the transaction.

An advantage of storing encrypted payment credentials on a remotely accessible server rather than on a secure element of a mobile device, in accordance with examples of the present invention, is that if the secure element of the mobile device is put into danger by a malicious third party and that third party obtains information stored in it, the information obtained by the third party will not include payment credentials. This is in contrast to scenarios where payment credentials are stored on the secure item and where the third party may fraudulently obtain and use these payment credentials.

In addition to this, in the event that the secure item is compromised or lost, the decryption keys stored in it can simply be revoked, without having to re-issue credentials.

An additional advantage of storing encrypted payment credentials on the remotely accessible server rather than on a secure element of a mobile device is that the mobile device does not need to comply with security regulations imposed by relevant regulations or compliance authorities . For example, the secure element does not need to comply with EMV or may not have to meet PCI DSS requirements.

Similarly, since the unique decryption key is stored only in the secure element of the consumer's mobile device, the corresponding encrypted payment credentials cannot be decrypted and consequently cannot be used, without the decryption key being released from the secure item in which it is safely stored. Therefore the consumer has final control over when their payment credentials can be used. Additionally, if the remotely accessible server is compromised by a malicious third party, encrypted payment credentials stored on it will be of no use to that third party without a corresponding unique decryption key.

Figures 9A to 9D are now described illustrating an alternative embodiment of the invention in which the provisioning system is provided by a kiosk (901).

Figure 9A illustrates a kiosk (901) that can be configured in retail stores, shopping malls, airports, and other public places. For example, the kiosk (901) can be conveniently configured at a mobile device retailer or mobile network operator store to allow users to provision their recently purchased mobile device with digital wallet capabilities, in some examples, the kiosk (901). Can be screwed to the floor or to a wall with tamper-proof hardware. The kiosk (901) can also be deployed to be small, light and compact enough to be portable so that the kiosk (901) can be easily moved from location to location. For example, in some examples, the kiosk (901) can be implemented in a form factor similar to a tablet or laptop computer.

Kiosk 901 includes a display 902, a mobile device interface 910, and a credential storage instrument reader 920. The display (902) can be surrounded by a housing. The display (902) can be positioned at a suitable height (eg, on a counter) to allow a user to easily read or view information or images provided on the display (902). The display 902 can be used to provide instructions to the user during the digital wallet provisioning process. The display (902) can also be used to display advertisements, videos, and / or other images when the kiosk (901) is not in use. The display 902 can also act as a user input interface such as a touch screen to accept user input.

The mobile device interface (910) is used to establish a communication channel or link between the kiosk (901) and a mobile device. A mobile device may be a mobile phone, personal digital assistant, tablet computing device, portable media player device, or other suitable portable computing device that can store and run a digital wallet application. The mobile device interface (910) can be a physical connector as shown that can be plugged into a physical communication port of a mobile device. For example, the physical connector may be a USB connector that can be plugged into a USB port (for example, mini-USB) on a mobile device. The physical connector can also be a proprietary connector that is compatible with a proprietary communication port of some mobile device manufacturers. The physical connector can be provided as a plug, as part of a cable (for example, a retractable cable, an external cable, etc.) that can extend from the kiosk housing (901), or as part of a docking station or a platform built into the kiosk housing (901). In some embodiments, kiosk 901 can include multiple connector types such that kiosk 901 can be compatible with a number of mobile device manufacturers. In some embodiments, the mobile device interface (910) can be a wireless interface (eg, wireless transceiver) that is used to establish an ad hoc communication channel with a mobile device using NFC, RF, Bluetooth, Wi-Fi, or other wireless communication protocols during the digital portfolio provision process. The kiosk (901) can also include one or more physical connectors in combination with one or more wireless interfaces that can be used to establish a communication channel with a mobile device.

Credential storage instrument reader (920) from kiosk (901) is used to read or access a credential storage instrument (905) (also referred to herein as a portable payment device) to obtain credentials and / or other user or account information stored on the credential storage instrument (905). The credential storage instrument reader (920) can be a magnetic stripe reader or a chip card reader to read credentials from the credential storage instrument (905) through physical contact with the credential storage instrument (905). The credential storage instrument reader (920) can be an infrared scanner such as a barcode or QR code scanner to read credentials that are encoded as an image, or it can be a contactless card reader capable of communicating with the credential storage instrument (905) via NFC, RF, Bluetooth, Wi-Fi or other wireless communication protocols to read credentials from the credential storage instrument (905) wirelessly when the storage instrument credentials (905) is in close proximity to the kiosk (901). In some embodiments, kiosk 901 may include one or more types of credential storage instrument reader described above.

The credential storage instrument (905) can be in the form of a card (for example, credit / debit and other payment card, identification card, driver's license card, transit card, access card, card of insurance, retail loyalty card, gift card, etc.) or other suitable structure. The credential storage instrument (905) can include a magnetic stripe and / or a memory chip to store the user's credentials. The credential storage instrument (905) can also be a printed medium that includes an image that encodes the user's credentials such as a barcode or a QR code. In some embodiments, the credential storage instrument 905 may also be a user's existing mobile device that has the user's credentials stored therein.

Credentials can include information stored in a credential vault that can be used to transact with the credential vault. For example, credentials may be information that is used to identify and / or verify the user, or to identify or access an account associated with the credential storage instrument. Credentials can include financial information, identification information, account information, transit information (for example, as on a subway or train ticket), access information (for example, as access plates), etc. Some examples of credentials include bank account information, primary account number (PAN), bank identification number (BIN), credit or debit card number, expiration date, name, username, date of birth, number of driver's license, address, social security number, passport number, insurance policy number such as car or health insurance account number, travel or retail loyalty program account number, gift card number , transit fee account number, employee identification number or the like. Credentials may also include additional information that is used to facilitate a transaction. For example, credentials can include a card verification value (CVV) and / or a service code used to facilitate the processing of a transaction.

In some examples, credentials may also include additional information that is used to facilitate a transaction, but is not stored in the credentials storage instrument (905) or cannot be retrieved by the credentials storage instrument reader (920) from the kiosk ( 901). For example, credentials may include a Card Verification Value 2 (CVV2) that is printed on the face of a credit card, but may not be retrieved by reading the card's magnetic stripe. Credentials can also include dynamic card verification code (dCVV) software that is used to generate a dCVV for individual transactions. For such credentials that are not stored in the credential storage instrument (905) or cannot be retrieved by the credential storage instrument reader (920), the kiosk (901) can obtain such credentials from the storage instrument issuer of credentials (905) during the provisioning process such that these credentials can be uploaded to the mobile device.

Credentials can be stored on a memory chip of the credential storage instrument (905) or can be encoded as a printed image on the credential storage instrument (905). Credentials stored in the credential storage instrument (905) can also be stored in the form of magnetic data tracks such as those traditionally associated with credit cards. Such tracks may include Track 1 and Track 2. Track 1 ("International Air Transport Association") stores more information than Track 2, and contains the name of the cardholder as well as account number and other discretionary data. This track is sometimes used by airlines when they secure reservations with a credit card. Track 2 ("American Banking Association") is the most commonly used today. This is the clue to be read by ATM and credit card verifiers. The ABA (American Banking Association) designed the specifications of this track and all banks in the world abide by it. Contains the cardholder's account, encrypted PIN, plus other discretionary data.

Figure 9B illustrates a block diagram of a kiosk (901) according to various embodiments. The kiosk (901) includes one or more processors (921) coupled to a storage medium (204). The storage medium 204 stores machine-readable code that can be executed by the processor 921 to provide digital wallet mobile device capabilities. Kiosk 901 includes one or more mobile device interfaces 910 and one or more credential storage instrument readers 920. Kiosk 901 additionally includes display 925 and sound system 924 that can be used to provide a user with visual and audio instructions during the digital wallet provisioning process. When kiosk 901 is not being used to provide a mobile device, display 925 and sound system 208 can be used to present other media such as announcements or informational videos and sounds. Kiosk 901 also includes user input interface 926 for receiving user input. The user input interface (926) can be implemented with one or more of a touch screen, a numeric keypad, a keyboard, a touchpad, a mouse, a touch pad, a microphone, or other suitable user input interface components. .

In some examples, kiosk 901 may include a network interface 923 to allow kiosk 901 to communicate, if necessary, with entities that may be involved with the digital wallet provisioning process. For example, network interface 923 can be used by kiosk 901 to communicate with an issuer of the credential storage instrument (for example, a bank that issued a credit card, a transit agency that issued a card transit access, a government agency that issued an ID card, a retailer that issued a loyalty program card, etc.). Network interface 923 can also be used by kiosk 901 to communicate with a trusted service manager to acquire security keys or tokens that are used to provide digital wallet mobile device capabilities. Kiosk 901 can also communicate with a mobile network operator through network interface 923 to verify or access information associated with a mobile device. The network interface (923) can be implemented as a wireless interface such as an Ethernet port or as a wireless interface such as a wireless transceiver that can access a network wirelessly (for example, using Wi-Fi or another wireless communication protocol. ).

Figure 9C illustrates a system (930) for providing a mobile device (931) with digital wallet capabilities using the kiosk (901). The mobile device 931 may be a recently purchased mobile device or it may be an existing mobile device that a user already owns. In some embodiments, the mobile device 931 can be preloaded with a digital wallet application, and the kiosk 901 is used to upload credentials to the digital wallet application of the mobile device 931. In other embodiments, kiosk 901 can be used to upload a digital wallet application along with personalized credentials to mobile device 931 if mobile device 931 does not include a preloaded digital wallet application.

According to some examples, the kiosk (901) is communicatively coupled to a reliable service manager (TSM) (933), for example, through a network (932). TSM (933) offers services to support contactless transaction services that are performed with mobile devices. The basic functionalities that can be provided by the TSM (933) include the ability to manage security keys or tokens that are used to access the secure element (SE) chip of a mobile device (for example, a secure memory chip or a secured partition of a memory) in which credentials of a digital wallet application can be stored. The SE is used by the mobile device (931) to host and store data and applications that require a high degree of security. The SE may be provided to the mobile device 931, for example, by a payment processing network entity such as a credit card issuer, by a contactless transaction service provider, by a mobile network operator. (MNO), through a mobile device manufacturer or through other appropriate entities. Access to the SE of the mobile device (931) can be obtained by obtaining the appropriate security key or token from the SE provider.

Although the TSM (933) is shown as a separate entity, in some embodiments, the TSM (933) can integrate with the issuer system (935) to activate and customize a digital wallet application with user credentials, or integrate with the kiosk (901). Upon request, the TSM (933) can obtain the appropriate security key or token from an SE provider to lock or unlock the SE on the mobile device (931), for example, to allow the kiosk (901) to load login credentials. user in the SE of the mobile device (931).

The provision of the mobile device 931 for digital wallet capabilities can be initiated when a user interacts with the kiosk 901 by providing user input to a kiosk 901 user input interface, for example, by touching a touch screen of the kiosk (901) or by pressing a key on a kiosk keyboard (901), etc. Upon user interaction, kiosk 901 can provide visual and / or audio instructions for the user to complete the provisioning process. For example, the kiosk (901) may display a message instructing the user to communicatively connect the user's mobile device (931) to the kiosk (901).

To communicatively connect the user's mobile device (931) to the kiosk (901), a user can physically connect the mobile device (931) to the mobile device interface (eg, a connector or cable) of the kiosk (901) for a communication channel by cable, or by placing the mobile device (931) in close proximity to the mobile device interface (eg, wireless transceiver) of the kiosk (901) to allow it to be established an ad hoc wireless communication channel between the mobile device (931) and the kiosk (901). The ad hoc wireless communication channel can be established through NFC, RF, Bluetooth, Wi-Fi or other suitable wireless communication protocols. In some embodiments, when kiosk 901 detects that a mobile device 931 is in close proximity, kiosk 901 may display a message asking if the user grants permission for kiosk 901 to establish a communication channel. wireless with mobile device (931).

Once a communication channel (wired or wireless) is established between the mobile device 931 and the kiosk 901, the kiosk 901 can additionally provide visual and / or audio instructions to the user to present a display instrument. storage of credentials (905) to continue the process of providing the digital wallet. For example, the kiosk (901) may instruct the user to place credential storage instrument (905) in physical contact with the credential storage instrument reader of kiosk (901) (for example, by sliding or inserting a band card card in a magnetic stripe reader, or by inserting a chip card into a chip card reader slot), or place credential storage instrument (905) in close proximity to the kiosk credential storage instrument reader ( 901) (for example, placing a contactless card in close proximity to a contactless card reader, or placing printed media with a barcode or QR code in front of an infrared scanner). After presenting the credential storage instrument (905) to the kiosk credential storage instrument reader (901), the kiosk (901) accesses the credential storage instrument (905) to read user credentials from the credentials (905). It should be noted that although in the above process a communication channel is first established between the mobile device (931) and the kiosk (901) before a credential storage instrument is presented to the kiosk (901), in some embodiments, A credential storage instrument may be presented to the kiosk (901) before communicatively connecting the mobile device (931) to the kiosk (901). Additionally, in addition to providing user input at the kiosk user input interface (901) to initiate the process, the digital wallet provisioning process can be initiated as an alternative simply by communicatively connecting the mobile device (931) to the kiosk (901 ) or by presenting a credential storage instrument to the kiosk (901).

Once the kiosk (901) has retrieved user credentials from the credential storage instrument (905), the kiosk (901) can perform a verification process to confirm that the user is authorized to provide the mobile device (931) with credentials of the credential storage instrument (905). In some examples, the verification process can be performed by kiosk (901) without requiring any additional user input. For example, the kiosk (901) can retrieve a mobile phone number and / or a mobile device identifier from the mobile device (931) that can be used to query the mobile service subscriber name associated with the mobile device (931) from the mobile network operator (936). The kiosk (901) can also retrieve the name on the credentials storage instrument (905), or query the name associated with the credentials storage instrument (905) using credentials retrieved from the credentials storage instrument (905) by contacting the emitter system (935). If the mobile service subscriber name matches the username of the credentials storage instrument (905), it can be assumed that the user is the appropriate owner of both the mobile device (931) and the credentials storage instrument (905). , and that the user is authorized to provide the mobile device (931) with credentials from the credential storage instrument (905).

It should be noted that embodiments of the present invention provide a more secure method of provisioning the mobile device (931) compared to some provisioning processes during air communication (OTA), because the credential storage instrument (905) is in physical possession of the user during the kiosk provision process. This can prevent, for example, a fraudulent user from providing a mobile device with stolen credentials when the fraudulent user does not have physical possession of the credential storage instrument.

In some examples, for additional security, before proceeding further with the provisioning process, the kiosk (901) may request that the user enter a PIN number associated with the credential storage instrument (905) to authenticate the user. The kiosk (901) can alternatively or additionally request that the user register in an online account provided by an issuer of the credential storage instrument (905) through a web-capable browser, and / or request that the user register with an online account provided by the mobile network operator of the mobile device (931).

After the kiosk (901) determines that the user is authorized to provide the mobile device (931) with credential storage instrument (905) credentials, the kiosk (901) can send a registration or activation request to the TSM ( 933). In some examples, the registration or activation request is sent with the appropriate personalization data (for example, credentials retrieved from the credential storage instrument (905)). The TSM (933) can process the registration or activation request by customizing a digital wallet application with the appropriate personalization data, unlock the SE of the mobile device (931) and provide the personalized digital wallet application to the kiosk (901) for download to device mobile (931). In some examples, for example, where the mobile device (931) includes a preloaded digital wallet application, the TSM (933) can process the request by unlocking the SE of the mobile device (931) to allow the kiosk (901) Transfer credentials retrieved from the credential storage instrument (905) to the SE of the mobile device (931). According to some examples, some or all of the functionality performed by the TSM (9) can be integrated into the kiosk (901).

Depending on the type of credential storage instrument (905) being used, additional credentials may be required that are not stored on the credential storage instrument (905), or additional credentials that cannot be read by the credential storage instrument reader. Kiosk credentials (901) to enable mobile device (931) to perform contactless transactions. For example, if the credential storage instrument (905) is a credit card, a dynamic card verification value (dCVV) may be required to perform contactless payment transactions made by the mobile device (931). In such examples, during the digital wallet provisioning process, the kiosk (901) can send a registration or activation request to the issuer system (935) to obtain additional credentials such as dCVV software that can be used by the device. mobile (931) to generate a dCVV when you make contactless payment transactions. Additional credentials (eg, dCVV software) obtained from the issuer system (935) can be stored in the SE of the mobile device (931) along with credentials retrieved from the credential storage instrument (905) during the process of providing the digital wallet. In some examples, the credentials retrieved from the credential storage instrument (905) can also be modified or augmented by the issuer system (935) before being stored on the mobile device (931). Credentials uploaded to the mobile device SE (931) by the kiosk (901) can also use data encryption standards such as RSA with a key of at least 1024 bits, triple data encryption standard (DES) , 128-bit Advanced Encryption Standard (AES), an RC4 stream encryption algorithm that uses a minimum key length of 128 bits, etc.

Once credentials from the credential storage instrument (905) have been loaded into a digital wallet application on the mobile device (931), the kiosk (901) can provide visual and / or audio instructions asking the user if the user wants upload credentials from additional credential storage instruments to the mobile device (931). If so, the process described above can be repeated for each credential storage instrument. In some examples, credential storage instruments can be processed in a batch mode. For example, the kiosk (901) may allow a user to first slide multiple credential storage instruments before the kiosk (901) begins uploading the respective credentials to the mobile device (931). Credentials from multiple credential storage instruments can be temporarily stored at kiosk (901), and once the user has submitted the desired number of credential storage instruments to kiosk (901), kiosk (901) below begins the provisioning process uploads the credentials to the mobile device (931).

According to some examples, the kiosk (901) can also be used to transfer credentials from one digital wallet application to another. For example, when a user purchases a new mobile device, the user may already have a personalized digital wallet application on the user's old mobile device. The user may want to transfer the credentials stored on the old mobile device to the new one. Instead of presenting individual kiosk credential storage instruments (901) for reading, the user may place the user's old mobile device in close proximity to the kiosk credential storage instrument reader (901). The kiosk (901) can then access the digital wallet application stored on the old mobile device to retrieve the credentials stored therein. After retrieving the credentials from the old mobile device, the kiosk (901) can provide the new mobile device with the recovered credentials using the process described above.

In addition to or as an alternative to provisioning the mobile device (931), the kiosk (901) can also upload credentials to a cloud-based digital wallet (934). The cloud-based digital wallet (934) allows credentials to be stored in network-accessible storage that is external to the mobile device (931). Using the cloud-based digital wallet (934) has the advantage that once the credentials have been uploaded to the cloud-based digital wallet (934), the user can avoid having to transfer the credentials to a new mobile device every time the user changes mobile devices. Therefore, in some examples, a user can use the kiosk (901) to upload credentials from credential storage instruments to the cloud-based digital wallet (934) without the presence of a mobile device.

In some examples, the kiosk (901) can perform additional digital portfolio management functions. For example, once the digital wallet application has been provided and customized on the mobile device (931), the kiosk (901) may allow a user to purchase digital media for the mobile device (931) using credentials loaded into the application. of digital wallet. The kiosk (901) can also allow a user to deposit or add value to accounts associated with the credentials stored in the digital wallet application. For example, the kiosk (901) can allow the user to add value to a transit fee account stored in the digital wallet application. However, it should be noted that these additional functions are different from the digital portfolio provision process in that these additional functions require the Digital wallet application has the necessary credentials before these functions can be performed. In contrast, the provisioning process described in this document is used to provide the mobile device with credentials that the digital wallet application lacked before being provided by the kiosk (901). Kiosks according to embodiments of the invention may or may not provide the additional functions mentioned above.

Figure 9D illustrates a flow chart of a method (950) performed by a kiosk or other suitable computing devices to provide a digital wallet application with a mobile device in accordance with some embodiments. At block 951, a communication channel is established between a user's mobile device. The communication channel can be a wired connection or a wireless connection as described above. At block 952, a credential storage instrument such as a magnetic stripe card, chip card, or other credential storage instruments described above is accessed to retrieve credentials stored in the credential storage instrument. In block 953, it is determined whether the user is authorized to provide a digital wallet application for the mobile device with the retrieved credentials. This determination can be made according to any of the processes described above. If the user is determined to be unauthorized, at block 956, the process is terminated without the provision of the mobile device. If the user is determined to be authorized, then at block 954, a request is made to unlock the secure element (SE) of the mobile device. The SE can be unlocked with a security key or token provided by a TSM or by a kiosk with built-in TSM functionality. Once the SE of the mobile device is unlocked, a digital wallet application is provided for the mobile device by downloading the retrieved user credentials from the credential storage instrument on the SE. In some embodiments, the user credentials can be modified, increased (eg, with a CVV2), and / or encrypted before being stored in the SE of the mobile device. Method 950 can be repeated for multiple credential storage instruments. After the provisioning process, the mobile device SE is blocked to prevent unauthorized access.

It should be understood that the method (950) for providing a digital wallet application with a mobile device may include additional operations not shown in Figure 9D, or may include fewer operations in other examples. Additionally, some of the operations may be performed in a different order than that shown.

Figure 10 shows a lane flow diagram illustrating the flow between a mobile device (931), a kiosk (901), and a remotely accessible server such as a payment credential issuer (935) or a TSM ( 933) according to embodiments.

A consumer may present (1001) their portable payment device or credential storage instrument (eg, a payment card) at the kiosk that can extract payment credentials from the portable payment device. For example, the consumer may insert their payment card into a kiosk and a "transfer of credentials" transaction may be requested. The consumer can be notified for their payment card PIN which can be entered at the kiosk through a numeric keypad. The consumer can also provide (1002) an identifier, for example, the kiosk can also alert the consumer to an "alias" that is used as an identifier for the consumer and their mobile device.

The kiosk can connect (1003) to the consumer's mobile device as described above to establish (1004) a connection. The kiosk can use the provided consumer identifier to identify the mobile device for connection, for example, if the connection is wireless.

The kiosk may send (1005) an activation request to a remotely accessible server provided by a TSM to obtain authorization to store the payment credentials in the secure item associated with the mobile device and also to unlock the secure item. The activation request can use the identifier provided by the consumer that can be registered for the consumer's mobile device and / or secure element and the identifier can be used to identify (1006) the mobile device and its secure element. The TSM can unlock (1007/1008) the secure item associated with the mobile device.

Payment credentials can be provided (1009/1010) to the secure element of the mobile device using the kiosk connection. These can be safely provided to the secure element.

Additional credentials that are not stored on the portable payment device may also be required to be stored on the secure item to enable the mobile device to perform contactless transactions. For example, a dynamic card verification value (dCVV) may be required to perform contactless payment transactions made by the mobile device. In such embodiments, the kiosk may send a registration request (1011) to a remotely accessible server in an issuer system to obtain additional credentials. The identifier can be included in the request and used by the remotely accessible server to identify (1012) the correct additional credentials. The additional credentials can be, in one example, dCVV software that can be used by the mobile device to generate a dCVV when it performs contactless payment transactions. The registration request may include the identifier provided by the consumer to obtain the correct additional credentials for the consumer's portable payment device.

Additional credentials (eg dCVV software) obtained from the issuer system can be transmitted (1013/1014) to and stored in the secure item associated with the mobile device along with payment credentials retrieved from the kiosk during the wallet provisioning process digital. Alternatively, additional credentials can be communicated directly to the secure element of the mobile device.

Figure 11 illustrates an example of a computing device (1100) in which various aspects of the disclosure can be implemented. The computing device 1100 may be suitable for storing and executing computer program code. The various participants and elements in the system diagrams described above can use any suitable number of subsystems or components of the computing device (1100) to facilitate the functions described in this document.

The computing device (1100) may include subsystems or components interconnected through a communication infrastructure (1105) (eg, a communication bus, a crossbar device, or a network). The computing device 1100 may include at least one central processor 1110 and at least one memory component in the form of a computer readable medium.

The memory components can include system memory (1115), which can include read-only memory (ROM) and random access memory (RAM). A basic input / output system (BIOS) can be stored in ROM. System software can be stored in system memory (1115) including operating system software.

Memory components may also include secondary memory (1120). Secondary memory (1120) may include a fixed disk (1121), such as a hard disk drive, and optionally one or more removable storage interfaces (1122) for removable storage components (1123).

Removable storage interfaces (1122) can be in the form of removable storage drives (eg, magnetic tape drives, optical disc drives, floppy drives, etc.) for corresponding removable storage components (eg, a magnetic tape, an optical disc, a floppy disk, etc.), which can be written or read by the removable storage drive.

Removable storage interfaces (1122) can also be in the form of ports or connections to interact with other forms of removable storage components (1123) such as a flash memory drive, external hard drive, or removable memory chip, etc.

The computing device (1100) may include an external communication interface (1130) for operating the computing device (1100) in a network environment enabling data transfer between multiple computing devices (1100). Data transferred through the external communication interface (1130) can be in the form of signals, which can be electronic, electromagnetic, optical, radio, or other types of signal.

The external communication interface (1130) can enable data communication between the computing device (1100) and other computing devices including servers and external storage facilities. Web services can be accessible by the computing device (1100) through the communications interface (1130). The external communication interface (1130) can also enable other forms of communication to and from the computing device (1100) including voice communication, near field communication, Bluetooth, etc. The computer readable medium in the form of the various memory components can provide storage of computer executable instructions, data structures, program modules, and other data. A computer program product may be provided by a computer-readable medium that has stored computer-readable program code executable by the central processor (1110).

A computer program product may be provided by a non-transient computer readable medium, or it may be provided through a signal or other transient medium through the communication interface (1130).

Interconnection through the communication infrastructure (1105) allows a central processor (1110) to communicate with each subsystem or component and control the execution of instructions from the memory components, as well as the exchange of information between subsystems or components.

Peripherals (such as printers, scanners, cameras, or the like) and input / output (I / O) devices (such as a mouse, touchpad, keyboard, microphone, joystick, or the like) can be attached to the computing device (1100 ) either directly or through an I / O controller (1135). These components can be connected to the computing device (1100) by any number of means known in the art, such as a serial port.

One or more monitors (1145) can be attached through a display or video adapter (1140) to the computing device (1100).

Figure 12 shows a block diagram of a communication device (1200) that can be used in the embodiments of the disclosure. The communication device 1200 may be a cell phone, a basic phone, a smartphone, a satellite phone, or a computing device that has phone capability. The communication device 1200 may include a processor 1205 (eg, a microprocessor) to process the functions of the communication device 1200 and a display 1220 to allow a user to view phone numbers and other information and messages. The communication device (1200) may additionally include an input element (1225) to allow a user to enter information into the device (eg, input buttons, touch screen, etc.), a speaker (1230) to allow the User listens to voice communication, music, etc., and a microphone (1235) to allow the user to transmit their voice through the communication device (1200).

The processor (1210) of the communication device (1200) can be connected to a memory (1215). Memory 1215 may be in the form of a computer-readable medium that stores data and, optionally, computer-executable instructions. Memory (1215).

The communication device 1200 may also include a communication element 1240 for connection to communication channels (eg, a cell phone network, data transmission network, Wi-Fi network, satellite phone network, Internet network, Internet satellite network, etc.). The communication element 1240 can include an associated wireless transfer element, such as an antenna.

The communication element 1240 may include a subscriber identity module (SIM) in the form of an integrated circuit that stores an international mobile service subscriber identity and the related key used to identify and authenticate a subscriber using the device. communication (1200). One or more subscriber identity modules may be removable from the communication device (1200) or embedded in the communication device (1200).

Communication device 1200 may additionally include a contactless element 1250, which is typically implemented in the form of a semiconductor chip (or other data storage elements) with an associated wireless transfer element, such as an antenna. The contactless element (1250) can be associated with (eg, embedded within) the communication device (1200) and data or control instructions transmitted over a cellular network can be applied to the contactless element (1250) by means of a contactless element interface (not shown). The contactless element interface can operate to allow the exchange of data and / or control instructions between mobile device circuitry (and therefore the cellular network) and the contactless element (1250).

The contactless element (1250) may be capable of transferring and receiving data using a near field communication (NFC) capability (or near field communication medium) usually in accordance with a standard protocol or data transfer mechanism (eg example, ISO 14443 / NFC). Near-field communication capability is a short-range communication capability, such as radio frequency identification (RFID), Bluetooth, infrared, or other data transfer capability that can be used to exchange data between the communication device (1200) and an interrogation device. Therefore, the communication device (1200) may be capable of communicating and transferring data and / or control instructions through both a cellular network and near field communication capability.

Communication devices (1200) supporting mobile contactless payment typically support contactless transactions using the EMV contactless communication protocol (EMV-CCP), which is based on ISO 14443, to interact with merchant access devices. This capability is typically accomplished by implementing NFC. The NFC capability in the communication device (1200) could be enabled by an embedded NFC chip or by adding an external memory card or accessory containing the NFC chip. Additionally, the communication device (1200) usually includes a secure element (SE) (1260) either embedded in the handset or in the subscriber identity module (SIM) card. The SE (1260) can also be included in an addition device such as a Secure Digital Micro (SD) card, or an expansion component to add to a communication component of the communication device (1200).

The data stored in the memory (1215) can include: operation of data related to the operation of the communication device (1200), personal data (for example, name, date of birth, identification number, etc.), financial data ( for example, bank account information, a bank identification number (BIN), credit or debit card number information, account balance information, expiration date, loyalty provider account numbers, etc.), information transit (for example, as in a metro or train ticket), access information (for example, on access plates), etc. A user can transmit this data from the communication device (1200) to selected receivers.

The communication device 1200 can be, among other things, a notification device that can receive alert messages and access reports, a portable merchant device that can be used to transmit control data that identifies a discount to be applied, thus as a portable consumer device that can be used to make payments.

The foregoing description of the embodiments of the invention has been presented for the purpose of illustration; It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Those skilled in the art may appreciate that many modifications and variations are possible in light of the above disclosure.

Portions of this description describe the embodiments of the invention in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are commonly used by experts in processing techniques to effectively convey the substance of their work to other experts in the field. These operations, while being described functionally, computationally or logically, are understood to be implemented by means of computer programs or equivalent electrical circuits, microcode or the like. The operations described can be incorporated into software, firmware, hardware, or any combination thereof.

The software components or functions described in this application may be implemented as software code to be executed by one or more processors using any suitable computer language such as, for example, Java, C ++, or Perl using, for example, conventional or object-oriented techniques. . The software code can be stored as a series of instructions, or commands on a non-transient computer-readable medium, such as a random access memory (RAM), a read-only memory (ROM), a magnetic medium such as a disk hard or a floppy disk, or an optical medium such as a CD-ROM. Any such computer-readable medium may also reside on or within a single computing device, and may be present on or within different computing devices within a system or network.

Any of the steps, operations, or processes described in this document can be performed or implemented with one or more hardware or software modules, alone or in combination with other devices. In one embodiment, a software module is implemented with a computer program product comprising a non-transient computer readable medium containing computer program code, which may be executed by a computer processor to perform any or all of the steps, operations, or processes. described.

Claims (13)

1. A method of providing a digital wallet application on a mobile device (112, 212, 316, 931) with payment credentials that the digital wallet application lacked prior to provisioning, the payment credentials being usable by the device mobile (112, 212, 316, 931) in carrying out a contactless payment, the method being performed in a provisioning system (140, 240, 340, 901) and comprising the steps of: receipt (402, 422, 704) of payment credentials from a point of sale or ATM device (120, 222, 320, 920) in a financial transaction message, the payment credentials having been obtained by the point of sale or device from ATM (120, 222, 320, 920) from a portable payment device (114, 214, 314, 905) through a communication interface with or without contact of the point of sale or ATM device (120, 222, 320, 920) the portable payment device (114, 214, 314, 905) being presented by a consumer at the point of sale or ATM device (120, 222, 320, 920); reception (404, 424, 704), from the point of sale or ATM device (120, 222, 320, 920), of an identifier entered by the consumer in the financial transaction message; identification (406, 430, 705) of a mobile device (112, 212, 316, 931) or a secure element (113) in the mobile device (112, 212, 316, 931) that corresponds to the identifier; Y communication (410, 432, 707) of the payment credentials to the identified mobile device (112, 212, 316, 931) or the secure element (113) on the mobile device (112, 212, 316, 931), causing the Payment credentials are securely stored in the secure element (113) of the mobile device (112, 212, 316, 931), the secure element (113) being one of the group of: a secure element (113) provided in the device (112, 212, 316, 931), a secure element (113) embedded in a layer (318) that is located between a communication component (317) of the mobile device (112, 212, 316, 931) and an interface mobile device communication component (112, 212, 316, 931), and a secure element (113) provided in a mobile device communication component (317) (112, 212, 316, 931). 2. The method according to claim 1, which includes: request (408) authorization from a reliable service manager to access the secure element (113); and receive a security key to access the secure element (113). 3. The method as claimed in any one of the preceding claims, including: communicating (412) additional credentials to the identified mobile device (112, 212, 316, 931) or secure element (113) to be stored securely in association with the mobile device (112, 212, 316, 931), where additional credentials are required in use in addition to the payment credentials that effect a transaction. 4. The method according to claim 3, which includes: obtain additional credentials from a remotely accessible server (140, 240, 340,) using the identifier and forward the additional credentials to the mobile device (112, 212, 316, 931). 5. The method according to claim 3 or claim 4, wherein the additional credentials are in the form of a dynamic verification algorithm to generate dynamic verification values. 6. The method as claimed in any one of the preceding claims, wherein the method is repeated for multiple payment credentials to be stored securely in association with a single mobile device. The method as claimed in any one of the preceding claims, wherein the method is used to transfer payment credentials to a second mobile device from its existing secure storage on a first mobile device, wherein the payment device portable is the first mobile device. 8. A method of providing a digital wallet application on a mobile device (112, 212, 316, 931) with payment credentials that the digital wallet application lacked prior to provisioning, the payment credentials being usable by the device mobile (112, 212, 316, 931) in making a contactless payment, the method being performed at a point of sale or ATM device (120, 222, 320, 920) and comprising the steps of: obtaining (502) , by the point of sale or ATM device (120, 222, 320, 920), of payment credentials from a portable payment device (114, 214, 314, 905) through a communication interface with or without contact from the point of sale or ATM device (120, 222, 320, 920) presenting the portable payment device (114, 214, 314, 905) by a consumer at the point of sale or ATM device (120, 222, 320 , 920); reception (504), by the point of sale or ATM device (120, 222, 320, 920), of an identifier entered by the consumer at the point of sale or ATM device (120, 222, 320, 920); Y communication (506), by the point of sale or ATM device (120, 222, 320, 920), of the payment credentials and identifier in a financial transaction message to a provisioning system (140, 240, 340, 901 ) for Additional communication of the payment credentials to the mobile device (112, 212, 316, 931) or a secure element (113) of the mobile device, causing the payment credentials to be stored securely in the secure element (113), being the secure element (113) one of the group of: a secure element (113) provided in the mobile device (112, 212, 316, 931), a secure element (113) embedded in a layer (318) that lies between a communication component (317) of the mobile device (112, 212, 316, 931) and a communication component interface of the mobile device (112, 212, 316, 931), and a secure element (113) provided in a component of communication (317) of the mobile device (112, 212, 316, 931). 9. A method of providing a digital wallet application on a mobile device (112, 212, 316, 931) with payment credentials that the digital wallet application lacked prior to provision, the payment credentials being usable by the device mobile (112, 212, 316, 931) in making a contactless payment, the method being performed at a point of sale or ATM device (120, 222, 320, 920) and comprising the steps of: obtaining, by the point of sale or ATM device (120, 222, 320, 920), of payment credentials from a portable payment device (114, 214, 314, 905) through communication interface with or without contact of the point of sale or ATM device (120, 222, 320, 920) presenting (1001) the portable payment device (114, 214, 314, 905) by a consumer at the point of sale or ATM device (120, 222, 320, 920); reception, by the point of sale or ATM device (120, 222, 320, 920), of an identifier entered (1002) by the consumer at the point of sale or ATM device (120, 222, 320, 920); Y communication (1005), by the point of sale or ATM device (120, 222, 320, 920), of the identifier with an activation request to a reliable service manager (933, 935) to unlock (1008) a secure element (113) on the mobile device (112, 212, 316) identified by the identifier, communication (1009, 1010), by the point of sale or ATM device (120, 222, 320, 920) of the payment credentials to the mobile device (112, 212, 316, 931) or the unlocked secure element (113) of the mobile device, causing the payment credentials to be stored securely in the unlocked secure element (113), the secure element (113) being one of the group of: a secure element (113) provided in the mobile device (112, 212, 316, 931), a secure element (113) embedded in a layer (318) that is located between a communication component (317) of the mobile device (112, 212, 316, 931) and a communication component interface of the mobile device (112, 212, 316, 931), and a secure element (113) provided in a communication component (317) of the mobile device (112, 212, 316, 931). 10. A system (100, 200, 300) to provide a digital wallet application on a mobile device (112, 212, 316, 931) with payment credentials that the digital wallet application lacked prior to provision, the payment credentials usable by the mobile device (112, 212, 316, 931) in making a contactless payment, including a provisioning system (140, 240, 340, 901) comprising: a payment credential receiver (602) for receiving payment credentials from a point of sale or ATM device (120, 222, 320, 920) in a financial transaction message, the payment credentials having been obtained by the point of sale or ATM device (120, 222, 320, 920) from a portable payment device (114, 214, 314, 905) through a communication interface with or without contact of the point of sale or ATM device (120, 222, 320, 920) the portable payment device (114, 214, 314, 905) being presented by a consumer at the point of sale or ATM device (120, 222, 320, 920); an identifier receiver (604) for receiving, from the point of sale or ATM device (120, 222, 320, 920), an identifier entered by the consumer in the financial transaction message; an identification component (610) for identifying a mobile device (112, 212, 316, 931) or a secure element (113) in the mobile device (112, 212, 316, 931) that corresponds to the identifier; Y a communication module (612) to communicate the payment credentials to the identified mobile device (112, 212, 316, 931) or the secure element (113) in the mobile device (112, 212, 316, 931) to be stored in a way secure in the secure element (113) of the mobile device (112, 212, 316, 931), the secure element (113) being one of the group of: a secure element (113) provided in the mobile device (112, 212, 316 , 931), a secure element (113) embedded in a layer (318) that is located between a communication component (317) of the mobile device (112, 212, 316, 931) and a communication component interface of the mobile device (112, 212, 316, 931), and secure element (113) provided in a communication component (317) of the mobile device (112, 212, 316, 931). 11. The system according to claim 10, wherein the system includes: the point of sale or ATM device (120, 222, 320, 920) comprising: a component for obtaining payment credentials (652) to obtain payment credentials from the portable payment device (114, 214, 314, 905) through a communication interface with or without contact presenting the portable payment device (114 , 214, 314, 905) by the consumer at the point of sale or ATM device; an identifier receiver (654) for receiving the identifier entered by the consumer at the point of sale or ATM device; a communication module (656) to communicate the payment credentials and identifier to the provisioning system (140, 240, 340, 901) for additional communication of the payment credentials to the mobile device (112, 212, 316, 931) to be safely stored in the secure element (113) of the mobile device (112, 212, 316, 931). 12. A computer program product to provide a digital wallet application on a mobile device (112, 212, 316, 931) with payment credentials that the digital wallet application lacked prior to provision, with the payment credentials being usable by the mobile device (112, 212, 316, 931) in making a contactless payment, the computer program product comprising a computer readable medium that has stored computer readable program code to perform the steps of: receipt (402, 422, 704) of payment credentials from a point of sale or ATM device (120, 222, 320, 920) in a financial transaction message, the payment credentials having been obtained by the point of sale or device from ATM (120, 222, 320, 920) from a portable payment device (114, 214, 314, 905) through a communication interface with or without contact of the point of sale or ATM device (120, 222, 320, 920) the portable payment device (114, 214, 314, 905) being presented by a consumer at the point of sale or ATM device (120, 222, 320, 920); reception (404, 424, 704), from the point of sale or ATM device (120, 222, 320, 920) in the financial transaction message, of an identifier entered by the consumer; identification (406, 430, 705) of a mobile device (112, 212, 316, 931) or a secure element (113) in the mobile device (112, 212, 316, 931) that corresponds to the identifier; Y communicate (410, 432, 707) the payment credentials to the identified mobile device (112, 212, 316, 931) or the secure element (113) on the mobile device (112, 212, 316, 931), causing the credentials are stored securely in the secure element (113) of the mobile device (112, 212, 316, 931), the secure element (113) being one of the group of: a secure element (113) provided in the mobile device (112, 212, 316, 931), a secure element (113) embedded in a layer (318) that is located between a communication component (317) of the mobile device (112, 212, 316, 931) and an interface of communication component of the mobile device (112, 212, 316, 931), and a secure element (113) provided in a communication component (317) of the mobile device (112, 212, 316, 931). 13. A computer program product to provide a digital wallet application on a mobile device (112, 212, 316, 931) with payment credentials that the digital wallet application lacked prior to provision, the payment credentials being usable by the mobile device (112, 212, 316, 931) in making a contactless payment, the computer program product comprising a computer readable medium that has stored computer readable program code to perform the steps of: obtaining, by a point of sale or ATM device (120, 222, 320, 920), payment credentials from a portable payment device (114, 214, 314, 905) through the contact or contactless communications interface of the point of sale or ATM device (120, 222, 320, 920) presenting (1001) the portable payment device (114, 214, 314, 905) by a consumer at the point of sale or ATM device (120, 222 , 320, 920); reception, by the point of sale or ATM device (120, 222, 320, 920), of an identifier entered (1002) by the consumer at the point of sale or ATM device (120, 222, 320, 920); Y communication (1005), by the point of sale or ATM device (120, 222, 320, 920), of the identifier with an activation request to a reliable service manager (933, 935) to unlock (1008) a secure element (113) on the mobile device (112, 212, 316) identified by the identifier, communication (1009, 1010), by the point of sale or ATM device (120, 222, 320, 920) of the payment credentials to the mobile device (112, 212, 316, 931) or the unlocked secure element (113) , causing payment credentials to be securely stored in the unlocked secure element (113) of the mobile device, the secure element (113) being one of the group of: a secure element (113) provided on the mobile device (112, 212, 316, 931), a secure element (113) embedded in a layer (318) that is located between a communication component (317) of the mobile device (112, 212, 316, 931) and a communication component interface of the mobile device (112, 212, 316, 931), and a secure element (113) provided in a communication component (317) of the mobile device (112, 212, 316, 931).