AUTH FAQ

Find out which deposits, withdrawals, connections, and controls your platform can configure with AUTH before you integrate.

What does AUTH do?

AUTH by zerohash is an onchain authentication and account-linking layer for account-to-account movement of digital assets. With AUTH, your end users link institutional accounts (such as an exchange) or digital asset wallets and authorize transfers without copying wallet addresses or choosing a blockchain network. Removing these manual steps reduces opportunities for address-entry and network-selection errors.

AUTH structures transfers around authenticated, end-user-permissioned accounts instead of raw wallet addresses. For regulated financial platforms, it combines account linking with zerohash infrastructure and configurable transfer controls, rather than providing a wallet connection alone. Your platform chooses the transfer types, connections, assets, and controls enabled with zerohash.

Integrate an AUTH-enabled software development kit (SDK) to offer this experience in your application. See How AUTH works for the end-user flow and AUTH overview for the product entry point.

How do I get access to AUTH?

Contact zerohash about AUTH setup to discuss access, product configuration, and testing. If you operate an institutional account or digital asset wallet service and want to join the network, see Become an AUTH Partner.

Does AUTH support deposits and withdrawals?

Yes, for the products and connections enabled for your platform. A deposit moves digital assets from an end user’s external account toward your platform’s configured destination; a withdrawal moves funds from your platform toward a supported institutional account or digital asset wallet.

AUTH supports funding flows through zerohash Account Funding and Crypto Transfers. Confirm the product, assets, and connections available for your platform with zerohash. Funding and settlement steps differ by product. See Getting started with AUTH for the SDK guides.

Which institutional accounts and digital asset wallets can end users connect?

Review the AUTH network for listed institutional accounts and digital asset wallets. Use the Connection control to choose which available connections appear to your end users. Confirm support for your product, asset, and network with zerohash before enabling a connection; a network listing does not establish availability for every combination.

Is every AUTH provider an AUTH partner?

No. An AUTH provider is an external institutional account or digital asset wallet provider represented in the AUTH network. An AUTH partner is an institution that partners with zerohash to serve as an AUTH provider. Some digital asset wallet integrations are providers without being partners. See the AUTH glossary for the definitions.

Which assets and networks are available, and how is the network selected?

AUTH removes manual blockchain network selection from the end-user transfer experience. Your platform still chooses the assets and networks enabled for each product with zerohash. Confirm support for each provider, asset, and network combination, and test the transfer details shown in your selected SDK before rollout. See Configure AUTH and How AUTH works.

Does every AUTH transfer convert between digital assets and fiat?

No. The Fund Withdrawals SDK with AUTH guide describes a fiat-funded withdrawal, while the Crypto Withdrawals SDK guide describes a digital-asset withdrawal without that conversion. Confirm the deposit or withdrawal product and funding model you need with zerohash before implementation.

Can I use AUTH in a mobile application?

Yes. Use the native iOS and Android SDK guides to access all AUTH features on mobile. Confirm connection availability and device requirements for your chosen SDK during setup; a web integration on mobile may expose different connections.

Which controls can I configure?

Choose the transfer types, institutional accounts, digital asset wallets, assets, and networks your platform offers with zerohash using Configure AUTH. Review AUTH controls for connection selection, name matching, and the non-AUTH-initiated transaction block. Confirm the settings enabled for your platform before relying on them.

These controls support your platform’s risk and compliance workflows. For example, name matching compares end-user information with information received from an institutional account. Account authentication alone does not establish that every external account has completed know your customer (KYC) checks or that the source of funds has been verified; confirm provider data availability and the applicable matching flow with zerohash.

What happens if an end user sends a deposit outside AUTH?

If your platform has enabled the non-AUTH-initiated transaction block, received funds enter recovery_quarantine instead of becoming available for ordinary end-user activity. Handle the deposit status webhook and direct the end user to the agreed recovery flow. Confirm the control is enabled before relying on this behavior.

How do I track a transfer after an end user submits it?

Consume the AUTH and product-specific webhooks enabled for your platform. A submitted transfer is not necessarily settled or available to the end user. Use Getting started with AUTH to identify status handling and webhook references for your product.

Can I test AUTH in Cert?

Use Cert (the test environment) to test your configured integration with simulated transactions. Not every external provider or exception path is documented as testable there. Agree on a test plan with zerohash for flows you cannot reproduce in Cert; see Getting started with AUTH.