{"id":1702,"date":"2017-06-13T17:37:33","date_gmt":"2017-06-13T12:07:33","guid":{"rendered":"http:\/\/blog.payumoney.com\/?p=1702"},"modified":"2025-10-05T00:03:37","modified_gmt":"2025-10-04T18:33:37","slug":"update-alert-improved-payment-gateway-integration-guide","status":"publish","type":"post","link":"https:\/\/payu.in\/blog\/update-alert-improved-payment-gateway-integration-guide\/","title":{"rendered":"Update alert – Improved Payment Gateway Integration Guide"},"content":{"rendered":"

If you are a semi techie running your own online business, you\u2019d know the struggle of evaluating and integrating various products\/services in the market to either extend your product offering or to simplify the daily running of your business. But if you are a tech developer, you have to go one step further, you\u2019d need to actually understand almost every possible detail about this new product you are trying to integrate, dodge your way through different APIs and finally test it. Developing a payment gateway is no different!<\/p>\n

At PayUmoney, we get around 6000 to 8000 inquiries weekly from the above stakeholders to help them in the payment gateway integration process. PayUmoney\u2019s updated and improved payment gateway Integration guide is an attempt to help them breeze through the integration process. Let\u2019s walk through the guide improvements:<\/p>\n

Overview & Reference Sections<\/strong><\/span><\/h2>\n

Every product listed in the Payumoney developer guide is now divided into two sections. An overview section that gives an overall product overview for the startup founder and a reference section that gives a detailed integration reference to the developer integrating with us.<\/p>\n

From the first set of feedbacks that we have received, this division of content has helped our merchants, especially the non-tech founders quickly evaluate us without getting lost in the technical details. Developers are also able to understand what the product is about first and do a deep dive into the technical integration reference.<\/p>\n

\"integration<\/a><\/p>\n

Clean API Documentation<\/strong><\/span><\/h2>\n

\u00a0<\/strong>API Documents have to be accurate, clean and well presented. And the latest trend in the API Documentation world is the three-panel design documentation. So we reinvented our API documentation using ReDoc<\/strong> – a powerful tool that helps us describe our APIs adhering to OpenAPI Specification.<\/p>\n

Here, the left panel contains a scroll-synchronized reference menu. The middle panel contains endpoints\/methods documentation. And the right panel contains various samples: request samples, response samples and code samples.<\/p>\n

\"integration<\/a><\/p>\n

We now have the ability to clearly document complex request\/response payloads. The nested schemas are now displayed beautifully with the ability to expand and collapse. All these without compromising on accuracy as documentation is directly generated from the source code.<\/p>\n

\"integration<\/a><\/p>\n

Downloadable Integration Kits<\/strong><\/span><\/h2>\n

The aim of the developer documentation is to make integration as seamless as possible. How much easier can it be, if all you would need to test a sample integration is to download an integration kit, host it on your local machine and click pay.<\/p>\n

The kit handles request generation and response handling for you. All you would need to do is:<\/p>\n