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

# The payment flow

> From partner submission to offer, payout, and payer repayment.

1. **Submitted.** A partner sends a candidate obligation with the business, payer, amount, due date, and evidence reference. It enters Already's intake queue.
2. **Offer live.** An operator reviews the submission, selects a funding pool with capacity, prices the offer, and publishes it. The business can review the net amount, fee, terms, expiry, and payout bank.
3. **Accepted.** The business accepts the exact offer terms. Already requests the advance to the selected bank. Acceptance alone is not proof that a bank transfer completed.
4. **Paid out.** The payment provider reports completion and Already reconciles the transfer. The business sees the amount sent. A late failure or return can reverse that status and raise an exception.
5. **Repaid.** The payer pays the obligation. Already records the receipt after reconciliation. Recovered principal and fee income are accounted for separately in the funding pool.

The business may leave an offer unaccepted. An expired or withdrawn offer releases its reserved capacity; a new quote requires a new offer. The payer's obligation remains due on its original terms.

## Pricing in the current demo

For a published early-payment offer, the configured demonstration pricing is 1.5% of face amount per 30 days, prorated by the number of days to the due date:

```text theme={null}
fee = face amount × 0.015 × days to due ÷ 30
business receives = face amount − fee
```

For example, a $2,040 obligation due in 48 days has a $48.96 fee and \$1,991.04 in net proceeds. The exact published offer controls the transaction; the example is not a promise that every obligation will qualify or have the same terms.

See [banking](https://docs.already.finance/money/banking.md) for how sandbox transfer states map to what the portal displays.


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