Late binding tokens
First Claim
Patent Images
1. A late binding token system, comprising:
- a token server of an issuer, the token server communicating with a network;
a merchant server communicating with the network;
an account server, storing information for a consumer, communicating with the network;
a physical late binding token, from the issuer, including a locator code initially binding the late binding token to only the token server when the consumer receives the physical late binding token, and including a memory for storing a public/private key pair;
a client software communicating with the late binding token server and at least one of the merchant server and the account server for verifying the bindings of the physical late binding token with the token server, the merchant server and the account server, the consumer communicating with at least one of the merchant server and the account server via the client software to perform a transaction;
first software associated with the late binding token and executable by said client software for retrieving said locator code from said physical late binding token for establishing communication between said client software and the token server via the network, the first software verifying the physical late binding token to the token server; and
second software, provided to said client software via the network, for binding the consumer to the account server, for transactions between the client software, the merchant server, the account server, the late binding token, and the token server;
wherein the second software binds the token to the account server only after the first software verifies the late binding token with the token server; and
wherein if the token server has previously verified the late binding token and if the late binding token has been previously bound to the account server, the token server requests payment from the account server to the merchant server while only disclosing selected information of the consumer to the merchant server.
0 Assignments
0 Petitions
Accused Products
Abstract
A system for verifying intent in a card not present transaction is provided. The system includes a late binding token that is distributable to consumers without necessarily being bound to an account. The system also includes a client software that locates a token server configured to facilitate managing and communicating with the late binding token. The system also includes a protocol concerning how to build a verifiably secure structured proposal that carries an offer to the consumer through the client software.
-
Citations
21 Claims
-
1. A late binding token system, comprising:
-
a token server of an issuer, the token server communicating with a network; a merchant server communicating with the network; an account server, storing information for a consumer, communicating with the network; a physical late binding token, from the issuer, including a locator code initially binding the late binding token to only the token server when the consumer receives the physical late binding token, and including a memory for storing a public/private key pair; a client software communicating with the late binding token server and at least one of the merchant server and the account server for verifying the bindings of the physical late binding token with the token server, the merchant server and the account server, the consumer communicating with at least one of the merchant server and the account server via the client software to perform a transaction; first software associated with the late binding token and executable by said client software for retrieving said locator code from said physical late binding token for establishing communication between said client software and the token server via the network, the first software verifying the physical late binding token to the token server; and second software, provided to said client software via the network, for binding the consumer to the account server, for transactions between the client software, the merchant server, the account server, the late binding token, and the token server; wherein the second software binds the token to the account server only after the first software verifies the late binding token with the token server; and wherein if the token server has previously verified the late binding token and if the late binding token has been previously bound to the account server, the token server requests payment from the account server to the merchant server while only disclosing selected information of the consumer to the merchant server. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 19, 21)
-
-
12. A method for securely indicating verifiable consumer intent to enter into a transaction, comprising:
-
receiving a physical late binding token of an issuer, the late binding token including a memory for storing a public/private key pair communicating with a network and including a locator code initially binding the late binding token to only an associated token server of the issuer when a consumer receives the late binding token; verifying the bindings of the physical late binding token via a client software communicating with the token server and at least one of a merchant server, a consumer, an account server storing information for the consumer, and the late binding token; communicating with the merchant server via the client software to perform a consumer transaction; executing a first software, associated with the late binding token, for retrieving the locator code from the late binding token for establishing a communication link between the physical late binding token and the token server, via the network, initially binding the physical late binding token to the token server, and verifying the late binding token to the token server; providing a second software to the client software via the network, for binding the consumer to the account server for transactions between the client software, the merchant server, the account server, the late binding token, and the token server, to create respective bindings between the late binding token and at least one of the consumer and the account server; verifying that the offering from the merchant was correctly displayed to the user via the second software, only after the first software verifies the late binding token with the token server; and if the display of the offering from the merchant was successfully verified, verifying that the input from the user was correctly communicated to at least one of the merchant server or the account server while only disclosing selected information of the consumer to the merchant. - View Dependent Claims (13, 14, 15, 16, 17, 18, 20)
-
Specification