Real-time mobile wallet server
Techniques and apparatuses for providing wallet server information to an entity using a real-time mobile wallet server (MWS) are disclosed herein. The MWS may receive a request for personal information from an entity. The MWS may then display to a user a summary of the request, a list of selections available in the wallet server that may satisfy the request, and a list of selectable response options for the user to choose to respond to the entity. In some aspects, the wallet server may store username and associated passwords, payment information, and/or contact information. In further aspects, the MWS may generate limited-use payment information associated with existing payment information. The MWS may communicate ad hoc messaging to the entity using voice-based or real-time text-based communications over an established communication link between the MWS and entity.
1. A method comprising:
receiving, by a mobile wallet application executed by one or more processors of a user device and from an entity device, a request for a type of personal information, the request being associated with a transaction between a merchant associated with the entity device and a customer associated with the user device;
outputting, by the mobile wallet application, a security request for authorization to access the personal information;
receiving the authorization to access the personal information;
presenting, by the mobile wallet application, information related to the request including:
the type of personal information requested;
an identity of the merchant associated with the entity device that sent the request;
a first location of the merchant associated with the entity device; and
a list of selectable items filtered to exclude other types of personal information other than the type of personal information requested;
receiving a selection of a selectable item from the list of selectable items that have been filtered;
determining that a location limit is associated with transmission, to the entity device, of the selectable item corresponding to the selection, wherein the location limit defines a pre-defined distance between the first location of the merchant associated with the entity device and a second location of the user device;
determining that the first location of the merchant associated with the entity device is within the pre-defined distance of the second location of the user device; and
transmitting, by the mobile wallet application executed by the one or more processors of the user device, the selectable item corresponding to the selection to the entity device.
2. The method as recited in claim 1 , wherein the selected item comprises one of a payment instrument, contact information, or username and password information.
3. The method as recited in claim 1 , further comprising terminating communication between the mobile wallet application and the entity device after passage of a predetermined amount of time.
4. The method as recited in claim 1 , wherein the request includes a message body including a description of the request and the identity of the merchant associated with the entity device that sent the request.
5. The method as recited in claim 1 , wherein the selected item comprises a limited-use payment instrument that is generated by a payment provider or by the mobile wallet application and includes a predetermined number of allowable uses, the method further comprising discarding the limited-use payment instrument in response to a determination that a number of uses of the limited-use payment instrument has reached or exceeded the predetermined number of allowable uses.
6. The method as recited in claim 1 , further comprising transmitting a secondary message from the user device that maintains the mobile wallet application to the entity device via at least one of a voice over internet protocol (VoIP) or a text-based messaging protocol to communicate an ad hoc response to the request.
7. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed, cause one or more processors to perform operations comprising:
determining that a location limit is associated with transmission of requested information from a mobile wallet application of a device to an entity device associated with a merchant, wherein:
the location limit defines a pre-defined distance between a first location of the merchant associated with the entity device and a second location of the device; and
the requested information is associated with a transaction between the merchant associated with the entity device and a customer associated with the device;
determining that the first location of the merchant associated with the entity device is within the pre-defined distance of the second location of the device;
implementing a security feature associated with the mobile wallet application that authorizes access to the requested information;
identifying items that are stored locally in the mobile wallet application of the device and that are of a particular type of the requested information;
causing the identified items to be presented; and
in response to receiving a selection of at least one of the identified items, causing the at least one of the identified items selected to be transmitted to the entity device.
8. The one or more non-transitory computer-readable media as recited in claim 7 , wherein the at least one of the identified items selected comprises at least one of payment information, contact information, or username and password information.
9. The one or more non-transitory computer-readable media as recited in claim 7 , wherein the identified items comprises a plurality of payment instruments.
10. The one or more non-transitory computer-readable media as recited in claim 7 , wherein the operations further comprise:
determining that a request requesting the requested information is received from the entity device within a predetermined time period; and
allowing transmission of the at least one of the identified items to the entity device.
11. The one or more non-transitory computer-readable media as recited in claim 7 , wherein a request requesting the requested information includes a message body including a description of the request and a name of the merchant associated with the entity device that sent the request.
12. The one or more non-transitory computer-readable media as recited in claim 7 , wherein the at least one of the identified items selected include at least a limited-use payment instrument that is generated by a payment provider or by the mobile wallet application, the limited-use payment instrument having a predetermined number of allowable uses, the operations further comprising:
determining, after the selection of the limited-use payment instrument, that the predetermined number of allowable uses has been reached or exceeded; and
discarding the limited-use payment instrument in response to determining that the predetermined number of allowable uses has been reached or exceeded.
13. The one or more non-transitory computer-readable media as recited in claim 7 , wherein the operations further comprise transmitting a secondary message from the device to the entity device via at least one of a voice over internet protocol (VoIP) or a text-based messaging protocol to communicate an ad hoc response to the request.
14. A system comprising:
at least one computing device configured to implement one or more services, wherein the one or more services are configured to:
store a mobile wallet associated with a user;
in response to receiving a request for information stored in the mobile wallet, cause a security request for authorization to access the information to be output;
in response to receiving the authorization to access the information, cause a list of items to be presented via a presentation device, wherein the list of items presented is associated with a type of the information requested;
process a selection of an item listed;
determine that a location limit is associated with transmission of the selection of the item to an entity device from which the request was received, wherein the location limit defines a pre-defined distance between a first location of a merchant associated with the entity device and a second location of the at least one computing;
determine that the first location of the merchant associated with the entity device is within the pre-defined distance of the second location of the at least one computing device; and
cause the selection of the item to be transmitted to the entity device from which the request was received.
15. The system as recited in claim 14 , wherein the request includes a message body including a description of the request and a name of the merchant associated with the entity device from which the request was received.
16. The system as recited in claim 14 , wherein the item comprises at least a limited-use payment instrument that is generated by a payment provider or by the mobile wallet, the limited-use payment instrument having a predetermined number of allowable uses, wherein the one or more services are further configured to:
determine, after the selection of the limited-use payment instrument, that the predetermined number of allowable uses has been reached or exceeded; and
discard the limited-use payment instrument in response to determining that the predetermined number of allowable uses has been reached or exceeded.
17. The system as recited in claim 14 , wherein the one or more services are further configured to cause a secondary message to be transmitted from the at least one computing device to the entity device via at least one of a voice over internet protocol (VoIP) or a text-based messaging protocol to communicate an ad hoc response to the request.
18. The method as recited in claim 1 , further comprising:
outputting, by the mobile wallet application, a prompt to approve or to reject the request; and
receiving an instruction to approve the request prior to transmitting the selected item to the entity device.
19. The one or more non-transitory computer-readable media as recited in claim 7 , wherein the operations further comprise:
causing a prompt to approve or to reject the transmission of the at least one of the identified items to be output; and
confirming that an instruction to approve the transmission of the at least one of the identified items has been received prior to causing the at least one of the identified items to be transmitted to the entity device.
20. The system as recited in claim 14 , wherein the one or more services are further configured to:
output a prompt to approve or to reject the request; and
confirm that an instruction to approve the request has been received prior to causing the selection of the item to be transmitted to the entity device.
21. The system as recited in claim 14 , wherein the item is usable by the entity device to complete a data form.