Payments
Payment provider integrations: from months to days
A new modular payment service and AI-ready integration standards cut the time to add a payment provider from months to about a week.
- Role
- Architect & lead developer
- Time to integrate a new provider
- Months → days
- Analysis, development and QA per provider
- ~5 days
- Development effort per provider
- 1 day
Context
A payment platform needed to offer more alternative payment providers. Each one had its own API, flows and edge cases.
Problem
Every provider integration took weeks or months. The existing systems were fragmented and tightly coupled, so each integration meant changes across several places and a long stabilisation period.
Approach
I designed a new Spring service around a robust core, shared modules and isolated provider modules, communicating via Protobuf. A provider module can be added or changed without touching the core or the other providers.
I also wrote integration standards as markdown files for AI agents. When a new provider is needed, its documentation is given to the agent, which produces an integration that follows the same structure every time.
Outcome
Integration time dropped from months to days: around two days of analysis, one day of development and two days of QA. Engineering stopped being the bottleneck — the pace of delivery is now set by QA and analytics.
Stack
- Java
- Spring Boot
- Protobuf
- Kafka
- Docker
- Kubernetes