Choose your role
An institution can be a source issuer, custodian, application operator, receiver or verifier. Each role needs an explicit capability and trust boundary. Begin with what the integration will actually do, the supported assets and value, and who is authorized to act.
Receiving and reconciliation
A receiver must inspect source integrity, ownership, recipient binding, exact units and predecessor relationships. Connected credit must be once-only and recoverable after a lost response. Retained offline receipt must stay distinct from confirmed spendable account credit.
Custody responsibilities
Device manufacturers supply protected authority and irreversible state. Operating systems preserve it across crashes and restoration. Browser vendors expose the bound operation safely. Integrators admit the exact evidence and qualify it under the supported trust policy. No single advertised feature substitutes for the complete path.
Prepare evidence artifacts
Record versions, build identity, configuration scope, fixtures, expected refusals and actual results. Retain original sources and reproducible commands. Financial conservation, interrupted operations and physical-device behavior need evidence appropriate to the deployed implementation, beyond pure reference tests.
Assess and maintain
Use the public Conformance workspace and independent receiver materials. Publish exclusions honestly. Reassess after changing custody, storage, trust policy, recovery or financial execution. Conformance is a maintained technical result rather than an institution-wide badge.
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.