Transaction services data system

• US 9,070,123 B2
• Filed: 12/21/2011
• Issued: 06/30/2015
• Est. Priority Date: 12/21/2011
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Theado, Brian P., Nguyen, Khoa N., Palmer, Lloyd S. Jr.
• Primary Examiner(s): Whipple, Brian P
• Assistant Examiner(s): EDWARDS, JAMES A
• Application Number:
  US13/332,422
• Publication Number:
  US 20130166638A1
• Time in Patent Office: 1,287 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/425 using two different networks, one for transaction and one for security confirmation

Abstract

A device may include a transaction web server. The transaction server may be configured to receive a hypertext markup language HTTP message that includes information sent from a transaction device, determine whether the message is a request to authorize a transaction or a request to settle a transaction, route a first portion of the HTTP message to a customer device to obtain an authorization from the customer device when the HTTP message is a request to authorize the transaction, and route a second portion of the HTTP message to the customer device to settle the transaction when the HTTP message is a request to settle a transaction.

Claims

1. A device comprising:

a transaction web server configured to;

receive a hypertext transfer protocol (HTTP) message that includes information sent from a transaction device;

determine whether the message is a request to authorize a transaction or a request to settle the transaction;

route a first portion of the HTTP message to a customer device to obtain an authorization from the customer device when the HTTP message is a request to authorize the transaction; and

route a second portion of the HTTP message to the customer device to settle the transaction when the HTTP message is a request to settle the transaction,

wherein, the transaction web server, when routing the first portion of the HTTP message to the customer device, is further configured to forward the first portion of the HTTP message to gateway applications, and

wherein the gateway applications are configured to;

receive the first portion of the HTTP message;

perform a lookup of a destination address of the customer device based on information provided in the first portion of the HTTP message; and

send a portion of the first portion to the customer device.

2. The device of claim 1, wherein the gateway applications are further configured to:

establish a socket connection to the customer device.

3. The device of claim 1, wherein the gateway applications are further configured to:

send an acknowledgment message to the transaction web server, wherein the acknowledgement message indicates that the gateway applications are connected to the customer device.

4. The device of claim 1, wherein the gateway applications, when sending the portion of the first portion to the customer device, are further configured to:

send the portion of the first portion to the customer device in accordance with Visa II protocol.

5. The device of claim 1, wherein the gateway applications are further configured to:

receive a reply from the customer device, wherein the reply indicates whether the transaction is authorized; and

forward the reply to the transaction device.

6. The device of claim 1, wherein the gateway applications are further configured to:

send an end-of-text (EOT) message to the transaction web server when the gateway applications are unable to establish a connection to the customer device.

7. The device of claim 1, wherein the transaction web server, when routing the second portion of the HTTP message to the customer device, is further configured to:

forward the second portion of the HTTP message to the gateway applications, and

wherein the gateway applications are further configured to;

receive the second portion of the HTTP message; and

send a portion of the second portion of the HTTP message to the customer device.

8. The device of claim 7, wherein the transaction web server is further configured to:

determine whether a first byte of the second portion indicates at least one of;

a start of text;

an acknowledgment;

a bell;

a synchronization;

or

a negative acknowledgment, and

wherein the transaction web server is further configured to;

determine, when the first byte of the second portion indicates the acknowledgment, whether the acknowledgment is correctly ordered among a series of messages received from the gateway applications.

9. The device of claim 1, further comprising:

a supervisor application configured to at least one of;

configure at least one of the transaction web server or the gateway applications;

start one or more of the transaction web server or the gateway applications;

or

send health check messages to the gateway applications.

10. The device of claim 9, wherein the supervisor application, when starting the one or more of the transaction web server or the gateway applications, is further configured to:

determine that the supervisor application is recovering from a crash;

identify one or more of the gateway applications that are active when the supervisor application crashed;

terminate the one or more of the gateway applications while the supervisor application is recovering from a crash; and

spawn the one or more of the gateway applications after the supervisor application has recovered from the crash.

11. The device of claim 10, wherein the supervisor application is further configured to:

perform health checks on the spawned one or more of the gateway applications; and

include identifiers for the spawned one or more of the gateway applications in a list of alive applications.

12. A method comprising:

receiving by a processor associated with a transaction web server, a hypertext transfer protocol (HTTP) message that includes information sent from a transaction device;

determining, by the processor, whether the message is a request to authorize a transaction or a request to settle a transaction;

routing, by the processor, a first portion of the HTTP message to a customer device to obtain an authorization from the customer device when the HTTP message is a request to authorize the transaction, wherein routing the first portion of the HTTP message includes;

forwarding the first portion of the HTTP message to gateway applications, wherein the gateway applications receive the first portion of the HTTP message, perform a lookup of a destination address of the customer device based on information provided in the first portion of the HTTP message, and send a portion of the first portion to the customer device based on the destination address; and

routing, by the processor, a second portion of the HTTP message to the customer device to settle the transaction when the HTTP message is a request to settle a transaction.

13. The method of claim 12, further comprising:

receiving, from the gateway applications, an acknowledgement message, wherein the acknowledgement message indicates that the gateway applications are connected to the customer device.

14. The method of claim 12, further comprising:

receiving, via the gateway applications, a reply sent from the customer device, wherein the reply indicates whether the transaction is authorized.

15. The method of claim 12, wherein routing the second portion of the HTTP message to the customer device includes:

forwarding the second portion of the HTTP message to the gateway applications, wherein the gateway applications establish a connection to the customer device and forward portion of the second portion of the HTTP message to the customer device via the connection.

16. The method of claim 12, wherein the first portion and the second portion are different,

wherein the first portion of the HTTP message includes information identifying at least one of a user or a user device associated with the transaction, and

wherein the second portion of the HTTP message includes information about the transaction.

17. A non-transitory computer-readable medium to store instructions, the instructions comprising:

one or more instructions that, when executed by a processor associated with a transaction web server, cause the processor to;

receive a hypertext transfer protocol (HTTP) message that includes information sent from a transaction device;

determine whether the message is a request to authorize a transaction or a request to settle a transaction;

route a first portion of the HTTP message to a customer device to obtain an authorization from the customer device when the HTTP message is a request to authorize the transaction, wherein gateway applications receive the first portion of the HTTP message, perform a lookup of a destination address of the customer device based on information provided in the first portion of the HTTP message, and send a portion of the first portion to the customer device based on the destination address; and

route a second portion of the HTTP message to the customer device to settle the transaction when the HTTP message is a request to settle a transaction.

18. The non-transitory computer-readable medium of claim 17, wherein the one or more instructions further cause the processor, when routing the second portion of the HTTP message to the customer device, to:

forward the second portion of the HTTP message to the gateway applications, wherein the gateway applications establish a connection to the customer device and forward a portion of the second portion of the HTTP message to the customer device via the connection.

19. The non-transitory computer-readable medium of claim 18, wherein the one or more instructions further cause the processor, when forwarding the second portion of the HTTP message to the customer device via the connection, to:

extract an acknowledgment from the second portion,

determine whether the acknowledgment is correctly ordered among a series of messages received from the gateway applications, and

resend the second portion if the acknowledgment is incorrectly ordered among the series of messages received from the gateway applications.

20. The non-transitory computer-readable medium of claim 17, wherein the instructions further comprise:

one or more instructions that, when executed by a supervisor application coupled to the transaction web server, cause the supervisor application to;

determine that the supervisor application is recovering from a crash,

identify one or more of the gateway applications that are active when the supervisor application crashed;

terminate the one or more of the gateway applications while the supervisor application is recovering from a crash; and

restart the one or more of the gateway applications after the supervisor application has completed recovering from the crash.