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

# What Kira is

Kira is infrastructure for moving money on behalf of your own customers.

You are a business with customers who need to receive money, hold it, and pay it out — and doing that yourself means bank relationships, compliance obligations, and a different integration for every country and payment rail. Kira is the layer that already has those, exposed as one interface you build against once.

## What you get

**Accounts your customers can be paid into.** Kira opens an account for each of your customers, with real bank details a payer can send money to. Money that arrives is credited to that customer, not pooled into yours.

**A way to pay anyone out.** Once money has arrived, it can be sent onward — to a supplier's bank account, to a contractor abroad, or to a digital wallet.

**Stablecoins on both sides.** A customer can be paid in digital currency as well as by bank transfer, and paid out the same way. It is another route in and another route out, not a product you have to adopt to use the rest.

**The compliance that lets both happen.** Before a customer can hold or move money, they have to be identified and checked. Kira runs that verification and tells you where each customer stands.

**A record of everything.** Every movement has a status you can read, and Kira notifies you when one changes, so your own system never has to guess.

## What Kira is not

<Note>
  Kira is not a bank and does not hold a customer relationship with your customers. **You** own that relationship: your customers see your product, and Kira is the layer underneath it. Kira does not decide who your customers are, what you charge them, or what a payment is for — you do, and Kira carries it out and keeps the record.
</Note>

## Who this is for

Two audiences build on Kira, and they arrive with different questions:

* **A business paying people or companies** — suppliers, contractors, sellers on your platform. Your question is how money gets out, on what rail, and when it lands.
* **A business collecting money** — subscriptions, invoices, marketplace balances. Your question is how money gets in, whose it is once it arrives, and how you draw it down.

Most integrations do both. **[Pick your use case](/overview/pick-your-use-case)** lays out the four shapes and points each one at the right place to start.

## What it costs

Kira charges when money moves, and nothing when it sits still. **[How you're charged](/overview/how-you-are-charged)** explains the model without a single field name.

## Where to go next

<CardGroup cols={2}>
  <Card title="How money moves" icon="arrow-right-arrow-left" href="/overview/how-money-moves">
    The end-to-end path, from a customer signing up to money landing.
  </Card>

  <Card title="How you're charged" icon="receipt" href="/overview/how-you-are-charged">
    What Kira charges for, and what it does not.
  </Card>

  <Card title="Pick your use case" icon="signs-post" href="/overview/pick-your-use-case">
    Four shapes an integration takes. Find yours.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/get-started/access">
    For the engineer: credentials to first payout.
  </Card>
</CardGroup>