Systems and methods for translating data read from proxy APIs into computing code

1. A method of automatically generating sample code for an application programming interface (API) for payment processing in a payment network, the method comprising:

detecting, by at least one processor, a change in acquirer processor-specific API data;

updating, by the at least one processor, a backend generator according to the detected change in the acquirer processor-specific API data;

reading, by the at least one processor, an acquirer processor-specific API enabling third party access to an acquirer processor's formats for payment processing in a payment network, using an acquirer processor-specific API reader;

generating, by the at least one processor, the acquirer processor-specific API data using the acquirer processor-specific API reader, the acquirer processor-specific API data describing the acquirer processor's formats for payment processing in the payment network;

passing, by the at least one processor, the acquirer processor-specific API data to a language-specific backend module;

converting, by the at least one processor, the acquirer processor-specific API data into a format compatible with an output generator using the language-specific backend module;

passing, by the at least one processor, the converted acquirer processor-specific API data and a language-specific template corresponding to the acquirer processor-specific API data to the output generator using the backend generator; and

generating, by the at least one processor, language-specific sample code by the output generator using the converted acquirer processor-specific API data and the language-specific template corresponding to the acquirer processor-specific API data.

2. The method of claim 1 , wherein the method is performed within a continuous integration system.

3. The method of claim 1 , further comprising:

validating the generated language-specific sample code; and

updating the backend generator according to a result of the validation.

4. The method of claim 3 , wherein the validation includes performing round-trip test transactions with an acquirer processor using configuration files and sample transaction data.

5. A computer system for automatically generating sample code for an application programming interface (API) for payment processing in a payment network, the computer system comprising:

a memory having processor-readable instructions stored therein; and

a processor configured to access the memory and execute the processor-readable instructions, which when executed by the processor configure the processor to perform a plurality of functions, including functions to:

detect a change in acquirer processor-specific API data;

update a backend generator according to the detected change in the acquirer processor-specific API data;

read an acquirer processor-specific API enabling third party access to an acquirer processor's formats for payment processing in a payment network, using an acquirer processor-specific API reader;

generate the acquirer processor-specific API data using the acquirer processor-specific API reader, the acquirer processor-specific API data describing the acquirer processor's formats for payment processing in the payment network;

pass the acquirer processor-specific API data to a language-specific backend module;

convert the acquirer processor-specific API data into a format compatible with an output generator using the language-specific backend module;

pass the converted acquirer processor-specific API data and a language-specific template corresponding to the acquirer processor-specific API data to the output generator using the backend generator; and

generate language-specific sample code by the output generator using the converted acquirer processor-specific API data and the language-specific template corresponding to the acquirer processor-specific API data.

6. The computer system of claim 5 , wherein the plurality of functions are performed within a continuous integration system.

7. The computer system of claim 5 , wherein the plurality of functions performed by the processor when executing the processor-readable instructions further includes functions to:

validate the generated language-specific sample code; and

update the backend generator according to a result of the validation.

8. The computer system of claim 7 , wherein the validation includes performing round-trip test transactions with an acquirer processor using configuration files and sample transaction data.

9. A non-transitory computer readable medium storing a program causing a computer to execute a method of automatically generating sample code for an application programming interface (API) for payment processing in a payment network, the method comprising:

detecting, by at least one processor, a change in acquirer processor-specific API data;

updating, by the at least one processor, a backend generator according to the detected change in the acquirer processor-specific API data;

reading, by the at least one processor, an acquirer processor-specific API enabling third party access to an acquirer processor's formats for payment processing in a payment network, using an acquirer processor-specific API reader;

generating, by the at least one processor, the acquirer processor-specific API data using the acquirer processor-specific API reader, the acquirer processor-specific API data describing the acquirer processor's formats for payment processing in the payment network;

passing, by the at least one processor, the acquirer processor-specific API data to a language-specific backend module;

converting, by the at least one processor, the acquirer processor-specific API data into a format compatible with an output generator using the language-specific backend module;

passing, by the at least one processor, the converted acquirer processor-specific API data and a language-specific template corresponding to the acquirer processor-specific API data to the output generator using the backend generator; and

generating, by the at least one processor, language-specific sample code by the output generator using the converted acquirer processor-specific API data and the language-specific template corresponding to the acquirer processor-specific API data.

10. The non-transitory computer readable medium of claim 9 , wherein the method is performed within a continuous integration system.

11. The non-transitory computer readable medium of claim 9 , the method further comprising:

validating the generated language-specific sample code; and

updating the backend generator according to a result of the validation.

12. The non-transitory computer readable medium of claim 11 , wherein the validation includes performing round-trip test transactions with an acquirer processor using configuration files and sample transaction data.

13. A computer system for automatically generating sample code for an application programming interface (API) for payment processing in a payment network, the computer system comprising:

a memory;

at least one processor;

a backend generator configured to:

detect, by the at least one processor, a change in acquirer processor-specific API data;

update, by the at least one processor, a backend generator according to the detected change in the acquirer processor-specific API data;

read, by the at least one processor, an acquirer processor-specific API enabling third party access to an acquirer processor's formats for payment processing in a payment network using an acquirer processor-specific API reader;

generate, by the at least one processor, the acquirer processor-specific API data using the acquirer processor-specific API reader, the acquirer processor-specific API data describing the acquirer processor's formats for payment processing in the payment network;

pass, by the at least one processor, the acquirer processor-specific API data to a language-specific backend module;

convert, by the at least one processor, the acquirer processor-specific API data into a format compatible with an output generator using the language-specific backend module;

pass, by the at least one processor, the converted acquirer processor-specific API data and a language-specific template corresponding to the acquirer processor-specific API data to the output generator using the backend generator; and

an output generator configured to:

generate, by the at least one processor, language-specific sample code using the converted acquirer processor-specific API data and the language-specific template corresponding to the acquirer processor-specific API data.

14. The computer system of claim 13 , wherein the backend generator and the output generator operate within a continuous integration system.

15. The computer system of claim 13 , wherein the output generator is further configured to:

validate the generated language-specific sample code; and

update the backend generator according to a result of the validation.

16. The computer system of claim 15 , wherein the validation includes performing round-trip test transactions with an acquirer processor using configuration files and sample transaction data.