Techniques for mobile transaction processing
First Claim
1. A processor-implemented method programmed in a non-transitory processor-readable medium and to execute on one or more processors of a server configured to execute the method, comprising:
- receiving, at a server, a request to complete a transaction session occurring between a consumer and an enterprise terminal device, wherein the request comprises a uniform resource locator (URL) link specific to the transaction session;
generating, by the server, a unique token, wherein the token comprises the URL and a transaction ID;
providing, from the server, the unique token back to the enterprise terminal device for uniquely identifying the transaction;
acquiring, at the server, and from a mobile device the unique token that is signed by the mobile device;
validating, at the server, the signed token; and
completing, by the server, the transaction using payment details associated with the consumer.
6 Assignments
0 Petitions
Accused Products
Abstract
Techniques for automated mobile transaction processing are provided. A consumer traverses to a web portal or other type of enterprise terminal device of an enterprise and proceeds to shop. During checkout, the portal contacts a transaction service and is delivered back an identifying barcode or Quick Response (QR) code. The consumer uses a mobile device to scan the code and send it to the transaction service. Previously registered payment details of the consumer are located and payment is received from the consumer. The portal is notified that payment is completed by the transaction service.
-
Citations
9 Claims
-
1. A processor-implemented method programmed in a non-transitory processor-readable medium and to execute on one or more processors of a server configured to execute the method, comprising:
-
receiving, at a server, a request to complete a transaction session occurring between a consumer and an enterprise terminal device, wherein the request comprises a uniform resource locator (URL) link specific to the transaction session; generating, by the server, a unique token, wherein the token comprises the URL and a transaction ID; providing, from the server, the unique token back to the enterprise terminal device for uniquely identifying the transaction; acquiring, at the server, and from a mobile device the unique token that is signed by the mobile device; validating, at the server, the signed token; and completing, by the server, the transaction using payment details associated with the consumer. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
Specification