SYSTEMS AND METHODS FOR COMMUNICATING RISK USING TOKEN ASSURANCE DATA

• US 20150032625A1
• Filed: 07/24/2014
• Published: 01/29/2015
• Est. Priority Date: 07/24/2013
• Status: Abandoned Application

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Glenn Powell, John F. Sheets, Matthew Dill, Prasanna Laxminarayanan
• Inventors: DILL, Matthew, LAXMINARAYANAN, Prasanna, POWELL, Glenn, SHEETS, John F.
• Application Number:
  US14/340,344
• Publication Number:
  US 20150032625A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/40 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 Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: H04L 2209/42 Anonymization, e.g. involving pseudonyms
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 9/32 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

Abstract

Systems and methods for communicating risk using token assurance data 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. An authorization request message can include a token assurance level code that is indicative of a token assurance level associated with a generated token. External or internal entities may use the token assurance level to evaluate risk associated with a payment transaction that uses the token.

Claims

1. A method, comprising:

receiving, by a server computer, an authorization request message comprising a payment token, wherein the payment token is associated with a real account identifier;

determining, by the server computer, the real account identifier associated with the payment token;

generating, by the server computer, a modified authorization request message comprising the real account identifier, wherein the modified authorization request comprises a token assurance level code indicative of a level of confidence associated with the payment token; and

transmitting, by the server computer, the modified authorization request message to an issuer for approval.

2. The method of claim 1, wherein the issuer approval is based at least in part on the token assurance level code.

3. The method of claim 1, wherein the level of confidence associated with the payment token comprises a level of confidence that the payment token was requested by an account holder of an underlying payment account associated with the real account identifier.

4. The method of claim 1, wherein the token assurance level code indicates an authentication method associated with the payment token.

5. The method of claim 4, wherein the authentication method comprises at least one of:

no authentication, network authentication, or issuer authentication.

6. The method of claim 1, wherein the token assurance level code is based at least in part on a transaction history associated with the real account identifier.

7. The method of claim 1, wherein the authorization request message is received by the server computer from a merchant computer.

8. The method of claim 1, further comprising:

receiving an authorization response message from the issuer;

generating a modified authorization response message comprising the payment token and the token assurance level code; and

transmitting the modified authorization response message to a merchant computer.

9. The method of claim 1, wherein before receiving the authorization request message, the payment token is generated and provided to the server computer by an account issuer.

10. The method of claim 9, wherein the token assurance level code is generated at the time the payment token is generated.

11. A server computer comprising a processor and a computer readable medium comprising code, executable by the processor, for implementing a method comprising:

determining, by the server computer, the real account identifier associated with the payment token;

generating, by the server computer, a modified authorization request message comprising the real account identifier, wherein the modified authorization request comprises a token assurance level code indicative of a level of confidence associated with the payment token; and

transmitting, by the server computer, the modified authorization request message to an issuer for approval.

12. The server computer of claim 11, wherein the issuer approval is based at least in part on the token assurance level code.

13. The server computer of claim 11, wherein the level of confidence associated with the payment token comprises a level of confidence that the payment token was requested by an account holder of an underlying payment account associated with the real account identifier.

14. The server computer of claim 11, wherein the token assurance level code indicates an authentication method associated with the payment token.

15. The server computer of claim 14, wherein the authentication method comprises at least one of:

no authentication, network authentication, or issuer authentication.

16. The server computer of claim 11, wherein the token assurance level code is based at least in part on a transaction history associated with the real account identifier.

17. The server computer of claim 11, wherein the authorization request message is received by the server computer from a merchant computer.

18. The server computer of claim 11, wherein the method further comprises:

receiving an authorization response message from the issuer;

generating a modified authorization response message comprising the payment token and the token assurance level code; and

transmitting the modified authorization response message to a merchant computer.

19. The server computer of claim 11, wherein before receiving the authorization request message, the payment token is generated and provided to the server computer by an account issuer.

20. The server computer of claim 11, wherein the token assurance level code is generated at the time the payment token is generated.