Track record · Principal Engineer
Xendit
Owning the disbursement engine that moved billions of rupiah every month at one of Southeast Asia's payments unicorns — where "mostly reliable" isn't an option.
Owning the disbursement engine that moved billions of rupiah every month at one of Southeast Asia's payments unicorns — where "mostly reliable" isn't an option.
At payments scale, software isn't judged by features — it's judged by whether the money always arrives, exactly once, on time. Xendit was moving billions of rupiah in disbursements every month across fragmented banking rails, growing 30%+ year over year.
That kind of hyper-growth strains everything at once: the core banking APIs, the reliability guarantees, and the roadmap. A single reconciliation bug isn't a support ticket — it's real money in the wrong place.
At payments scale, correctness isn't a quality bar you aim for — it's the product itself. The disbursement engine was built around three non-negotiables: idempotency, so a retry after a dropped connection never pays anyone twice; reconciliation, so every rupiah that leaves matches every rupiah recorded and received; and correctness under load, so hyper-growth traffic never quietly becomes a money bug.
Those three principles are what decide whether a payments platform can be trusted with real money at all. They aren't advanced features — they're the floor. And they're the same floor we build to for every payment flow we touch, whether it moves billions a month or a merchant's first sale.
At payments scale, the money always arriving — exactly once, on time — is the entire product.
The rigor that fintech demands — idempotent, reconciled, correct under load — is the same rigor Thirteen brings to every payment flow we build, at any size.
Tell us the problem. We'll tell you honestly whether we're the team to solve it.