Methods and systems for providing payment credentials
US-2015363781-A1 · Dec 17, 2015 · US
US12400223B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12400223-B2 |
| Application number | US-202217676041-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 18, 2022 |
| Priority date | Jul 24, 2013 |
| Publication date | Aug 26, 2025 |
| Grant date | Aug 26, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for interoperable network token processing are provided. A network token system provides a platform that can be leveraged by external entities (e.g., third party wallets, e-commerce merchants, payment enablers/payment service providers, etc.) or internal payment processing network systems that have the need to use the tokens to facilitate payment transactions. A token registry vault can provide interfaces for various token requestors (e.g., mobile device, issuers, merchants, mobile wallet providers, etc.), merchants, acquirers, issuers, and payment processing network systems to request generation, use and management of tokens. The network token system further provides services such as card registration, token generation, token issuance, token authentication and activation, token exchange, and token life-cycle management.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: receiving, by a token processing server computer, a token request comprising a real account identifier from a token requestor computer, the token request requesting a token to be issued as substitute for the real account identifier; performing, by the token processing server computer, an authentication method among a plurality of authentication methods on one or more of the real account identifier, the token or a holder of the real account identifier; determining, by the token processing server computer, a token assurance level based on the authentication method, wherein the token assurance level indicates a level of confidence that the token was requested by a genuine account holder of the real account identifier; identifying, by the token processing server computer, a token requestor communication interface provided by the token processing server computer; transmitting, by the token processing server computer via the token requestor communication interface, the token representing the real account identifier to the token requestor computer, wherein the token requestor computer is authorized to obtain the token through the token requestor communication interface; receiving, by the token processing server computer from a merchant computer, an authorization request message comprising the token for a transaction; determining, by the token processing server computer, the real account identifier associated with the token; generating, by the token processing server computer, a modified authorization request message comprising the real account identifier and the token assurance level associated with the token; identifying, by the token processing server computer, an issuer communication interface provided by the token processing server computer, wherein the issuer communication interface executes on an issuer computer; transmitting, by the token processing server computer via the issuer communication interface, the modified authorization request message to the issuer computer for approval, wherein the issuer computer is authorized to receive the token assurance level associated with the token through the issuer communication interface, wherein the issuer computer authorizes the modified authorization request message at least based on the token assurance level received via the issuer communication interface; receiving, by the token processing server computer from the issuer computer, an authorization response message comprising the real account identifier; generating, by the token processing server computer, a modified authorization response message including the token and the token assurance level; and transmitting, by the token processing server computer, the modified authorization response message to the merchant computer. 2. The method of claim 1 , wherein the issuer computer generates an authorization response message comprising the real account identifier, and transmits the authorization response message comprising the real account identifier to the token processing server computer. 3. The method of claim 1 , further comprising: before receiving the authorization request message, receiving, by the token processing server computer, the token from the issuer computer, wherein the token assurance level is generated by the issuer computer along with the token. 4. The method of claim 1 , further comprising: upon receiving the authorization request message comprising the token: validating, by the token processing server computer, the token if the token assurance level is below a predetermined threshold; and bypassing validation of the token if the token assurance level is above a predetermined threshold. 5. The method of claim 1 , further comprising: before receiving the authorization request message, generating, by the token processing server computer, the token along with the token assurance level. 6. The method of claim 1 , wherein the token request further comprises an expiration date for the real account identifier, and the method further comprises sending, by the token processing server computer, an expiration date for the token to the token requestor computer. 7. The method of claim 1 , wherein the token request comprises a CVV2 value associated with the real account identifier, and wherein the authentication method comprises a CVV2 check. 8. The method of claim 1 , wherein the token requestor computer is a mobile phone. 9. The method of claim 1 , further comprising: performing, by the token processing server computer, a clearing process using the token and the token assurance level. 10. The method of claim 1 , further comprising: determining, by the token processing server computer, that one or more successful transactions have been performed using the token; and updating the token assurance level to a higher token assurance level based on the one or more successful transactions. 11. A token processor server computer comprising a processor and a non-transitory computer readable medium storing instructions that, when executed by the processor, cause the processor to perform the steps of: receiving a token request comprising a real account identifier from a token requestor computer, the token request requesting a token to be issued as substitute for the real account identifier; performing an authentication method among a plurality of authentication methods on one or more of the real account identifier, the token or a holder of the real account identifier; determining a token assurance level based on the authentication method, wherein the token assurance level indicates a level of confidence that the token was requested by a genuine account holder of the real account identifier; identifying a token requestor communication interface provided by the token processing server computer; transmitting, via the token requestor communication interface, the token representing the real account identifier to the token requestor computer, wherein the token requestor computer is authorized to obtain the token through the token requestor communication interface; receiving, from a merchant computer, an authorization request message comprising the token for a transaction; determining the real account identifier associated with the token; generating a modified authorization request message comprising the real account identifier and the token assurance level associated with the token; identifying an issuer communication interface provided by the token processing server computer, wherein the issuer communication interface executes on an issuer computer; transmitting, via the issuer communication interface, the modified authorization request message to an issuer computer for approval, wherein the issuer computer is authorized to receive the token assurance level associated with the token through the issuer communication interface, wherein the issuer computer authorizes the modified authorization request message at least based on the token assurance level received via the issuer communication interface; receiving, from the issuer computer, an authorization response message comprising the real account identifier; generating a modified authorization response message including the token and the token assurance level; and transmitting the modified authorization response message to the merchant computer. 12. The token processing server computer of claim 11 , wherein the instructions, when executed by the processor, further cause the processor to perform the step of: before receiving the authorization request message, receiving the token from the issuer computer. 13. The token processing server compu
involving fraud or risk level assessment in transaction processing · CPC title
Financial cryptography, e.g. electronic payment or e-cash · CPC title
Anonymization, e.g. involving pseudonyms · CPC title
including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials} · CPC title
Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.