Payment Gateway
One payment service for the company's products, with Midtrans and BCA channels, manual settlement and a log of every callback.
- Type
- Internal and SaaS
- Stack
- Laravel
- Role
- Backend developer.
The problem
Each product was wiring its own payment integration, so a changed callback or a failed settlement had to be fixed in several places.
What I decided
- Gave every product its own credentials, transactions and webhook log, so one installation serves several applications without mixing them.
- Kept the incoming payload in the database and moved a transaction through pending, paid and cancelled, so a disputed payment can be traced.
Where it landed
Became the payment layer reused by the restaurant POS, the photo contest, top-up and membership.
All projectsNext project: Jova Resto
Client systems stay private: no source code, internal URLs or production screenshots appear here. Every figure comes from the repositories or a read-only count on the production database.