Settlement
The two movements behind every payin — crediting the subaccount, and delivering the funds to you.
A payin moves money twice, and the two movements answer two different questions. Crediting the subaccount is your decision: when does the end user's balance reflect the payment? Delivering the funds to you is Mono's job: how does the real money reach the funding account, the actual bank account backing your program? Each movement has its own page, because they run on different clocks, different fields, and different webhooks.
| Movement | Money | Decided by | Reported through |
|---|---|---|---|
| Crediting the subaccount | Virtual | You | payin_subaccount_credited, the payin's state |
| Delivering to your funding account | Real | Mono | funds_delivery_status, the payin_settlement_batch_* events |
The two are genuinely independent: with the on_approval trigger, the subaccount is credited before the real money has reached you — the delivery catches up on its own schedule.
Crediting the subaccount
The trigger you choose, the webhook, and the amount your users see.
Delivering to your funding account
Automatic and manual modes, settlement batches, and their lifecycle.
Next steps
- Settlement flow — the end-to-end walkthrough with webhooks.
- Payins — the fields both movements live on.
- Settlement batches API reference — the full schemas.