Settlement

Collecting the payment is half the story; this flow covers the other half: how the money that payers sent becomes a balance in your bank account. It walks how Mono delivers the funds, the webhooks that report each step, and what your reconciliation should check at the end of the day.

If you have not read the Settlement concept yet, start there: this page assumes you know what a settlement batch is.

Before you start

You will need:

• Payins reaching approved_in_provider (any of the collection flows produces them).
• A webhook endpoint subscribed to the payin_settlement_batch_* events.

How the delivery runs

1. Payins accumulate. Every approved payin destined for your funding account waits as pending_to_deliver.
2. Mono groups them into a batch. payin_settlement_batch_created lists exactly which payins the batch covers and what each delivers. A single day can produce several batches.
3. The delivery runs. processing means the delivery is under way; completed means the money reached your funding account. If you read a batch in retryable or failed, Mono is handling it and you do not need to act.
4. Payins are stamped. Each covered payin gets settlement_batch_id and funds_delivery_status: "completed".

Reconciling settlements

• Batch → bank statement: match each payin_settlement_batch_completed to one credit on your bank statement for total_amount.
• Batch → payins: GET /v1/core/payins/settlement_batches/{id} returns the covered payins with their funding_amount. The sum is the batch total, no payin missing, none twice.
• Leftovers: a payin approved late in the day can still be pending_to_deliver at the close; it arrives in the day's last batch. If a payin stays undelivered for more than a day, contact Mono support with its id.

Next steps

• Settlement concept: states, batching, and the fields involved.
• Payins: the per-payin delivery fields.
• Webhooks: the three settlement batch events in context.