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

# Use cases

> Wherever money moves: card payments, swaps, DeFi yield, and the list goes on.

Any payment can carry a chance to win. The business funds it from a budget it already spends, Fade's vault pays the reward, and the odds are on-chain before the draw.

> [card] [Card payments](https://docs.fade.finance/use-cases/card-payments.md)
>
> **Cashback, but the whole purchase.** A card issuer adds a ticket to each card payment, paid from the rewards budget it already spends. Most payments go through as usual. Now and then, the next notification says it's on us.

> [card] [Swaps](https://docs.fade.finance/use-cases/swap-win-back.md)
>
> **Now and then, 20% off the swap.** A wallet or a swap screen pays a ticket from its fees or its rewards budget, so the trade costs nothing extra. Most swaps go through as usual. About 1 in 10 gets a fifth of the trade back.

> [card] [DeFi yield](https://docs.fade.finance/use-cases/rewards.md)
>
> **Rewards on top of the yield.** A lending pool, a staking protocol or a vault funds Fade tickets for its depositors from its own incentives budget, on top of the yield it pays. The usual rate does not move. Monthly interest, deposit milestones, loyalty seasons: the app picks the moments, at a cost it knows upfront.

> [card] [And the list goes on.](https://docs.fade.finance/use-cases/checkout-win-back.md)
>
> **Anywhere a stablecoin moves, a payment can be on us.** Merchants and checkouts ("1 order in 100 is on us"), mints, deposits, loyalty programs.

## What every use case shares

* **A fixed cost, set upfront.** The business pays the ticket price on every payment. Its cost never depends on who wins. See [Who pays what](https://docs.fade.finance/build/who-pays-what.md).
* **No prize pool, no draws to run.** Fade's vault pays every reward, in full.
* **One instruction in the payment it already sends.** `open_ticket` joins the payment's own transaction, so the customer signs nothing extra. See [Integration overview](https://docs.fade.finance/build/overview.md).
* **An offer of its own design.** The same budget can pay a small reward often or the whole payment rarely. The program checks the arithmetic.

> [!NOTE]
>
> The business offering the reward runs it as organiser and is responsible for the rules of each market it serves. Fade is the technology provider. See [Legal framework](https://docs.fade.finance/legal-framework.md) for the design rules and a summary by region.


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