Partner fintech escrow: the initial commit was already a whole platform
The first XcroPay repo snapshot: public web, mobile, admin, API, shared schemas, migrations, docs, integrations, and brand assets — platform-shaped from the start.
The XcroPay repo's local git history starts on April 13. But that first snapshot was not small.
It already had a monorepo shape: API service, public web, admin app, mobile app, shared package, Supabase migrations, provider clients, docs, brand assets, EAS configuration, Railway configuration, tests, and deployment setup.
What that means
Escrow is not a single screen. It needs users, identity, bank accounts, transactions, disputes, messages, ratings, notifications, uploads, admin actions, provider webhooks, rate limiting, validation, and public trust surfaces.
A project that ships all of that as a monorepo from the start has already made real decisions about how these pieces talk to each other — shared schemas, shared types, shared clients. Those decisions are much harder to make mid-build than they are upfront.
What the scope says about the work
The client details stay private here. What I can say is that the engineering problem was platform-scale from day one: frontend, backend, mobile, shared contracts, infrastructure docs, provider integrations, and operational surfaces all moving together.
That kind of coordination across a monorepo is a different problem than building a single service. The benefit is that contracts stay honest across boundaries. The cost is that every change touches more files, more types, more tests, and more migration surface. Both are true, and both are worth knowing going into it.