Systems and methods for translating data read from proxy APIs into computing code
A method for automatically generating sample code for an API for payment processing in a payment network includes reading an acquirer processor-specific API for payment processing in a payment network using an acquirer processor-specific API reader, generating acquirer processor-specific API data using the acquirer processor-specific API reader, converting the acquirer processor-specific API data into a format compatible with an output generator, and generating language-specific sample code by the output generator using the converted acquirer processor-specific API data and a language-specific template.
1. A method of automatically generating code for an application programming interface (API) for electronic transactions processing in an electronic transactions network, the method comprising:
receiving API specification information corresponding to the API of a particular acquirer processor;
generating API data that is specific to the particular acquirer processor and that describes the API, based on the API specification information; and
generating the code for the API for the electronic transactions processing in the electronic transactions network, by using a backend generator to pass the API data and a language-specific template corresponding to the API data to an output generator.
2. The method of claim 1 , further comprising:
detecting a change in the API specification information,
wherein the generating the code for the API comprises generating the code for the API, based on detecting the change in the API specification information.
3. The method of claim 1 , wherein the code enables a merchant to interact with the particular acquirer processor.
4. The method of claim 1 , wherein the API specification information is API specification documents.
5. The method of claim 1 , wherein the code for the API is specific to a particular process flow between a payment platform and the particular acquirer processor.
6. The method of claim 5 , wherein the particular process flow includes at least one of cardholder authentication, transaction submission, fraud detection, or transaction reversal.
7. A device for automatically generating code for an application programming interface (API) for electronic transactions processing in an electronic transactions network, the device comprising:
a memory configured to store instructions; and
a processor configured to execute the instructions to perform operations comprising:
receiving API specification information corresponding to the API of a particular acquirer processor;
generating API data that is specific to the particular acquirer processor and that describes the API, based on the API specification information; and
generating the code for the API for the electronic transactions processing in the electronic transactions network, by using a backend generator to pass the API data and a language-specific template corresponding to the API data to an output generator.
8. The device of claim 7 , wherein the operations further comprise:
detecting a change in the API specification information,
wherein the generating the code for the API comprises generating the code for the API, based on detecting the change in the API specification information.
9. The device of claim 7 , wherein the code enables a merchant to interact with the particular acquirer processor.
10. The device of claim 7 , wherein the API specification information is API specification documents.
11. The device of claim 7 , wherein the code for the API is specific to a particular process flow between a payment platform and the particular acquirer processor.
12. The device of claim 11 , wherein the particular process flow includes at least one of cardholder authentication, transaction submission, fraud detection, or transaction reversal.
13. A non-transitory computer-readable medium storing instructions that, when executed by a processor for automatically generating code for an application programming interface (API) for electronic transactions processing in an electronic transactions network, cause the processor to perform operations comprising:
receiving API specification information corresponding to the API of a particular acquirer processor;
generating API data that is specific to the particular acquirer processor and that describes the API, based on the API specification information; and
generating the code for the API for the electronic transactions processing in the electronic transactions network, by using a backend generator to pass the API data and a language-specific template corresponding to the API data to an output generator.
14. The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise:
detecting a change in the API specification information,
wherein the generating the code for the API comprises generating the code for the API, based on detecting the change in the API specification information.
15. The non-transitory computer-readable medium of claim 13 , wherein the code enables a merchant to interact with the particular acquirer processor.
16. The non-transitory computer-readable medium of claim 13 , wherein the code for the API is specific to a particular process flow between a payment platform and the particular acquirer processor.
17. The non-transitory computer-readable medium of claim 16 , wherein the particular process flow includes at least one of cardholder authentication, transaction submission, fraud detection, or transaction reversal.