1
Authenticate & bind wallet
Secure session, MFA, and wallet-bound KYC integrity via BFF headers.
ERC-3643 · MiCA · GDPR · AML/KYCCompliance infrastructure
Compliance infrastructure
for tokenized real-world assets
Permissioned real-world asset tokenization with off-chain KYC/AML and on-chain transfer rules — production-grade compliance infrastructure.
Designed for EU and international issuers: explicit compliance states, data minimization, and no raw PII on-chain — only hashes and registry proofs.
MiCAEU alignment
ERC-3643security token
0PII on-chain
Compliance flow
2
Submit & track KYC
Reference-only onboarding with live AML status until approve or reject.
3
Operate with guardrails
Subscribe, redeem, and transfer only when compliance rules and registry state allow.
Aligned with EU and international security-token regulation
MiCA-orientedGDPR data minimizationERC-3643 / T-REXAudit trailWallet binding
Who it is for
Three primary actors — each with a clear outcome in the same compliance graph.
Issuers & admins
Approve KYC, configure asset rules, pause transfers, and monitor on-chain receipts from one control room.
Investors
Register, bind a wallet, track AML status, and operate subscriptions or redemptions when verified.
Compliance & ops
Audit document hashes, eligibility states, blockchain transactions, and lifecycle events without raw PII on-chain.
Built for regulated asset issuance
Operational tooling for permissioned RWA programs — from regulated onboarding to on-chain transfer guardrails.
Identity & access
MFA-protected sessions, optional wallet binding, and role-aware routing — investor and issuer surfaces remain segregated.
KYC & eligibility
AML-aligned document references hashed off-chain; live status, reject reasons, and explorer links when approved on-chain.
Lifecycle operations
Subscriptions, redemptions, fee quotes, and portfolio context in one workspace — gated until identity is verified.
Compliance controls
Per-asset rules, audit events, pause/unpause, and blockchain transaction monitoring for issuer operations.
How it works
A standard operational path from sign-up to on-chain eligibility.
- 1
Sign up or sign in
Sign in with email and password to enter the secured workspace.
- 2
Bind wallet & submit KYC
Investors attach a wallet and submit a document reference; status updates until terminal.
- 3
Approve in issuer console
Compliance team reviews the queue, approves identity, and confirms registry on-chain.
- 4
Operate lifecycle
Subscribe, redeem, or pause — gated by the same eligibility enforced by the security token.
Compliance scope
Transparent scope — platform strengths and deployment considerations.
Strengths
- End-to-end traceability from KYC hash to registry proof
- Dual blockchain gateways (legacy registry + ERC-3643 / T-REX)
- Clear UX for pending, approved, rejected, and chain errors
- BFF session integrity with wallet-bound KYC header
Limits
- Jurisdiction-specific legal review remains mandatory
- External KYC/AML and oracle providers configured per deployment
- Chain network and custody model chosen by the issuer
- Regulatory authorization is the issuer's responsibility
Platform capabilities
Extended capabilities in the integrated compliance stack.
Portfolio chart
Performance view for verified investors.
Fee quotes
Subscription and redemption fees surfaced before submission.
Pause / unpause
Issuer circuit-breaker mirrored on-chain.
Audit feed
Operational events with consistent compliance status language.
API resilience
BFF retry when the compliance API is temporarily unavailable.
Explorer links
On-chain receipt verification after registry approval.
Trust by design
Security and UX patterns aligned with regulated tokenization platforms — clarity first, enforcement on-chain.
Off-chain PII, on-chain proofs
Document hashing keeps sensitive data off the ledger; only hashes and registry eligibility sync on-chain.
Predictable compliance states
Pending, approved, rejected, and chain-failure states use consistent operational language.
Operational resilience
BFF retry on API outages, rate limits, and issuer authorization patterns for production uptime.
Ready to operate a compliant tokenization program?
Walk the investor path, approve KYC in the issuer console, and trace eligibility from document hash to on-chain registry — in one regulated interface.