Use casesExchanges, brokers, wallets and custodians
Check for a person before funds leave
HEIP tells your server whether a person is in control when a withdrawal, transfer or recovery is requested. Your platform decides what happens.
Request
Withdrawal requested
0.42 BTC to a new address
The login was genuine. The withdrawal might not be.
An account can pass KYC, a password and MFA, and still be driven by someone else minutes later: a script, a remote operator, a hijacked session. Withdrawals are irreversible. The check has to happen when the money moves.
Why now
- 46%
- of account-takeover incidents in 2025 were associated with financial services
- Source: Imperva, Bad Bot Report 2026
What you get
- A check at the moment of withdrawal, not only at sign-in
- Because HEIP checkswhether a person was in control of the session when the withdrawal was requested
- Step-up only for the withdrawals that need it
- Because HEIP checksyour policy for that action, so routine transfers stay fast
- A reason for every held withdrawal
- Because HEIP checksand returns those reasons with a record id
- Protection against replayed or reused approvals
- Because HEIP checksthat the approval token was issued for this withdrawal, in this session, and used once
- No new personal data in your stack
- Because HEIP checkswithout identity, biometrics or what the customer types
Actions to protect
| Action | Suggested policy | On step up, you usually |
|---|---|---|
| Withdrawal or transfer | Critical | Passkey or hardware key, or hold for review |
| Adding a withdrawal address | Critical | Passkey, plus a cooling-off period you already use |
| Account recovery | Critical | Your recovery flow's strongest check |
| Changing email, password or 2FA | Critical | Re-authenticate |
| Trade confirmation | Fast | Ask to confirm again |
Policies are named presets you set per action. Critical asks for the most evidence. Fast suits frequent actions that still matter. Standard fits everyday actions. Observe never blocks.
Where it fits
HEIP works alongside the controls you already run. It is not a custodian and never touches funds.
Works alongside
- KYC and identity checks
- Passwords, MFA and passkeys
- Transaction monitoring
- Wallet-risk screening
Roll it out on withdrawals
Baseline
Pick withdrawals. Note how they're protected today.
Observe
HEIP decides on real traffic but blocks no one.
Compare
Review its decisions against what you already know.
Enforce
Turn it on for withdrawals only if it earns it.
Most teams go from observe to enforce in 6 to 8 weeks. Observe mode blocks no one while you compare. How onboarding works
Questions
Does HEIP hold or move funds?
No. HEIP returns a decision to your server. Your platform executes, holds or refuses the withdrawal.
Does it slow down withdrawals?
Only a step-up adds a step for the customer. The decision itself is a single call from your server.
Can we run it beside our current rules first?
Yes. In observe mode HEIP records what it would have decided and changes nothing for your customers.
Do you need customer identity data?
No. HEIP never receives names, documents, wallet ownership data or anything the customer types.
Trust has to move with the action.
When digital actions can be automated, trust must move with them.