Wireless peer to peer mobile wallet connections
US-10057225-B1 · Aug 21, 2018 · US
US12277235B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12277235-B2 |
| Application number | US-202318214848-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 27, 2023 |
| Priority date | Dec 12, 2018 |
| Publication date | Apr 15, 2025 |
| Grant date | Apr 15, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for peer-to-peer secure document exchange are disclosed. The system may allow a document provider to securely transmit a certified document to a document verifier using decentralized storage. The verifier system may generate a session key pair and transmit the session public key to a trusted API provider. The trusted API provider may generate a session nonce. The verifier system may transmit the session nonce to the provider system. The provider system may use the session nonce to retrieve the session public key. The provider system may encrypt a certified document using the session public key and store the encrypted certified document in the decentralized storage. The verifier system may retrieve the encrypted certified document by polling the trusted API provider based on the session nonce. The verifier system may decrypt the encrypted certified document using the session private key.
Opening claim text (preview).
Therefore, the following is claimed: 1. A method, comprising: receiving, by a Trusted Application Programming Interface (API) Provider, an invocation from a provider system; receiving, by the Trusted API Provider, a polling request comprising a session nonce from a verifier system; retrieving, by the Trusted API Provider, a session document locator based at least in part on the session nonce in response to receiving the polling request; and storing, by the Trusted API Provider, the session document locator associated with the session nonce in response to the invocation by the provider system. 2. The method of claim 1 , further comprising retrieving, by the Trusted API Provider in response to retrieving the session document locator, an encrypted certified document by sending a query to a decentralized storage system, the query being based at least in part on the session document locator. 3. The method of claim 1 , further comprising sending, by the Trusted API Provider, the encrypted certified document to the verifier system. 4. The method of claim 2 , wherein the decentralized storage system comprises a blockchain. 5. The method of claim 1 , further comprising: generating, by the Trusted API Provider, the session nonce; receiving, from the verifier system by the Trusted API Provider, a session public key; and storing, by the Trusted API Provider, the session nonce and the session public key to a decentralized storage system. 6. The method of claim 1 , wherein generating the session nonce further comprises adding, by the Trusted API Provider, a timestamp to the session nonce, the timestamp indicating an expiration for the session nonce. 7. The method of claim 1 , wherein the session nonce comprises an alphanumeric string of characters. 8. A non-transitory computer-readable storage medium tangibly encoded with computer executable instructions, that when executed by a computing device, perform a method comprising: receiving, by a Trusted Application Programming Interface (API) Provider, an invocation from a provider system; receiving, by the Trusted API Provider, a polling request comprising a session nonce from a verifier system; retrieving, by the Trusted API Provider, a session document locator based at least in part on the session nonce in response to receiving the polling request; and storing, by the Trusted API Provider, the session document locator associated with the session nonce in response to the invocation by the provider system. 9. The non-transitory computer-readable storage medium of claim 8 , further comprising retrieving, by the Trusted API Provider in response to retrieving the session document locator, an encrypted certified document by sending a query to a decentralized storage system, the query being based at least in part on the session document locator. 10. The non-transitory computer-readable storage medium of claim 8 , further comprising sending, by the Trusted API Provider, the encrypted certified document to the verifier system. 11. The non-transitory computer-readable storage medium of claim 9 , wherein the decentralized storage system comprises a blockchain. 12. The non-transitory computer-readable storage medium of claim 8 , further comprising: generating, by the Trusted API Provider, the session nonce; receiving, from the verifier system by the Trusted API Provider, a session public key; and storing, by the Trusted API Provider, the session nonce and the session public key to a decentralized storage system. 13. The non-transitory computer-readable storage medium of claim 8 , wherein generating the session nonce further comprises adding, by the Trusted API Provider, a timestamp to the session nonce, the timestamp indicating an expiration for the session nonce. 14. The non-transitory computer-readable storage medium of claim 8 , wherein the session nonce comprises an alphanumeric string of characters. 15. A computer system comprising: a processor; and a non-transitory memory configured to communicate with the processor, the non-transitory memory having instructions stored thereon that when executed by the processor cause the processor to perform operations comprising: receiving, by a Trusted Application Programming Interface (API) Provider, an invocation from a provider system; receiving, by the Trusted API Provider, a polling request comprising a session nonce from a verifier system; retrieving, by the Trusted API Provider, a session document locator based at least in part on the session nonce in response to receiving the polling request; and storing, by the Trusted API Provider, the session document locator associated with the session nonce in response to the invocation by the provider system. 16. The computer system of claim 15 , further comprising retrieving, by the Trusted API Provider in response to retrieving the session document locator, an encrypted certified document by sending a query to a decentralized storage system, the query being based at least in part on the session document locator. 17. The computer system of claim 15 , further comprising sending, by the Trusted API Provider, the encrypted certified document to the verifier system. 18. The computer system of claim 15 , further comprising: generating, by the Trusted API Provider, the session nonce; receiving, from the verifier system by the Trusted API Provider, a session public key; and storing, by the Trusted API Provider, the session nonce and the session public key to a decentralized storage system. 19. The computer system of claim 15 , wherein generating the session nonce further comprises adding, by the Trusted API Provider, a timestamp to the session nonce, the timestamp indicating an expiration for the session nonce. 20. The computer system of claim 15 , wherein the session nonce comprises an alphanumeric string of characters.
Interprogram communication · CPC title
Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy · CPC title
involving a third party or a trusted authority · CPC title
using hash chains, e.g. blockchains or hash trees · CPC title
involving time stamps, e.g. generation of time stamps · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.