Sanctioned-entity identification,
with a record that holds up.
Send Clarado a name. It checks the global sanctions and watch lists, weighs how strong the match really is, and returns one clear decision: clear, review, or blocked. Every check is written to a tamper-evident ledger, so months later you can prove exactly what you checked and when.
A duty that is easy to get wrong, in both directions.
Banks, exchanges, marketplaces and exporters are required to check the people and companies they deal with against government sanctions and watch lists. The stakes are lopsided. Miss a real match and the fines are severe and the reputational damage is worse. Block an innocent customer and you lose the sale and insult them. The lists are long and change constantly; names arrive misspelled, transliterated and in different alphabets; and most teams still handle it with a fragile spreadsheet or a heavy, costly vendor platform that takes months to install. Clarado makes it a single, trustworthy call.
Match. Decide. Prove.
Matching across spellings, transliterations and alphabets, scored so a weak partial match can never block a sale on its own. Strong corroboration blocks; a thin signal is shown, never enforced.
Every request resolves to clear, review, or blocked. When anything is uncertain Clarado answers review, never a silent clear — a held case is a question for a human, not a risk that slipped through.
Every check is written to a tamper-evident ledger with a signed chain, so no entry can be quietly changed after the fact. Months later, the answer to what you checked and when is already there.
The answer is half of it. The proof is the other half.
Most tools of this kind treat the audit trail as an afterthought and bolt it on late, when a regulator or a customer finally demands it. Clarado is built on a tamper-evident ledger from the first day: append-only, signed, with actor and before/after state. For work where trust is the product — sanctioned-entity identification, compliance, regulated operations — that is the difference between a demo and something a serious buyer will actually run.
No record is updated or deleted. Corrections are new facts, and the history stays intact.
Each entry is cryptographically chained to the last, so tampering is detectable, not silent.
Who was checked, what was decided, what changed — reconstructable on demand for an auditor or partner.
What runs, and what it runs on.
| Area | What it does | Built on |
|---|---|---|
| Public | Service-status endpoint for uptime checks. | Clarado core |
| Customer / integrator | Identification API, one name or in batch; read-back of any past check; a billing settlement signal; signed webhooks. | RCI Auth per-client keys · FARO alerts · tamper-evident ledger |
| Admin / compliance | Single sign-on with roles for owner, compliance officer, reviewer and auditor; a review and adjudication queue; subscriber and API-key management; list and threshold control. | RCI Auth SSO · tamper-evident ledger audit · RCI Projects |
| Platform / data | Sanctions-list ingest and refresh; the name-matching engine; an append-only audit trail; data erasure by key destruction; usage analytics; in-app bug reporting. | trade.gov list source · FARO · Usher · RCI Reports · tamper-evident ledger |
RCI modules in amber; third-party sources in grey.
Screen with confidence. Prove it later.
See Clarado against your onboarding and transaction flow, with your own names in the loop.