> For the complete documentation index, see [llms.txt](https://whitepaper.digitap.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.digitap.app/product/compliance-and-regulation-the-future-of-omni-banking/current-compliance-and-regulatory-landscape.md). # Current Compliance and Regulatory Landscape DigiTap has a dual requirement from the fact that the platform enables interchangeable use of fiat and cryptocurrency, connecting users to both centralized banking systems and decentralized blockchain networks. At present, compliance obligations include: * KYC (Know Your Customer) and KYB (Know Your Business) verification to prevent fraud and illicit activity. * AML (Anti-Money Laundering) and CTF (Counter-Terrorist Financing) protocols to meet global financial security standards. * Data protection and privacy compliance, such as GDPR in the EU and equivalent frameworks in other regions. * Jurisdiction-specific banking regulations, often requiring licensing or partnerships with regulated banks for fiat services. * Restrictions on crypto transactions in certain countries due to unclear or restrictive legislation. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://whitepaper.digitap.app/product/compliance-and-regulation-the-future-of-omni-banking/current-compliance-and-regulatory-landscape.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.