Crediting the subaccount
When a payin credits the subaccount — the trigger you choose, the webhook, and the amount.
This is the first of the two settlement movements: the virtual money — the credit on Core's ledger that makes the payment visible as balance in the subaccount. This movement is your decision: you choose when it happens. The second movement — the real money reaching your bank account — is Mono's job and has its own page: Delivering to your funding account.
Choosing the trigger
subaccount_disbursement_trigger decides the moment of the ledger credit. Your program sets the default, and every template or intent can override it for its own payins:
| Trigger | Subaccount credited when… |
|---|---|
on_approval | The provider approves the payment. The natural fit for Bre-B, where approval and money movement are seconds apart. |
on_funds_delivery | The real money reaches its destination account. |
What the credit looks like
The credit is announced by the payin_subaccount_credited webhook and the payin moves to subaccount_credited — for most integrations, the "payment complete" signal. subaccount_amount is the credited value, in the subaccount's currency, and the fees charged on the payin are already reflected: calculated_fees on the payin breaks them down.
From this moment the end user can see and use the balance, regardless of where the real money is.
Independent from funds delivery
The two settlement movements are genuinely independent: with on_approval, the subaccount is credited before the real money has reached you — the funding-account delivery catches up on its own schedule, and reports through its own fields and webhooks. Choose on_funds_delivery when your product must not show balance until the money is physically yours.
Next steps
- Delivering to your funding account — the second movement.
- Payins — the states and fields around the credit.
- Fees — what is deducted when the subaccount is credited.