How AUTH works

Follow an end user’s deposit or withdrawal through an AUTH-enabled software development kit (SDK), and identify where your platform’s configuration shapes the flow.

AUTH connects an end user’s external institutional account (held by a provider, such as an exchange) or wallet (controlled by its holder) to a supported transfer flow. The steps shown depend on the provider, the product you integrate, and your platform’s configuration. See the AUTH network for supported providers and wallets.

End-user flow

1. Open the flow: The end user opens the AUTH-enabled deposit or withdrawal experience in your platform’s application
2. Accept agreements: The end user reviews and accepts any agreements presented for the selected flow
3. Connect an account: The end user chooses an available institutional account or wallet and completes the connection steps, including provider login when required
4. Review the transfer: The end user chooses a supported asset and checks the network and any amounts or fees shown by the selected product
5. Submit and track: The end user submits the transfer and follows its status in your platform’s application

A submitted transfer is not necessarily completed. Integrate transaction-status webhooks to distinguish submission from confirmation, completion, failure, and recovery. Screens and steps vary by SDK and external account; test the end-user experience for your selected integration.

Deposits and withdrawals

For a deposit, the end user initiates a transfer from an external account toward the account used by your platform. For a withdrawal, the end user initiates a transfer from your platform toward a supported external account or wallet. The Fund Withdrawals SDK with AUTH guide covers a fiat-funded withdrawal; other withdrawal products have different funding and settlement steps.

Account types and network selection

Use the Connection control to choose which institutional accounts and wallets appear to end users.

Choose supported assets and blockchain networks with zerohash as part of AUTH configuration. Do not assume every provider supports every network: check the network shown in the end user’s review step, and test each provider, asset, and product combination you enable. There is no documented universal rule for automatic network selection.

Get started with AUTH to configure and test an integration.