Pre-provisioned Payment Token Identification via Database Lookup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for mobile payments using pre-provisioned payment tokens lack the ability to identify the account provider and payment network, as this information is typically unknown until a user registers the device, limiting their functionality in transactions.
Innovation Solution
A system comprising a database and network communication devices that retrieve and provide token information, including a link account number identifying the financial service provider and payment network associated with a pre-provisioned payment token, enabling identification during transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If pre-provisioned payment tokens are used on third-party devices, then the device can conduct payment transactions without requiring network connectivity for provisioning, but the token does not identify the account provider or payment network
Solution Approach 1:
The system segments the token information into two parts: the payment token itself (stored on the third-party device) and the account provider/payment network identification information (stored separately in a database). This allows the token to function independently while the identification information is retrieved on-demand during transactions.
Solution Approach 2:
The system introduces an intermediary database that stores the mapping between payment tokens and their associated account provider/payment network information. This intermediary enables third-party devices to use pre-provisioned tokens while still providing the necessary identification information to payment terminals through the database lookup process.
2Reliability
If payment tokens are provisioned without network connectivity, then third-party devices can store and use tokens independently, but the tokens lack associated financial institution and payment network information
Solution Approach 1:
The system performs preliminary actions by pre-provisioning payment tokens on third-party devices during manufacturing or setup, without requiring network connectivity or user registration. The tokens are ready for immediate use, and the associated identification information is pre-stored in the database for retrieval during transactions.
Solution Approach 2:
The system creates a copy of the token information architecture where the payment token is stored on the third-party device while a corresponding record containing the account provider and payment network identification is maintained in the database, enabling the token to function with full identification capability without being physically present on the device.
3Loss of information
If traditional payment token methods require network connectivity for provisioning, then the token can be associated with account information, but devices without data reception capability cannot receive provisioning data
Solution Approach 1:
The system extracts the provisioning requirement from the device by separating the token storage function (on the device) from the information retrieval function (via database lookup during transaction). This extraction allows devices without data reception capability to use pre-provisioned tokens while the identification information is obtained through the intermediary database system.
Data Source
AI summary
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.


