Configure AUTH

Determine which AUTH products, connections, assets, networks, controls, and status delivery your platform will want configured with zerohash.

zerohash will configure your platform to enable the specific customer experience you desire. Once you confirm configuration, you can test what your end users see.

Configuration checklist

1. Select products and transfer directions - Tell zerohash which deposit or withdrawal products will use AUTH. Use Getting started with AUTH to identify the SDK guide for each product
2. Choose connections - Decide whether end users can connect institutional accounts, wallets, or both. Use the Connection control and AUTH network to identify which connections to show for each product
3. Select assets and networks - Check supported assets and instruments, then tell zerohash which assets and blockchain networks to enable for each product. Plan to test each enabled provider, asset, and network combination
4. Agree on controls - Decide whether your platform needs name matching or the non-AUTH-initiated transaction block. Confirm the effective settings with zerohash using the controls overview
5. Confirm status delivery - Give zerohash your transaction-status webhook callback URL. Plan how your application will show pending, completed, failed, and recovery outcomes using Getting started with AUTH

Optional: Set transfer precision and limits

If your ledger cannot support an asset’s full on-chain precision, ask zerohash whether you can set a maximum number of decimal places for that asset and network. A transfer exceeding the configured precision is rejected with an HTTP 400 response rather than truncated.

If your platform needs minimum or maximum per-transaction amounts or daily transaction limits, discuss them with zerohash. Confirm which limits apply to each enabled product, their denominations and thresholds, and what happens when a transfer exceeds a limit.

Optional: Restrict provider visibility during rollout

To test a new institutional account provider with selected end users in production, ask zerohash whether you can restrict its visibility to a list of participant codes. Confirm that this option applies to your provider and product before planning the rollout.

Once zerohash confirms your configuration, get started with AUTH to obtain access, integrate an SDK, and test transaction statuses. Contact zerohash about AUTH setup to request configuration.