One use wearable

Disclosed embodiments include methods, systems, and computer-readable media configured to, for example, provide payment tokens for conducting transactions, as well as reprovisioning tokens, on wearable devices without Bluetooth® or other network connectivity beyond NFC radio.

TECHNICAL FIELD

The present disclosure relates to systems and methods for enabling the use of assistive technologies to assist in the selection of information.

BACKGROUND

Many forms of mobile payments are available to consumers today. While traditional methods such as cash and credit cards remain popular, many consumers also use new forms of payment made available via electronic computing devices. For example, many devices contain near-field communication (“NFC”) capability, which allows a payment to be initiated when the device is placed into close proximity with an NFC reader. The payment terminal obtains payment account information through the NFC reader and then communicates with an appropriate financial network or other back-end processing system to authorize the transaction.

Payment tokens are typically used to secure data processed by mobile devices equipped with NFC technology when conducting payment transactions with contactless payment cards, contactless payment terminals, and/or other NFC equipped cell phones. But existing methods and devices for employing payment tokens typically require network connectivity beyond NFC technology in order to request and/or receive payment tokens for mobile payment transactions and to authorize the transactions. Moreover, existing systems that employ NFC technology typically use Bluetooth® or similar wireless technology that are too expensive and/or involve hardware ill-suited for wearable technology.

Thus, certain aspects of the disclosed embodiments provide methods and systems that enable the use of payment tokens to conduct transactions, as well as the reprovisioning of payment tokens, on wearable devices without Bluetooth® or other network connectivity beyond NFC radio. Other aspects are also provided as disclosed below.

SUMMARY

Disclosed embodiments include methods, systems, and computer-readable media configured to, for example, provide payment tokens for conducting transactions, as well as reprovisioning tokens, on wearable devices without Bluetooth® or other network connectivity beyond NFC radio.

In one aspect, the disclosed embodiments may include a wearable device comprising a near field communication (NFC) system for performing one or more transactions using NFC radio. The device may further include a secure element for providing an environment in which processes and data are be securely stored and executed, the secure element including a plurality of slots. The device may also include at least one storage device storing instructions for conducting a transaction, and at least one processor configured to execute the instructions to perform operations. The operations may include establishing NFC radio communication with a third-party device, and identifying an active slot associated with a token. The operations may also include providing, by the established NFC radio communication and in response to a request by the third-party device, the token stored in the active slot of the secure element.

In another aspect, the disclosed embodiments may include a system for issuing and reprovisioning tokens for wearable devices having NFC radio. The system may include a token vault configured to store one or more tables including a plurality of records associated with one or more tokens, wherein the plurality of records includes a plurality of fields for each token including at least a token value, an account number, a confidence score, secure element slot data, and user preferences. The system may include a token vault operator server configured to access the one or more tokens from the token vault provisioned to a secure element of a wearable device associated with a wearable device ID and having a display and a near field communication (NFC) controller. The system may be configured to process authorization requests, received from a merchant device configured to generate and send token authorization requests, for at least one token stored in the token vault associated with the wearable device ID, and provide data from the token vault based on the account number, confidence score, secure element slot data, and user preferences associated with the at least one token.

The disclosed embodiments also include a system comprising a database configured to store a plurality of tokens, each token of the plurality of tokens associated with a user. The system may also include at least one network communication device, a storage device comprising instructions, and at least one processor configured to execute the instructions to perform a method. The method may comprise receiving a request for account information from a third-party device, the request for account information comprising at least a token. The method may also comprise accessing the database to identify token information associated with the token, the token information comprising at least the requested account information, a confidence score associated with the token, and one or more user preferences. The method may further include determining whether the confidence score exceeds a predetermined threshold, and determining whether the one or more user preferences require an additional security measure before providing the requested account information. The method may also include providing the requested financial account information to the third-party device after determining that the confidence score exceeds a predetermined threshold and the one or more user preferences do not require an additional security measure.

Aspects of the disclosed embodiments may include tangible computer-readable media that stores software instructions that, when executed by one or more processors, are configured to and capable of performing and executing one or more of the methods, operations, or the like consistent with the disclosed embodiments. Also, aspects of the disclosed embodiments may be performed by one or more processors that are configured as special-purpose processor(s) based on software instructions that are programmed with logic and instructions that perform, when executed, one or more operations consistent with the disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to the disclosed embodiments, examples of which are illustrated in the accompanying drawings. Wherever convenient, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

