Table of Contents
Denied party screening for marketplaces is a check you run on the people who buy and sell on your platform. It compares their names against government watchlists. If a buyer, seller, or their address matches a sanctioned party, you stop the transaction. An online marketplace connects many small traders. That scale makes screening harder, and it makes the risk bigger.
Marketplaces are not simple shops. You hold seller accounts, buyer accounts, payment flows, and shipping data. Any of those can involve a party that a government has restricted. This guide explains what to screen, when to screen, and how to keep the process fair to honest users. For the wider topic, start with our guide to denied party screening.
Why marketplaces carry extra risk
A single exporter knows its customers. A marketplace does not. You onboard thousands of sellers and millions of buyers. You rarely meet them. Bad actors like that anonymity. They open accounts, sell goods, and move money through your rails.
Regulators expect you to know who uses your platform. If a sanctioned person sells through you, the platform can be liable. The same rule applies to buyers in embargoed regions. Ignoring this can bring real fines. See our overview of the penalties for dealing with a denied party.
Who and what you need to screen
Screening is not just for sellers. Many parties touch a marketplace order. Each one can carry risk. Map them before you build any rules.
- Sellers and their business owners
- Buyers and their shipping addresses
- Payout recipients and bank details
- Drop-ship suppliers behind a seller
- Freight and logistics partners on the order
Beneficial ownership matters too. A clean seller name can hide a sanctioned owner. Watchlist rules often cover companies that a listed person owns. Read our explainer on the 50 percent rule for sanctions to see why ownership counts.
The lists to check
You screen against government lists, not a private guess. Different lists cover different risks. A marketplace that ships worldwide should check several. Start with the main US lists, then add local ones for your region.
| List | What it flags |
|---|---|
| OFAC SDN List | Sanctioned people and firms you cannot deal with |
| BIS Entity List | Parties of export concern needing a license |
| Denied Persons List | People barred from US export activity |
| Consolidated Screening List | Many US lists combined in one search |
The consolidated list is a handy starting point. It pulls several US sources together. You still add sanctions lists from your own jurisdiction. Match your list set to where your buyers and sellers live.
When to screen in the user journey
Timing decides how well screening works. Check too late and goods already shipped. Check only once and you miss new listings. Build screening into set points in the flow.
At onboarding
Screen every new seller before they list. Screen the owner and the payout account too. Block the account if you get a confirmed match. This stops bad actors at the door.
At checkout
Screen the buyer name and the ship-to address. A clean seller can still ship to a denied party. Hold the order if a match appears. Release it only after review.
On a schedule
Lists change often. A user who was clean last month may be listed today. Re-screen your active accounts on a set cycle. Our guide on how often to run denied party screening covers good timing.
Handling matches and false positives
Most alerts are not real hits. Common names trigger many matches. A buyer named John Smith is not a sanctioned John Smith. You need a review step, not an instant ban. That keeps honest users happy.
Compare more than the name. Check date of birth, country, and address. Look at how strong the match is. Clear the alert if the details do not line up. Keep a record of why you cleared it. Our guide on false positives in denied party screening shows the full method.
Watch for evasion too. Some users hide who they are. A payout to a different country than the seller is a warning sign. Learn the common sanctions evasion red flags so your team spots them.
Automate at marketplace scale
Manual screening breaks at volume. You cannot check millions of orders by hand. Automated screening runs the check in the background. It flags only the alerts that need a human. Your team then reviews that smaller pile.
Good automation still needs people. A tool flags a match. A trained reviewer makes the call. See our comparison of automated versus manual denied party screening to balance the two.
- Screen at onboarding, checkout, and on a cycle
- Use an API so checks run in real time
- Route only real alerts to human review
- Log every decision for your audit trail
Keep records of what you screened and when. A clear audit trail proves you did the work. It also helps if a regulator asks questions later.
Frequently Asked Questions
Does a small marketplace really need to screen?
Yes. Sanctions rules apply by activity, not by company size. A small platform can still touch a denied party. Start simple and grow the process. Our guide for denied party screening for small business shows a lean setup.
Do I screen buyers or only sellers?
Both. Sellers move goods and receive payouts. Buyers receive shipments and can sit in embargoed places. Screen every party in the order. That includes the ship-to address on each sale.
What if the seller uses a hidden supplier?
Drop-ship suppliers add risk you cannot see. Ask sellers to name their suppliers. Screen those parties where you can. Flag sellers who refuse to share this detail.
Key Takeaways
Denied party screening keeps sanctioned users off your platform. Screen sellers, buyers, owners, and payout accounts. Check them at onboarding, at checkout, and on a schedule. Use government lists, review matches with care, and automate to handle scale. Keep a record of every decision. To build this into your platform, read the full denied party screening hub and then contact our team for help.