Open Receive in your account.
Choose your supported payment link, copied button or in-person QR. An amount can prefill a request. A trusted order has its own exact order contract; an editable request does not create an immutable merchant order.
The standard of the proof-native economy
One payment page.The whole record.
Give the person paying a clear next step. Keep the confirmed payment connected to the recipient, amount and original evidence.
Let the payer choose the supported method.
The hosted page supports card, account balance and the current Reserve, Settlement and Settlement Reserve Note paths. Available methods and any additional card funding are shown in the actual review.
Confirm credit before delivery.
The actual result must match the recipient, exact amount and original operation. A checkout screen, redirect or message is not a confirmed payment. Keep the returned reference so a lost response can recover the same result.
Build on the same standard.
Use the existing SDK, MCP and AI Skills for the integration your application needs. The payment quick start and typed example cover the supported merchant lifecycle without creating a second ledger or new financial authority.
Source. Authority. Continuity.
What is yours
stays connected to you.
The original carries the proof. The standard preserves its identity, ownership and supported history. Receiz provides the reality-grade infrastructure through its SDK, MCP and AI Skills.
Clear scope. Exact meaning.
Understand
the distinction.
Do I need Business to receive a payment?
Core supported financial operations are available without Business. Business adds the agent and business tools under its own plan.
Does a scan authorize payment?
A link or QR opens the request. The payer reviews and authorizes the actual operation. Their signature and exact approval remain in the existing financial path.
Reality-grade banking