Building Tazapay's product foundations from seed to Series A

Cross-border B2B payments in emerging markets is genuinely complex — fragmented rails, inconsistent compliance regimes, and failure modes that vary by corridor. Most platforms weren't built for the merchants actually operating in these conditions.

I joined Tazapay before there was a product. Just a problem worth solving and a small founding team. Over four years, I helped take it from zero to a platform with card coverage across 173 countries and local payment support in 70+ markets — working directly with the founders, embedded with engineering and ops, making product decisions daily.

No roadmap. No brief. No existing product to reference.

I worked directly with the founders to define the initial product scope — running early merchant interviews, mapping the core transaction flow end to end, and understanding where the real friction was.

The answer wasn't obvious: merchants weren't just struggling with slow payments, they were struggling with trust. Every step of the flow — onboarding, KYC, initiating a payout — had to feel credible enough that a business would trust us with a real transaction.

We scoped v1 tightly: just enough to validate the model and sign first customers.

As the company grew, my focus shifted from "get it out" to "make it work at scale." Three parallel problems needed solving simultaneously.

• Merchant flows Expanding to new countries meant each market had its own compliance requirements, local payment methods, and edge cases. KYB was especially complex — what a business needed to prove legitimacy in one country looked entirely different in another. I redesigned our core flows to be flexible by default: built once, adapted per market rather than rebuilt from scratch every time.

• Internal tooling Managing cross-border transactions at scale meant the ops team was constantly handling exceptions — compliance flags, failed payouts, KYC edge cases. Sensitive documents were being shared over email, creating compliance risk and audit headaches. I embedded with the ops team and led a platform redesign that centralized document handling. Transaction monitoring dropped from 1 hour to 20 minutes. KYC review dropped from 40 minutes to 15.
• Process I established how product decisions got made — how we scoped work with engineering, how we handed off, how we handled it when compliance requirements changed mid-build. A small team moving fast in a regulated domain needs clear process or it breaks. I built that process.

As Tazapay entered new payment corridors — eventually spanning 173 countries for card coverage and 70+ markets for local collections and payouts — I embedded with engineering and compliance to make sure expansion didn't mean rework.

I made the deliberate call early to invest in shared patterns and flexible architecture rather than ship faster and patch later. When we added new markets, we weren't starting over. The ops team could onboard new payment methods without the product breaking. Engineering could move faster because the product logic was consistent.

Coordinating across engineering, ops, and compliance teams across time zones — making product decisions that account for technical constraints, compliance requirements, and operator needs simultaneously — that's where most of my energy went. Not design. Product ownership.

Building in payments forces clarity. Mistakes are expensive, compliance is non-negotiable, and merchants have zero tolerance for confusion at the moment of a transaction. It taught me to think in systems, make decisions under uncertainty without waiting for perfect information, and work across engineering, legal, and ops as a peer — not a handoff point.