Confirm a destination really belongs to your vendor before the money leaves — and meet every payer the moment funds land. The confirmation-of-payee that traditional rails just mandated, and crypto never had.
There is no chargeback, no recall desk, no "wrong account" form. One pasted look-alike address is an existential loss — and attackers seed your own history with them.
Attackers plant addresses that share your vendor's first and last characters, hoping you copy the wrong one. Losses run to eight figures on a single mistake.
The EU made Verification of Payee mandatory on bank rails. There is no equivalent for a wallet address — that gap is what Pre-Flight closes.
Every pre-flight is logged: what was checked, what it found, who approved. When anyone asks how you control sends, the answer is filed.
Vernier verifies and records — it never moves, holds, or returns funds. A reading, never "safe to send."
0xab3d…9e21 resembles the address you've paid before — but is not it. It reached your history only through zero-value transfers, a common poisoning pattern.
→ The confirmed address is on your ticket. Send to that one.
Push payments land before you've screened a thing. Inbound Watch screens every payer at settlement — and holds the surprises for a person, without ever touching the money.
The sender address resolves to the entity behind it — a name on the arrival, not a hex string in your treasury.
A free OFAC oracle read on every payer, every arrival — it never counts against your plan.
Matched against your open invoices and payment history. A first-time payer, an unexpected amount, or a known payer on a never-seen address holds for review.
Routine arrivals file silently; held ones record who reviewed and what they decided. The receive side of your book, screened and written down.
Pre-Flight on every send, Inbound Watch on every arrival — free for 7 days, then from $79/mo. Pre-Flight is never metered.