When evaluating technology partners, a focus solely on features overlooks a crucial element – the underlying architecture. From our perspective as longtime industry developers and leaders, an API-first strategy is not merely a technical consideration; it's a fundamental principle that drives agility and innovation for your organization. This architectural approach provides the essential building blocks for fluid integration, accelerated growth, and the strategic flexibility necessary to adapt effectively to evolving business demands.
From a business leader's perspective, the value of an API-first partner is significant and multifaceted, ultimately contributing to agility, innovation, and long-term growth. By understanding how an API-first architecture benefits the business, leaders can ensure their evaluation of technology aligns with strategic goals.
Here are 6 business considerations mapped against the value of an API-first architecture to help leaders drive these discussions:
- Increased Speed and Agility: An API-first approach allows for faster integration of new features and services. Instead of monolithic development, components can be built and connected independently, accelerating time-to-market for new offerings and enabling quicker responses to changing market demands. Working with a vendor that can build without re-architecting existing infrastructure is critical for reducing downtime or disruptions.
- Enhanced Innovation and Flexibility: By providing well-defined and accessible APIs, a partner like Peach enables the business to experiment with new technologies and integrate with a wider ecosystem of third-party services. This fosters innovation by making it easier to build upon existing capabilities and create unique solutions without being locked into a single vendor's roadmap.
- Reduced Integration Complexity and Costs: A partner with a strong API-first strategy provides clear documentation and well-structured interfaces, significantly reducing the complexity and cost associated with integrating their services with the business's existing infrastructure. This lowers development overhead and accelerates the adoption of new capabilities.
- Future-Proofing and Adaptability: An API-first foundation makes the business more adaptable to future technological advancements. As new technologies and platforms emerge, integrating them becomes significantly easier through well-defined APIs, protecting the business's investment and ensuring long-term viability.
- Stronger Partnerships and Ecosystem Potential: A partner with a robust API strategy fosters a collaborative environment. It allows for easier integration with other partners and the creation of a richer ecosystem of services around the core offering, potentially unlocking new revenue streams and business opportunities.
- Data Accessibility and Insights: Well-designed APIs provide structured access to data, enabling the business to extract valuable insights for better decision-making, personalized customer experiences, and the development of data-driven products and services.
In summary, an API-first software partner acts as an enabler, providing the building blocks and connectivity that allow the business to be more agile, innovative, efficient, and ultimately more successful in a rapidly evolving digital landscape. They empower the business to own its technology roadmap and create differentiated value.
Check out other Tools for Leaders like our guide for recommended questions to facilitate a discussion on buy, build, or integrate.
Ready to chat about Peach’s API first loan servicing platform and how we can help you maximize your tech infrastructure and customer servicing solutions?
lender’s priority list. But that doesn’t mean compliance is straightforward, even for lenders with the most earnest intentions. Often, legacy infrastructure is the culprit, making it difficult for lenders to take the actions clearly outlined in the law. Even regulations that haven’t changed for some time—like the—still present significant challenges for many lenders.
The SCRA grants active-duty service members the ability to request certain protections during the period of their deployment, enabling them to devote their energy to serving the country. These protections include a reduction in interest rate to a maximum of six percent on any pre-service loans. While the SCRA in its current version has been law since 2003, the number of recent enforcement actions indicates just how difficult it is for many lenders to comply with the SCRA’s interest rate protections.
Blunt tools in the absence of a scalpel
For example, in October of 2022 the Department of Justice (DOJ) announced that the financial leasing arm of GM agreed to pay over $3.5 million to resolve allegations in relation to
Peach’s approach to SCRA
At Peach, we brought real-life lending experience to the design of our platform. So from day one, we recognized the importance of being able to make retroactive changes to loans. (There are numerous applications beyond SCRA, including our Supported Portfolio Migration.) In the case of SCRA, Peach has long enabled lenders to retroactively change interest rates and waive past fees—as separate, manual actions.
Peach’s approach to SCRA
This was functional, but the ideal way to implement SCRA is to make these changes simultaneously. We now support this capability by leveraging the power of Peach's Loan Replay™ engine, which can make changes to the ledger at any time, and then recalculate a loan’s history in light of those changes. The new combined functionality is as user-friendly for your agents as processing a payment.
Peach’s approach to SCRA
Specifically, the new SCRA feature allows your agents to perform the following adjustments simultaneously on a loan of an active-duty service member:
- Lower interest rates to 6% (and lower the recurring payment during the active-duty period to account for the interest rate reduction)
- Waive fees, if necessary
- Enact these changes retroactively, if necessary, and replay the loan history with the rate and fee adjustments
- Preview the intended changes
“We launched our first product on Peach in six weeks. Eighteen months later.”
John Smith, CMO
Our SCRA functionality is available via API as well as through our white-label agent tool. The white-label agent interface can be seen here:
Peach’s approach to SCRA
Our SCRA functionality is available via API as well as through our white-label agent tool. The white-label agent interface can be seen here:
For those working directly with the API, this can be as simple as sending the following request body to the SCRA endpoint:
You’ll receive a response with either the actual post-SCRA adjusted payment plan or a preview of it. Below is a comparison of a payment plan prior to the SCRA adjustment, and the expected payments after the SCRA adjustment. The SCRA period is in effect for the first two months, and thus you will see the interest rates lowered to 6% in the response body (and the recurring amount due lowered by the amount of the interest rate reduction for the two relevant months). The origination fee has also been canceled.
The breadth of loan data needing to be adjusted means that rewriting loan histories requires the right design and abstractions, and having a built-in layer of abstraction to handle retroactive changes is the only feasible approach. Because of our team’s combined experience in the real world of lending, we know that the need to edit past loan events is inevitable. So we’ve designed a system that makes these changes as painless and automated as possible.
