AUTH controls
Compare AUTH Connection, name-match, and non-AUTH-initiated transaction controls and plan your Platform configuration.
AUTH controls
Bring the latest digital asset security and transaction management controls to your platform.
Your platform’s configuration determines which institutional accounts and wallets end users can connect, whether name matching applies, and how deposits initiated outside AUTH are handled. Choose providers, assets, and networks separately in Configure AUTH.
| Control | Purpose | Configuration |
|---|---|---|
| Connection | Limits the institutional accounts and wallets end users can use | Select account types and providers with zerohash |
| Name match | Compares end-user information with external account information; timing and outcome depend on the configured flow | Agree on the matching flow and settings with zerohash |
| Non-AUTH-initiated transaction block | Prevents deposits initiated outside AUTH from becoming available as ordinary end-user deposits | Request the setting from zerohash |
Choose the controls for your integration
- Choose connections - Review the Connection control to decide which institutional accounts and wallets end users can access
- Choose a name-matching flow - Review name matching if you need to compare the end-user record with information from an institutional account. Distinguish matching after a deposit arrives but before crediting from post-credit exception reporting
- Decide how to handle deposits outside AUTH - Review non-AUTH-initiated transaction handling if you want those deposits withheld from ordinary end-user availability. Plan how you will show the status and direct end users to recovery options
- Confirm your settings - Give zerohash your control choices along with your supported assets and networks. See Configure AUTH for the full setup checklist
Contact zerohash about AUTH controls to confirm availability and your platform’s effective settings.
Updated 20 days ago
Did this page help you?