FIG. 1is a block diagram of an exemplary system100for performing one or more operations, consistent with the disclosed embodiments. In one embodiment, system100may include one or more wearable devices110, one or more user devices120, one or more wearable issuer servers130, one or more financial service provider (FSP) servers140, one or more token vault operator servers150, one or more token vaults155, and/or network170. Consistent with disclosed embodiments, user115may be associated with user device120and/or wearable device110. The components and arrangement of the components included in system100may vary. Thus, system100may include other components that perform or assist in the performance of one or more processes consistent with the disclosed embodiments.

Components of system100may be computing systems configured to provide methods and systems that enable the use of tokens (e.g., a secure software mechanism that may be used to authorize operations) to conduct payment transactions, as well as reprovision of payment tokens, on wearable devices without Bluetooth® or other network connectivity beyond NFC radio, consistent with disclosed embodiments. As further described herein, components of system100may include one or more computing devices (e.g., computer(s), server(s), etc.), memory storing data and/or software instructions (e.g., database(s), memory device(s), etc.), and other known computing components. In some embodiments, the one or more computing devices may be configured to execute software instructions stored on one or more memory devices to perform one or more operations consistent with the disclosed embodiments. Components of system100may be configured to communicate with one or more other components of system100, including systems associated with wearable device110, user device120, wearable issuer server130, financial service provider (FSP) server140, token vault operator server150, or token vault155. In certain aspects, users may operate one or more components of system100to initiate and provide input for one or more operations consistent with the disclosed embodiments.

A financial service provider (not shown) may be an entity that provides, maintains, manages, or otherwise offers financial services. For example, financial service provider may be a bank, credit card issuer, or any other type of financial service entity that generates, provides, manages, and/or maintains financial service accounts for one or more cardholders. Financial service accounts may include, for example, credit card accounts, loan accounts, checking accounts, savings accounts, reward or loyalty program accounts, and/or any other type of financial service account known to those skilled in the art. Financial service provider include infrastructure and components that are configured to generate and/or provide financial service accounts such as credit card accounts, checking accounts, debit card accounts, loyalty or reward programs, lines of credit, or the like.

For example, a financial service provider may include one or more FSP servers140. In one aspect, FSP servers140may be one or more computing devices configured to perform one or more operations consistent with disclosed embodiments. In one aspect, FSP servers140may be a desktop computer, a server, or any other type of computing device. FSP servers140may include one or more processors configured to execute software instructions stored in memory. The one or more processors may be configured to execute software instructions that when executed by a processor performs known Internet-related communication and financial service-based processes.

