Method, System, and Computer Program Product for Dynamic Development of an Application Programming Interface

Abstract

A method for dynamic development of an application programming interface (API) including: receiving a first data file; generating an API configured to receive client data associated with a transaction message, where the generating the API includes: providing a data agnostic template; for each specific data parameter of the plurality of specific data parameters, assigning each template field with a corresponding specific data entry associated with the specific data parameter; and configuring a second user interface associated with the API by associating at least one display parameter with each specific data parameter of the plurality of specific data parameters; and displaying the second user interface such that a field displayed by the second user interface is configured to receive the data associated with each specific data parameter of the plurality of specific data parameters.

What is claimed is: 
     
         1 . A method for processing a transaction associated with an onboarded acquirer system, comprising:
 onboarding, with at least one processor, a first acquirer system associated with an acquirer by:
 receiving, with at least one processor and from the first acquirer system, a first data file comprising a plurality of data entries, wherein the plurality of data entries comprise static transaction data associated with the first acquirer system; and 
 generating, with at least one processor, a second data file having a predetermined format, the second data file comprising at least a portion of the static transaction data; and 
 storing, with at least one processor, the second data file; 
   receiving, with at least one processor and from the first acquirer system, an abbreviated transaction message associated with a payment transaction, wherein the abbreviated transaction message comprises dynamic data associated with the payment transaction;   in response to receiving the abbreviated transaction message, determining, with at least one processor, that the acquirer system associated with the payment transaction is the first acquirer system;   generating, with at least one processor, an authorization request, wherein the authorization request comprises at least a portion of the dynamic data from the abbreviated transaction request and at least a portion of the static transaction data from the stored second data file; and   communicating, with at least one processor, the authorization request to an issuer system to cause the issuer system to generate an authorization decision associated with the payment transaction.   
     
     
         2 . The method of  claim 1 , wherein the static transaction data comprises an identifier associated with the first acquirer system, and the abbreviated transaction message comprises the identifier. 
     
     
         3 . The method of  claim 2 , wherein the acquirer system associated with the payment transaction is determined based on the identifier from the abbreviated transaction message. 
     
     
         4 . The method of  claim 1 , wherein the dynamic transaction data comprises transaction data that can be different from transaction to transaction for the first acquirer system. 
     
     
         5 . The method of  claim 1 , wherein the static transaction data comprises transaction data that does not change for the first acquirer system from transaction to transaction. 
     
     
         6 . The method of  claim 1 , wherein the abbreviated transaction message does not comprise at least a portion of the static data from the stored second data file. 
     
     
         7 . The method of  claim 1 , wherein the dynamic data from the abbreviated transaction request and the static transaction data from the stored second data file comprise at least one data element associated with data elements defined by ISO 8583. 
     
     
         8 . A system for processing a transaction associated with an onboarded acquirer system comprising at least one processor programmed or configured to:
 onboard a first acquirer system associated with an acquirer by:
 receiving, from the first acquirer system, a first data file comprising a plurality of data entries, wherein the plurality of data entries comprise static transaction data associated with the first acquirer system; and 
 generating a second data file having a predetermined format, the second data file comprising at least a portion of the static transaction data; and 
 storing the second data file; 
   receive, from the first acquirer system, an abbreviated transaction message associated with a payment transaction, wherein the abbreviated transaction message comprises dynamic data associated with the payment transaction;   in response to receiving the abbreviated transaction message, determine that the acquirer system associated with the payment transaction is the first acquirer system;   generate an authorization request, wherein the authorization request comprises at least a portion of the dynamic data from the abbreviated transaction request and at least a portion of the static transaction data from the stored second data file; and   communicate the authorization request to an issuer system to cause the issuer system to generate an authorization decision associated with the payment transaction.   
     
     
         9 . The system of  claim 8 , wherein the static transaction data comprises an identifier associated with the first acquirer system, and the abbreviated transaction message comprises the identifier. 
     
     
         10 . The system of  claim 9 , wherein the acquirer system associated with the payment transaction is determined based on the identifier from the abbreviated transaction message. 
     
     
         11 . The system of  claim 8 , wherein the dynamic transaction data comprises transaction data that can be different from transaction to transaction for the first acquirer system. 
     
     
         12 . The system of  claim 8 , wherein the static transaction data comprises transaction data that does not change for the first acquirer system from transaction to transaction. 
     
     
         13 . The system of  claim 8 , wherein the abbreviated transaction message does not comprise at least a portion of the static data from the stored second data file. 
     
     
         14 . The system of  claim 8 , wherein the dynamic data from the abbreviated transaction request and the static transaction data from the stored second data file comprise at least one data element associated with data elements defined by ISO 8583. 
     
     
         15 . A computer program product for processing a transaction associated with an onboarded acquirer system, the computer program product comprising at least one non-transitory computer-readable medium including one or more instructions that, when executed by at least one processor, cause the at least one processor to:
 onboard a first acquirer system associated with an acquirer by:
 receiving, from the first acquirer system, a first data file comprising a plurality of data entries, wherein the plurality of data entries comprise static transaction data associated with the first acquirer system; and 
 generating a second data file having a predetermined format, the second data file comprising at least a portion of the static transaction data; and 
 storing the second data file; 
   receive, from the first acquirer system, an abbreviated transaction message associated with a payment transaction, wherein the abbreviated transaction message comprises dynamic data associated with the payment transaction;   in response to receiving the abbreviated transaction message, determine that the acquirer system associated with the payment transaction is the first acquirer system;   generate an authorization request, wherein the authorization request comprises at least a portion of the dynamic data from the abbreviated transaction request and at least a portion of the static transaction data from the stored second data file; and   communicate the authorization request to an issuer system to cause the issuer system to generate an authorization decision associated with the payment transaction.   
     
     
         16 . The computer program product of  claim 15 , wherein the static transaction data comprises an identifier associated with the first acquirer system, and the abbreviated transaction message comprises the identifier. 
     
     
         17 . The computer program product of  claim 16 , wherein the acquirer system associated with the payment transaction is determined based on the identifier from the abbreviated transaction message. 
     
     
         18 . The computer program product of  claim 15 , wherein the dynamic transaction data comprises transaction data that can be different from transaction to transaction for the first acquirer system. 
     
     
         19 . The computer program product of  claim 15 , wherein the static transaction data comprises transaction data that does not change for the first acquirer system from transaction to transaction. 
     
     
         20 . The computer program product of  claim 15 , wherein the abbreviated transaction message does not comprise at least a portion of the static data from the stored second data file.