> For the complete documentation index, see [llms.txt](https://brd-digital.gitbook.io/brd-digital-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brd-digital.gitbook.io/brd-digital-docs/compliance/aml.md). # AML The AML/CFT program: risk-based controls, sanctions screening at the gate and continuously, transaction monitoring, and reporting. BRD runs a risk-based AML program aligned with applicable standards, with comprehensive anti-money-laundering and counter-terrorism-financing controls. In practice, the program shows up in four places: ## At the gate Every organization and authorized user is screened before access — sanctions lists, beneficial ownership, and the coherence of the stated use case with the applicant's profile. Jurisdictions without adequate AML/CFT frameworks are restricted outright; see [KYC](/brd-digital-docs/compliance/kyc.md). ## On every flow Transactions are monitored against your organization's profile. Payments from unrelated third parties, out-of-pattern flows, or transfers where the payment profile calls for context may be **held pending documentation** — an invoice, a contract, a source-of-funds record. Responding quickly with the requested documentation is the fastest path through a hold. ## Continuously Screening does not stop at onboarding. Sanctions lists change, ownership changes, and monitoring runs for the life of the relationship. Material changes on your side — ownership, control, jurisdiction — should be reported to the desk as they occur. ## In reporting obligations Suspicious activity is reported to the competent authorities as required. This is stated plainly so there is no ambiguity: BRD's obligations under the applicable framework take precedence, and tipping-off rules mean the desk cannot always discuss why a particular payment was held. ## What this means for your operations * Fund operations from accounts and wallets belonging to your verified organization. * Include payment references exactly as issued. * Keep supporting documentation for commercial payments where you would keep it anyway — corridor payments may ask for it. See [Settlement Flow](/brd-digital-docs/cross-border/settlement-flow.md). Questions about a specific requirement? [Contact the compliance team](/brd-digital-docs/resources/contact.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://brd-digital.gitbook.io/brd-digital-docs/compliance/aml.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.