Skip to content
Pages/Legal & Compliance
Page

Wallet Verification

Crypto payments can’t be reversed. If you send funds to the wrong address, they’re gone, and paying a sanctioned address can put your organization in legal trouble. Wallet Verification lets you confirm, before you pay someone for the first time, that the wallet really belongs to them and can receive what you’re about to send. It also shows you the OFAC sanctions screening result for every wallet you hold.

You’ll find it in the sidebar under Legal & Compliance → Wallet Verification.

Most lost payments aren’t hacks. They’re ordinary mistakes and ordinary scams:

  • A wrong address. A character is missed in a copy-paste, or the address comes from an old invoice or the wrong spreadsheet row.
  • A swapped address. Someone impersonating a vendor emails our wallet has changed, please pay this one instead.
  • The right wallet on the wrong network. The address is correct, but the owner can’t access funds sent on the network or in the asset you chose.
  • A sanctioned address. A counterparty’s wallet is on an OFAC sanctions list, or gets listed after you first paid it.

Verification catches the first three. The owner proves they control the wallet by reporting a small amount only they could see. They also tell you which networks and assets the wallet can receive. Screening catches the fourth, before you pay rather than after. Together they give you a dated record for every wallet, which helps when an auditor or your board asks how you check counterparties.

  1. You add the wallet and choose the network you plan to pay on.
  2. Mezzanine sends it a small, random amount of USDC, between $0.10 and $0.99. The deposit comes from Mezzanine, not from your accounts.
  3. You send the owner a secure link. Mezzanine gives you a ready-to-send message; you pass it on however you normally talk to them.
  4. The owner signs in and enters the exact amount they received (the page waits until the deposit has landed before asking), then says which networks and assets the wallet accepts.
  5. The wallet is marked Verified. You can pay it knowing it reaches the right person.

The whole thing takes you about two minutes, and the owner about one. For the full walkthrough, see Verify someone’s wallet with a test transaction.

If you already know a wallet belongs to its owner, a teammate can verify it manually instead. They attest the address with a screenshot or document, a note, or both; no deposit is sent and the owner gets no link. The address is still screened first. See Verify a wallet manually.

Screening needs nothing from you. Mezzanine checks every wallet address you hold against the wallet addresses on OFAC’s sanctions lists: your contacts’ wallets, your own entities’ wallets and your teammates’ wallets, Safes and exchange accounts included. A result is kept for 30 days; after that, the address is screened again the next time it’s loaded. To look a counterparty up, see Check a counterparty against sanctions lists.

  • Before the first payment to a new vendor, contributor or grantee: verify the wallet and confirm its screening reads Pass.
  • Whenever someone gives you a new address, even if the request looks like it came from someone you know. This is when verification matters most.
  • Before an unusually large payment to a wallet you haven’t paid in a while.
  • When you’ll pay on a different network or asset from the one you tested. A wallet is only confirmed for the networks and assets its owner listed.
  • When preparing for an audit or board review, to show every wallet has been verified and screened.

The list has two tabs, Wallets and Bypass log, switched at the left of its header. Beside the switch are the search box and, on Wallets, the Status and Network filters, with Clear to reset your search and filters. The count at the right of the header reads how many wallets there are, such as 9 wallets, or how many your search and filters leave, such as 4 of 9. On Bypass log it counts entries, such as 12 events.

Every wallet across your contacts, your entities and your team, and where each one stands. Wallets whose verification changed most recently come first, and a wallet moves to the top when screening flags it. Search by a wallet’s name, its owner’s name, or its full address.

Each row shows the Wallet (its name, with its short address and its owner beneath), its Verification and its OFAC screening. Click the wallet’s name, or anywhere on the row, to open it in the panel.

The Verification column tells you whether a wallet has proved it belongs to its owner:

You see What it means What to do
Verified · date The owner confirmed the amount. Hover to see what was confirmed and by whom Pay it, on the networks and assets listed for it
Verified manually · date A teammate attested the wallet belongs to its owner. Hover to see who and when Pay it, on the networks and assets listed for it
Pending The test was sent; the owner hasn’t finished yet Wait, or choose Share link again in the row’s ⋮ menu to re-send them the link
Unverified This wallet hasn’t been verified Choose Verify wallet in the row’s ⋮ menu
Failed The test deposit didn’t arrive Choose Reverify in the row’s ⋮ menu to try again
Locked The owner entered the wrong amount too many times Choose Reverify in the row’s ⋮ menu to send a new amount and link
Expired The owner didn’t finish within 7 days Choose Reverify in the row’s ⋮ menu to send a new link

