Define the identity behind the order
Use known legal names and IDs for the parties your policy selects. Keep the store or order reference as context.
Sanctions screening for ecommerce and marketplace teams
Screen the parties behind your commerce relationships.
Run sanctions checks for sellers, suppliers and payout parties. Review possible matches and save the reasons for each choice. Keep those results with the right store or order.
Paid plans start at $59/month for 5,000 checks each month. API and review dashboard included. See pricing.
250 free live screenings. One lifetime allowance. No credit card required.
SanctionsKitIllustrative workflow
Seller & partner review
WorkflowNext step
Individual sellerReview identity
Business merchantCompare source facts
Existing partnerRevisit the relationship
Keep every seller attached to its result.
API requests and portfolio batches share the review workflow.
Built around your work
An order has more than one useful name field.
A store may keep its name when the legal seller changes. The payout recipient can be different again. Past sales and a familiar storefront do not settle a possible match for a new company.
Keep order exceptions understandable
Screen a merchant portfolio in a batch or connect checks to onboarding through the API. Track errors as well as completed results.
Use clear application states
Review possible matches and changes to the legal seller. Handle fraud, bank ownership, goods, and destination checks separately.
Put it into practice
Connect screening to the next business step.
The storefront and payout agreement name different businesses.
An online store keeps its brand while the legal seller changes. Operations needs to find the new company’s result without losing the former seller’s history.
The store reference links distinct party checks. Reviewers can explain which person or company each result covers.
- 01
Choose the relevant workflow
Identify the actual seller, supplier, buyer, or recipient required for the check. Confirm the role and known details.
- 02
Screen the known legal identity
Run the chosen sources and save result IDs. Assign possible matches and leave failed checks open.
- 03
Record the next action
Record the review and link it to your commerce process. Revisit the party list when a seller or payout recipient changes.
A fictional store moves into a company
An invented sole trader moves the store into Example Meadow Retail Ltd. The platform records the company as a new subject. The person’s earlier screening remains in history. If policy requires a check of a changed payout recipient, that party is identified separately too.
A company-name match reaches the reviewer with the seller reference. The analyst compares source facts and known registry details, notes missing evidence, and follows the review process. Good sales history does not resolve a name match. Payout approval stays in the platform’s own workflow.
Scroll horizontally to compare every column.
| Work item | Screening evidence | Boundary |
|---|---|---|
| Storefront | Commercial reference that connects the work. | A store name is not necessarily the legal seller. |
| Legal seller | Person or organization subject and selected-source result. | A change of legal entity needs its own review. |
| Payout recipient | Separate identity and any required screening. | Bank-account control and payment-fraud checks remain separate. |
Test a merchant change and a portfolio file
Start free with 250 live screenings. Use them in the API or dashboard. Your first workspace gets this allowance once, with no monthly reset. No credit card is needed.
Try a legal seller and payout party with facts your team may share. Ask a reviewer to find each result before and after a company change. Each result should show who was checked.
The optional demo uses made-up records for a quick tour. Use the sandbox to test errors without using live checks.
Try a small batch for an existing merchant list and the API for an onboarding event. Match every row to a result or error. Add related-party checks and rescreens to your estimate on pricing. Confirm the exact sources in coverage before production.
Use store references without confusing identities
The store name helps staff find the relationship. It does not always identify the legal seller. Keep the actual subject and role clear when the same storefront starts trading through a new company or changes its payment details.
The customer-screening guide gives examples of evidence review. Sanctions checks do not replace fraud checks, bank-account verification, or decisions about restricted goods and shipping destinations. Keep those tasks and their approvals in your process.
TRY IT WITH YOUR TEAM
See if SanctionsKit fits your team.
Check your sources, try a free live check and estimate your monthly cost.
Check source coverage
Find your required sources, what they cover and when they were refreshed.
Explore coverageTry a match review
Use your free live checks to find possible matches. Compare the evidence and save a decision.
Start with 250 free checksEstimate monthly cost
Count new checks, rows in uploaded lists and repeat checks from monitoring.
See workload examples
Evaluate the fit
Screening questions for ecommerce.
Is a store-name check enough to screen a seller?
Not always. Find the actual legal person or company behind the store and use its known details. Keep the storefront label as context. A trading name alone may describe a different or incomplete subject.
Can we screen suppliers as well as merchants?
Yes. Screen each required person or company with the appropriate sources. Use relationship types or your own references to keep the role clear. Your policy determines which suppliers, buyers, or other parties need checks.
Does sanctions screening replace fraud checks?
No. It checks names against the lists you choose. Your team still needs to check payment fraud, who owns the bank account, identity and account abuse.
Can we check an existing merchant portfolio?
Yes, with supported JSON or JSONL batches. Each row has its own result and coverage. Track failed rows, review possible matches, and count completed subjects when estimating usage. Native Excel and CSV uploads are not supported.
Does a no-match approve a shipment of goods?
No. It does not resolve restricted goods, destination rules, end use, or other shipping controls. Finish the separate checks required for the order.
See SanctionsKit in action
Explore screening and review for ecommerce.
Start with 250 free live checks. Use the API or dashboard to review matches and save decisions. Choose a paid plan when you need more checks.
250 free live screenings. One lifetime allowance. No credit card required.