US 11,810,105 B2
System and method for authorizing and provisioning a token to an appliance
Surendra Vyas, Bangalore (IN); Vaibhav Shukla, Bangalore (IN); Sindhu Shankar Rao, Bangalore (IN); Satya Prakash Tripathi, Bangalore (IN); and Som Madhab Bhattacharya, Bangalore (IN)
Assigned to Visa International Service Association, San Francisco, CA (US)
Filed by Visa International Service Association, San Francisco, CA (US)
Filed on Jun. 22, 2020, as Appl. No. 16/907,827.
Claims priority of provisional application 62/864,109, filed on Jun. 20, 2019.
Prior Publication US 2020/0402044 A1, Dec. 24, 2020
Int. Cl. G06Q 20/36 (2012.01); G06Q 20/40 (2012.01); G06Q 20/14 (2012.01)
CPC G06Q 20/3678 (2013.01) [G06Q 20/3674 (2013.01); G06Q 20/405 (2013.01); G06Q 20/145 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method for authorizing and provisioning a token to an appliance, comprising:
registering, with at least one processor, an original account identifier to at least one appliance, wherein the original account identifier comprises a device account number (DPAN) and is not associated with any user account identifier when registered;
associating, with at least one processor, a device token to the DPAN, wherein the device token is in an inactive state and is stored by the at least one appliance, and wherein the at least one processor does not store the DPAN on the at least one appliance;
associating, with at least one processor, a user account identifier to at least one of the device token and the DPAN registered to the at least one appliance;
activating the device token with at least one processor and based at least in part on the association of the user account identifier with at least one of the device token and the DPAN;
storing, with at least one processor, the association of the DPAN and the device token in a token vault;
storing, with at least one processor, an association of a user account token associated with the user account identifier and the device token in a cloud-based token vault that is separate from the token vault;
receiving, from the at least one appliance, a transaction request for a transaction, the transaction request comprising the device token;
identifying, with at least one processor, the user account identifier based on the device token received in the transaction request;
determining, with at least one processor, that the transaction is authorized based at least partially on the association of the user account token and the device token stored in the cloud-based token vault; and
in response to determining that the transaction is authorized, processing the transaction.