In software development, efficiency often hinges on choosing between building from scratch or leveraging pre-built solutions. For Cashfree Payments, a

Manual to Automated: The Evolution of Cashfree Payments’ SDK Journey

submited by

Style Pass

2024-11-27 10:30:11

In software development, efficiency often hinges on choosing between building from scratch or leveraging pre-built solutions. For Cashfree Payments, an API-first company, this decision has shaped our journey in building Software Development Kits (SDKs) to simplify and enhance our merchants’ integration experience. Initially, we took the manual route, crafting SDKs line by line to align with our API updates. But as we grew and the demand for seamless integration increased, we saw the need to evolve — moving from fully manual development to a more automated, streamlined approach.

Cashfree Payments, as an API-first company, constantly writes new APIs and modifies existing ones. These APIs are made available to merchants, enabling them to integrate our products seamlessly. A merchant can write their own network layer and independently integrate all required APIs. However, this approach involves the complexity of building all necessary data models to handle requests and responses.

What if we could simplify this process for them while also allowing them to modify network-level configurations (such as setting up proxies, timeouts, and connection pooling)? By taking the other route, integration would save development time and expedite production. The developer will just end up writing code that is as simple as Cashfree.PGFetchOrder() to get the details of an order.