From a static list to live merchant screening in three steps
01
02
03
Build your blocklist
Screen every merchant, and the network around them
Act on a clear, defensible result
Automatically screen every new merchant against your blocklist and their connected entities before they onboard.

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


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.
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.
01
02
03
Build your blocklist
Screen every merchant, and the network around them
Act on a clear, defensible result
Block one merchant, catch the network. Blocklist maps connected entities - shared registrations, reused domains, same operator behind a new name.
Every block shows the matched property, the reason, and a confidence level. Your compliance team can explain and defend every decision.
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.
Turn every blocked merchant into stronger protection for every future onboarding.



A blocklist is a maintained list of known-bad merchants your risk team screens every new applicant against. Ballerine lets you build and manage your own list, and automatically checks new applicants against it including connected entities like UBOs, associated domains, and related businesses, not just exact name matches.
When a match is detected, the applicant is flagged in your workflow with the match details (which entity matched, why, connection type). Your team decides what to do: Auto-decline, escalate to manual review, or request more info. Ballerine surfaces the signal; you set the policy.
It checks beyond the merchant name related entities, beneficial owners, domains, and connected businesses are all screened. A bad actor who reapplies under a new business name but the same UBO or domain gets caught.
Yes. You can import your own internal blocklist and layer it with data from industry sources, card scheme programs (like Mastercard's MATCH/Member Alert), and partner-shared lists - all managed in one place.
