Find the recipient
Use a Receiz username, a payment request or a receiving link. Suggestions can include existing conversations and matching public profiles. A display name helps discovery; the resolved account identity determines the payment destination. Review that destination before approval.
One amount
Enter the amount you want to send. Funding uses available Reserve first and Settlement for any remainder. You do not need to choose between them. When both contribute, the receipt retains both components and their exact source basis.
Review before approval
Account access does not authorize a payment. The review identifies the recipient, amount and supported execution. Your device signs the exact action. A link, QR code, conversation or assistant suggestion cannot substitute for your approval.
One financial result
An operation can carry several records: the money movement, delegated authorization and its proof. Related evidence belongs inside the payment view. Separate evidence records do not mean the account was debited twice. The financial result is checked against its signed operation.
Recover an interrupted payment
A missing response does not establish failure. The application retains the exact attempted operation and checks its result before retrying. Do not create a different payment merely because a confirmation was interrupted. This preserves once-only execution across uncertain responses.
Follow the value
The receipt connects the event to available funding evidence. Object-level FIFO attribution is explicitly calculated from the recorded source basis and spend order. It explains which sources support a spend without claiming the original pooled transfer recorded an individual object allocation.
Method, sources and assessment
This explanation describes the supported implementation. Exact protocol requirements come from the pinned Receiz contracts and original sources. A reference result does not qualify a production deployment or a physical device.