Apparatuses, methods and systems for a universal payment integrator
View Patent ↗The APPARATUSES, METHODS AND SYSTEMS FOR A UNIVERSAL PAYMENT INTEGRATOR (hereinafter “UPI”) implement efficient and scalable monitoring, regulation, and allocation of computational processing, data, labor, and/or the like resources within an enterprise. The UPI may facilitate transactions by providing information for payments, money transfers, and/or the like to a wide variety of different banks and/or other financial institutions. Different banking institutions may have different informational needs and/or requirements in order to effectuate a payment. The UPI provides facilities that are integrated with enterprise data resources to allow quick, efficient, and tailored provision of the specific information needed to complete payments and clear transactions by different banks having different informational needs.
1. A universal payment integrating processor-implemented method, comprising:
registering a live online occurrence of a payment condition comprising a financial payment target identifier associated with a plurality of financial payment targets for different financial institutions;
querying a database using the financial payment target identifier to create a dynamic data-structure-tracking syntax-configured string associated with the financial payment targets, wherein the syntax-configured string consists of a plurality of component parts delimited by syntax separators, and where each part of the string tracks a separate data structure and reflects the hierarchical organizational structure for an enterprise;
utilizing the created dynamic data-structure tracking syntax-configured string and the financial payment target identifier to generate a request to at least one business grammar rule database containing a plurality of business grammar rules for the enterprise and the associated financial payment targets;
obtaining and evaluating at least one business grammar rule for the enterprise from the at least one business grammar rule database, and determining a plurality of additional payment data listings that need to be accessed based on the evaluated business grammar rule and the associated financial payment targets;
selectively evaluating and obtaining at least one universal data variable based on the associated financial payment targets, the additional payment data listings that need to be accessed based on said evaluation, and further based on a presence of user-defined associated universal variables for at least one payment table field, wherein the universal data variables comprise user-defined intermediate data objects that allow access and mapping of logically interrelated payment table fields in a plurality of disparate relational databases and external data sources containing enterprise-specific data and the financial payment targets data in a live online session, not requiring rebuilding of a full mapping between the fields in disparate relational databases, and wherein the universal data variables are organized into a hierarchical structure following a business grammar construct for the enterprise and each segment of the hierarchy follows a user-defined business grammar token type, and wherein the selective evaluation and use of the universal variables is also dependent on the evaluated business grammar rules for the enterprise and associated financial payment targets;
querying a payment data listing for each of a plurality of financial payment targets based on the financial payment target identifier and the evaluation of associated universal data variables linked to a plurality of payment data table fields for the associated financial payment targets;
retrieving the payment data listing for each of the plurality of financial payment targets based on the querying;
accessing payment data contained in the payment data table fields linked to the plurality of universal data variables utilized with the each payment data listing; and
providing accessed payment data to effectuate a payment associated with the payment condition for a plurality of financial payment targets for different financial institutions.
2. The method of claim 1 , wherein the payment condition is a payment request and registering occurrence of the payment condition further comprises:
receiving the payment request.
3. The method of claim 2 , wherein the payment request is received from the financial payment target.
4. The method of claim 1 , wherein the payment condition is a scheduled payment time and registering occurrence of the payment condition further comprises:
observing an occurrence of the scheduled payment time.
5. The method of claim 4 , wherein the scheduled payment time recurs periodically.
6. The method of claim 1 , wherein at least one of the financial payment targets is a bank.
7. The method of claim 6 , wherein the accessed payment data is provided to the bank to effectuate the payment associated with the payment condition.
8. The method of claim 1 , wherein at least one of the financial payment targets is a commercial counterparty.
9. The method of claim 8 wherein querying a payment data listing based on the financial payment target identifier further comprises:
querying a bank identifier based on the financial payment target identifier; and
querying a payment data listing based on the bank identifier.
10. The method of claim 8 wherein querying a payment data listing further comprises:
querying a descriptive business grammar configured string based on the financial payment target identifier; and
querying a payment data listing based on at least one token of the descriptive business grammar configured string.
11. The method of claim 1 , wherein the financial payment target identifier comprises a file transfer protocol address.
12. The method of claim 11 , wherein the file transfer protocol address is a secure file transfer protocol address.
13. The method of claim 1 , wherein providing accessed payment data further comprises:
configuring accessed payment data as a structured payment file.
14. The method of claim 13 , wherein the structured payment file is configured in accordance with configuration instructions associated with the financial payment target identifier.
15. The method of claim 13 , wherein the structured payment file comprises a fixed length file.
16. The method of claim 13 , wherein the structured payment file comprises a delimited file.
17. The method of claim 13 , wherein the structured payment file comprises an XML file.
18. The method of claim 13 , wherein the structured payment file comprises a spreadsheet file.
19. A universal payment integrating apparatus, comprising:
a memory;
a processor disposed in communication with said memory and configured to issue a plurality of processing instructions stored in the memory, wherein the processor issues instructions to:
register a live online occurrence of a payment condition comprising a financial payment target identifier associated with a plurality of financial payment targets for different financial institutions;
query a database using the financial payment target identifier to create a dynamic data-structure-tracking syntax-configured string associated with the financial payment targets, wherein the syntax-configured string consists of a plurality of component parts, delimited by syntax separators, and where each part of the string tracks a separate data structure and reflects the hierarchical organizational structure for an enterprise;
utilize the created dynamic data-structure tracking syntax-configured string and the financial payment target identifier to generate a request to at least one business grammar rule database containing a plurality of business grammar rules for the enterprise and the associated financial payment targets;
obtain and evaluate at least one business grammar rule for the enterprise from the at least one business grammar rule database, and determine a plurality of additional payment data listings that need to be accessed based on the evaluated business grammar rule and the associated financial payment targets;
selectively evaluate and obtain at least one universal data variable based on the associated financial payment targets, the additional payment data listings that need to be accessed based on said evaluation, and further based on a presence of user-defined associated universal variables for at least one payment table field, wherein the universal data variables comprise user-defined intermediate data objects that allow access and mapping of logically interrelated payment table fields in a plurality of disparate relational databases and external data sources containing enterprise-specific data and the financial payment targets data in a live online session, not requiring rebuilding of a full mapping between the fields in disparate relational databases, and wherein the universal data variables are organized into a hierarchical structure following a business grammar construct for the enterprise and each segment of the hierarchy follows a user-defined business grammar token type, and wherein the selective evaluation and use of the universal variables is also dependent on the evaluated business grammar rules for the enterprise and associated financial payment targets;
query a payment data listing for each of a plurality of financial payment targets based on the financial payment target identifier and the associated universal data variables linked to a plurality of payment data table fields for the associated financial payment targets; the payment data listing utilizing a plurality of universal data variables linked to a plurality of the payment data table fields in at least one database, wherein at least one of said universal data variables comprises an intermediate data object that allows access to a plurality of database relational structures, to disparate databases, and to external data sources, wherein at least one universal data variable provides database access query languages details and relational database organization structures and details necessary for accessing said database relational structure, and wherein at least one of said universal data variables is organized into a hierarchical structure comprising a family, a subfamily and a field name;
retrieve the payment data listing for each of the plurality of financial payment targets based on the querying;
access payment data contained in the payment data table fields linked to the plurality of universal data variables utilized with the each payment data listing; and
provide accessed payment data to effectuate a payment associated with the payment condition for a plurality of financial payment targets for different financial institutions.
20. A non-transitory processor readable storage medium for universal payment integration system and; comprising:
a plurality of processing instructions stored in the non-transitory storage medium and issuable by a processor to:
register a live online occurrence of a payment condition comprising a financial payment target identifier associated with a plurality of financial payment targets for different financial institutions;
query a database using the financial payment target identifier to create a dynamic data-structure-tracking syntax-configured string associated with the financial payment targets, wherein the syntax-configured string consists of a plurality of component parts, delimited by syntax separators, and where each part of the string tracks a separate data structure and reflects the hierarchical organizational structure for an enterprise;
utilize the created dynamic data-structure tracking syntax-configured string and the financial payment target identifier to generate a request to at least one business grammar rule database containing a plurality of business grammar rules for the enterprise and the associated financial payment targets;
obtain and evaluate at least one business grammar rule for the enterprise from the at least one business grammar rule database, and determine a plurality of additional payment data listings that need to be accessed based on the evaluated business grammar rule and the associated financial payment targets;
selectively evaluate and obtain at least one universal data variable based on the associated financial payment targets, the additional payment data listings that need to be accessed based on said evaluation, and further based on a presence of user-defined associated universal variables for at least one payment table field, wherein the universal data variables comprise user-defined intermediate data objects that allow access and mapping of logically interrelated payment table fields in a plurality of disparate relational databases and external data sources containing enterprise-specific data and the financial payment targets data in a live online session, not requiring rebuilding of a full mapping between the fields in disparate relational databases, and wherein the universal data variables are organized into a hierarchical structure following a business grammar construct for the enterprise and each segment of the hierarchy follows a user-defined business grammar token type, and wherein the selective evaluation and use of the universal variables is also dependent on the evaluated business grammar rules for the enterprise and associated financial payment targets;
query a payment data listing for each of a plurality of financial payment targets based on the financial payment target identifier and the associated universal data variables linked to a plurality of payment data table fields for the associated financial payment targets; the payment data listing utilizing a plurality of universal data variables linked to a plurality of the payment data table fields in at least one database;
retrieve the payment data listing for each of the plurality of financial payment targets based on the querying;
access payment data contained in the payment data table fields linked to the plurality of universal data variables utilized with each payment data listing;
comprising the payment data listing, wherein at least one of said universal data variables comprises an intermediate data object that allows access to a plurality of database relational structures, to disparate databases, and to external data sources, wherein at least one universal data variable provides database access query languages details and relational database organization structures and details necessary for accessing said database relational structure, and wherein at least one of said universal data variables is organized into a hierarchical structure comprising a family, a subfamily and a field name; and
provide accessed payment data to effectuate a payment associated with the payment condition for a plurality of financial payment targets for different financial institutions.
21. The method of claim 1 , wherein the data-structure-tracking syntax-configured strings are dynamically formed and are hierarchically organized through a user interface that defines the hierarchical organization and business grammar rules for each part of the string to track interrelated payment tables and data for the enterprise and the associated financial payment targets.
22. The storage medium of claim 21 , wherein the data-structure-tracking syntax-configured strings are dynamically formed and are hierarchically organized through a user interface that defines the hierarchical organization and business grammar rules for each part of the string to track interrelated payment tables and data for the enterprise and the associated financial payment targets.