Method and system for managing data and enabling payment transactions between multiple entities

• US 8,856,043 B2
• Filed: 02/17/2012
• Issued: 10/07/2014
• Est. Priority Date: 02/18/2011
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Faith, Patrick, Carlson, Mark, Harris, Theodore D.
• Primary Examiner(s): Augustin, Evens J
• Application Number:
  US13/400,000
• Publication Number:
  US 20120215693A1
• Time in Patent Office: 963 Days
• Field of Search: 709/214, 463/16
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/401 Transaction verification

Abstract

A system for conducting payment transaction includes a network-enabled server that communicates with one or more user devices, other network-enabled server computers, and a payment processing network server computer. The network-enabled server facilitates transactions between one or more merchants and users by a managing data flow and interactions between the merchants and the users, providing storage area for storing of all transaction related documents, and providing seamless integration with a payment processing network for payment processing.

Claims

1. A system for processing transactions, the system comprising:

a payment processing network server computer to communicate with an issuer to process payment requests; and

a network-enabled server computer comprising a processor and a memory device coupled to the processor, the memory device comprising instructions executable by the processor to communicate with one or more external systems, wherein the instructions are further executable by the processor to;

receive a payment request, from a first merchant computer associated with a first entity, for authorizing payment for a transaction corresponding to a service provided by the first entity to a user;

send, to the first merchant computer, a request for additional information to validate the transaction, wherein the additional information includes audio, video, documentation, or a combination thereof, and wherein the additional information is produced for providing the service to the user;

in response to receiving the additional information, send, to a second merchant computer associated with a second entity, the additional information to validate the transaction based on the additional information;

receive, from the second merchant computer, a response indicating validation of the transaction, wherein validation of the transaction is determined using the additional information;

send a validation request to a user device to validate the payment request;

receive, from the user device, a response to the validation request;

receive, from the user device, an alias identifier for a user associated with the transaction;

determine payment account information for the user based at least in part on the alias identifier; and

communicate the payment account information to the payment processing network server computer, wherein the payment processing network server computer processes the payment for the transaction using the payment account information.

2. The system of claim 1 wherein the instructions are further executable by the processor to:

receive information from the payment processing network server computer indicating successful processing of the payment for the transaction; and

communicate the information to one or both of the first merchant computer or the user device.

3. The system of claim 1 wherein the payment processing network server computer is configured to:

communicate with the issuer associated to authorize the payment using the payment account information; and

communicate with an acquirer associated with the first merchant to complete payment for the transaction.

4. The system of claim 1 wherein the network-enabled server computer communicates with the user device and the first merchant computer using WSDL or JSON messaging techniques.

5. The system of claim 1 wherein the network-enabled server computer communicates with the user device and the first merchant computer using RESTful computing techniques.

18. The system of claim 1 wherein the instructions are further executable by the processor to:

receive, from the second merchant computer, a user validation request to determine whether the user received the service provided by the first entity for the transaction, wherein the validation request is sent to the user device in response to receiving the user validation request.

19. The system of claim 1 wherein the instructions are further executable by the processor to:

determine that the response to the validation request indicates that the user received the service provided by the first entity for the transaction; and

upon determining, based on the response to the validation request, that the user received the service provided by the first entity, send, to the second merchant computer, a notification that the user received the service provided by the first entity.

20. The system of claim 19 wherein the instructions are further executable by the processor to:

in response to the notification, receive, from the second merchant computer, payment account information for the second entity; and

communicate the payment account information for the second entity to the payment processing network server computer.

6. A method for processing a payment transaction, the method comprising, by a server computer:

receiving, from a first merchant server computer associated with a first entity, a transaction authorization request for payment related to a transaction corresponding to a service provided by the first entity to a user;

sending, to the first merchant server computer, an information request for additional information to validate the transaction, wherein the additional information includes audio, video, documentation, or a combination thereof, and wherein the additional information is produced for providing the service to the user;

receiving, from the first merchant server computer, the additional information responsive to the information request;

sending, to a second merchant server computer associated with a second entity, the additional information to validate the transaction based on the additional information;

receiving, from the second merchant server computer, a response indicating validation of the transaction, wherein the validation is determined using the additional information;

sending, to a user device associated with the user, a validation request to validate the transaction;

receiving, from the user device, validation information to validate the transaction;

receiving, from the user device, alias information associated with the user of the user device;

sending, to a payment processing network server computer, payment account information associated with the alias information and transaction information;

receiving, from the payment processing network server computer, results of payment transaction processing for the transaction; and

sending, to the first merchant server computer, the results of the payment transaction processing.

7. The method of claim 6 wherein the transaction authorization request, the additional information, the validation request, the validation information, the alias information, and the results of the payment transaction processing are sent using one or both of WSDL or JSON techniques.

8. The method of claim 6 wherein the transaction authorization request, the information request, the validation request, the validation information, the alias information, and the results of the payment transaction processing are sent using RESTful computing techniques.

9. The method of claim 6 wherein the transaction authorization request includes alias information of the user.

10. The method of claim 9 further comprising:

prior to sending the validation request, consulting an alias database to determine the user device associated with the alias.

11. The method of claim 6 wherein the payment account information is stored in the server computer.

12. A server computer comprising:

a processor; and

a memory device coupled to the processor, the memory device comprising instructions executable by the processor to communicate with one or more external systems, wherein the instructions are further executable by the processor to;

receive a payment request, from a first merchant computer associated with a first entity, for authorizing payment for a transaction corresponding to a service provided by the first entity to a user;

send, to the first merchant computer, a request for additional information to validate the transaction, wherein the additional information includes audio, video, documentation, or a combination thereof, and wherein the additional information is produced for providing the service to the user;

in response to receiving the additional information, send, to a second merchant computer associated with a second entity, the additional information to validate the transaction based on the additional information;

receive, from the second merchant computer, a response indicating validation of the transaction, wherein the validation is determined using the additional information;

send a validation request to a user device to validate the payment request;

receive, from the user device, a response to the validation request;

receive, from the user device, an alias identifier for a user associated with the transaction;

determine payment account information for the user based at least in part on the alias identifier; and

communicate the payment account information to a payment processing network server computer, wherein the payment processing network server computer processes the payment for the transaction using the payment account information.

13. The server computer of claim 12 further comprising:

an alias database comprising information about one or more aliases; and

an alias hierarchy database comprising association information between an alias and one or more objects associated with the alias.

14. The server computer of claim 13 wherein the one or more aliases comprise identifiers associated with a plurality of entities, wherein an entity includes an individual or a company.

15. The server computer of claim 13 wherein the alias database includes payment account information associated with an alias.

16. The server computer of claim 13 wherein the one or more objects include mobile communication devices, televisions, and gaming consoles.

17. The server computer of claim 12 wherein the instructions are further executable by the processor to:

receive, from the second merchant computer, a user validation request to determine whether the user received the service provided by the first entity for the transaction, wherein the validation request is sent to the user device in response to receiving the user validation request.