# US 10,482,455 B2 · Pre-provisioned wearable token devices > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,482,455 B2 - Document ID: US10482455B2 - Status: Granted - Kind: B2 - Application number: 15/142,994 - Filed: 2016-04-29 - Published: 2016-11-03 - Granted: 2019-11-19 - Earliest claimed: 2015-05-01 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Lawrence Douglas - Web page: https://patentgrep.com/patent/US10482455B2 ## CPC - G06Q 20/3672: {initialising or reloading thereof} - G06Q 20/227: {characterised in that multiple accounts are available, e.g. to the payer} - G06Q 20/321: {using wearable devices} - G06Q 20/3227: {using secure elements embedded in M-devices} - G06Q 20/3278: {RFID or NFC payments by means of M-devices} - G06Q 20/385: {using an alias or single-use codes} - G06Q 20/405: {Establishing or using transaction specific rules} - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract Disclosed embodiments include methods, systems, and computer-readable media configured to, for example, enable parties conducting transactions to identify a financial institution and payment network for a financial account associated with a pre-provisioned payment token using existing payment protocols. The method may include receiving from a third-party device a request for funding account information that identifies a token that does not identify a financial service provider or a payment network. The method may further include accessing a database to retrieve token information associated with the token, the token information include a link account number that indicates a funding account, a financial service provider associated with the funding account, and a payment network, and user preferences associated with the token. The method may further include providing the link account number to the third-party device in response to the request for funding account information according to the one or more user preferences. ## Claims ### Claim 1 A system, comprising: a database configured to store a plurality of pre-provisioned, wearable device tokens; at least one network communication device; a storage device comprising instructions; and at least one processor configured to execute the instructions to perform operations, comprising: receiving a request for funding account information from a third-party device, the request for funding account information identifying one of the pre-provisioned tokens without identifying a financial service provider or a payment network; accessing the database to retrieve token information associated with the pre-provisioned token identified in the request, the token information comprising at least (i) a plurality of link account numbers that each indicate a corresponding funding account, a corresponding financial service provider associated with the funding account, and a corresponding payment network, and (ii) one or more user preferences associated with the pre-provisioned token indicating which link account number from among the plurality of link account numbers to select based on the requesting third party or a transaction amount; selecting one of the link account numbers based on at least one of the user preferences; and providing the selected link account number to the third-party device in response to the request for funding account information. ### Claim 2 (depends on 1) The system of claim 1, wherein the third-party device comprises a merchant device. ### Claim 3 (depends on 1) The system of claim 1, wherein the user preferences indicate when additional information is required at the third-party device based on a set of predefined settings. ### Claim 4 (depends on 1) The system of claim 1, wherein the identified pre-provisioned token comprises one of the pre-provisioned tokens that is received by the third-party device from a wearable device. ### Claim 5 (depends on 4) The system of claim 4, wherein the identified pre-provisioned token is received by the third-party device via near field communication. ### Claim 6 A method, comprising: receiving a request for funding account information from a third-party device, the request for funding account information identifying a pre-provisioned token stored in a database, the request not identifying a financial service provider or a payment network; accessing the database to retrieve token information associated with the pre-provisioned token identified in the request, the token information comprising at least (i) a plurality of link account numbers that each indicate a corresponding funding account, a corresponding financial service provider associated with the funding account, and a corresponding payment network, and (ii) one or more user preferences associated with the pre-provisioned token that indicate which link account number from among the plurality of link account numbers to select based on the requesting third party or a transaction amount; selecting one of the link account numbers based on at least one of the user preferences; and providing the selected link account number to the third-party device in response to the request for funding account information. ### Claim 7 (depends on 6) The method of claim 6, wherein the third-party device comprises a merchant device. ### Claim 8 (depends on 6) The method of claim 6, wherein the user preferences indicate when additional information is required at the third-party device based on a set of predefined settings. ### Claim 9 (depends on 6) The method of claim 6, wherein the identified pre-provisioned token comprises one of the pre-provisioned tokens that is received by the third-party device from a wearable device. ### Claim 10 (depends on 9) The method of claim 9, wherein the identified pre-provisioned token is received by the third-party device via near field communication. ### Claim 11 A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising: receiving a request for funding account information from a third-party device, the request for funding account information identifying a pre-provisioned token stored in a database, the request not identifying a financial service provider or a payment network; accessing the database to retrieve token information associated with the pre-provisioned token identified in the request, the token information comprising at least (i) a plurality of link account numbers that each indicate a corresponding funding account, a corresponding financial service provider associated with the funding account, and a corresponding payment network, and (ii) one or more user preferences associated with the pre-provisioned token that indicate which link account number from among the plurality of link account numbers to select based on the requesting third party or a transaction amount; selecting one of the link account numbers based on at least one of the user preferences; and providing the selected link account number to the third-party device in response to the request for funding account information. ### Claim 12 (depends on 11) The non-transitory computer readable medium of claim 11, wherein the third-party device comprises a merchant device. ### Claim 13 (depends on 11) The non-transitory computer readable medium of claim 11, wherein the user preferences indicate when additional information is required at the third-party device based on a set of predefined settings. ### Claim 14 (depends on 11) The non-transitory computer readable medium of claim 11, wherein the identified pre-provisioned token comprises one of the pre-provisioned tokens that is received by the third-party device from a wearable device.