TRANSACTION SERVICES DATA SYSTEM

• US 20130166638A1
• Filed: 12/21/2011
• Published: 06/27/2013
• 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.
• Granted Patent: US 9,070,123 B2
• Time in Patent Office: Days
• US Class Current: 709/204
• 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 to;

receive a hypertext transfer protocol (HTTP) message, from a device, 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.

2. The device of claim 1, further comprising:

gateway applications configured to;

receive the first portion of the HTTP message from the transaction web server;

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

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

wherein when the transaction web server routes the first portion of the HTTP message to the customer device, the transaction web server forwards the first portion of the HTTP message to the gateway applications.

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

establish a socket connection to the customer device.

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

send an acknowledgment message to the transaction web server to indicate that the gateway applications are connected to the customer device.

5. The device of claim 3, wherein when the gateway applications send a portion of the first portion to the customer device, the gateway applications are configured to:

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

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

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

forward the reply to the transaction device.

7. The device of claim 3, 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.

8. The device of claim 1, further comprising:

gateway applications configured to;

receive the second portion of the HTTP message;

connect to the customer device; and

send a portion of the second portion of the HTTP message to the client device,

wherein when the transaction web server routes the second portion of the HTTP message to the customer device, the transaction web server forwards the second portion of the HTTP message to the gateway applications.

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

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

a start of text;

an acknowledgment;

a bell;

a synchronization;

or

a negative acknowledgment.

10. The device of claim 9, wherein when the transaction web server determines that the first byte of the second portion indicates an acknowledgment, the transaction web server is further configured to:

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

11. The device of claim 8, further comprising:

a supervisor application configured to at least one of;

configure the transaction web server or the gateway applications on the device;

or start the transaction web server or the gateway applications on the device;

or

send health check messages to the gateway applications.

12. The device of claim 11, wherein when the supervisor application starts the transaction web server or the gateway applications, the supervisor is further configured to:

determine whether the supervisor is recovering from a crash;

kill one or more of the gateway applications when the one or more of the gateway applications are up when the supervisor determines that the supervisor is recovering from a crash; and

spawn one or more gateway applications when the supervisor determines that the supervisor is not recovering from a crash.

13. The device of claim 12, wherein the supervisor application is further configured to;

perform health checks on the spawned gateway applications; and

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

14. A method comprising:

processing hypertext transfer protocol (HTTP) messages, including;

receiving a HTTP message from a transaction device;

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

forwarding a first portion of the HTTP message to the customer device to settle the transaction when the HTTP message is a request to settle a transaction; and

forwarding a second portion of the HTTP message to the customer device to authorize the transaction when the HTTP message is a request to authorize the transaction; and

routing transaction messages, including;

establishing a connection to the customer device; and

sending a portion of the first portion of the HTTP message to the customer device over the connection.

15. The method of claim 14, wherein the processing HTTP messages further includes:

receiving a reply from gateway applications;

determining whether the reply includes one of;

a start of text;

or

a bell.

16. The method of claim 14, further comprising:

supervising the processing HTTP messages and the routing transaction messages, including;

performing health checks on the processing HTTP messages and the routing transaction messages.

17. The method of claim 16, wherein the supervising the processing HTTP messages and the routing transaction messages includes:

stopping the processing HTTP messages.

18. A computer-readable medium, comprising computer-executable instructions, for causing one or more processors executing the computer-executable instructions to:

render web services, wherein the instructions for causing the one or more processors executing the instructions to render the web services include instructions for causing the one or more processors to;

receive a hypertext markup language (HTTP) message, from a device, 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;

forward a first portion of the HTTP message to the customer device to settle the transaction when the HTTP message is a request to settle a transaction; and

forward a second portion of the HTTP message to the customer device to authorize the transaction when the HTTP message is a request to authorize the transaction.

19. The computer-readable medium of claim 18, further comprising computer-executable instructions for causing the one or more processors executing the instructions to route transaction messages, wherein the instructions for causing the one or more processors executing the instructions to route transaction messages include instructions for causing the one or more processors to:

establish a connection to the customer device; and

send a portion of the first portion of the HTTP message to the customer device over the connection.

20. The computer-readable medium of claim 18, further comprising computer-executable instructions for causing the one or more processors executing the instructions to supervise processes, wherein the instructions for causing the one or more processors executing the instructions to supervise processes include instructions for causing the one or more processors to:

start a process for rendering web services and a process for routing transaction messages; and

perform health checks on the process for routing transaction messages.