Platform

Layer 1 · Where every flow begins

Universal Financial Identity

What it is. One human-readable handle — myqr.at/pedro — that stands in for every account number, wallet ID, card token and QR string a person or business owns.

The problem it removes. Fragmentation. Today a payee shares different credentials for every rail and every counterparty, and each shared credential is a liability. With MYQR, the handle is shared; the credentials never are.

myqr.at/pedroResolutionAny railSettlement

The routing brain

Payment Orchestration

What it is. The logic layer that decides, per payment, which rail carries the money — bank transfer, wallet, card, national QR — based on availability, cost, and the payee's preferences.

The problem it removes. Hard-wired integrations. Senders and platforms stop choosing rails; they address an identity and the orchestration layer finds the best available path — with splits, fallbacks and scheduling applied automatically.

IdentityRouting rulesBest available rail

One rail among many

QR

What it is. First-class support for national and scheme QR standards — including MMQR interoperability — as acceptance and presentment surfaces for the identity.

The problem it removes. QR silos. A QR code becomes one more way to reach a MYQR identity, not another closed system. QR is a rail here — never the product.

ScanIdentity resolutionRail of choice

Value at rest

Wallet

What it is. Stored value attached to the identity — funded from any rail, held securely, spent or paid out through the same universal handle.

The problem it removes. Wallet lock-in. The wallet serves the identity rather than trapping it: balances stay reachable from every connected rail and platform in the ecosystem.

Fund from any railWalletSpend / pay out anywhere

Acceptance

Merchant

What it is. Merchant acceptance built on the identity: one onboarding gives a business a payable handle at the counter (QR), online, and inside partner platforms.

The problem it removes. Multiple acquiring relationships for multiple channels. The merchant is onboarded once; every channel reaches the same identity and settles to the same place.

Customer paysMerchant identitySingle settlement

Bills, delivered to the identity

Bill Presentment

What it is. Billers present invoices directly to a MYQR identity — utilities, tuition, rent, government fees — structured, itemised, and payable in place.

The problem it removes. Bills scattered across postal mail, email and a dozen biller apps. One identity means one inbox for everything owed.

BillerPresented to handlePayable in place

Bills, settled from the identity

Bill Payment

What it is. Settlement of presented bills from the same handle — from wallet balance or any connected rail, one at a time or on schedule.

The problem it removes. The gap between seeing a bill and paying it. Presentment and payment are two halves of one flow, not two products.

Presented billPay from handleBiller settled

Where every flow ends

Settlement

What it is. Final delivery of funds on the rails institutions already run — bank accounts, wallets, cards, national QR systems — domestically and cross-border.

The problem it removes. New rails. MYQR doesn't move money on infrastructure of its own; it makes existing infrastructure reachable through one identity. Institutions keep their rails, their customers, and their regulatory perimeter.

Orchestrated paymentExisting railsFunds delivered