US 12,033,122 B2
Systems and methods for configuring serverless authorization stream access (ASA) for virtual bank account transactions
Kamil Sindi, New Canaan, CT (US); Jason William Kruse, Portland, OR (US); Jonathan Andrew Oei, Pacific Palisades, CA (US); and Zhengyang Cong, New York, NY (US)
Assigned to Lithic, Inc., New York, NY (US)
Filed by Lithic, Inc., New York, NY (US)
Filed on Jul. 7, 2022, as Appl. No. 17/859,977.
Prior Publication US 2024/0013177 A1, Jan. 11, 2024
Int. Cl. G06Q 20/10 (2012.01); G06Q 20/08 (2012.01); G06Q 20/40 (2012.01)
CPC G06Q 20/108 (2013.01) [G06Q 20/0855 (2013.01); G06Q 20/401 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method comprising, by one or more servers associated with a receiver processor platform:
receiving, by the receiver processor platform, from a server of a payment processor, via an assisted code deployment API provided by the receiver processor platform, a request by the payment processor for the receiver processor platform to launch an authorization system utilizing a customized authorization stream access (ASA) transaction schema based on customized authorization source code, wherein the customized ASA transaction schema and customized authorization source code are unique to the payment processor, wherein the request comprises a plurality of custom source code snippets generated by the payment processor associated with a plurality of customized schema parameters for the customized ASA transaction schema based on the customized authorization source code, wherein the customized ASA transaction schema based on the customized authorization source code enables the payment processor to issue a plurality of virtual bank accounts (VBANs) to one or more users associated with the payment processor, and wherein the customized ASA transaction schema based on the customized authorization source code is configured to generate, by the receiver processor platform, for each VBAN issued by the payment processor, a transaction resource configuration based on the customized ASA transaction schema based on the customized authorization source code, and authorize, for each VBAN, transaction authorization requests based on the corresponding transaction resource configuration, each transaction authorization request being associated with a request to transfer resources to a receiving entity from the user associated with the payment processor and the VBAN;
retrieving, by the receiver processor platform, from a database associated with the receiver processor platform, a pre-configured ASA transaction schema comprising a plurality of source code modules and source code functions based on a plurality of pre-configured schema parameters;
generating, by the receiver processor platform, the customized authorization source code unique to the payment processor by integrating the plurality of custom source code snippets associated with the plurality of customized schema parameters into the plurality of source code modules and source code functions of the pre-configured ASA transaction schema to generate the customized authorization source code unique to the payment processor;
generating, by the receiver processor platform, the customized ASA transaction schema unique to the payment processor based on the customized authorization source code;
launching, by the receiver processor platform, the authorization system utilizing the customized ASA transaction schema based on the customized authorization source code in a system working environment of the receiver processor platform;
activating, by the receiver processor platform, via the database associated with the receiver processor platform, the customized ASA transaction schema unique to the payment processor based on the customized authorization source code, wherein activating the customized ASA transaction schema enables the payment processor to issue the plurality of VBANs;
receiving, from a third-party server, a transaction authorization request to authorize a first transaction associated with a first VBAN, wherein the first VBAN is issued by the payment processor based on the customized ASA transaction schema unique to the payment processor;
determining, for the first VBAN, based on a corresponding first transaction resource configuration generated by the receiver processor platform based on the customized ASA transaction schema based on the customized authorization source code, whether one or more authorization parameters of the first transaction resource configuration corresponding to the first VBAN are satisfied; and
transmitting, to the third-party server, responsive to determining whether the one or more authorization parameters of the first transaction resource configuration are satisfied, a transaction authorization response indicating whether the first transaction is authorized.