Put your value to work
Use confirmed funds to pay someone, create a Note or back an asset or currency. Keep ownership and source history connected as value moves. One account gives you familiar money and the evidence behind it.
Choose what you are adding
Deposit supports different incoming sources. Funding the account, depositing a completed Note, retaining an original proof and requesting physical asset intake establish different facts. The account admits the result appropriate to that source; selecting an option does not create funds.
Card funding
Use the supported checkout to fund the account by card. The card flow has its own review and processor result. A completed checkout screen alone is not a substitute for the verified funding result that makes money available. Pending operations retain their references for recovery.
Deposit an original Note
Open the original Note image or supported source. The reader checks its carried proof and recipient binding. A completed account-destination Note can be received and retained offline. Connection reconciles the exact deposit and confirms once-only credit before that amount can be spent from the account.
Keep the original
A screenshot or converted image may remove the proof embedded in the original. Preserve the received file intact. Displayed artwork, a denomination or a successful upload is not itself evidence of an issued Note, ownership or account credit.
Physical items
Physical intake needs a verifiable item, custody evidence and a defined transferable claim. An intake request records a request. Admitted custody and ownership require their corresponding proofs and supported execution; neither follows automatically from a description or photograph.
After confirmation
The confirmed result belongs to account history with its source and moment. If a response is lost, resume the saved operation instead of funding again. This is how incoming value remains connected to its origin without counting the same event twice.
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.