> 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

**Effective date: 13th September 2026**

This document explains the current provider roles in the service supplied by **Layer Flow Gateway, Inc.** It is a service directory, not a statement that every named technology vendor is regulated or that every integration is available worldwide. Our Privacy Policy explains processing purposes, recipients, international transfers and rights.

## 1. Verification, software and infrastructure

| Provider            | Role in LFG                                                                                 | Responsibility and limits                                                                                                                                                                                                                                                                                                                         |
| ------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Didit               | LFG’s own applicant KYC/KYB, verification results and review support                        | LFG is responsible for its account admission process and data use. Didit performs checks under the applicable arrangements; authorised LFG administrators can view results and associated information.                                                                                                                                            |
| 1inch               | Classic Swap Aggregation API v6.0 for user-directed quotes and transaction data             | 1inch returns the route and transaction data directly to the user. The user reviews and signs every swap. LFG does not receive or transmit the order, select the route, sign or broadcast the swap, and its swap fee is currently disabled. For EU/EEA customers, swaps into USDT are disabled.                                                   |
| Web3Auth            | Non-custodial wallet, authentication, signing-flow and transaction-broadcast infrastructure | Neither Web3Auth nor LFG can sign alone. LFG cannot possess or reconstruct the private key, change transaction instructions or broadcast independently. Web3Auth is not an LFG recovery service; users must export and retain the recovery material for every wallet because LFG cannot recover it after closure or loss of required device data. |
| Amazon Web Services | Primary LFG application hosting and storage                                                 | Main reported application region: eu-central-1, Frankfurt, Germany. This does not determine every personnel or sub-processor access location.                                                                                                                                                                                                     |
| Sentry              | Mobile error and crash diagnostics                                                          | EU ingestion is configured. Actual collection and retention are limited as described in the Privacy and Cookie Policies.                                                                                                                                                                                                                          |
| OneSignal           | Mobile notification delivery and associated device/notification records                     | Notification permissions, any separate data-collection consent and deletion are managed separately as described in the Privacy and Cookie Policies.                                                                                                                                                                                               |

LFG may use additional necessary blockchain-node, screening, communications or support infrastructure within the recipient categories in its Privacy Policy. Its current contractual processor record must identify the actual providers used. A planned integration does not become operational merely because it appeared in an earlier list.

## 2. Financial-service integrations

| Provider brand                    | Enabled type of service                                               | Important limit                                                                                                                                                           |
| --------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Coinbase                          | On-ramping to supported USDC                                          | Only the appropriate provider entity, country, customer type, network and funding method. Coinbase Spend Permissions is not LFG’s current subscription billing mechanism. |
| Transak                           | On-ramping to supported USDC                                          | Personal and business coverage must be established separately for the relevant product.                                                                                   |
| MoonPay                           | On-ramping to supported USDC                                          | Personal and business coverage must be established separately for the relevant product.                                                                                   |
| OwlPay / Harbor                   | Off-ramping from supported USDC and bank payouts for eligible senders | EU-citizen individual senders and EU-incorporated business senders cannot currently onboard. EU payout destinations do not remove the sender restriction.                 |
| Sumsub, through Owl’s arrangement | Owl’s separate business verification for its off-ramp                 | This is not the same process as LFG’s Didit onboarding. Owl’s terms and privacy arrangements govern that provider relationship.                                           |

The specific legal entity supplying a financial service, its customer agreement, any relevant permission and the applicable fees are identified in its onboarding or checkout. LFG must only enable a route supported by that entity’s actual product coverage. Listing a provider is not a financial-services passport for LFG or a promise that the provider accepts all users of its brand worldwide.

No Ramp Network integration is included in this current directory. The listed providers’ unintegrated products are not LFG features.

## 3. Fees, outages and responsibilities

Owl’s current customer off-ramp fee is 0.50% of the off-ramped amount. LFG receives a referral commission from Owl out of that fee; it does not increase the 0.50% customer charge. The confidential commission percentage is not part of this customer document. Separate costs, if any, are shown in the applicable quote. LFG’s current 1inch swap fee is zero, and LFG receives no transaction-based compensation from swaps or payments; network and applicable provider costs remain separate.

Each provider is responsible for its own service under its agreement and applicable law. LFG remains responsible for its own duties, including the accuracy of its representations and any applicable obligation concerning the integration or selection of a provider. A provider failure does not automatically exclude all LFG liability.

Provider complaints should be addressed to the provider supplying the disputed service. LFG support can help identify the appropriate provider and address the LFG part of a complaint. Closing LFG does not automatically close a provider account, revoke an external wallet approval or erase records an independent provider lawfully retains.

## 4. Changes and enquiries

We update this directory when an integration materially changes. We obtain any additional consent required for a new processing purpose and honour any contractual processor-change procedure that applies. Contact **<legal@getlfg.app>** for privacy or contractual questions and **<support@getlfg.app>** for a service problem.

***
