> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onstacks.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Providers

> The settlement partners behind Onstacks ramps and how routing picks one.

Onstacks routes each transaction to a licensed provider for the fiat leg. You do not integrate providers directly and you do not need accounts with them.

## How routing works

The full picture is on [Ramps flow](/ramps/how-it-works#intelligent-routing). In short:

1. Eligible providers are those with an enabled route for the corridor, within the amount limits, and available in the destination country.
2. Each eligible provider is quoted. Quotes are normalized so they compare on the amount the recipient receives after fees.
3. In `manual` mode you pick. In `auto` mode Onstacks picks by price, then by recent reliability.
4. If a provider fails after submission the intent is marked `failed` and funds are released. Automatic failover between providers is on the roadmap.

## Provider identity in responses

Quotes and intents carry `provider_id` and a display name. The response header `X-Onstacks-Provider-Network-Mode` tells you whether the routing backend served the request from live provider inventory (`core`), a mix (`hybrid`), or sandbox mock data (`mock`).

## Provider onboarding

Nothing to do. Adding a provider is an Onstacks-side change and shows up as new corridors in `GET /v1/corridors`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.