StatusSolution for gaming and payments

Sanctions, PEP and adverse media.Screened after sign-up too.

VerifyMe screens your customers against PEP, sanctions and adverse media sources at onboarding, and keeps screening the same file 24/7 after that. You set the thresholds. Every hit and every decision is logged.

Screening hit · month 5Found by ongoing monitoring
SanctionsListed after onboardingHit
PEPNo matchClear
ProductVerifyMe
ServiceSet up and tuned with you
Expertise30 years of identity data
The problem

PEP and sanctionschange every day.

3

Screening types VerifyMe keeps running on the same customer file after onboarding: PEP, sanctions and adverse media.Source: VerifyMe, trustbystrike.com

RecordMonth 0
ScreeningNo hit
StatusApproved

A customer is screened at sign-up

Example: a customer opens an account. The name is screened against PEP, sanctions and adverse media sources. There is no hit.

RecordMonth 5
ScreeningNo hit
StatusSanctioned, unknown to you

A sanctions list is updated

The customer's name is added to a sanctions list. If you only screened at sign-up, your file still says the customer is clear.

RecordMonth 11
PEP statusNot a PEP
StatusPEP, unknown to you

The customer takes a public role

The customer is appointed to a public office. Your file still treats them as a standard customer, without enhanced checks.

The result: a customer who was clear on day one, and a file that never heard otherwise.

See the solution →
The solution

One solution.Three parts.

A one-off screen tells you who a customer was on the day they signed up. Staying compliant needs screening that keeps running, thresholds that fit your risk policy, and people who know where screening goes wrong. We bring all three.

Product

VerifyMe

Screening at onboarding and ongoing monitoring on the same customer file, inside one flow.

Runs 24/7Live
PEP, sanctions and adverse media
Thresholds you can tune
Every decision logged
Service · Day one, then ongoing

We set it up and tune it with you

We build the flow with you and set thresholds that match your risk policy.

  • Test with fake data in a sandbox
  • See the effect on review volume
  • Embedded in your own page
Expertise · 30 years

Identity data and compliance

We have worked with identity data for regulated organisations for 30 years.

  • ISO 27001 certified
  • Hosted and operated in the EU
  • 300 clients in regulated markets
How it fits

One file per customer.Screened every day.

The customer is screened once at onboarding. After that, monitoring keeps running on the same file. When a list or a source changes and the customer matches, the hit lands with your team.

Screening queueAll 4To act on 3Example
CustomerCheckWhy it firedResult
C-1042SanctionsPut on a list after onboardingHit, sent to review
C-2210PEPAppointed to a public officeReview
C-3381Adverse mediaNamed in a news reportFlagged
C-4019All checksNo change since the last checkClear
1

A customer is onboarded

Screened once in your VerifyMe flow.

2

Monitoring keeps running

24/7, on the same customer file.

3

A source changes

A new entry matches the customer.

4

The hit reaches your team

Logged with the check, the source and the rule.

No re-onboardingNo second customer fileNo developer release
What it picks up

PEP and sanctions.Adverse media.

Choose a change to see what happens at the source, what reaches your systems and what your team can do with it.

24/7Ongoing monitoring
3Screening types
1File per customer
7+Languages in the flow
ISO 27001Certified

VerifyMe is live in 8 industries, with connections to local registries and KYC providers per country. Thresholds and review rules follow your own risk policy.

What you get

Hits when lists change.Fewer false alarms.

A change on a list reaches the customer's file when it happens, instead of at the next periodic review.

01

Changes found when they happen

Monitoring runs 24/7 on the same file, so a new listing does not wait for a periodic review.

24/7 monitoringOn the same file
02

Fewer false positives

Tune the thresholds and see what each change does to the volume your team has to review.

Review volume visiblePer threshold change
03

One flow, one file

Onboarding, screening and monitoring run in the same VerifyMe flow. There is no second tool to keep in sync.

No second customer fileOne flow
04

Ready for an audit

Every decision is logged with the check, the source and the rule that applied.

Every decision loggedCheck, source and rule
Our view
“A clean screen at sign-up only tells you about that day. Lists keep changing, so the screening has to keep running on the same file.”
STRIKE Group · VerifyMe team
30 yrsExperience in identity and data
300Clients across regulated markets
ISO 27001Certified, hosted in the EU
How we start

A test in the sandbox.Before you go live.

You see how screening and thresholds behave in your own flow before any real customer is checked.

1

Book a call

Tell us your markets, your risk policy and how you screen today.

A 30-minute call
2

Test in the sandbox

Run the flow with fake data and tune the thresholds. No real check is run.

Sandbox
3

Go live

Embed the flow in your own page. Monitoring starts on every new file.

24/7 monitoring

Pieter Stam

Your contact at Strike Group

Tell me how you screen customers today and where the false positives come from. I'll set up a sandbox test with you.

Book a 30-minute call
info@trustbystrike.com · +31 (0)88 835 70 70
FAQ

What complianceteams ask first.

Something else? Ask it in the call. You speak to the people who build the flow.

What does VerifyMe screen against?

PEP, sanctions and adverse media sources. Screening runs at onboarding and keeps running on the same customer file after that.

How often are existing customers screened?

Ongoing monitoring runs 24/7 on the same file. A new match is raised when it happens, not at the next periodic review.

Can we control how many false positives we get?

Yes. Thresholds are tunable, and you can see the effect of a threshold change on your review volume.

Can we show an auditor why a decision was made?

Every decision is logged with the check, the source and the rule that applied.

Do we need a developer to change the flow?

No. You change the flow in the builder, without a developer or a release cycle. You can test changes with fake data in a sandbox first.

What does it cost?

Pricing depends on your volumes and the checks in your flow. We go through it in the first call.

Keep screeningafter sign-up.

We set up a sandbox test with you, so you see how screening and thresholds behave before any real customer is checked.

Sanction screeningSee it in your own flowBook a demo