> For the complete documentation index, see [llms.txt](https://help.getlfg.app/p/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getlfg.app/p/agreements/integrated-service-providers.md). # Integrated service providers In accordance with **Sections 1.8, 7.8, and 11.1** of the LFG Terms of Service, this document identifies the third-party partners whose regulated services, software, or infrastructure are integrated into the LFG "Orchestrator" platform. > \[!IMPORTANT] **NOTICE:** This list is non-exhaustive. LFG may integrate additional providers, sub-processors, or regional partners from time to time to ensure service continuity and regional compliance. Your use of specific features is subject to the independent terms of the relevant provider. *** ## 1. Identity & Compliance (KYC/KYB) These providers facilitate the identity verification and AML screening required to access LFG-Verified status. | Provider | Role | Service Link | | ---------- | ------------------------------------------- | --------------------------------- | | **Sumsub** | Global KYC/KYB & Identity Orchestration | [sumsub.com](https://sumsub.com/) | | **Didit** | Identity Verification & Digital Credentials | [didit.me](https://didit.me/) | *** ## 2. Blockchain Analytics & Monitoring These providers supply the risk signals and wallet screening data used to identify and mitigate exposure to illicit activity. | Provider | Role | Service Link | | ------------------ | ----------------------------------------------- | ----------------------------------------------- | | **Merkle Science** | Real-time Transaction Monitoring & Risk Signals | [merklescience.com](https://merklescience.com/) | | **AML Bot** | Wallet Screening & AML Compliance | [amlbot.com](https://amlbot.com/) | *** ## 3. On/Off-Ramp & Settlement Services Licensed financial institutions facilitating fiat-to-crypto and crypto-to-fiat conversions. **LFG is not a party to these transactions.** | Provider | Role | Primary Jurisdictions | | ---------------- | ---------------------------------------------- | ------------------------------------------------ | | **OwlPay** | Business Settlement & Automated Payouts | UAE, SE Asia, and Approved Regions | | **Coinbase** | Fiat-to-Crypto Rails & Institutional Liquidity | Global (Excluding Prohibited Jurisdictions) | | **Transak** | Retail Fiat-to-Crypto On-Ramp | Approved Jurisdictions Globally (130+ Countries) | | **MoonPay** | Retail Fiat-to-Crypto On-Ramp | Approved Jurisdictions Globally | | **Ramp Network** | Retail Fiat-to-Crypto On-Ramp | Approved Latin American & Global Regions | *** ## 4. Technical Infrastructure (Sub-processors) The core infrastructure providers that host our software and manage the underlying node data. | Provider | Role | Region | | ----------------------------- | ------------------------------ | --------------------------------- | | **Amazon Web Services (AWS)** | Cloud Hosting & Data Storage | UAE / Global Infrastructure Nodes | | **Google Cloud Platform** | Application Logic & Analytics | Global | | **Alchemy / Infura** | Blockchain Node Infrastructure | Global | *** ## 5. Important Legal Disclosures ### Regulatory Reliance & Disclaimer of Warranty LFG selects its Third-Party Providers based on their public representations regarding their licensing, regulatory standing, and regional authorizations. * **Independent Duty:** Each provider is solely responsible for maintaining the licenses, permits, and regulatory approvals required to operate in their respective jurisdictions. * **No Supervisory Role:** LFG does not act as a regulatory supervisor for these entities. We do not warrant, guarantee, or represent that any Third-Party Provider will remain licensed or compliant at all times. * **Limitation of Liability:** LFG shall not be held responsible for any service disruptions, asset freezes, or financial losses caused by a provider’s regulatory non-compliance, license revocation, or sudden withdrawal from a market. Any claims arising from such lapses must be brought directly against the relevant provider. ### Service Availability & Reliance If any provider listed above experiences a **Force Majeure** event (as defined in Section 19 of our ToS), the corresponding LFG feature will be temporarily unavailable. LFG is not liable for failures or delays caused by these third-party dependencies. ### Fee Markups & Commissions As disclosed in **Section 7.8 of the ToS**, the total fee displayed in the LFG interface for conversion services may include a software markup or commission set by LFG. By initiating a transaction, you agree to the total fee displayed at the point of instruction. *** ### Dispute Resolution Any corporate or integration disputes arising out of the platform’s utilization of these providers are governed exclusively by the overarching corporate framework set forth in Section 17 of the LFG Terms of Service: | Associated LFG Entity | Forum / Forum Rules | Location / Seat | | --------------------------- | --------------------------------------------- | --------------- | | **Layer Flow Gateway FZCO** | DIAC (Dubai International Arbitration Centre) | Dubai, UAE | --- # 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://help.getlfg.app/p/agreements/integrated-service-providers.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.