mCards Controlled Funding
Someone else's money, spent under their rules.
A sponsor funds another person's card at the moment of the tap, from the sponsor's own bank account or card, and only if the transaction obeys the rules they set. No prefunding, no stored value, no shared wallet.
What you can build
Families
Allowance that never leaves the parent's accountA kid sees the rules in plain language, previews a purchase before making it, and taps. The parent watches the cap draw down as real money moves — only at the tap.
Employers
Spend programs instead of expense reportsCompany money stays in the company account until an employee makes a compliant purchase. Finance sees which rules decline the most, and offboarding is one call.
Marketplace
Anyone can back a moment, togetherA time-boxed, purpose-shaped pot of someone else's money — shared by link, stacked by several sponsors at once, split across them automatically at the tap.The documents
OverviewWhat the system does: domain model, the two gates, waterfall routing, privacy, and the limitations worth knowing before you build.API referenceEvery endpoint, with request/response pairs captured from a live server: headers, schemas, ETags, idempotency, pagination, errors.Sample promptsThree ready-to-paste briefs that get an agentic development platform to build a complete two-sided product on this API.Agent build guideA prompt-shaped brief for developers and coding agents: call sequences, per-surface UI patterns, anti-patterns, acceptance scenarios.These pages render docs/api/*.md from the repository, so the deployment and the source never disagree. Every example in the reference is real traffic captured against a running server by scripts/capture-doc-examples.ts.