US 12,456,126 B2
Systems and processes that augment transparency of transaction data
Gerardo Trevino Rojas, W Lake Hills, TX (US)
Assigned to Paybook, Inc., W Lake Hills, TX (US)
Appl. No. 17/635,341
Filed by Paybook, Inc., W Lake Hills, TX (US)
PCT Filed Aug. 13, 2020, PCT No. PCT/US2020/046215
§ 371(c)(1), (2) Date Feb. 14, 2022,
PCT Pub. No. WO2021/030609, PCT Pub. Date Feb. 18, 2021.
Claims priority of provisional application 62/886,808, filed on Aug. 14, 2019.
Prior Publication US 2022/0277321 A1, Sep. 1, 2022
Int. Cl. G06Q 30/0201 (2023.01); G06Q 20/38 (2012.01); G06Q 50/00 (2024.01)
CPC G06Q 30/0201 (2013.01) [G06Q 20/3827 (2013.01); G06Q 50/01 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method comprising:
receiving, by one or more servers of a transaction management platform and from a user device of an authorized user of the transaction management platform, an indication of a financial account of an entity at a financial institution;
determining, by the one or more servers of the transaction management platform and based at least in part on data associated with the financial account and without further user input, a jurisdiction of the financial account;
determining, by the one or more servers of the transaction management platform and based at least in part on an application of rules and the jurisdiction, whether to use (1) the transaction management platform as an interface to the financial institution or (2) a third party device as the interface to the financial institution;
transmitting, by the interface to the financial institution, financial account credentials for the financial account and an authorization token for the financial institution;
receiving, by the interface and from the financial institution, the authorization token, wherein receiving the authorization token comprises receiving the authorization token via communication with the third party device or performing a handshake internally with a syncing application programming interface (API) associated with the one or more servers;
storing, by the interface, the authorization token;
transmitting, by the interface and to the financial institution, the authorization token and a request for transaction data associated with the financial account, wherein the transaction data is associated with one or more financial transactions;
responsive to a determination by an API associated with the financial institution that the authorization token is valid, receiving, by the interface and from the financial institution, the transaction data;
transmitting, by the interface to the syncing API, the transaction data;
generating, by the syncing API, an authenticating token;
storing, by the one or more servers, the transaction data and the authenticating token; and
based at least in part on receiving an instruction from the authorized user, publishing, by the one or more servers of the transaction management platform, the transaction data to create published transaction data, wherein publishing comprises allowing access to at least a portion of the transaction data.