Collect for something specific
A club is collecting for a room booking. Its coordinator can share their receiving link so each member has a clear destination. Each confirmed contribution has its own payment record and receipt. The coordinator can connect those references to the group’s existing records.
Give contributors the result
If a contributor asks whether their payment arrived, open the incoming record and share its receipt. They can check the amount and time against their own payment. Any acknowledgment your organization issues can refer to that same event.
Pay the agreed recipient
For a supplier payment or a mutual-aid contribution, review the intended account and amount before approving. Keep the resulting receipt with the group’s decision record. Choosing a receiving account and deciding who may authorize the payment remain responsibilities of the group.
Keep a community original
Publish an event, image or written account intended for public release as an asset. Give it a clear author, context and statement of rights. Its original preserves the version you shared, and its own page gives people a place to inspect it.
Plan for a connection gap
A completed addressed Note can be verified and saved offline. Keep the original file intact. Deposit confirms on connection before the recipient uses that amount for another account payment. Further fully offline spending has separate protected-custody requirements.
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.