| CPC G06Q 20/383 (2013.01) [G06Q 20/02 (2013.01); G06Q 20/0652 (2013.01); G06Q 20/085 (2013.01); G06Q 20/108 (2013.01); G06Q 20/202 (2013.01); G06Q 20/204 (2013.01); G06Q 20/3672 (2013.01); G06Q 20/3674 (2013.01); G06Q 20/4012 (2013.01); G06Q 20/40145 (2013.01); G06Q 20/4037 (2013.01); G06Q 20/42 (2013.01); G06Q 40/02 (2013.01); H04L 63/0853 (2013.01); G06Q 2220/00 (2013.01); H04W 80/12 (2013.01)] | 14 Claims |

|
1. A temporary digital wallet system comprising:
a database having an association between a user device and an account stored thereon;
a digital transactions server comprising one or more processors configured to:
receive a request from the user device to generate one or more anonymous payment tokens;
transmit a notification to the user device configured to prompt entry of authentication credentials;
compare received authentication credentials to credentials associated with the account stored in the database;
generate the one or more anonymous payment tokens based on the received authentication credentials corresponding to the credentials associated with the account, wherein the one or more anonymous payment tokens comprise an alphanumeric code associated with the account, wherein the one or more anonymous payment tokens indicate a maximum amount associated with at least one anonymous payment token of the one or more anonymous payment tokens, a time by which the at least one anonymous payment token expires if not used, a geographical area to which use of the at least one anonymous payment token is limited, or any combination thereof;
send the one or more anonymous payment tokens to the user device;
receive an additional request to authorize an electronic transaction associated with the one or more anonymous payment tokens from a merchant server communicatively coupled to a point of sale system, wherein the point of sale system is configured to receive the one or more anonymous payment tokens without receiving personally identifiable information of a user associated with the user device and send the one or more anonymous payment tokens to the digital transaction server;
confirm the one or more anonymous payment tokens correspond to the account based on the alphanumeric code;
determine whether the account has sufficient funds to complete the electronic transaction;
in response to determining that the account has sufficient funds to complete the electronic transaction, transmit an additional notification to the user device configured to prompt entry of additional authentication credentials to authenticate the electronic transaction based on the received authentication credentials associated with the account;
compare received additional authentication credentials to additional credentials associated with the account;
authenticate the electronic transaction based on the received additional authentication credentials associated with the account; and
authorize the one or more anonymous payment tokens to enable the electronic transaction via the user device based on authenticating the electronic transaction and determining that the account has sufficient funds.
|