The OFAC screening column shows the wallet’s last sanctions screening, with the date it was screened:

You see What it means What to do
Pass · date The address passed its last screening Nothing
Flagged · date The address matched a sanctions list Don’t pay it. Raise it with whoever handles compliance
Re-screen due · date The last result is over 30 days old Nothing. It’s screened again automatically. Check back before paying
Not screened No result yet, or screening couldn’t be completed Reload the page later. Don’t treat it as passed

Each status has a mark beside it in the same color. Green means verified, or passed screening. Red means a test failed or locked, or the address was flagged. Amber means something is still outstanding: the wallet is pending, expired or unverified, or its re-screen is due. A wallet that hasn’t been screened has a dashed gray outline.

To see every flagged wallet at once, choose OFAC flagged in the Status filter. It lists flagged wallets whatever their verification status, including ones verified before they were flagged.

What the owner, or the teammate who verified it, said the wallet can receive is in the wallet’s panel, under Accepts on its Verification tab. All EVM networks or All assets means it accepts everything. For a Safe or an onchain exchange account, the network is fixed to the account’s own.

Everything you can do with a wallet is in its row’s ⋮ menu; the row has no button of its own. The menu offers:

  • Verify wallet for a wallet that has never been verified, or Reverify for any other. Both open the Verify wallet window, where you choose Test transaction or Verify manually.
  • Share link again and Send new test in their place while a test is waiting on the owner.
  • Verify manually, for a wallet that isn’t verified.
  • View wallet, which opens the wallet in the panel on its Overview tab.
  • Open contact, which opens the wallet’s owner.

A wallet Blocked by OFAC screening offers only View wallet and Open contact.

To verify a wallet that isn’t listed yet, click Actions at the top right of the page, then Add Wallet. While your organization has no wallets, the empty list also offers Add wallet.

The page updates itself while a test is pending, so you’ll see the owner’s confirmation arrive without reloading.

Only wallets appear here. Bank accounts aren’t verified or screened on this page.

The list only shows wallets you have permission to see. If you can’t see your own entities’ wallets or your teammates’ wallets, a box above the list reads Some addresses aren’t shown and names the permission you need for each, with a link to request it. Until you have them, a list with no Flagged wallets only means none of the wallets you can see are flagged.

Click a wallet to open it on the right, on its Verification tab. Click the same row again to close it. A row in the Bypass log opens its wallet here too.

The tab starts with one line on where the wallet stands. Below it:

  • Accepts: the networks and assets the wallet can receive.
  • Test transaction: the network and asset of the latest test, the date it was sent, whether the deposit is Settled, In flight or Failed, and the transaction hash. Click the hash to copy it. The icon beside it opens the transaction in a block explorer.
  • Manual verification, in place of Test transaction for a wallet verified by hand: who verified it, when, the prior transaction they cited, the evidence they attached and their note.
  • OFAC screening: the last result, when the address was screened, and the list a flagged address matched.
  • History: every verification of this wallet, newest first. A test that was withdrawn or superseded by a newer one reads Replaced. A test deposit the contact skipped while entering their payment details counts as withdrawn.
  • Bypasses: payments that went ahead to this wallet even though it wasn’t verified for them. It only appears when there are some.

The buttons at the bottom of the panel depend on where the wallet stands:

The wallet is You see
Not verified Verify wallet
Waiting for the owner Share link again and Send new test
Verified Reverify
Failed, locked or expired Verify again

Verify wallet, Reverify and Verify again open a choice between Test transaction and Verify manually. A wallet Blocked by OFAC screening has no buttons.

A record of every payment that went ahead to a wallet that hadn’t passed verification, newest first. Each entry shows:

  • When: the day it happened. Hover the date for the exact time.
  • Payment: the amount, with the payment’s description beneath. Click the amount to open the payment on the right, with the details and actions it has under Move Money.
  • Wallet: the wallet’s name, with its owner and the payment’s network beneath. Click the name to open the wallet on the right.
  • Why: Wallet untested when the wallet was never verified, or “network not confirmed” or “asset not confirmed” when the payment used a network or an asset the owner didn’t confirm.
  • Step: where the payment went ahead, such as Approved or Proposed, with who did it beneath. Click their name to see their details.

