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

# Use cases

> Who closes Stellar accounts, and what they recover when they do.

Every Stellar account holds XLM it cannot spend: a 1 XLM minimum balance (two base reserves), plus 0.5 XLM for each trustline, offer, data entry, and extra signer. That XLM comes back only when the account closes cleanly, and a clean close is exactly what LumenWipe does, whether through the guided web app or programmatically through the REST API and TypeScript SDK.

The audiences below all end up at the same `ACCOUNT_MERGE`, but they arrive from very different places.

<CardGroup cols={2}>
  <Card title="Individuals" icon="user" href="/use-cases/individuals">
    Close an old wallet, exit DeFi positions, and cash out to an exchange in one guided flow.
  </Card>

  <Card title="Wallets and exchanges" icon="wallet" href="/use-cases/wallets-and-exchanges">
    Offer account closure inside your own product with the SDK, keeping your own signer.
  </Card>

  <Card title="Embedded wallet platforms" icon="layer-group" href="/use-cases/embedded-wallet-platforms">
    Recover the XLM that activated each user account when that user leaves. Pollar, our first
    integration partner, is building exactly this.
  </Card>

  <Card title="Businesses and operations teams" icon="building" href="/use-cases/businesses-and-operations">
    Decommission fleets of payout, deposit, and campaign accounts with batch analysis.
  </Card>
</CardGroup>

## Building an integration?

Embedding the wind-down in another product does not change who holds the keys: signing always happens with your own infrastructure, and LumenWipe never touches funds. If you are considering an integration, open an issue on [GitHub](https://github.com/LumenWipe/lumenwipe) and we will help you scope it.