Self-hosted Wallet Proofs
Use Self-hosted Wallet Proofs to request evidence for a customer's control over a wallet address, track their response, and review the result. Choose a method that works with the customer's wallet and your verification process. For the underlying concept, see address ownership.
Choose a Proof Method
| Method | Compatibility | Customer effort | Staff/API involvement and completion |
|---|---|---|---|
| Digital signature (AOPP) | A supported asset and a wallet that can sign the required message | Open the portal link and sign a message; no transfer of funds | Request and share the link. 21 Travel Rule checks the signature automatically and marks a valid proof Verified. |
| Satoshi test | Any supported digital asset with a wallet that can send from the address being verified | Send the requested amount, pay network fees, and submit the transaction ID before the deadline | A compliance officer or custody integration checks the transfer and approves it to mark the proof Verified. |
| Visual proof | Any supported digital asset; the wallet must let the customer show evidence of address ownership | Provide screenshots or a screen recording | Review the evidence and upload it alongside the address. The record displays as Verified after upload. |
Use AOPP when the asset and wallet support message signing. A Satoshi test is an alternative when signing is unavailable and the customer can send a transfer. Use visual proof when your process calls for a staff review of screenshots or recordings. Check supported assets, including the separate list for digital signatures, before requesting evidence.
Request and Verify Evidence
- Prepare the request. Have the customer ID, digital asset, and wallet address ready. AOPP can also collect the wallet address from the customer. For Satoshi tests, review the time limit and base amounts and provide a deposit address for the test transfer.
- Collect evidence. Click
AOPP Portal LinkorSatoshi Test Link, fill in the form, and send the generated link to your customer. Follow the AOPP Portal or Satoshi Proof Portal walkthrough. For visual evidence collected outside the portals, use Visual Proof. - Check the result. Open the request in the Proofs Overview. A valid AOPP signature is verified automatically. For a submitted Satoshi test, check that the transaction sent the requested amount from the customer's address to your deposit address, then approve or decline the proof.
The Satoshi portal collects a transaction ID; it does not verify the blockchain transfer. Completing the test requires manual verification or a custody integration that checks the transfer and records the assessment through the API. See the portal integration workflow to automate requests and track status changes.
Follow Up on a Proof
| Status | Meaning | Next step |
|---|---|---|
| Pending | An AOPP signature or Satoshi transaction ID is still outstanding | Open the proof details to copy the portal link and follow up with the customer. |
| Submitted | A Satoshi transaction ID is available, but the transfer has not been verified | Check the transfer and approve or decline the proof. |
| Verified | A signature passed verification, a Satoshi test was approved, or visual evidence was uploaded | Review the proof details and retain the evidence for your compliance records. |
| Failed | A Satoshi test expired or was declined | Review the reason. For expired requests, follow the retry guidance below. |
Only Satoshi tests use Submitted. A pending signature proof requested without
a wallet address shows Awaiting address until the customer submits a valid
signature. See proof details for the information
available at each stage.
For expired Satoshi tests,
open the proof's detail view and click Request another proof to start a new
time window. Send the new portal link to the customer.
Find and Keep Your Records
Use the Proofs Overview to find requests with filtering and sorting. Open a proof to review its evidence and event history, or export proofs for your records.