Where we build
Mumbai HQ + remote collaborators across India
unitpe is a lean Mumbai team building two complementary platforms — a modern payment gateway layer and bank-backed fintech infrastructure — so teams can move money with fewer vendors and more reliability.
We stay Mumbai-first and go remote across India when it helps us ship faster without losing operating discipline.
Snapshot
unitpe exists so ambitious fintech teams don’t have to stitch together five vendors just to move money in, move money out, and reconcile the truth.
Where we build
Mumbai HQ + remote collaborators across India
What we ship
Payments products + bank-backed infra (connected-banking and beyond)
How money flows
Non-custodial: transactions run via partner PAs / partner banks
One company, two platforms
We operate under one legal entity, but we keep product boundaries crisp: Payments and Fintech Infrastructure are separate platforms with separate surfaces, while sharing the same engineering standards and operational discipline.
Team
We stay intentionally small so the people closest to the problem can make the call — fast.
A compact group of engineers, product builders, compliance-minded operators, and GTM folks who’ve lived payments and settlement realities.
Banking, risk, and operations specialists who keep us sharp on compliance, onboarding, and long-tail edge cases.
Weekly build cadence, tight shipping loops, async updates when remote, and demos that keep everyone aligned on what shipped.
What we build
Collect, execute, reconcile, and report — with platform primitives designed for real ops teams, not just happy-path demos.
A developer-first payment gateway experience designed for fast integrations, clean reporting, and high conversion — powered through RBI-authorized Partner Payment Aggregators where applicable.
Bank-backed rails and tooling that sit on top of the Merchant’s own current account — connected-banking workflows, operational dashboards, and APIs built for fintech teams.
Payouts and business workflows like payroll, vendor payments, and reconciliation — initiated by the Merchant and executed through partner rails (bank/PA) with audit-grade visibility.
Built for teams that ship
Our goal is simple: reduce your integration surface area and your operational burden. Clean APIs, predictable behavior, and reporting that matches what actually happened.
Trust
Payments isn’t just code — it’s controls, auditability, and the ability to answer “what happened?” instantly.
We don’t hold or control Customer or Merchant funds. Payments are processed/settled by Partner PAs, and banking flows execute through the Merchant’s bank account with partner banks.
Least-privilege access, strong audit trails, and a build process that treats security as a feature — not a checklist. We also aim to align with PCI-DSS and SOC frameworks as we scale.
We design for real-world behavior: monitoring, anomaly detection, and operational guardrails so Merchants can ship faster without losing control.
Why we’re here
Everything we build ladders up to one idea — money movement should feel inevitable for Merchants and transparent for Partners.
Mission
Build dependable rails that let fintech teams move money without babysitting legacy systems — fast integrations, clear controls, and fewer failure points.
Vision
Become India’s most trusted partner for payments and fintech infrastructure by pairing product craft with bank-grade rigor and operational transparency.
How we operate
We’d rather stay small, decisive, and extremely hands-on than grow for the sake of headcount.
We launch thin slices, capture merchant signal, and iterate until the flow feels inevitable — speed with accountability.
Same docs, same dashboards, same truth. Whoever sees the issue first fixes it — engineering, ops, or GTM.
Partner feedback, compliance notes, and operational learnings live in open docs so decisions are made with context.
Edge cases aren’t edge cases in fintech. We design for retries, reconciliation, and operational reality from day one.
We build clean abstractions around partner rails so your team has consistent APIs even when the ecosystem changes.
Want to build with us?
If you care about reliability, clean abstractions, and shipping with discipline — we’ll get along.