Transaction Monitoring Policy
Last updated: November 11, 2026
1. Overview
Glide, operated by Montauk Analytics Inc., monitors customer activity to detect money laundering, terrorist financing, sanctions evasion and fraud. Monitoring combines automated controls with manual review. Some automated controls run before a transaction and can stop it. Automated sanctions screening and monitoring rules raise alerts, which our compliance team reviews manually, recording the outcome on the alert or on a compliance case.
Glide is not a bank. Fiat accounts and payments are provided by licensed partners, which also monitor the regulated legs they perform.
2. Controls Before a Transaction
- Sanctions screening of the recipient wallet on outgoing crypto transfers made through Glide.
- Account status checks: frozen, suspended or closed accounts cannot move money in the web and mobile apps.
- Verification requirements: fiat services, such as bank account details, deposits and bank transfers, require completed identity (KYC) or business (KYB) verification. Bank payouts are carried out by Noah, our regulated payments partner, which only pays out from KYC-approved accounts.
- Limits on swaps, link-based and invite payments, and on any transfer Glide signs under a permission you have granted.
- Duplicate-submission protection on supported payment flows, so a retried request cannot send funds twice.
3. Monitoring Rules
Glide's payment processing includes a rules engine for post-transaction monitoring. When a rule that Compliance has enabled is triggered, it raises an alert for manual review. The rules engine supports rules for large transactions, aggregate activity, possible structuring, new accounts, payments to new beneficiaries, rapid movement of funds and crypto transfers, selected by monitoring, that may need Travel Rule information.
By procedure, Compliance decides which rules are enabled and sets their thresholds on a risk basis. Thresholds and rule parameters are internal and are not published. Each rule has a severity (low, medium, high or critical), and the enabled rules and their performance are reviewed at least quarterly.
4. Sanctions Screening
Wallet addresses are screened with Chainalysis's sanctions screening service. A match on an outgoing transfer blocks it, and a match on an incoming deposit flags it; either raises a critical alert. If the screening service is unavailable, outgoing transfers are blocked.
Customers who complete verification, and verified businesses with their directors and owners, are screened against sanctions and politically exposed person (PEP) lists by our verification partner as part of verification.
5. Alert Investigation
An alert records what raised it and its severity and, where known, the customer and the transaction concerned. Compliance triages alerts in order of severity, critical first.
A compliance analyst reviews each alert manually and either closes it, recording the resolution, or opens a compliance case. Changes staff make to an alert's status in the admin console are recorded in the audit log.
6. Cases & Reporting
A compliance case records its evidence, comments and status changes, and cannot be closed until a decision is recorded: cleared, escalated, report filed or offboarded.
Where activity is suspicious, Compliance files a report with the competent authority. We do not tell a customer that a report has been or will be filed; doing so (“tipping off”) is prohibited by law.
7. Travel Rule
For fiat transfers, the licensed partner that executes the transfer carries the Travel Rule obligation, and Glide passes it the originator and beneficiary details it requires. Glide does not currently exchange Travel Rule messages with other virtual asset service providers. Compliance reviews the crypto transfers its monitoring selects; how transfers are selected for review is internal and is not published.
8. Records
Alerts, case files, decisions and screening outcomes are retained for 7 years after account closure, or longer under a legal hold. This is longer than the five-year minimum the Bank Secrecy Act requires. Administrator actions are written to an append-only, hash-chained audit log.
9. Review & Contact
We review this policy at least annually. Questions: privacy@glide.co.