> For the complete documentation index, see [llms.txt](https://docs.yifi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yifi.io/coverage/providers.md).

# Providers

### On-chain (DEX aggregation)

* **Cross-chain routes** are multi-step and **not** atomic; they combine bridging and swapping across networks.
* **MEV and front-running protection** is available on this rail (for example via CoW Swap), which matters for larger trades.
* **Token approvals** are resolved per route, including intermediate contracts used by some aggregators and explicit allowance-spender handling where required.

#### On-chain providers

* **LI.FI**
* **Rango Exchange**

### Off-chain (CEX aggregation)

* **Widest coverage.** The broadest range of assets and chains, including non-EVM networks.
* **No wallet connection, no gas** required from the user, which lowers the barrier for embedded and non-DeFi surfaces.

#### Off-chain providers

* **Quickex**
* **ChangeNow**
* **SwapGate**
* **SimpleSwap**
* **Letsexchange**
* **FixedFloat**

{% hint style="info" %}
Because off-chain routes involve a third-party exchanger, that provider may run its own KYC and impose its own limits. See [KYC Labels](#r6s).
{% endhint %}

### Private

Two Off-chain providers are used – one per exchange leg.

* **Private (XMR-hop)** – an intermediate hop in Monero.
* **Stealth (stable-hop)** – a stablecoin hop, removing volatility.

See [Private Swaps](/swap-types/private-swaps.md) to learn more of how it work under the hood.

### KYC Labels <a href="#r6s" id="r6s"></a>

Some routes, particularly off-chain (CEX), pass through providers that may run their own identity verification. To help users choose, the interface can display a KYC Label indicating the verification regime a given provider applies on its own side.

#### What a KYC Label is <a href="#r6u" id="r6u"></a>

* An informational indicator of the identity-verification regime a provider is expected to apply.
* Attached per provider, so users can weigh a route before selecting it.

and what KYC label is not:

* **It is not a guarantee.** A provider can change its process, request documents, or apply verification at its own discretion.
* **It is not YiFi performing KYC.** YiFi Swap does not itself run identity verification or collect KYC data from users.
* **It is not advice** or an endorsement of any provider.

#### Where KYC happens <a href="#r76" id="r76"></a>

When a user transacts through an off-chain provider, the relationship is directly with that provider under its own terms. That provider, not YiFi, may perform KYC: request documents, impose limits, and freeze, delay, reject, or reverse a transaction.

On-chain (DEX) routes are non-custodial and generally do not involve provider-side KYC, though users remain responsible for their own legal and regulatory compliance.

{% hint style="info" %}
**KYC Labels are indicative only**. Always direct users to the selected provider's own terms for the authoritative verification requirements. YiFi's overall compliance approach is described in the [AML/KYC Compliance](https://app.notion.com/legal/aml-kyc-compliance.md) policy.
{% endhint %}

### Provider risk

Routing across third-party providers carries risks the integrator should surface to users:

* **Smart-contract / router risk** on the on-chain rail – third-party routers can contain bugs or be exploited.
* **Off-chain provider risk** – an exchanger may require KYC and can freeze, delay, or reject a transaction under its own terms.
* **Execution risk** – quotes are indicative and the final outcome depends on slippage, route availability, and network or bridge conditions.