Electronic receipt dispensing system and method
US-2024338665-A1 · Oct 10, 2024 · US
US10380583B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-10380583-B1 |
| Application number | US-201313831563-A |
| Country | US |
| Kind code | B1 |
| Filing date | Mar 14, 2013 |
| Priority date | Dec 17, 2012 |
| Publication date | Aug 13, 2019 |
| Grant date | Aug 13, 2019 |
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.
A computer-implemented system and method that includes receiving via a messaging hub a code and an identifier for a merchant from a first financial institution, determining, by the messaging hub, a second financial institution based at least partially on the code, sending the code and the merchant identifier to the second financial institution, and receiving from the second financial institution account information to be sent to the first financial institution. The system and method includes sending the account information to the first financial institution to allow the first financial institution to process the payment from an account held by a payor to an account held by the merchant.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for processing a mobile wallet transaction between a merchant and a payor, the method performed by one or more processors of a messaging hub computer system, the method comprising: receiving, by the messaging hub computer system, a request for a dynamic token on behalf of a payor, the request for the dynamic token including an identifier associated with a second financial institution of a plurality of second financial institutions and a payment identifier; routing, by the messaging hub computer system, the request to a second financial institution computing system associated with the second financial institution to facilitate generation of the dynamic token; receiving, by the messaging hub computer system, a message including the dynamic token from a first financial institution computer system associated with the merchant, the first financial institution computing system being associated with a first financial institution, the dynamic token including a code comprising encoded account information of the payor associated with an account held by the payor with the second financial institution, wherein the message includes a merchant identifier identifying the merchant; decoding, by a validator of the messaging hub computer system, the code included with the dynamic token; matching, by the validator of messaging hub computer system, the decoded code with information in a table that identifies the second financial institution; identifying, by the validator of messaging hub computer system, the second financial institution from the plurality of second financial institutions based on the decoding and the matching; routing, by the messaging hub computer system, the dynamic token and the merchant identifier to the second financial institution computer system responsive to identifying the second financial institution; receiving, by the messaging hub computer system from the second financial institution computer system, the account information for the account held by the payor, the account information obtained based on decoding the encoded account information included in the dynamic token; routing, by the messaging hub computer system, the account information to the first financial institution computer system, thereby enabling the first financial institution to process a payment from the account held by the payor to an account held by the merchant as part of the mobile wallet transaction; receiving, by the messaging hub computer system, an indication of whether the mobile wallet transaction has been approved or denied from the first financial institution computer system; and facilitating, by the messaging hub computer system, a display of the indication on a mobile device associated with the payor. 2. The method of claim 1 , wherein the dynamic token is formatted to be compatible with messaging hub requirements. 3. The method of claim 1 , wherein the dynamic token is displayable as a QR code that is scannable by one of a point of sale device of the merchant and the mobile device of the payor. 4. The method of claim 1 , wherein routing the account information to the first financial institution computer system enables the payment to be processed without transmitting the account information to either the payor or the merchant. 5. The method of claim 1 , wherein any merchant devices and any payor devices fail to receive the account information. 6. The method of claim 1 , wherein the account information is not shared between the payor and the merchant. 7. A messaging hub computer system, comprising: one or more processors; and machine readable storage media coupled to the one or more processors and having instructions stored therein that are executable by the one or more processors to process a mobile wallet transaction between a payor and a merchant, the instructions when executed by the one or more processors cause the one or more processors to: receive a request for a dynamic token on behalf of the payor, the request for the dynamic token including an identifier associated with a second financial institution from a plurality of second financial institutions and a payment identifier; route the request to a second financial institution computing system associated with the second financial institution for generation of the dynamic token; receive a message from a first financial institution, the message including a merchant identifier associated with the merchant and the dynamic token, the dynamic token including a code comprising encoded account information for the payor associated with an account held by the payor with the second financial institution; decode the code included with the dynamic token; match the decoded code with information in a table that identifies the second financial institution; identify the second financial institution from the plurality of second financial institutions based on the decoding and the matching; responsive to identifying the second financial institution, route the dynamic token and the merchant identifier to the second financial institution computer system; receive, from the second financial institution, the account information for the account held by the payor, the account information obtained based on decoding the encoded account information included in the dynamic token; route the account information to the first financial institution, enabling the first financial institution to process a payment from the account held by the payor to an account held by the merchant as part of the mobile wallet transaction; receive an indication of whether the mobile wallet transaction has been approved or denied from the first financial institution; and facilitate a display of the indication on a mobile device associated with the payor. 8. The computer system of claim 7 , wherein the dynamic token is formatted to be compatible with messaging hub requirements. 9. The computer system of claim 7 , wherein the dynamic token is displayable as a QR code that is scannable by one of a point of sale device of the merchant and the mobile device of the payor. 10. The computer system of claim 7 , wherein routing the account information to the first financial institution enables the payment to be processed without transmitting the account information to either the payor or the merchant. 11. The computer system of claim 7 , wherein any merchant devices and any payor devices fail to receive the account information. 12. The computer system of claim 7 , wherein the account information is not shared between the payor of the mobile wallet account and the merchant. 13. A computer-implemented method performed by one or more processors of a messaging hub computer system to process a mobile wallet transaction of a payor at a merchant, the method comprising: receiving, by the messaging hub computer system, a request for a dynamic token, the request for the dynamic token including an identifier associated with a second financial institution of a plurality of second financial institutions and a payment identifier; routing, by the messaging hub computer system, the request to a second financial institution computing system associated with the second financial institution for generation of the dynamic token; receiving, by the messaging hub computer system, a message from a first financial institution computer system associated with the merchant, the message including a merchant identifier associated with the merchant and the dynamic token, the dynamic token including a code comprising encoded account information of the payor associated with an account held by the payor with the second financial institut
using electronic wallets or electronic money safes · CPC title
Point-of-sale [POS] network systems · CPC title
insuring higher security of transaction · CPC title
specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems · CPC title
Payment circuits · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.