A merchant (not shown) may be an entity that offers goods, services, and/or information, such as a retailer (e.g., Macy's®, Target®, etc.), grocery store, service provider (e.g., utility company, etc.), or any other type of entity that offers goods, services, and/or information that consumers (e.g., end-users or other business entities) may purchase, consume, use, etc. In one example, a merchant may be associated with a merchant brick and mortar location that a user (e.g., user115) may physically visit and purchase a product or service. The merchant may also include back- and/or front-end computing components that store data and execute software instructions to perform operations consistent with disclosed embodiments, such as computers that are operated by employees of the merchant (e.g., back office systems, etc.).

The merchant may include merchant device160. Merchant device160may include one or more computing systems, such as server(s), desktop computer(s), point-of-sale device(s), etc., that are configured to execute stored software instructions to perform operations associated with a merchant, including one or more processes associated with processing purchase transactions, generating transaction data, generating product data (e.g., SKU data) relating to purchase transactions, etc. Merchant device160may perform one or more operations consistent with the disclosed embodiments. The disclosed embodiments are not limited to any particular configuration of merchant device160. As one example, merchant device160may be a point-of-sale system like a cash register. Merchant device160may comprise functionality and/or hardware operable to receive wireless communications from wearable device110and/or user device120. For example, merchant device160may be configured to utilize technologies such as near field communication (NFC) radio, RFID, infrared, electric field, magnetic fields, or other technologies, in order to initiate and/or process a purchase or other transaction.

Merchant device160may also generate and send token authorization requests to systems, such as token vault operator server150and/or token vault155. For example, merchant device160may receive a token from wearable device110as part of a payment transaction for services and/or good rendered, and merchant device160may send the token (along with other information) to token vault operator server150and/or token vault155requesting financial account information associated with the token with which to complete a payment transaction. Thus, merchant device160may also generate and send transaction requests to systems, such as FSP server140. Such transaction requests may comply with ISO 8583. For example, upon receiving financial account information associated with the token, merchant device160may generate an ISO 8583 message to FSP server140indicating that an account holder would like to make a debit transaction for the purchase price of the rendered good or service.

Merchant device160may include a contactless payment terminal (not shown) comprising any known NFC device designed to communicate (directly or indirectly) with other components of system100. For example, the contactless payment terminal (CPT) may be a point of sale (POS) terminal, automated teller machine (ATM), or any other device that is configured to communicate with NFC mobile devices (e.g., wearable device110and/or user device120) to facilitate a financial transaction according to disclosed embodiments.

Wearable device110may be wearable computing devices configured to communicate with other components of systems100to perform one or more processes consistent with disclosed embodiments. For example, wearable device110may include memory devices configured to store information (e.g., one or more tokens) that may be transmitted to a merchant device (e.g., merchant devices160) for use in processing a transaction.

FIG. 2depicts an exemplary wearable device110, consistent with disclosed embodiments. In one embodiment, wearable device110may include components that may execute one or more processes to initiate a financial transaction by, for example, transmitting a token associated with a financial account to merchant device160. As shown inFIG. 2, wearable device110may include a display210, processor220, a memory230, a near field communication (NFC) controller240comprising at least a secure element250, and/or an I/O component260.

Display210may be a device component configured to convey information to a user, such as user115. For example, display210may be a screen display, one or more LED light(s), etc. In some embodiments, display210may be configured to displaying optical payment methods, such as token slots/tokens, or providing information to the user.

Processor220may include one or more known processing devices, from microcontrollers configured to process simple logic commands, such as PIC microcontrollers, MIPS microcontrollers, etc., to more powerful microprocessors including the Pentium™ or Xeon™ family manufactured by Intel™, the Turion™ family manufactured by AMD™, or any of various processors manufactured by Sun Microsystems. The disclosed embodiments are not limited to any type of processor(s) configured in wearable device110.

Memory device230may include one or more storage devices configured to store information. For example, in some embodiments, memory device230may store instructions that may be executed by a processor, such as processor220. Memory device230may store data that may reflect any type of information in any format that the system may use to perform operations consistent with the disclosed embodiments.

In some embodiments, processor220may execute one or more programs stored by memory device230. For example, processor220may execute a transaction program configured to provide a token stored in secure element250to a merchant device (e.g., a POS device) when user115operates wearable device110to complete a financial transaction.

NFC controller240may be a device with logic that is configured to execute NFC-related operations. Alternatively, NFC controller240may be software that is stored in memory device230, or a separate memory device in wearable device110. NFC controller240may operate and be configured according to architectures and designs known to one of ordinary skill in the art. In one embodiment, NFC controller240includes a secure element250providing an environment in which processes and data may be securely stored and/or executed. In other embodiments, secure element250may be separate from NFC controller240, such as a separate embedded device in wearable device110, such as a SIM/UICC card that functions as the secure element, or software located in memory230that may or may not be the same memory that hosts NFC controller240. For example, secure element250may provide delimited memory for applications operating according to disclosed embodiments. In certain embodiments, secure element250may be configured and operate as known secure elements for NFC devices. For example secure element250may store applications, slot information, credentials (e.g., tokens), and/or other information associated with secure execution of applications.

For example, as shown inFIG. 3, secure element250may comprise memory storing one or more token slots (fields251) and token values (fields252). For example, secure element may comprise five slots251A-E corresponding to five token values252A-E. According to some embodiments, each token value252A-E may correspond to a different financial account of user115held with the financial service provider associated with FSP server140. In other embodiments, one or more token values252A-E may correspond to the same financial account of user115held with the financial service provider associated with FSP server140. As discussed in more detail below, upon communicating with, e.g., merchant device160, wearable device110may identify a slot251A-D and transmit a corresponding token252A-E to merchant device160that the underlying merchant may use to obtain a financial account associated with the token in token vault115. In some embodiments, wearable device110may be preprogrammed with an active slot to use when communicating with a merchant device160. In other embodiments, wearable device110may identify a slot251dynamically based on, for example, a rotating basis, a command from another system100component (e.g., merchant device160, FSP server140, token vault operator server150, etc.).

I/O devices260may also include one or more digital and/or analog devices that allow user115to interact with wearable device110, such as a touch-sensitive area, buttons, or microphones. I/O devices260may also include one or more accelerometers to detect the orientation and inertia of wearable device110. I/O devices304may also include other components known in the art for interacting with user115, such as optical, magnetic, vibration, or other sensors capable of detecting interaction with wearable device110by user115.

In some embodiments, wearable device110may be a passive device having no internal power supply. For example, wearable device110may draw power to operate from, for example, an NFC reader associated with merchant device160. In other embodiments, wearable device110may be a semi-passive device having an internal power supply for operating circuitry of wearable device110but drawing power from, for example, an NFC reader associated with merchant device160in order to communicate. In still other embodiments, wearable device110may be an active device having an internal power supply capable of operating all aspects of wearable device110.

Wearable device110may be any device configured to be worn or carried by a user, such as a user115. For example, wearable device110may be incorporated into a wearable item such as a wristband, jewelry, eyeglasses, sunglasses, watch, piece of clothing (e.g., shirt, shoe, pants, jacket, etc.), etc., may include an attachment device (e.g., a clip) to allow it to be attached to a wearable item (e.g., belt may be incorporated into an item that is normally carried by a user or held in the user's pocket (e.g., smartphone, wallet, keys), and the like. In some embodiments, wearable device110may be a component of or incorporated into a commercially available wearable computing device, such as Google Glass®, a smartwatch, etc.

User device120may be one or more computing devices configured to perform one or more operations consistent with disclosed embodiments. User device120may be a desktop computer, a laptop, a server, a mobile device (e.g., tablet, smart phone, etc.), or any other type of computing device. For exemplary purposes, aspects of the disclosed embodiments are described with reference to user device120as a mobile client device, such as a smart phone, tablet, or the like. As mentioned herein, however, the disclosed embodiments are not limited to such examples. For example, user device120could be a laptop, a desktop, or any other device.

User device120may include one or more processors configured to execute software instructions stored in memory, such as memory included in user device120. User device120may include software that when executed by a processor performs known Internet-related communication, content display processes, and/or disclosed token vault processes for a user of user device120. For instance, user device120may execute browser or related mobile display software that generates and displays interfaces including content on a display device included in, or in communication with, user device120. User device120may be a mobile device that executes mobile device applications and/or mobile device communication software that allows user device120to communicate with components over network170, and generates and displays content in interfaces via a display device included in user device120. The disclosed embodiments are not limited to any particular configuration of user device120. For instance, user device120may be a mobile device that stores and executes mobile applications that provide token vault functions offered by token vault operator server150and/or financial service-related functions offered by FSP server140.

Wearable issuer server130may be one or more devices associated with an entity (not shown) that manufactures, sells, promotes, or otherwise provides wearable devices, such as wearable devices110. In some embodiments, wearable issuer server130may communicate with user device120, FSP server140, and/or token vault operator server150to, for example, associate one or more financial accounts of user115in token vault155with one or more tokens stored in secure element250of wearable device110.

Token vault operator server150may be one or more devices associated with an entity (not shown) that monitors and/or controls access to token vault155. For example, token vault operator server150may be operated by VISA®, MasterCard®, or any other entity controlling a payment rail capable of facilitating a transaction from FSP server140for an account of user115to a merchant associated with merchant device160. In other embodiments, may be one or more devices associated with the issuer of wearable device(s)110, a financial service provider, etc. Thus, in some embodiments, token vault operator server150may be part of wearable issuer server130, FSP server140, etc.

Token vault operator server150may execute software that provides data used for generating and displaying interfaces, including content on a display device included in, or connected to, user device120, a POS associated with merchant device160, etc. In some embodiments, token vault operator server150may provide one or more web sites, online portals, APIs, etc. that are accessible by user device120, FSP server140, wearable issuer server130, and/or merchant device160over network170. The disclosed embodiments are not limited to any particular configuration of token vault operator server150.

Token vault(s)155may include one or more memory devices that store information and are accessed and/or managed through token vault operator server150. By way of example, token vault(s)155may include Oracle™ databases, Sybase™ databases, or other relational databases or non-relational databases, such as Hadoop sequence files, HBase, or Cassandra. The databases or other files may include, for example, data and information related to generated token(s), token relationships to financial accounts of user(s)115, financial records, purchase transaction data, etc. Systems and methods of disclosed embodiments, however, are not limited to separate databases.

In one aspect, token vault operator server150may include token vault(s)155. Alternatively, token vault(s)155may be located remotely from the token vault operator server150. Token vault(s)155may include computing components (e.g., database management system, database server, etc.) configured to receive and process requests for data stored in memory devices of token vault(s)155and to provide data from token vault(s)155.

FIG. 4is a diagram of exemplary information stored in token vault(s)155, consistent with disclosed embodiments. In one aspect, token vault(s)155stores one or more tables that contain records402,404,406, and408. Each of records402,404,406, and408contain one or more fields401(e.g.,401A,401B,401C,401D, and401E). The fields, records, and values therein inFIG. 4are exemplary and are provided to illustrate embodiments of the disclosure.

For example, each record may contain field401A, entitled for exemplary purposes as “Token Value.” Field401A may contain a unique token value. Token values may be generated, for example, by wearable issuer server130, token vault operator sever150, or other components of system100. For example, wearable issuer server130may generate one or more token values and store the token value(s) in the secure element250when constructing wearable device110. Wearable issuer server130may transmit the generated token(s) to token vault155(via, e.g., token vault operator sever150), which may be inserted into token vault(s)155as an entry under field401A.

Each record may also contain field401B, entitled for exemplary purposes as “Account Number.” Field401B may contain an account number associated with a financial account of a user (e.g., user115) issued by a financial service provider (e.g., associated with FSP server140). For example, consistent with disclosed embodiments, user115may purchase a wearable device110from an issuer of wearable devices and operate user device120to link with a financial account(s) of user115with one or more token(s) stored in secure element250of the wearable device110. In response, token vault155may associate the identified token (which are stored under field401A) with the financial account of user115by inserting the financial account number in a corresponding field401B.

Each record may also contain field401C, entitled for exemplary purposes as “Confidence Score.” Field401C may contain a representation of the estimated likelihood that one or more of the wearable device, secure element, token, or financial account associated with a given row402-408has become compromised. For example, if user115reports wearable device110and/or secure element250stolen, token vault155may insert a confidence score in field401C that results in the denial of requests for financial account numbers401B using token values401A associated with the stolen wearable device110and/or secure element250. In other embodiments, transactions associated with account numbers401B may be monitored for fraudulent activity by one or more components of system100, and token vault155may update the confidence score indicated in field401C based on monitored activities. Thus, in some embodiments, token vault155may deny requests for financial account numbers401B using token values401A associated with confidence scores that have fallen below a threshold.

Each record may also contain field401D, entitled for exemplary purposes as “Secure Element Slot Data.” Field401D may contain data associated with the slot(s) of a secure element250. For example, field401D may indicate the slot of secure element250in which tokens indicated in field401A are stored in secure element250(e.g., one or more of slots251A-D ofFIG. 3). In some embodiments, only one slot251of secure element250may be active at a time (e.g., token vault155will only provide an account number associated with secure element155when the requesting party—e.g., merchant device160—requests the account using the token stored in an active slot). Thus, field401D may store data indicating, among other things, the number of slots available on a given secure element250, as well as the active slot. In some embodiments, the active slot may rotate through available slots such that the active slot of a secure element250is predictable to both token vault155and secure element250, but not unauthorized parties. In other embodiments, token vault155may indicate to secure element250(via, e.g., an NFC device at merchant device160) which slot is active before providing a token to merchant device160as part of a purchase transaction with user115.

Each record may also contain field401E, entitled for exemplary purposes as “User Preferences.” Field401E may contain account token vault preferences of a user (e.g., user115). For example, consistent with disclosed embodiments, user preferences may indicate which account from among a polarity of accounts to use based on set of predefined circumstances. For example, multiple financial accounts may be associated with a token, and user preferences401E may instruct token vault operator server150to return a first financial account for purchases made for a first merchant, a second financial account for transactions exceeding a predetermine amount, etc. Moreover, the user preferences may indicate that token vault operator server150should return the account number associated with the financial account that would provide a purchase discount, maximize rewards associated with a loyalty program, etc. In other embodiments, when each financial account is associated with a separate token, token vault operator server150may request the token value associated with the preferred account according to user preferences when presented with a request for a financial account number. User preferences401F may further indicate that token vault operator server150should prompt merchant device160(e.g., a POS terminal) to request a PIN, biometrics, etc. for transactions would lower confidence score401C (e.g., due to a higher risk associated with an new merchant, uncharacteristically high transaction amount, etc.). Token vault155may associate the identified token (which are stored under field301A) with the user preferences by inserting the user preferences in a corresponding field401E.

One of ordinary skill will understand that token vault155may contain other fields and/or additional types of data. For example, token vault155may contain information such as security codes (e.g., CVV, CVV2) associated with account numbers401B, may contain expiration dates associated with account numbers401B, may contain names on payment cards associated with account numbers401B, etc. Moreover, whileFIG. 1depicts a single token vault155, one of ordinary skill will understand that a plurality of token vaults155may be employed operated by the same and/or different components of system100may be possible.

Network170may be any type of network configured to provide communications between components of system100. For example, network170may be any type of network (including infrastructure) that provides communications, exchanges information, and/or facilitates the exchange of information, such as the Internet, a Local Area Network, wireless network (e.g., a Wi-Fi/802.11 network), NFC, magnetic fields, Optical code scanner, infrared, or other suitable connection(s) that enables the sending and receiving of information between the components of system100. In other embodiments, one or more components of system100may communicate directly through a dedicated communication link(s) (shown and not shown).

It is to be understood that the configuration and boundaries of the functional building blocks of system100have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. For example, wearable device110, user device120, wearable issuer server130, FSP server140, token vault operator server150, or token vault155may constitute a part of components of system100other than those specifically described, or may constitute a part of multiple components of system100(i.e., a distributed system). Moreover, token vault operator server155and token vault155may be separate and distinct from other components of system100(as shown), or token vault operator server155and token vault155may be may be part another component of system100, such as FSP server140.

FIG. 5is a diagram of another exemplary system500, consistent with disclosed embodiments. Variations of exemplary system500may be used by user device120, wearable issuer server130, FSP server140, token vault operator server150, and/or token vault155. In one embodiment, system500may comprise one or more processors521, one or more input/output (I/O) devices522, and one or more memories523. In some embodiments, system500may take the form of a server, general purpose computer, mainframe computer, or any combination of these components. In some embodiments, system500may take the form of a mobile computing device such as a smartphone, tablet, laptop computer, or any combination of these components. Alternatively, system500may be configured as a particular apparatus, embedded system, dedicated circuit, or the like based on the storage, execution, and/or implementation of the software instructions that perform one or more operations consistent with the disclosed embodiments.

Processor521may include one or more known processing devices, such as mobile device microprocessors or any various other processors. The disclosed embodiments are not limited to any type of processor(s) configured in system200.

Memory523may include one or more storage devices configured to store instructions used by processor521to perform functions related to disclosed embodiments. For example, memory523may be configured with one or more software instructions, such as program(s)224that may perform one or more operations when executed by processor521. The disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks. For example, memory523may include a single program224that performs the functions of the user device120, or program224may comprise multiple programs. Memory523may also store data225that is used by one or more programs. In certain embodiments, memory523may store software that may be executed by processor(s)221to perform one or more processes consistent with disclosed embodiments.

I/O devices522may be one or more devices configured to allow data to be received and/or transmitted by system200. I/O devices522may include one or more digital and/or analog devices that allow system200to communicate with other machines and devices, such as other components of system100. I/O devices522may also include one or more digital and/or analog devices that allow a user to interact with system200such as a touch-sensitive area, keyboard, buttons, or microphones. I/O devices522may also include other components known in the art for interacting with a user.

The components of system500may be implemented in hardware, software, or a combination of both hardware and software, as will be apparent to those skilled in the art. For example, although one or more components of system500may be implemented as computer processing instructions, all or a portion of the functionality of system500may be implemented instead in dedicated electronics hardware.

System500may also be communicatively connected to one or more database(s)527. System500may be communicatively connected to database(s)527through network170. Database527may include one or more memory devices that store information and are accessed and/or managed through system500. By way of example, database(s)527may include Oracle™ databases, Sybase™ databases, or other relational databases or non-relational databases, such as Hadoop sequence files, HBase, or Cassandra. The databases or other files may include, for example, data and information related to the financial records, purchase transaction data, etc. Systems and methods of disclosed embodiments, however, are not limited to separate databases. In one aspect, system500may include database527. Alternatively, database527may be located remotely from the system500. Database527may include computing components (e.g., database management system, database server, etc.) configured to receive and process requests for data stored in memory devices of database(s)527and to provide data from database527.

FIG. 6is a flow chart of an exemplary wearable device issuer process600, consistent with disclosed embodiments.

In step602, wearable device110may be constructed. For example, a manufacturer may produce a wristband, jewelry, watch, money clip, wallet, key, keyfob or some other type of item that includes the components of wearable device110and may be worn or carried by user115. In step604, the wearable device110(or, more particularly, secure element250of wearable device110) may be associated with a wearable device ID. For example, wearable issuer server130may generate a wearable device ID and associate it with the constructed wearable device110. One or more tokens may also become generated (step606) and stored on secure element250(step608). In some embodiments, wearable issuer server130may generate the one or more tokens. One of ordinary skill in the art, however, would understand that systems associated with other entities of system100, such as token vault operator server150or FSP server140, may generate the tokens that become stored in secure element250. At step610, wearable issuer server130may associate the wearable device ID with the generated one or more tokens. Wearable issuer server130may further transmit the wearable device ID, generated one or more tokens, and association information to token vault155(via, e.g., token vault operator server150). In some embodiments, wearable issuer server130may transmit the wearable device ID, generated one or more e tokens, and association information in response to a request by token vault155upon a user115initiating a wearable device configuration process700, as discussed below in more detail.

FIG. 7is a flow chart of an exemplary wearable device configuration process700, consistent with disclosed embodiments. For ease of discussion, process700may be discussed from the perspective of wearable issuer server130. It should be understood, however, that other components of system100—such as token vault operator server150—may execute one or more steps of process700.

At step702, wearable issuer server130may provide one or more interface(s) to user device120. For example, user115may purchase wearable device110and operate user device120to access a web site, online portal, API, etc., provided by wearable issuer server130in order to activate wearable device110for use in financial transactions. At step704, wearable issuer server130may receive a wearable device ID from user device120via the provided interface(s). Based on the received wearable device ID, wearable issuer server130may identify one or more tokens stored on secure element250of the wearable device110associated with the received wearable ID (step706). Wearable issuer server130may also receive user personal information personal information from the user device120via the provided interface (step708). For example, wearable issuer server130may receive personal information including, but not limited to, user115's name, address, social security number, phone numbers, financial account numbers, access credentials to one or more financial accounts, and the like. For example, user115may operate user device120to provide wearable issuer server130with an indication as to which financial accounts user115would like to associate with the one or more tokens identified in step706. In some embodiments, at step710, wearable issuer server130may interact with one or more other components of system100—such as FSP server140—to authenticate user115or otherwise confirm the identify and provided personal information provided by user115operating user device120. At step712, wearable issuer server130may transmit the received financial account information to token vault155for association with the provided wearable device ID and associated tokens (e.g., the tokens associated with the wearable device ID at step610/612).

FIG. 8is a flow chart of an exemplary user purchase process800, consistent with disclosed embodiments. For ease of discussion, process800may be discussed from the perspective of token vault operator server150and token vault155. It should be understood, however, that other components of system100—such as FSP server140—may execute one or more steps of process800.

At step802, token vault operator server150may receive a request for financial account information associated with a token. For example, user115may present wearable device110during checkout at a merchant associated with merchant device160. Wearable device110may pass a token stored on secure element250to merchant device160via NFC controller240, and merchant device160may, in turn, request the account number associated with the passed token in order to complete a financial transaction. At step804, token vault operator server150may access token vault155to identify one or more fields (e.g.,401B-401E) associated with the received token. Token vault operator server150may further identify a confidence level associated with the token (e.g., field401C) (step806) and determine whether the confidence level exceeds a threshold (step808). If the confidence level associated with the token meets or exceeds the threshold (step808; YES), token vault operator server150may provide merchant device160with the requested financial account information (step810). If the confidence lever associated with the token falls below the threshold (step808; NO), token vault operator server150may deny the request for financial account information made by merchant device160(step810). In some embodiments, token vault operator server150may require additional authentication data (e.g., PIN, biometric data, etc.) before providing the requested financial account information (step not shown). In some embodiments, token vault operator server150may provide reprovisioning data for reprovisioning secure element250with new token information according to method discussed with respect toFIG. 9below. After providing reprovisioning data, token vault operator server150may update token vault155to associate a new token with the identified one or more fields (e.g.,401B-401E) previously associated with the received token.

FIG. 9is a flow chart of an exemplary secure element reprovisioning process900, consistent with disclosed embodiments. For ease of discussion, process900may be discussed from the perspective of token vault operator server150and token vault155. It should be understood, however, that other components of system100—such as FSP server140—may execute one or more steps of process900.

At step904, token vault operator server150may identify a secure element250for reprovisioning. Reprovisioning may refer to, for example, replacing or token on secure element250or setting another slot of secure element as the active slot for use in transactions.

In some embodiments, token vault operator server150may identify an element250for reprovisioning when a confidence score401C falls below acceptable limits. In some embodiments, confidence score401C of a secure element250may fall below acceptable limits after token vault operator server150receives an indication from another component of system100(shown or not shown) that token401A has become compromised (e.g., stolen, associated with potentially fraudulent activity, etc.). Additionally or alternatively, token vault operator server150may reprovision secure elements250on a regular timetable. In such embodiments, token vault operator server150may identify an element250for reprovisioning after determining that the period of time since the last time the secure element250was reprovisioned exceeds a certain limit.

At step906, token vault operator server150may determine whether secure element250includes a plurality of slots, and that at least one slot from the plurality of slots is available (e.g., includes a token not associated with a financial account). For example, token vault operator server150may access Secure Element Slot Data associated with the token in field401D of token vault155. If another slot is available on secure element250(step906; YES), token vault operator server150may update token vault155(step908) to associate the token of the available slot with the account number401B, user preferences401F, etc.

Additionally or alternatively, secure element250may include a plurality of slots each having a token associated with the same financial account, and secure element250and token vault operator server150may automatically increment through the plurality of slot after every use of the wearable device110to make a purchase transaction. In such embodiments, no communication need take place between secure element250and token vault operator server150to reprovision the secure element250.

At step910, token vault operator server150may provide an indication of the active slot for updating the secure element250. For example, token vault operator server150may cause merchant device160(e.g., POS terminal) and/or user device120to display an indication of the new active slot. Wearable device110and/or secure element250may be manipulated to switch the active slot on the secure element250. For example, wearable device110and/or secure element250may include a binary addressing switch panel, multipole toggle switches, and/or other type of physical mechanism for manipulating the active slot of secure element250. In other embodiments, wearable device110may include a vibration sensor capable of recognizing physical gestures of user115(e.g., tapping on the wearable device110). In still other embodiments, wearable device110may be configured to receive a magnetic trigger for switching the polarity of components indicating the active slot of wearable device110.

Regardless of the means for altering the active slot of secure element250, wearable device110may include a display for conveying the current active slot setting of secure element150. For example, where a secure element comprises four slots, the second of which is the active slot, wearable device110may cause two LED lights of a display to light up.

If another slot is not available on secure element250(step906; NO), token vault operator server150may determine whether wearable device912may receive a new token (step912). If so (step912; YES), token vault operator server150may provide a new token to wearable device110for storage on secure element250. For example, token vault operator server150may determine that wearable device110may receive NFC radio communications from merchant device160. Upon such a determination, token vault operator server150may transmit the new token to merchant device160via, e.g., network170, and merchant device160may transmit the new token to wearable device110via NFC radio for storage on secure element250.

If token vault operator server150determines that wearable device912may receive not a new token (step912; NO), token vault operator server150may issue a new secure element for wearable device110. For example, token vault operator server150may determine that wearable device110includes a removable secure element250. Upon such a determination, token vault operator server150may cause a new secure element250storing the new token to become provided to user115for installation in wearable device110.

At step920, token vault operator server150may update token vault155to reflect the new token slot and/or token value associated with wearable device110.

The foregoing description has been presented for purposes of illustration. It is not exhaustive and is not limited to the precise forms or embodiments disclosed. Modifications and adaptations of the embodiments will be apparent from consideration of the specification and practice of the disclosed embodiments. For example, the described implementations include hardware and software, but systems and methods consistent with the present disclosure can be implemented as hardware alone. Furthermore, although aspects of the disclosed embodiments are described as being associated with data stored in memory and other tangible computer-readable storage mediums, one skilled in the art will appreciate that these aspects can also be stored on and executed from many types of tangible computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or CD-ROM, or other forms of RAM or ROM.

Computer programs based on the written description and methods of this specification are within the skill of a software developer. The various programs or program modules can be created using a variety of programming techniques. For example, program sections or program modules can be designed in or by means of Java, C, C++, assembly language, or any such programming languages. One or more of such software sections or modules can be integrated into a computer system, computer-readable media, or existing communications software.