Know when a merchant changes, before it costs you
Monitoring pulse
Live
5,120
Monitored
46
Changes open
4 min
Median triage
Changes caught · last 6 re-scans
Feb
Mar
Apr
May
Jun
Jul
Zoven re-scans every approved merchant on a schedule, compares each scan against the last, and tells your team what changed. Quiet merchants stay quiet, and every real change opens a case.
Trusted by risk and compliance teams
Watch every merchant, without watching all of them
The point of monitoring is to catch the one merchant that changed. Zoven does the re-scanning and the comparing, so your team only looks at what actually moved.
Group merchants into cohorts
Bundle entities by risk rating or MCC code and give the whole group one schedule. Merchants that match join the cohort on their own.
One schedule
for the whole cohort, not each merchant
Every scan compared to the last
Each re-scan is diffed against the previous one, then split into what changed, what it means for risk, and what stayed the same, with the highest-impact moves at the top.
Ranked
by risk weight, highest first
Every scan kept on the record
Scans are never overwritten. Each re-scan links to the one before, so you can open any entity and see exactly what was known, and when.
Full history
every scan, never overwritten
What a missed change really costs
A clean merchant at onboarding is not a clean merchant forever. The one that turned after go-live is the chargeback, the fine, or the name in the news you did not see coming.
A clean score has a shelf life
The merchant that passed at onboarding can quietly change its category, swap in a redirect, or move its storefront months later. The tell is in the next scan, not the original application.
Risk does not stop at sign-up
A merchant that scored clean today can drift into something else next quarter. Onboarding is one moment; the exposure lasts the whole relationship.
Re-reviewing by hand cannot keep pace
Every approved merchant deserves the same rigour on every cycle, but a person re-reading sites one by one cannot re-check a thousand of them on schedule. Something always gets skipped.
One re-scan, one diff, one case
Zoven re-scans a merchant on your schedule, checking the sections most likely to drift, and compares each result against the last. Any meaningful change becomes a case with a fresh score, and the before and after stays attached, so a decision made today still makes sense next quarter.
Bluepeak Retail
Jul 12 re-scan
was 41 · +21 drift
Website
live → redirects
MCC category
5045 → 7995
Certificate
valid → valid
Adverse media
none → 1 hit
Sanctions
clear → clear
3 changes · case opened
You scope each re-scan
Pick the sections a cohort re-checks, across identity, compliance, domain, contact and adverse media. Stable areas sit out.
No manual re-reviews
Set a cadence once and the whole portfolio re-scans on its own, every time.
A change, not just a new number
Each re-scan comes with a plain call: no change, review, re-run EDD, or offboard.
The before and after stays visible
Every factor that moved between scans is on the record, so any change is easy to defend.
The checks a re-scan can run
A re-scan re-checks the sections you scope for a cohort and compares them against the last scan. These are the dimensions it can watch for drift.
Business category
Detects when the site’s real MCC drifts away from what was approved.
Redirects & domain
Catches a silent switch to another domain or a new redirect after go-live.
TLS certificate
Flags new expiry, self-signing, or a broken trust chain since the last scan.
Adverse media
Re-searches news and court records for anything new on the entity.
Sanctions & PEP
Re-runs AML screening against sanctions, PEP and watchlists on every cycle.
Storefront
AI vision re-checks premise photos for a moved or faked setup.
Registration status
Re-verifies company registration and licence validity.
Contact & payment
Re-confirms contact details and payment routing haven’t changed.
The dimensions re-checked vary by market and plan.
From a schedule to a case, in three steps
Set a cadence and the re-scans run on their own. Your team only steps in when something actually changes.
Set the cadence
Choose weekly, monthly, or quarterly re-scans per merchant or portfolio, through the API or the dashboard. No manual re-reviews.
01
weekly, monthly, or quarterly
Zoven re-scans
The engine re-checks the sections you scoped for the cohort, compares them against the last scan, and attaches the difference.
02
re-scanned automatically, end to end
Your team reviews the change
Any meaningful change lands as a case in a queue. Dismiss, escalate, re-run EDD, or offboard, with a full audit trail.
03
review and sign off with maker-checker
Re-scan · Bluepeak Retail
LOW → HIGH
MCC changed to high-risk
Insight
Prohibited keyword appeared
Difference
SSL still valid
Unchanged
The change feed, sorted so nothing hides
Every re-scan splits into three: insights worth a look, plain differences, and everything that stayed the same. Your team reads the changes, not the whole profile again.
Set the cadence
Re-scan weekly, monthly, or quarterly.
Scope the scan
Re-scan only the modules you care about.
Sorted changes
Every change split into insights, differences, and unchanged.
Alerts to cases
Each alert opens a case: dismiss, escalate, or offboard.
Connect it to how you already work
Schedule re-scans and pull changes through the channels your team and systems already use.
REST API
Trigger a re-scan and pull the diff report by ID.
Webhooks
Get a callback the moment a re-scan finds a change.
Dashboard
Set cadences and review diffs without writing code.
API keys
Secret keys for your servers, publishable keys for the browser.
Cohort management
Create cohorts and set their schedules from the API or the dashboard.
Scan history
Fetch an entity’s full chain of scans and the diff between any two.
Alerts feed
Every change surfaces as an alert in the monitoring section for review.
Audit export
Export an entity’s scan history and decisions for a regulator.
Available channels vary by market and plan.
A platform built for a monitoring desk
The parts that make Ongoing Monitoring fit how your team already works, not the other way round.
Cohorts & scope
Group merchants into cohorts, set each one’s cadence, and scope every re-scan to the checks that matter. When something moves, an agent summarises it.
Cohorts group entities by risk rating or MCC code
Each cohort runs weekly, monthly, quarterly, or on demand
Scope a re-scan to only the modules you care about
Cohort · High-risk merchants
214 entities
SCHEDULE
Quarterly · next run Aug 1
The whole cohort re-scans together on this cadence, and Auto Re-scan keeps membership current.
Auto Re-scan
SCOPE
4 of 6 modules re-checked
Business identity, adverse media, sanctions and certificate. Skips the modules that rarely move.
Scoped re-scan
Membership · Risk ≥ High, MCC 5045
auto-updated
Cadence & thresholds
Set the re-scan cadence and the drift bands that match your risk appetite, so changes and recommendations reflect your policy.
Drift bands
None
0
Minor
1–15
Notable
16–30
Major
31+
Action per band
None
Keep monitoring on schedule
Minor
Log the change, no action
Notable
Send for analyst review
Major
Escalate for EDD or offboarding
The re-scan chain
Every scan is a permanent record. Each re-scan links to the one before and compares against it, so an entity’s full history is one click away.
Original scan · onboarding
Mar 12 · risk 41
Re-scan · scheduled
May 12 · risk 41 · no change
Re-scan · scheduled
Jul 12 · risk 62 · +21 drift
Compared against May
3 differences · 1 insight surfaced
Catches the change a spot-check would miss
The depth behind the diff: the checks that separate a merchant that quietly turned from one that stayed the same.
Re-reads the site to detect the real business category and flags it when it moves away from what was approved
Re-checks where a URL really lands, so a silent switch to another domain after go-live gets caught
AI vision re-checks premise photos for a setup that moved, a faked visit, or a mismatch with the map listing
Re-inspects the TLS certificate for new expiry, self-signing, and a broken trust chain since the last scan
Good to know
How does ongoing monitoring work?
Put an approved merchant into monitoring and Zoven re-scans its full profile on the cadence you set. Each re-scan re-checks the same 40+ signals used at onboarding, compares the result against the previous scan, and turns any meaningful change into a case. Merchants that didn’t change stay quiet and out of the queue.
How often does it re-scan?
What counts as a change worth a case?
Can our team review before acting on a change?
How does the AI monitoring agent fit in?
Bring a handful of approved merchants to a walkthrough and watch them re-scan, diff, and land in a queue.