Click an entry to open its wallet on the right. The search box finds entries by wallet name or address, owner, payment description, teammate, network or asset among those loaded so far; Load more at the bottom brings in older ones. While a search hides some entries, the count reads how many it leaves, such as 3 of 12.

Only entries made while Wallet Verification Mode is on (see below) appear here. Until there are some, the log reads No bypasses. A payment to a wallet not confirmed for its network and asset is logged here while Wallet Verification Mode is on. It’s the place to look when you need to show that exceptions were tracked.

Wallet Verification Mode is on for every organization unless an admin turns it off, in System Controls → Organization Settings.

While it’s on, anyone who approves, signs or executes a payment to a wallet that hasn’t passed verification sees a warning, such as Wallet not verified, that reads Send a test transaction or mark it as verified before this payment goes out. To go ahead, they tick I understand this wallet isn’t verified for this payment and want to proceed. Before that, the payment’s panel in Requires Action lists the same warning first under Flags, marked Added automatically, and counts it in the row’s flag icon. The payment isn’t blocked, but each exception is recorded in the Bypass log, with the step it was taken at: proposed, approved, signed or executed. Wherever the warning appears, someone with Start wallet verification can click Send a test transaction or mark it as verified in it instead, and verify the wallet without leaving the payment.

With it off, nobody sees the warnings and nothing new appears in the Bypass log. See Turn on Wallet Verification Mode.

  • The owner needs no Mezzanine account. They confirm with their email address and a one-time code.
  • Links expire after 7 days and work once. If you send a new test to the same wallet, the old link stops working, so always send the owner the latest one.
  • The owner gets 5 tries to enter the right amount. After that the link locks, and you’ll need to send a new test.
  • Every address is screened before a test is sent. If an address is flagged, no test is sent, and you’ll see This address was flagged by OFAC screening; no test was sent. Don’t pay that wallet; raise it with whoever handles compliance.
  • A flagged address can’t be paid. Mezzanine blocks payments to it. There’s no override: if you think a result is wrong, take it to your compliance lead before doing anything else.
  • You can’t run a screen by hand. Screening and re-screening happen automatically.
  • The same result shows everywhere. Next to a wallet address across Mezzanine there are two marks: its verification, then a shield for its screening. A verified wallet’s mark is green with a check, and its shape tells you how it was verified: a circle for a test transaction, a person for a manual verification, a ribbon for a wallet Mezzanine provided, which needs no test. The shield is green when the address passed screening, red with a cross when it’s flagged, and a dashed gray outline when it hasn’t been screened. Hover either mark for the detail, for example “Passed OFAC sanctions screening on date.” or Flagged by OFAC sanctions screening. This wallet cannot receive payments.
  • Supported networks: Ethereum, Base, Arbitrum, Optimism, Avalanche and Hyperliquid. Safes and onchain exchange accounts are tested on their own network automatically.
  • Verified means verified for what the owner listed. If you later pay on a different network or in a different asset, verify again or check what its panel lists under Accepts first.
  • There’s a limit of 100 tests per organization per day. Past it, a send fails with Your organization has started 100 wallet verifications in the last 24 hours. Try again later.
  • A manual verification never expires. It records who attested the wallet and the evidence they gave, which you can see in the wallet’s panel. A newer verification replaces it. An address flagged by screening can’t be verified manually: you’ll see This address was flagged by OFAC screening, so it can’t be verified.
To… You need the permission
See this page View contacts and View wallet verification
See your own entities’ wallets on it View entities as well
See your teammates’ wallets on it View team as well
Add wallets and send tests Start wallet verification, plus Add and edit contacts to add a new wallet
Verify a wallet manually Start wallet verification. Attaching a file also needs permission to edit the wallet’s account: Add and edit contacts for a contact’s wallet, Manage entities for one of your entities’ wallets, Manage team for a teammate’s. Without it, a note on its own is enough
Turn Wallet Verification Mode on or off Edit general organization settings

If you can’t open the page, it tells you which permission is missing and lets you request it. If you can see the page but not start tests, the menu items and buttons that start one explain why when you click them.