Use Cases
Eight everyday flows, one resolution layer underneath all of them.
Driver Wallet
Earnings land the moment the work ends.
Platform payouts route to a wallet attached to the driver's identity: spendable, billable, paid out to a connected destination.
See the flow →
Diaspora Remittance
Send to a name, not a corridor.
The sender addresses a handle. Routing, currency and the receiving network are resolved behind it, on licensed partner networks.
See the flow →
Digital Bills
One inbox for everything owed.
Utilities, tuition, rent and government fees arrive at the identity — structured, itemised and payable in place.
See the flow →
Government Benefits
Programs pay verified identities, auditably.
Disbursement reaches the citizen rather than an intermediary, with a per-payment trail agencies can examine.
See the flow →
Payroll
One payout file, every destination.
Employers pay identities instead of maintaining bank details. Staff choose where value lands, and change it without a form.
See the flow →
Healthcare
Bills and claims settle against one patient identity.
Providers present, patients pay and insurers reimburse through the same handle — no re-keying account details at each step.
See the flow →
Education Overseas
Tuition paid from home, received locally.
One invoice to the family identity, payable from abroad, without the institution running cross-border payment infrastructure.
See the flow →
Tourism
Visitors pay like locals.
A traveller's home identity resolves onto the local network at the counter — no declined foreign cards, no hidden conversion.
See the flow →Illustrative use cases. Value movement is executed by licensed partner institutions; connections shown are design pathways, subject to partnership and technical implementation.
Every journey below is the same four ideas at work — financial identity, resolved and routed by destination resolution, running on a financial operating system, adopted through a financial ecosystem. Only the people change.
Pay Anyone
Send money to a person, not an account number.
Sharing an IBAN, a wallet ID or a card number is friction at best and a liability at worst. With MYQR, the recipient shares one handle; how the money arrives is their choice, not the sender's problem.
Merchant Payments
One identity makes a business payable everywhere.
A merchant onboards once and becomes payable at the counter, online and inside partner apps. Every channel reaches the same identity; every sale settles to the same place.
Accept payments at the counter and online with one onboarding — no channel-by-channel acquiring.
Driver Wallet
Earnings land the moment the work ends.
Drivers live on their earnings; weekly batch payouts are a legacy constraint, not a law of nature. Platform payouts route to a wallet attached to the driver's identity — spendable, billable, paid out to a connected destination.
MYR1,284.50
Spendable now · payout to a connected destination
- Platform payoutMobility · 14:22+186.00
- Platform payoutMobility · 11:05+142.50
- Payout to bankPartner network · in progress−400.00
Illustrative concept interface. Not a live product screenshot. Balances and transactions are examples; value movement is executed by licensed partner institutions.
Ecosystem use case: designed for mobility flows across JAYRIDE and FAIRYDE, subject to partnership and technical implementation.
Diaspora Remittance
Send money home with the handle you already use.
Remittances today mean corridor-specific apps, agent codes and re-typed account numbers. With a universal identity on both ends, sending money home is the same gesture as paying a neighbour.
Digital Bills
Bills find the identity — one inbox for everything owed.
Utilities, tuition, rent, government fees: today they scatter across paper, email and a dozen apps. Presented to a MYQR identity, they arrive structured, itemised and payable in place.
MYR148.20
Presented to myqr.at/jay
- Usage — 41 days112.40
- Service charge24.80
- Tax11.00
Illustrative concept interface. Not a live product screenshot. "Metro Water" is an example biller; amounts and dates are examples used to show a structured, itemised bill arriving at an identity.
Government Benefits
Aid reaches verified identities — auditable end to end.
Disbursement programs fail at the last mile: wrong accounts, ghost recipients, no audit trail. Paying a verified identity closes that gap, and every movement is recorded.
Payroll
Pay a whole workforce by handle — across banks and wallets, in one run.
A payroll file full of account numbers is fragile and stale. A payroll file of handles never goes out of date: each employee keeps their destination current behind their own identity.
Education
Tuition presented once — payable from anywhere.
Schools bill families; families are often split across borders. Presentment to the family's identity means one invoice, payable domestically or from abroad, without the school running payment infrastructure.
Healthcare
Billing that respects privacy.
Health payments carry sensitive context. Identity resolution moves the money without moving the details: the provider is paid, the patient's accounts stay private, the record stays clean.
Tourism
Visitors pay like locals.
A tourist's home payment systems don't work abroad — unless the national systems interoperate. MYQR resolves a foreign handle onto local networks, so the visitor scans what locals scan and the merchant settles how merchants settle.
The intended integration pathway for national payment systems — interoperation, not competition.
Find your flow
Every use case above runs on the same identity, resolution and settlement layer.