Secure Digital Communications

1. A method for secure mobile wallet communications, the method comprising: using one or more processors: receiving a message from a second mobile wallet addressed to a first mobile wallet, the message including a portion encrypted with a private key of the second mobile wallet; retrieving a public key of the second mobile wallet; decrypting the portion with the public key to create a decrypted portion; determining that a hash of the message matches a data field containing a hash in the decrypted portion; responsive to determining that the hash of the message matches the hash in the decrypted portion, marking the message as having come from the second mobile wallet; sending a challenge to the second mobile wallet, the challenge requesting details about at least one of: account details of a user of the first mobile wallet, transaction details of the user of the first mobile wallet, a predetermined data field known to both the first and second mobile wallets, or driver's license information of the user of the first mobile wallet; receiving a challenge-response; determining whether the challenge-response includes a correct answer to the challenge; responsive to determining that the challenge-response includes the correct answer, marking the message from the second mobile wallet as authenticated; and presenting an indication that the message is authenticated and that the message came from the second mobile wallet.

2. The method of claim 1 , wherein retrieving the public key of the second mobile wallet comprises: contacting a public key server of a domain of the second mobile wallet.

3. The method of claim 1 , wherein retrieving the public key, decrypting the portion with the public key, determining that the hash of the message matches the hash in the decrypted portion, marking the message, and presenting the indication are done automatically in response to receiving the message.

4. The method of claim 1 , wherein at least one of: retrieving the public key, decrypting the portion with the public key, determining that the hash of the message matches the hash in the decrypted portion, marking the message, or presenting the indication is done upon receipt of a user request in response to receiving the message.

5. The method of claim 1 , wherein retrieving the public key, decrypting the portion with the public key, determining that the hash of the message matches the hash in the decrypted portion, marking the message, and presenting the indication are done automatically based upon determining that a type of the message is a predetermined type of message.

6. The method of claim 1 , comprising: receiving a second message from a third mobile wallet; determining that a hash of the second message does not match a hash in a decrypted portion of the second message; responsive to determining that the hash of the second message does not match the hash in the decrypted portion of the second message, marking the second message as suspicious; and presenting a second indication that the second message is unverified to the user.

7. A device for facilitating secure mobile wallet communications, the device comprising: a hardware processor; a memory comprising instructions that when performed by the processor, causes the processor to perform operations to at least: receive a message from a second mobile wallet addressed to a first mobile wallet, the message including a portion encrypted with a private key of the second mobile wallet; retrieve a public key of the second mobile wallet; decrypt the portion with the public key to create a decrypted portion; determine that a hash of the message matches a data field containing a hash in the decrypted portion; responsive to a determination that the hash of the message matches the hash in the decrypted portion, mark the message as having come from the second mobile wallet; send a challenge to the second mobile wallet, the challenge requesting details about at least one of: account details of a user of the first mobile wallet, transaction details of the user of the first mobile wallet, a predetermined data field known to both the first and second mobile wallets, or driver's license information of the user of the first mobile wallet; receive a challenge-response; determine whether the challenge-response includes a correct answer to the challenge; responsive to a determination that the challenge-response includes the correct answer, mark the message from the second mobile wallet as authenticated; and present an indication that the message is authenticated and that the message came from the second mobile wallet.

8. The device of claim 7 , wherein the operations to retrieve the public key of the second mobile wallet comprises operations to at least: contact a public key server of a domain of the second mobile wallet.

9. The device of claim 7 , wherein the operations to retrieve the public key, decrypt the portion with the public key, determine that the hash of the message matches the hash in the decrypted portion, mark the message, and present the indication done automatically in response to receipt of the message.

10. The device of claim 7 , wherein at least one of the operations to retrieve the public key, decrypt the portion with the public key, determine that the hash of the message matches the hash in the decrypted portion, mark the message, or present the indication is done upon receipt of a user request in response to a receipt of the message.

11. The device of claim 7 , wherein the operations to retrieve the public key, decrypt the portion with the public key, determine that the hash of the message matches the hash in the decrypted portion, mark the message, and present the indication done automatically based upon a determination that a type of the message is a predetermined type of message.

12. The device of claim 7 , wherein the operations further comprise operations to: receive a second message from a third mobile wallet; determine that a hash of the second message does not match a hash in a decrypted portion of the second message; responsive to the determination that the hash of the second message does not match the hash in the decrypted portion of the second message, mark the second message as suspicious; and present a second indication that the second message is unverified to the user.

13. A non-transitory machine readable medium for secure mobile wallet communications, the machine readable medium comprising instructions, which when performed by the machine, causes the machine to perform operations comprising: receiving a message from a second mobile wallet addressed to a first mobile wallet, the message including a portion encrypted with a private key of the second mobile wallet; retrieving a public key of the second mobile wallet; decrypting the portion with the public key to create a decrypted portion; determining that a hash of the message matches a data field containing a hash in the decrypted portion; responsive to determining that the hash of the message matches the hash in the decrypted portion, marking the message as having come from the second mobile wallet; sending a challenge to the second mobile wallet, the challenge requesting details about at least one of: account details of a user of the first mobile wallet, transaction details of the user of the first mobile wallet, a predetermined data field known to both the first and second mobile wallets, or driver's license information of the user of the first mobile wallet; receiving a challenge-response; determining whether the challenge-response includes a correct answer to the challenge; responsive to determining that the challenge-response includes the correct answer, marking the message from the second mobile wallet as authenticated; and presenting an indication that the message is authenticated and that the message came from the second mobile wallet.

14. The machine readable medium of claim 13 , wherein the operations of retrieving the public key of the second mobile wallet comprises the operations of: contacting a public key server of a domain of the second mobile wallet.

15. The machine readable medium of claim 13 , wherein the operations of retrieving the public key, decrypting the portion with the public key, determining that the hash of the message matches the hash in the decrypted portion, marking the message, or presenting the indication are done automatically in response to receiving the message.

16. The machine readable medium of claim 13 , wherein at least one of the operations of retrieving the public key, decrypting the portion with the public key, determining that the hash of the message matches the hash in the decrypted portion, marking the message, or presenting the indication is done upon receipt of a user request in response to receiving the message.

17. The machine readable medium of claim 13 , wherein the operations of retrieving the public key, decrypting the portion with the public key, determining that the hash f the message matches the hash in the decrypted portion, marking the message, and presenting the indication are done automatically based upon determining that a type of the message is a predetermined type of message.

18. The machine readable medium of claim 13 , wherein the operations further comprise: receiving a second message from a third mobile wallet; determining that a hash of the second message does not match a hash in a decrypted portion of the second message; responsive to determining that the hash of the second message does not match the hash in the decrypted portion of the second message, marking the second message as suspicious; and presenting an indication that the second message is unverified to the user.