Secure payment method and system
DCFirst Claim
1. A server-based method of facilitating payment by a user registered with a server, the method comprising, at the server:
- using a processor to generate, for the user, a code and store the code in a memory;
transmitting, via a communication module, the code to a mobile device of the user;
transferring information characterizing a payment instrument from the user to a payment-processing entity utilizing a server routing or a redirect client-side script without storing the payment-characterizing information at the server after completion of the registration;
receiving, from the payment-processing entity via the communication module, a token encoding the user'"'"'s account-identifying information;
using the processor to computationally associate the token with the user;
receiving, from a merchant device via the communication module, the code and a payment amount;
using the processor to match the received code to the user and retrieve the token associated with the user; and
providing the token and the payment amount to the payment-processing entity, via the communication module, to cause completion of a transaction between the user and the merchant,wherein providing the code or token alone does not enable completion of the transaction.
17 Assignments
Litigations
0 Petitions
Accused Products
Abstract
Representative embodiments of a server-based method of facilitating payment by a user registered with the server include, at the server, generating and storing, for the user, a code readable by a merchant device, transmitting the code to a mobile device of the user, facilitating provision of information characterizing a payment instrument from the user to a payment-processing entity without storing the data at the server, receiving, from the payment-processing entity, a token indicative of the payment instrument but not encoding data that would enable use of the instrument, associating the token with the user, receiving, from a merchant, the code and a payment amount, matching the received code to the user and retrieving the token associated with the user, and providing the token and the payment amount to the payment-processing entity to facilitate completion of a transaction between the user and the merchant.
27 Citations
14 Claims
-
1. A server-based method of facilitating payment by a user registered with a server, the method comprising, at the server:
-
using a processor to generate, for the user, a code and store the code in a memory; transmitting, via a communication module, the code to a mobile device of the user; transferring information characterizing a payment instrument from the user to a payment-processing entity utilizing a server routing or a redirect client-side script without storing the payment-characterizing information at the server after completion of the registration; receiving, from the payment-processing entity via the communication module, a token encoding the user'"'"'s account-identifying information; using the processor to computationally associate the token with the user; receiving, from a merchant device via the communication module, the code and a payment amount; using the processor to match the received code to the user and retrieve the token associated with the user; and providing the token and the payment amount to the payment-processing entity, via the communication module, to cause completion of a transaction between the user and the merchant, wherein providing the code or token alone does not enable completion of the transaction. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A server for facilitating payment by a user registered with the server, the server comprising:
-
a processor; a processor-executable code-generation module for generating, for the user, a code; a communication module; a web server for generating a form-containing web page and associated programming for execution on a client-side computer, the programming being executable to cause transmission of information entered on the form to a payment-processing entity utilizing a server routing or a redirect client-side script without storing the entered information at the server after completion of the registration; and a database for storing a token received from the payment-processing entity via the communication module and associating the token with the user; wherein the processor is configured to; (i) operate the communication module to cause the code to be transmitted to a mobile device of the user, (ii) operate the communication module to receive, from a merchant, the code and a payment amount, (iii) match the received code to the user and retrieving the token associated with the user, and (iv) following the match, operate the communication module to provide the token and the payment amount to a payment processor to cause completion of a transaction between the user and the merchant, and further wherein providing the code or token alone does not enable completion of the transaction. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
Specification