Payment architecture · 2019
One payment service, shared across products.
Kinacu Systems
Leading the extraction of payment capabilities from a monolith into a reusable service for Kinacu’s own product and multiple client applications.
The context
Payment changes were a recurring maintenance concern across products. Kinacu’s original product continued alongside client work after full-time development stopped in 2017. When revisiting it later, I led a move from the monolith toward microservices, choosing payments as a capability to extract.
We used Stripe and in-app payments across multiple clients. A shared service offered a way to maintain those integrations in one place and make improvements available to both client applications and our own product.
My contribution
- Chose the service boundary. Identified payments as a useful capability to move out of the monolith, with the goal of reducing maintenance effort and cost.
- Built for reuse. Created a generic payment service to support multiple clients as well as Kinacu’s own product.
- Centralized payment integrations. Brought Stripe and in-app payment handling into the shared service.
- Simplified ongoing updates. Made payment changes deployable through the common service, so improvements could serve existing and new client integrations.
The outcome
Payment handling became a shared capability across products. The extraction separated payment maintenance from the original monolith and gave client applications a common integration point.
The architectural value was a focused service boundary around recurring work: payment updates could be maintained centrally instead of being repeated across individual products.