Compliance Providers handle KYC and AML. Our API formats these results as reusable W3C verifiable credentials. Relying Parties can validate in milliseconds with no duplicate checks, no shared PII, and a full audit trail.
Performs KYC, AML, and compliance checks using its own processes.
Formats issuer-attested results as signed W3C credentials, anchored on-chain
Checks credential validity: signature, revocation, issuer trust
We never see your customers' PII. We never make compliance decisions. We are infrastructure.
Identity verification accuracy
Compliance decision correctness
Data quality of attested claims
Credential format integrity (W3C)
Cryptographic signature validity
On-chain anchor availability
Acceptance policy definition
Issuer trust decisions
Regulatory compliance of decisions
Invalid signature — rejected by verifier automatically
Revoked credential — rejected by verifier automatically
Incorrect KYC data — issuer responsibility
Policy mismatch — relying party responsibility
The Compliance Provider performs KYC/AML using its own processes. Then they call our API to format the results as a signed W3C Verifiable Credential.
The credential is cryptographically signed and anchored on-chain for independent auditability. The issuer's attestation is preserved exactly as provided.
Any Relying Party checks the credential's validity (signature, revocation status, issuer trust) in milliseconds without re-doing KYC.
Relying parties accept existing credentials instead of repeating KYC from scratch.
Check credential validity in milliseconds, not hours or days.
W3C Verifiable Credentials v2.0 with auditable attestations.
Reduce onboarding friction and improve conversion rates.
| Plan | Included | Overage | |
|---|---|---|---|
| Starter Free | 50 issuances/month | -- | Get Started |
| Professional Popular | 500 issuances/month | $0.20 per issuance | Subscribe |
| Enterprise | Unlimited | $0.12 per issuance | Contact Us |
| Plan | Included | Rate | |
|---|---|---|---|
| Developer Free | 100 checks/month | -- | Get Started |
| Protocol Popular | 5,000 checks/month | $0.05 per check | Subscribe |
| Enterprise | Custom | Custom | Contact Us |
A Verifiable Credential is a W3C-standard digital document that is cryptographically signed by the issuer and can be independently verified by anyone without calling back to the issuer. Unlike a PDF or database record, it cannot be forged or tampered with, and the holder controls who sees it. Only a SHA-256 hash is stored on-chain; the actual data stays off-chain in the holder's control.
Call POST /v1/onboard with your organization name. You'll receive a DID, an ADMIN API key, and your signing key pair (private key stored server-side, encrypted at rest). You start at the UNVERIFIED tier and can submit a verification request to upgrade to VERIFIED, REGULATED, or INSTITUTIONAL which determines what credential types you can issue.
Call POST /v1/verify with the credential JWT. The API checks the cryptographic signature, on-chain revocation status, expiration, and (optionally) your policy requirements like minimum issuer tier or reputation score. You get back a pass/fail decision, a confidence score, and freshness information in milliseconds.
Only the SHA-256 hash of each credential and its status (active, revoked, or expired). No personal data, names, documents, or claim details ever touch the chain. This gives you tamper-proof auditability without any privacy exposure.
Yes. Only the Compliance Provider can revoke a credential. This revocation is enforced both in the SDK and on the smart contract. Revocation is instant and permanent: any Relying Party checking that credential will immediately see it as revoked. Other credentials for the same subject are unaffected.
Yes. The credential is issued to you and you decide who to present it to. With SD-JWT (Selective Disclosure), you can reveal only specific claims; for example, proving your country of residence without exposing your full name or date of birth. Your private key never leaves your control.
The SDK ships with five built-in types: KYC Basic (country + method), KYC Standard (document-verified identity), KYC Enhanced (full due diligence with risk scoring), AML Screening (sanctions, PEP, adverse media), and Accredited Investor (SEC qualification). Each has a validated schema with required fields.
Compliance Providers are classified into four tiers: UNVERIFIED, VERIFIED, REGULATED, and INSTITUTIONAL. Higher tiers unlock more credential types and require economic staking plus a verification review by Platform Administrators at Verified Credentials. Relying Parties can set minimum tier requirements in their policies; for example, only accepting credentials from REGULATED or higher issuers.
The architecture is designed for regulatory compatibility: no PII on-chain, holder-controlled disclosure, full audit trails, and instant revocation. For regulated production deployment, you'll integrate with a licensed KYC/AML provider and add an HSM for key storage. The SDK provides the credential infrastructure; compliance decisions remain with the Compliance Provider.
Expiration is checked dynamically at verification time. The API response includes a freshness indicator (fresh, aging, stale, critical, expired) and days until expiry so Relying Parties and Subjects can plan renewals. Credentials can be renewed via POST /v1/credentials/renew which revokes the old credential and issues a new one with updated expiration in a single call.