Blocklisted merchants

Block a bad merchant once.
Catch them every time they try to come back differently.

Automatically screen every new merchant against your blocklist and their connected entities before they onboard.

Trusted by

A merchant you terminated just 
re-registers and tries again

A static list only catches an exact name match, so the same operator can return under a slightly different name and pass straight through.

Without Blocklist

Bad merchants tracked in scattered spreadsheets and analyst memory.

Screening catches the exact name only, so a small change slips through.

Knowledge stays trapped with one analyst or one team.

VMSS and MATCH cover terminated merchants only. They do not address other types of blocklisting reasons.

With Blocklist

A living blocklist your team controls and grows.

Every applicant screened automatically against your list.

Connected entities flagged too, not just the single name.

Every block explainable and audit-ready.

Build your list

From a static list to live merchant screening in three steps

01

02

03

Build your blocklist

Add your blocklisted merchants, their identifying properties, and the reasons they were blocklisted.

Screen every merchant, and the network around them

When you screen a new merchant, we enrich their data, uncover related entities, and compare those properties against your blocklist to identify hidden matches.

Act on a clear, defensible result

If a match is found, we alert you and show exactly which blocklisted merchant was matched, which properties triggered the match, and why.

Everything your team needs to stop repeat offenders, built in

Multi-properties matching, not just exact-name matching.

Explainable blocks with property, reason, and confidence.

Audit-ready evidence on every match.

Connected entities analysis to identify matching properties across the merchant's eco-system.

Fits the screening flow your team already uses.

Pre-onboarding filtering for sales teams: reject known-bad leads across a shared network, without exposing each team's full list.

What we do differently
One bad merchant protects you from the rest.

Block one merchant, catch the network. Blocklist maps connected entities - shared registrations, reused domains, same operator behind a new name.

You always know exactly why a merchant was blocked.

Every block shows the matched property, the reason, and a confidence level. Your compliance team can explain and defend every decision.

MANAGE YOUR BLOCKLIST PROFESSIONALLY.

Maintain a single, shared blocklist your entire team can access. Add, edit, and organize entities with ease, and keep a complete version history of every change.

How it works

From your blocklist to a shared risk network

Turn every blocked merchant into stronger protection for every future onboarding.

How it works
Your blocklist, automated
  • Upload and manage your own list of known-bad merchants
  • Screen every applicant automatically at onboarding
  • Catch similar properties on connected entities
  • Explainable, audit-ready results on every match
Finding connected networks
Built-in network detection
  • Each blocked merchant automatically reveals related entities you did not add yourself
  • Shared registrations, reused domains, and overlapping operators are surfaced for you
  • Fraud rings hiding behind separate storefronts are flagged automatically when any connected merchant is blocked
Network intelligence
Shared industry protection
  • When another provider blocks a bad merchant, you benefit too - without seeing their confidential details
  • A merchant caught once is recognized across the entire network
  • The more providers participate, the harder it becomes for bad actors to find a way back in
faq

Questions, answered

What is a merchant blocklist and how does Ballerine's work?
What happens when a blocklist match is found during onboarding?
Does the blocklist only check the merchant name, or does it go deeper?
Can I import an existing blocklist or industry-shared lists into Ballerine?

Stop paying twice for the same bad merchant.