Paywize The money-movement backend we built for a UPI fintech
Paywize is a fintech platform for businesses moving money across payin, payout, and UPI rails. We built the backend in Laravel with a PostgreSQL ledger, Redis for hot paths, and Kafka behind webhook delivery, plus the merchant dashboard in Livewire and the developer APIs. The hard part was reconciling every rupee against bank and UPI settlement files without losing a transaction.
- Web Development
- Backend Engineering
- UI/UX Design
Paywize The money-movement backend we built for a UPI fintech - what we built and why.
Paywize is a fintech platform for businesses moving money across payin, payout, and UPI rails. We built the backend in Laravel with a PostgreSQL ledger, Redis for hot paths, and Kafka behind webhook delivery, plus the merchant dashboard in Livewire and the developer APIs. The hard part was reconciling every rupee against bank and UPI settlement files without losing a transaction.
What we had to solve.
Money movement has to clear real reconciliation and settlement under bursty traffic, not just render a clean dashboard.
- 01
Reconciling payin and payout ledgers against bank and UPI settlement files
- 02
Issuing and managing virtual accounts at scale without collisions
- 03
Guaranteeing webhook delivery for asynchronous transaction status
- 04
Keeping API latency low under bursty payment traffic
- 05
Maintaining an auditable trail for every state transition on a transaction
Who built it.
- 3 Backend Engineer
- 2 Frontend Engineer
- 1 UI/UX Designer
- 1 DevOps Engineer
- 1 QA Engineer
Built with.
-
Laravel -
Livewire -
PostgreSQL -
Figma -
Redis -
Node.js - AWS
-
Apache Kafka
-
{ 01 }
Virtual account management
We built virtual account provisioning that assigns accounts to merchants and maps inbound collections to the right ledger automatically, with no collisions at scale.
-
{ 02 }
Payin and payout engine
We modeled collections and disbursals as state machines that track each transaction from initiation to settlement. Every state transition is auditable.
-
{ 03 }
UPI payments
We wired UPI inbound payments into the same reconciliation pipeline, so status updates flow through one path regardless of rail.
-
{ 04 }
Developer APIs
We built documented endpoints for initiating transactions, querying status, and managing accounts, so businesses can run their payment ops programmatically.
-
{ 05 }
Webhook delivery
We built a Kafka-backed queue that retries event callbacks until acknowledged. Integrators never miss a status change.
Outcomes that matter.
Paywize got merchant payment operations on a single reconciled system with programmatic control over collections and disbursals, and an audit trail for every transaction.
-
99.9%
Payout webhook delivery
-
<200ms
Median API response time
-
24/7
Settlement reconciliation
Where it landed.
We delivered the reconciled payment backend, APIs, and operator dashboard that let Paywize move money across payin, payout, and UPI rails.
Like what you see? Let’s build something for your team.
Related case studies.
Have a project in mind?
Tell us where you are — pre-discovery, mid-build, or scaling. A senior engineer or designer will reply within one working day. No SDR, no slideware.
Share your context
Idea stage, mid-build, or scaling — tell us where you are. We sign an NDA before any specifics.
Speak to a senior
A senior engineer or designer joins the call within two working days to map your goals and constraints.
Get a real plan
A scope, an engagement model, and a delivery timeline tailored to your stage. No slideware.
Have a project in mind?
Tell us where you are — pre-discovery, mid-build, or scaling. A senior engineer or designer will reply within one working day. No SDR, no slideware.