Communication protocols for processing an authorization request in a distributed computing system

• US 10,540,656 B2
• Filed: 03/13/2019
• Issued: 01/21/2020
• Est. Priority Date: 03/13/2014
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Mohammed, Sayeed, Ovick, Joseph Bjorn, Kim, Nancy L., Salmon, Diane C.
• Primary Examiner(s): Gudorf, Laura A
• Application Number:
  US16/351,813
• Publication Number:
  US 20190213591A1
• Time in Patent Office: 314 Days
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/22 Payment schemes or models
• CPC Class Codes: G06Q 20/401 Transaction verification

Abstract

Systems and methods implementing a communication protocol for the authorization of transfer of resources in a computer system having a plurality of computers, including a centralized router connecting to source account controllers and destination account controllers that are connected to readers. A reader communicates a first authorization request having a source identifier to a portal coupled with a data storage storing data linking the source identifier to a linked identifier. The portal communicates with a respective linked account controller to obtain a response identifying an available resource. Based on the response, the reader generates a further authorization request for a requested resource from a source account identified by the source identifier to a destination account associated with the reader.

Claims

1. A computing system to implement a communication protocol, comprising:

a portal having a communication connection between the portal and a reader that is connected to a destination account controller, wherein the communication connection does not go through the destination account controller controlling a destination account associated with the reader, the portal configured to;

receive, through the communication connection, a first authorization request identifying a source account identifier, in response to the reader obtaining the source account identifier from a mobile device;

transmit, in response to the first authorization request and based on data linking the source account identifier and a linked identifier, a second authorization request to a linked account controller controlling a linked account identified by the linked identifier, the second authorization request including the linked account identifier;

receive, from the linked account controller, a first response to the second authorization request, the first response identifying an available resource for transferring from the linked account to the destination account; and

communicate, the first response to the reader to cause the reader to generate a third authorization request based on the available resource identified in the first response and transmit the third authorization request, the third authorization request including the source account identifier and a requested resource to be transferred to the destination account; and

a centralized router configured to;

receive the third authorization request from the reader via the destination account controller;

route the third authorization request to a source account controller that controls a source account identified by the source account identifier contained in the third authorization request; and

route a second response to the third authorization request from the source account controller to the reader via the destination account controller.

2. The computing system of claim 1, wherein the first response from the portal to the reader causes the reader to generate the third authorization request without obtaining the source account identifier again from the mobile device after the first authorization request is transmitted to the portal.

3. The computing system of claim 2, wherein the first response is communicated by the portal to the reader using the communication connection that does not go through the destination account controller.

4. The computing system of claim 1, wherein the communication connection through which the first authorization request is communicated from the reader to the portal is established via internet.

5. The computing system of claim 1, wherein the first response is communicated to the reader via the destination account controller.

6. The computing system of claim 5, wherein the portal causes the centralized router to route the first response to the destination account controller which further transmits the first response to the reader.

7. The computing system of claim 6, wherein the computing system identifies the destination account controller based on an identifier of the reader provided in the first authorization request and routes the first response to the destination account controller via the centralized router.

8. The computing system of claim 1, wherein the first response authorizes a transfer of the available resource identified in the first response and causes the reader to prompt for an input to accept or reject the transfer of the available resource from the linked account to the destination account associated with the reader.

9. The computing system of claim 8, wherein the first response causes the reader to determine the requested resource identified in the third authorization request, based on the available resource identified in the first response and the input to accept or reject the transfer of the available resource from the linked account to the destination account associated with the reader.

10. A non-transitory computer storage medium storing instructions configured to instruct a computing system to implement a communication protocol, the communication protocol comprising:

establishing a communication connection between a portal and a reader that is connected to a destination account controller, wherein the communication connection does not go through the destination account controller controlling a destination account associated with the reader;

receiving, in the portal through the communication connection from the reader, a first authorization request identifying a source account identifier obtained by the reader from a mobile device;

transmitting, by the portal in response to the first authorization request and based on data linking the source account identifier and a linked identifier, a second authorization request to a linked account controller controlling a linked account identified by the linked identifier, the second authorization request including the linked account identifier;

receiving, by the portal from the linked account controller, a first response to the second authorization request, the first response identifying an available resource for transferring from the linked account to the destination account; and

communicating, by the portal, the first response to the reader to cause the reader to generate a third authorization request based on the available resource identified in the first response and transmit the third authorization request, the third authorization request including the source identifier and a requested resource to be transferred to the destination account;

receiving, by a centralized router, the third authorization request from the reader via the destination account controller;

routing, by the centralized router, the third authorization request to a source account controller that controls a source account identified by the source identifier contained in the third authorization request; and

routing, by the centralized router, a second response to the third authorization request from the source account controller to the reader via the destination account controller.

11. A method for implementing a communication protocol, the method comprising:

establishing a communication connection between a portal and a reader that is connected to a destination account controller, wherein the communication connection does not go through the destination account controller controlling a destination account associated with the reader;

receiving, in the portal through the communication connection from the reader, a first authorization request identifying a source account identifier obtained by the reader from a mobile device;

transmitting, by the portal in response to the first authorization request and based on data linking the source account identifier and a linked identifier, a second authorization request to a linked account controller controlling a linked account identified by the linked identifier, the second authorization request including the linked account identifier;

receiving, by the portal from the linked account controller, a first response to the second authorization request, the first response identifying an available resource for transferring from the linked account to the destination account; and

communicating, by the portal, the first response to the reader to cause the reader to generate a third authorization request based on the available resource identified in the first response and transmit the third authorization request, the third authorization request including the source account identifier and a requested resource to be transferred to the destination account;

receiving, by a centralized router, the third authorization request from the reader via the destination account controller;

routing, by the centralized router, the third authorization request to a source account controller that controls a source account identified by the source identifier contained in the third authorization request; and

routing, by the centralized router, a second response to the third authorization request from the source account controller to the reader via that destination account controller.

12. The method of claim 11, wherein the first response authorizes the destination account controller to initiate a transfer of the available resource identified in the first response from the linked account to the destination account.

13. The method of claim 12, wherein the transfer is in response to the destination account controller receiving a transfer request from the reader identifying the source account identifier.

14. The method of claim 13, wherein the first response causes the reader to prompt for an input to accept or reject the transfer of the available resource from the linked account to the destination account associated with the reader;

and the transfer request is in response to an input accepting the transfer.

15. The method of claim 14, wherein the requested resource is determined based on the available resource identified in the first response and the input accepting the transfer of the available resource from the linked account to the destination account.

16. The method of claim 11, wherein the first response causes the reader to generate the third authorization request without obtaining the source account identifier again from the mobile device after the first authorization request is transmitted to the portal.

17. The method of claim 11, wherein the first response is communicated to the reader via the destination account controller.

18. The method of claim 17, wherein the communicating of the first response to the reader includes:

providing the first response to the centralized router to cause the centralized router to route the first response to the destination account controller, wherein the destination account controller provides the first response to the reader.

19. The method of claim 18, wherein the destination account controller is identified for routing the first response to the reader based on an identifier of the reader provided in the first authorization request.

20. The method of claim 11, wherein the first response from the portal to the reader causes the reader to generate the third authorization request without obtaining the source account identifier again from the mobile device after the first authorization request is transmitted to the portal.