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

# Why ramphub

RampHub exists to make ramp integrations feel like one clear flow instead of a pile of provider-specific edge cases.

> **Why this page matters**
> If you want the full mental model behind the API, read this page before wiring endpoints. It explains the problem RampHub solves, how the pieces fit together, and why the order lifecycle is designed the way it is.

## The problem

Most teams that want to add crypto buy or sell support run into the same issues:

1. Every provider has a slightly different request and response shape.
2. Routes change, so the “best” option today may not be the best option tomorrow.
3. Sell flows need bank resolution and payout validation before an order can even start.
4. Webhooks can arrive late or be missed, which makes UI state drift from the real trade state.
5. Fee handling becomes messy when the business wants to charge its own fee on top of provider routing.

That means your product team ends up building and maintaining a lot of plumbing that does not help the user complete a trade any faster.

## What RampHub fixes

RampHub puts one routing and lifecycle layer in front of multiple providers.

It gives you:

* one API key model
* one quote step
* one order creation step
* one place to recover trade state
* one webhook model
* one consistent way to attach business fees
* provider uptime and downtime awareness, so routing can favor healthy rails and avoid brittle ones

Instead of teaching your app how every provider works, you teach your app how RampHub works once.

## How it works

RampHub works as the routing and lifecycle layer between your app and multiple ramp providers.

If you want the step-by-step flow, read the [Quickstart](quickstart) page. This page focuses on the problem RampHub solves and the bigger product picture.

## Supported at a glance

### Providers

* UseBread
* Paycrest
* Flipeet
* Dexpay
* Pajcash

### Tokens

* USDT
* USDC
* SOL

### Networks

* Base
* BSC
* Ethereum
* Solana

## What users experience

From the user’s point of view, the trade feels simple:

1. They request a quote.
2. They confirm the order.
3. RampHub handles routing and provider settlement.
4. The app shows the live state until the trade completes.

The complexity stays behind the scenes where it belongs.

## What your app gets

RampHub is designed so the app team can focus on product instead of provider operations.

That means:

* fewer direct provider integrations
* less duplicate routing logic
* less manual bank and payout handling
* cleaner recovery when callbacks fail
* simpler fee collection for businesses

## Where to go next

* [Quickstart](quickstart)
* [Endpoints](../reference/endpoints)