Compliance Approach
A phased, jurisdiction-aware view of how FabStone approaches onboarding, monitoring, partner controls, and product rollout.
Introduction
FabStone follows a phased compliance model tailored by corridor, product surface, and partner context.
Compliance by design
Compliance considerations are integrated early into onboarding, permissions, reporting, and product access design.
Jurisdiction-aware rollout
Availability may vary by jurisdiction and corridor. Features can be limited or deferred based on legal analysis, readiness, or operational constraints.
Website content should not be interpreted as universal licensing or approval in all markets.
Onboarding and identity controls
Depending on context, controls may include:
- KYC/KYB checks,
- identity/business verification,
- sanctions and screening checks,
- enhanced review for higher-risk scenarios,
- and ongoing monitoring where required.
Transaction monitoring and reporting
- transaction monitoring and risk scoring,
- alerts and escalation workflows,
- case review processes,
- and recordkeeping/reporting where legally required.
Partner and institutional controls
Institutional access, API environments, pilots, and partner-facing capabilities may require additional onboarding, contractual controls, and approvals.
Restricted or limited use
FabStone may restrict or refuse access where legal, sanctions, fraud, security, or policy concerns are identified.
Project-linked and qualified-access features
Project-linked or qualified-access features are expected to follow separate eligibility standards, documentation, and legal review.
Regulatory engagement and review
FabStone's compliance approach may evolve with legal developments, product scope, and operating model updates.
Contact
This page is a public-facing summary and may be updated as compliance requirements and product scope evolve.