Introduction / Overview
About CZR Custody
Developer guidance for connecting wallet and transaction workflows to your institution’s systems.
Integration overview
Start by mapping customer or treasury accounts to wallets, then follow a transfer from the original request through approval, signing, network confirmation, and reconciliation. Identify which system owns each decision and record.
Wallets and addresses
Decide whether wallets represent individual customers, operating accounts, or reserves. Record which network and asset each deposit route accepts and whether it requires a memo or destination tag.
- Choose stable internal identifiers for accounts, wallets, and addresses.
- Keep network and asset identifiers with each deposit route.
- Define how you handle unsupported assets or unmatched deposits.
Transfers and approvals
Give each withdrawal or transfer an internal request reference. Track the original request, approval outcome, and eventual network transaction separately so your team can explain any hold, rejection, or delay.
Confirm authentication, permission scopes, retry behavior, and idempotency guarantees when reviewing the official API specification.
Explore Policy & ApprovalsStatus updates and reconciliation
Design reconciliation around the transfer reference and its network transaction identifier. If your integration uses callbacks, confirm signature verification, event ordering, delivery retries, and how to recover missed updates.
Test duplicate updates, delayed confirmations, and mismatches between transaction status and internal balances.
Integration checklist
- List target assets, networks, and expected peak volume.
- Map account ownership, wallet creation, and deposit routing.
- Document approval roles and signing authority.
- Agree on status handling, reconciliation cadence, and escalation owners.
- Confirm access to a test environment and current API documentation with CZR.
Request API access
Contact CZR Support for the current API reference, authentication requirements, SDK availability, and test environment details. Include your organization, use case, and target networks.
Contact Sales