AUTH FAQ

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

What does AUTH do?

AUTH lets an end user connect a supported institutional account or wallet through an AUTH-enabled software development kit (SDK) and initiate a deposit or withdrawal in your platform’s application. See How AUTH works for the end-user flow and AUTH overview for the product entry point.

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 wallet. Funding and settlement steps differ by product. See Getting started with AUTH for the SDK guides.

Which accounts and wallets can end users connect?

Review the AUTH network for listed institutional accounts and wallets. A listing does not guarantee that a connection supports your product, asset, network, or platform configuration. Use the Connection control to choose which available connections appear to end users.

Is every AUTH provider an AUTH partner?

No. An AUTH provider is an external account or wallet provider represented in the AUTH network. An AUTH partner is an institution that partners with zerohash to serve as an AUTH provider. Some 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?

Agree with zerohash on the assets and blockchain networks enabled for each product. The network available to an end user depends on the provider, asset, and your platform’s configuration; do not assume every provider supports every enabled network. Confirm the network-selection behavior for your enabled combinations and check the network shown at review. 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?

Review AUTH controls for connection selection, name matching, and the non-AUTH-initiated transaction block. Confirm the settings enabled for your platform 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.

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 wallet service and want to join the network, see Become an AUTH provider.