SYSTEM AND METHOD OF PROVIDING TOKENIZATION AS A SERVICE

• US 20130198080A1
• Filed: 01/28/2013
• Published: 08/01/2013
• Est. Priority Date: 01/26/2012
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Anderson, Lisa, Cushley, Seamus
• Granted Patent: US 9,830,595 B2
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/26 Debit schemes, e.g. "pay now"
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/383 Anonymous user system
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes

Abstract

Systems, devices, apparatuses, and methods for providing tokenization as a service are provided. Embodiments of the invention involve decoupling a “tokenization service” from other services offered by a merchant service provider, and offering the tokenization service as a stand-alone service. In accordance with an embodiment, a merchant service provider can receive payment data associated with a transaction between a consumer and a first entity. The merchant service provider can generate a payment token that represents the payment data and transmit a copy of the payment token to the first entity. The first entity can then transmit the payment token and order information to a second entity specified in the transaction. The merchant service provider can subsequently receive a request to complete the transaction from the second entity. The request can include the copy of the payment token from the second entity.

Claims

1. A method, comprising:

receiving, at a merchant service provider, payment data associated with a transaction between a consumer and a first entity, wherein the payment data is received from the consumer and bypasses the first entity;

generating, at the merchant service provider, a payment token that represents the payment data;

transmitting, from the merchant service provider, a copy of the payment token to the first entity, wherein the first entity transmits the copy of the payment token and order information associated with the transaction to a second entity specified in the transaction; and

receiving, at the merchant service provider, a request to complete the transaction from the second entity, wherein the request includes the copy of the payment token from the second entity.

2. The method of claim 1 further comprising:

authorizing the request to complete the transaction based on merchant information stored at the merchant service provider and context information associated with the payment token.

3. The method of claim 1 further comprising:

verifying that the copy of the payment token received from the second entity matches a copy of the payment token stored at the merchant service provider.

4. The method of claim 2 wherein authorizing the request to complete the transaction comprises:

determining whether the first entity has indicated that the second entity is a trusted entity.

5. The method of claim 2 wherein authorizing the request to complete the transaction comprises:

determining whether the merchant service provider has indicated that the second entity is a trusted entity.

6. The method of claim 2 wherein the context information includes one or more of an expiration time/date for the payment token, merchant identifiers for the first and second entities, and a transaction identifier.

7. The method of claim 1 wherein the request to complete the transaction includes a request for the merchant service provider to process the transaction on behalf of the second entity.

8. The method of claim 1 wherein the request to complete the transaction includes a request to return the payment data corresponding to the payment token to the second entity.

9. The method of claim 1 wherein the merchant service provider is a hosted order page (HOP) service provider and the payment data is received through a HOP.

10. The method of claim 1 wherein the merchant service provider is a silent order post (SOP) service provider and the payment data is received through a SOP.

11. An apparatus for enabling a consumer to purchase a transit product, comprising:

an electronic processor programmed to execute a set of instructions; and

a memory coupled to the electronic processor and storing the set of instructions;

wherein when executed by the electronic processor, the set of instructions cause the apparatus to

receive, at a merchant service provider, payment data associated with a transaction between a consumer and a first entity, wherein the payment data is received from the consumer and bypasses the first entity;

generate, at the merchant service provider, a payment token that represents the payment data;

transmit, from the merchant service provider, a copy of the payment token to the first entity, wherein the first entity transmits the copy of the payment token and order information associated with the transaction to a second entity specified in the transaction; and

receive, at the merchant service provider, a request to complete the transaction from the second entity, wherein the request includes the copy of the payment token from the second entity.

12. The system of claim 11 wherein the set of instructions further cause the apparatus to authorize the request to complete the transaction based on merchant information stored at the merchant service provider and context information associated with the payment token.

13. The system of claim 11 wherein the set of instructions further cause the apparatus to verify that the copy of the payment token received from the second entity matches a copy of the payment token stored at the merchant service provider.

14. The system of claim 12 wherein authorizing the request to complete the transaction comprises:

determining whether the first entity has indicated that the second entity is a trusted entity.

15. The system of claim 12 wherein authorizing the request to complete the transaction comprises:

determining whether the merchant service provider has indicated that the second entity is a trusted entity.

16. The system of claim 12 wherein the context information includes one or more of an expiration time/date for the payment token, merchant identifiers for the first and second entities, and a transaction identifier.

17. The system of claim 11 wherein the request to complete the transaction includes a request for the merchant service provider to process the transaction on behalf of the second entity.

18. The system of claim 11 wherein the request to complete the transaction includes a request to return the payment data corresponding to the payment token to the second entity.

19. The system of claim 11 wherein the merchant service provider is a hosted order page (HOP) service provider and the payment data is received through a HOP.

20. The system of claim 11 wherein the merchant service provider is a silent order post (SOP) service provider and the payment data is received through a SOP.