Resource distribution hub generation on a mobile device
US-2020351852-A1 · Nov 5, 2020 · US
US12597016B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12597016-B2 |
| Application number | US-202016808530-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 4, 2020 |
| Priority date | Mar 4, 2020 |
| Publication date | Apr 7, 2026 |
| Grant date | Apr 7, 2026 |
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 are disclosed for performing an electronic transaction using a hosted transaction page. One method comprises providing a hosted transaction page to a first data system, the hosted transaction page enabling the first data system to request an electronic transaction. Via the hosted transaction page, authentication data may be received from a user. The received authentication data may be encoded into a first format and tokenized into tokenized authentication data. The tokenized authentication data may then be transmitted to the first data system. An authorization request for performing the electronic transaction based on the tokenized authentication data may be received from the first data system, then transmitted to a second data system.
Opening claim text (preview).
What is claimed is: 1 . A method for performing an electronic transaction using a hosted transaction page, comprising: providing the hosted transaction page to a first data system, the hosted transaction page enabling the first data system to request an electronic transaction; receiving, via embedded frames of the hosted transaction page, authentication data from a user; upon receiving the authentication data, encoding the authentication data into a first format by the embedded frames of the hosted transaction page executing a programming language on the authentication data, wherein the first format is an encrypted format; validating the encoded authentication data in the first format and tokenizing the encoded authentication data in the first format into tokenized authentication data, wherein the tokenized authentication data is a low value token usable for a pre-determined amount of time or a high value token usable for recurring transactions; transmitting the tokenized authentication data to the first data system; receiving, from the first data system, an authorization request for performing the electronic transaction based on the tokenized authentication data; and transmitting the authorization request to a second data system. 2 . The method of claim 1 , further comprising: detokenizing the tokenized authentication data into the authentication data in the first format; and transmitting the authentication data in the first format to the second data system. 3 . The method of claim 2 , further comprising: receiving an authorization response, generated based on the authentication data in the first format, from the second data system; and transmitting the authorization response to the first data system. 4 . The method of claim 1 , wherein the embedded frame is configured to load and display content independent of the hosted transaction page. 5 . The method of claim 1 , wherein the authentication data includes at least one of: a personal identification number and a personal account number. 6 . The method of claim 1 , wherein the second data system comprises an Electronic Benefits Transfer (EBT) payment network. 7 . A system comprising: one or more computer readable media storing instructions for performing an electronic transaction using a hosted transaction page; and one or more processors configured to execute the instructions to perform operations comprising: providing the hosted transaction page to a first data system, the hosted transaction page enabling the first data system to request an electronic transaction; receiving, via embedded frames of the hosted transaction page, authentication data from a user; upon receiving the authentication data, encoding the authentication data into a first format by the embedded frames of the hosted transaction page executing a programming language on the authentication data, wherein the first format is an encrypted format; validating the encoded authentication data in the first format and tokenizing the encoded authentication data in the first format into tokenized authentication data, wherein the tokenized authentication data is a low value token usable for a pre-determined amount of time or a high value token usable for recurring transactions; transmitting the tokenized authentication data to the first data system; receiving, from the first data system, an authorization request for performing the electronic transaction based on the tokenized authentication data; and transmitting the authorization request to a second data system. 8 . The system of claim 7 , the operations further comprising: detokenizing the tokenized authentication data into the authentication data in the first format; and transmitting the authentication data in the first format to the second data system. 9 . The system of claim 8 , the operations further comprising: receiving an authorization response, generated based on the authentication data in the first format, from the second data system; and transmitting the authorization response to the first data system. 10 . The system of claim 7 , wherein the embedded frame is configured to load and display content independent of the hosted transaction page. 11 . The system of claim 7 , wherein the authentication data includes at least one of: a personal identification number and a personal account number. 12 . The system of claim 7 , wherein the second data system comprises an Electronic Benefits Transfer (EBT) payment network. 13 . A non-transitory computer-readable medium storing instructions for performing an electronic transaction using a hosted transaction page, the instructions, when executed by one or more processors, causing the one or more processors to perform operations comprising: providing the hosted transaction page to a first data system, the hosted transaction page enabling the first data system to request an electronic transaction; receiving, via embedded frames of the hosted transaction page, authentication data from a user; upon receiving the authentication data, encoding the authentication data into a first format by the embedded frames of the hosted transaction page executing a programming language on the authentication data, wherein the first format is an encrypted format; validating the encoded authentication data in the first format and tokenizing the encoded authentication data in the first format into tokenized authentication data, wherein the tokenized authentication data is a low value token usable for a pre-determined amount of time or a high value token usable for recurring transactions; transmitting the tokenized authentication data to the first data system; receiving, from the first data system, an authorization request for performing the electronic transaction based on the tokenized authentication data; and transmitting the authorization request to a second data system. 14 . The non-transitory computer-readable medium of claim 13 , the operations further comprising: detokenizing the tokenized authentication data into the authentication data in the first format; and transmitting the authentication data in the first format to the second data system. 15 . The non-transitory computer-readable medium of claim 14 , the operations further comprising: receiving an authorization response, generated based on the authentication data in the first format, from the second data system; and transmitting the authorization response to the first data system. 16 . The non-transitory computer-readable medium of claim 13 , wherein the embedded frame is configured to load and display content independent of the hosted transaction page. 17 . The non-transitory computer-readable medium of claim 13 , wherein the authentication data includes at least one of: a personal identification number and a personal account number. 18 . The method of claim 1 , wherein one or more fields in the embedded frames receiving the authentication data are masked with encrypted data before displaying to the user for confirmation of the electronic transaction, and wherein the authentication data includes sensitive user data for validating the electronic transaction. 19 . The method of claim 1 , further comprising: verifying the tokenized authentication data by comparing the tokenized authentication data with a stored tokenized data. 20 . The method of claim 1 , wherein the tokenized authentication data is unique per electronic transaction, and wherein the tokenized authentication data is
using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807) · CPC title
Verifying personal identification numbers [PIN] · CPC title
Government or public services (business processes related to the transportation industry G06Q50/40) · CPC title
Business processing using cryptography · CPC title
using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.