Verifex
Create an API key

Verifex Shield

Fraud and AML transaction monitoring

Check every transfer, withdrawal and payout against rules you own. Shield screens the other party for sanctions and PEP in the same call, and keeps a signed record of every decision.

Talk to us Read the Shield docs
Generally available. Switched on per account by Verifex.
Today's transactions

  • Card top-up, £120

    Normal for this customer

    Clear

  • Transfer, £6,000 to a new recipient

    Above the high-value limit

    Review

  • Five transfers of the same amount today

    Repeated amount pattern

    Review

  • Payout to a possible sanctions match

    Recipient needs a senior check

    Escalate

  • Transfer to a blacklisted account

    On your blacklist

    Block
Example screen. Not real customer data.
possible answers, from clear to block
5possible answers, from clear to block
APIs, one engine: native and SanctionScanner-compatible
2APIs, one engine: native and SanctionScanner-compatible
days of past decisions to test a rule change on
90days of past decisions to test a rule change on
webhook event types
17webhook event types

What Shield checks on every transaction

Send every transaction, including small ones. Velocity and AML rules only see what they are sent.

Amount and limits

High-value transfers, daily limits and amounts far above a customer's normal.

Velocity and patterns

Many transfers in a short time, or the same amount sent again and again.

New recipients

First payment to a beneficiary, or many different accounts in a month.

Device and behaviour

New devices and unusual session behaviour, when you send those signals.

Currency and merchant risk

Risk tables for currencies and merchant categories that you control.

Sanctions and PEP

The other side of the payment is screened through Verifex in the same call.

One clear answer for every transaction

A sanctions check that times out or cannot confirm a clean result never comes back as clear. The answer is held at review or above.

  • clearLet it through.
  • reviewLet it through, and a person looks at it (a case is opened).
  • delayHold it briefly, then review.
  • escalateHold it for a senior reviewer.
  • blockStop it. Always the answer for a blacklist hit, a strong sanctions match (score 95 or more) or a failed SIMA biometric check. A possible sanctions match escalates instead.

Rules your compliance team can change

New rules can run in shadow mode first, so they are recorded without changing any outcome until you are ready.
  1. 01

    Tune

    Change a threshold or score in the dashboard or by API. No engineering ticket.

  2. 02

    Simulate

    Run the change over up to 90 days of past decisions and compare the results.

  3. 03

    Deploy

    Ship exactly what you simulated, with a reason and an approver on record.

How rule changes work

Cases, lists and AML reports included

Cases

Every review opens a case with an append-only history, assignment and a final verdict.

Lists

Blacklists and whitelists for accounts and customers, applied on every decision.

Monthly AML reports

The S1 to S4 scenarios are counted per sender and beneficiary, with reports each month.

Webhooks

17 event types, from new decisions to closed cases and changed rules.

Cases, lists and reports in the docs

Moving from SanctionScanner? Keep your integration.

Shield speaks a SanctionScanner-compatible API: the same paths, fields and response envelope, plus Shield extensions. Most teams change the base URL and the key. New integrations can use the native API.

Send your first transaction Verifex vs SanctionScanner 
# SanctionScanner-compatible: same path, same fields
curl -X POST https://api.verifex.tech/api/Transaction/ExecuteTransaction \
  -u "key_id:vfx_your_api_key" \
  -H "Content-Type: application/json" \
  -d @transaction.json

A signed record of every decision

Each decision stores what Shield saw, the rule versions it used and the result, with a SHA-256 over the content and a server signature. The record cannot be edited, and you can replay a decision to check it gives the same answer with the rules it recorded.

Fraud and compliance stay separate

Shield uses the counterparty screen as an input, but a fraud result never becomes a sanctions result, and the reverse never happens either. Only a strong sanctions match blocks; a possible match escalates to a person.

Questions about Shield

Something else? Talk to us.
What is Verifex Shield?

Shield is fraud and AML transaction monitoring. You send each transaction; Shield answers clear, review, delay, escalate or block, with the rules that fired, a score, a sanctions and PEP screen of the other party, and a signed record of the decision.

Is Shield available now?

Yes, Shield is generally available. It is switched on per account by Verifex rather than through self-serve signup, so talk to us and we will enable it and set up your rules with you.

Can we move from SanctionScanner?

Yes. Shield offers a SanctionScanner-compatible API with the same paths, fields and response envelope, plus Shield's own extensions. Most integrations change the base URL and the API key.

Can our compliance team change rules without engineering?

Yes. A rule change is simulated over up to 90 days of past decisions, reviewed, and then deployed exactly as simulated, with a reason and an approver recorded against the new rule version.

Turn on Shield for your account

Tell us how your transactions flow and which decisions you need to control. We will switch Shield on and set up your first rules with you.

Talk to us Read the Shield docs

Generally available. Shield is switched on per account by Verifex; it is not open to self-serve signup. Example panels on this page are illustrative and do not represent a live customer event.