For the compliance lead at a payments team
Review the match.
Keep the reason.
Screen your customer CSV. Save who reviewed each match, the decision, and the reason. Re-screen selected customers daily or weekly on a paid plan.
Actual app views. Fictional customer and source records.
A reviewer's workflow
A customer check.
A decision you can trace.
Meet Alex Sample. One fictional customer,
shown in the actual CirclesCheck app.
Potential match · compare identifiers
Which customers need a closer look?
Alex Sample returns a potential name match. Compare the customer’s identifiers with the source record: the birth date conflicts, so the name alone cannot settle the review.
Screen a customer CSV
For the customer list on your desk
Review today's matches.
Plan the next checks.
CSV batch screening
Bring a customer list, check identifiers, and review results row by row. Failed rows stay visible so an incomplete batch cannot become a clean result.
See a sample CSVRecurring customer monitoring
Choose daily or weekly screening on a paid plan. Scans share your screening allowance; changed findings give your team a reason to return.
Plan your monitoringReview records and exports
Classify findings and save the reviewer’s reasoning. Keep a PDF with the screening evidence and the recorded decision.
Inspect the sample reportAPI integration
Screen during onboarding, review findings, and retrieve saved evidence through the API. Start with a sandbox key and keep credentials on your server.
Try the API examplesTest with the person who reviews your matches
Save one decision.
Open the evidence together.
Screen fictional customer data, record a review, and inspect the PDF with your colleague. Confirm the sources your customer list needs before production.