Account protection · Real-time

See the risk before you grant access or move money

Before you grant access, run a recovery, release a payment or accept a change to an account, check the risk behind the request: whether the number still belongs to your customer, and whether the session asking looks genuine.

A one-time passcode proves someone has the phone. It does not prove the phone is still your customer's. Provero shows you the risk first, so you know whether to proceed, step up or stop.

  • Before access, recovery or payout
  • The number and the session
  • Proceed, step up or stop

A passcode sent to a hijacked number hands over the account

Account takeover often starts with the phone number. A fraudster takes control of it, then asks for a password reset. Your system sends the code and the account is theirs.

Other attempts arrive through proxies, VPNs or connections with a record of abuse, asking to change the payee, the bank details or the contact number.

From there it is payouts and a customer who finds out after the money has gone.

What an unchecked number costs you

  • Payouts released to fraudsters.
  • Accounts taken over through password resets.
  • Reimbursement and investigation costs.
  • Customers who leave after their account is compromised.

Why passing a security step is not the same as being the customer

Passcodes, recovery flows and payout confirmations assume two things: the number still belongs to the customer, and the person asking is who they say.

Nothing in the code itself checks either. If the number has been taken over, the code goes to the fraudster and your system records a successful verification.

What Provero checks before you act on the request

At the moment of the sensitive action, Provero looks at the number the request relies on and at the session making it.

A number that has just changed hands

Signs the number has recently moved to a new SIM, the classic first step in a takeover.

A number that no longer fits the customer

Whether the person the number belongs to still matches the customer on your account.

A number with an unusual profile

Numbers whose type and history do not fit the account they are protecting.

A session that looks wrong

Requests arriving through proxies, VPNs, Tor or connections associated with known abuse.

What changes

Fewer account takeovers

Codes go only to numbers you have reason to trust.

Payouts that reach the right person

Money is not released on a number that has just changed hands.

Friction only where it is needed

Genuine customers proceed as normal. Risky requests step up.

Decisions you can explain

A clear reason behind every escalation.

Who it's for

Banks, lenders and fintechs

Check the number before payouts, payee changes and account recovery.

Gambling operators

Check before withdrawals and changes to payment details.

Marketplaces and online retailers

Protect seller payouts and stored-value accounts from takeover.

Contact centres

Check the number before an agent acts on a caller's request to change account details.

Where it fits

Provero runs at the moment of the sensitive action, before the code is sent or the money moves. Clean results proceed. Risky results escalate to review or an extra verification step.

Many changes are genuine, so the aim is to step up, not to block. Start with the actions where a hijacked number costs most: password resets, payouts and changes to bank or contact details.

Real-time
Before codes, resets, payouts and account changes.
At onboarding too
The KYC waterfall screens numbers before an account exists.

See the KYC waterfall →

Why Provero

  • Fast at the sensitive moment

    Built for real-time use, so the check fits between the request and the code being sent.

  • Resilient where it matters

    Multiple layers of redundancy protect the flows customers rely on to get into their accounts.

  • Wider verification, same integration

    When a request needs more, further identity checks are available through the same API and account.

Pricing

Priced per check from one prepaid balance and quoted on your volumes and the networks you need.

See pricing → Ask about volume pricing →

Account protection FAQ

Does this replace one-time passcodes?

No. It makes them safer. Check the number first, then send the code to a number you have reason to trust.

What should we do when a number has recently changed hands?

Step up. Ask for another verification step or send the action to review. Many changes are genuine, so blocking outright loses good customers.

Check the number before you send the code

Run a free check now. Then create an account and talk to us about protecting your own flows.