Address a verified recipient identity — not stored credentials.
Give customers, merchants or workers persistent payment identities while the infrastructure behind them can change. You address the identity; destination resolution determines where money actually arrives.
How MYQR works
Built for the institutions that pay people
Banks & Wallets
Become a destination your customers never re-enter. Verified connection, holder consent and contextual availability are platform concerns; custody and regulated execution remain yours. Banks & PSPs →
Merchants & Platforms
Marketplaces, merchant networks and QR acceptance on one identity. Recipient onboarding shrinks to "what's your MYQR?" Merchant payments →
Payouts & Workforce
Driver payouts, payroll, enterprise and government disbursements: one persistent payout address per recipient that survives every bank change. Payouts →
The architecture, honestly stated
Provider-neutral by design
Payment providers integrate through a uniform adapter contract. No provider is structurally privileged — including our first regulated providers. Platform →
Honest destination states
Connection, activation and contextual availability are separate dimensions in every API response — never collapsed into a single status. Sandbox objects are always explicitly labelled. Technology →
Channel-neutral APIs
Every MYQR surface — web, mobile, partners — consumes the same versioned /api/v1 contracts. Identity · Destination · Routing · Availability. Developers →
Developers
Build on the identity layer
Four primitives, webhook events, and a production-contract sandbox provider to integrate against before any live provider is in scope. Partner API access is provisioned per agreement during the current phase.
The regulatory boundary, by design
MYQR resolves the destination; payment execution is performed by the applicable licensed financial institution or payment provider. MYQR holds no customer funds, executes no transfers and never takes custody — the boundary that keeps your compliance analysis clean and our architecture provider-neutral.