Name match
Compare name matching before crediting with post-credit exception reporting, and plan deposit holds and recovery.
Name match
Determine whether to hold an end-user deposit for name matching before crediting or review exceptions after crediting.
Name matching compares end-user information with information received from an external institutional account. Before-credit matching can keep a deposit unavailable until the match completes; post-credit exception reporting identifies discrepancies after funds are credited. These are matching flows, not separate AUTH products.
| Flow | When matching occurs | Effect on end-user funds | Your platform’s action |
|---|---|---|---|
| Before crediting | After an on-chain deposit arrives, before funds become available to the end user | Funds remain unavailable while matching is pending; a failed match sends them to recovery_quarantine | Monitor transaction status and provide a recovery path when needed |
| Post-credit exception reporting | After crediting | A same-name exception report identifies discrepancies; the report does not hold the deposit before crediting | Review reported exceptions and decide whether to take action |
Confirm the matching flow, eligible institutional account providers, data availability, and reporting arrangements with zerohash. Do not assume the required external account information is available for every provider or deposit.
Before-credit matching
In the documented Account Funding deposit flow:
- Initiate a transfer - The end user selects an institutional account in an AUTH-enabled software development kit (SDK) and initiates a deposit
- Hold the deposit - The deposit arrives on-chain, but funds remain unavailable to the end user while matching is pending
- Compare account information - zerohash compares the end-user record with information received from the institutional account
- Resolve the match - If the match succeeds, the deposit continues through the configured funding flow. If it fails, the funds move to
recovery_quarantinefor recovery
Monitor the Account Funding webhook and the AUTH transaction statuses so your platform can show a pending, completed, or failed outcome. Confirm which account-match pending, timeout, and failure events apply to your integration during setup.
Post-credit exception reporting
A same-name exception report can identify discrepancies using information from participating institutional account providers. Discuss report availability, daily delivery, possible secure file transfer protocol (SFTP) delivery, and how your team handles discrepancies with zerohash before relying on this flow.
Post-credit reporting does not hold a deposit before crediting. If you need funds withheld until matching completes, agree on the before-credit flow with zerohash.
Configure name matching
- Choose a matching flow - Tell zerohash whether your platform needs before-credit matching, post-credit exception reporting, or neither
- Confirm data availability - Identify which institutional account providers and transactions can supply information for the selected flow
- Plan outcomes - Agree on how your platform will handle pending matches, mismatches, timeouts, and end-user recovery
Contact zerohash about name matching to confirm the available flow and your platform’s settings. See AUTH controls for the other controls.
Updated about 2 hours ago