Answers for onboarding, monitoring, and case review
The FAQ now lives on its own page so the menu entry, footer link, and support paths all land somewhere real inside the project.
FAQ
AML compliance in crypto covers the rules, processes, and tools used to detect money laundering, sanctions exposure, terrorist financing, and other financial crime risks.
For a crypto business, it also means documenting decisions clearly enough for partners, auditors, and regulators.
Without a clear AML process, a business increases its exposure to fines, blocked relationships, frozen assets, and avoidable operational risk.
Global expectations usually combine FATF guidance with local rules from the jurisdiction where the business operates and where its customers are located.
Exchanges, custodial wallets, OTC desks, brokers, and many service providers that handle funds or customer transactions typically need AML controls.
An AML check is a structured review of wallet history, counterparties, risk sources, and transaction context to determine whether a transfer should proceed or be escalated.
Common requirements include customer verification, transaction monitoring, risk scoring, recordkeeping, case documentation, and suspicious activity escalation.
Start with clear risk rules, choose the transactions and users that need mandatory screening, define escalation ownership, and keep every decision traceable.
KYC focuses on individuals, KYB on companies, and KYT on transaction behavior. Together they describe who the customer is, who the business is, and how value moves.
Yes. They help identify suspicious counterparties before funds move and give support teams a defensible reason to stop or review a payment.
Pick the review scope, set the alert thresholds, define case ownership, then connect onboarding, monitoring, and reporting so the same rules apply across teams.
Where support requests should go
The Help Center link now lands on this internal section. Use it as the support hub until a dedicated ticketing system is connected.
Start from the pricing or products pages, then move into contact if you need a custom setup.
Use the contact page and the verify section so users always know where to confirm official contacts.
Use the access page when the request is really about login, signup, or getting into the platform workflow.