Money movement covers what happens to funds after a payment succeeds: balances, the balance transaction ledger, payouts, and the payout destinations funds settle to. Your balance separates pending funds from available funds, while balance transactions give you a per-event ledger (charges, refunds, fees, holds, and payouts), each with gross, fee, and net amounts and links back to the originating order.
Payouts move available funds to a payout destination such as a bank account. Most merchants rely on automatic payouts driven by payout settings (interval, payout days, delay, and statement descriptor), but you can also create standard manual payouts. The initial destination is collected by embedded Account Onboarding. Later destination changes use the embedded Payouts component through a merchant account session. A payout tracks its status from creation through arrival, including failures and reversals. See Payouts for schedules, manual payouts, and failures.
A balance transaction's fee_money is Flint's own fee on that movement, never a provider cost passed through. At API version 2026-09-07, fee charges are positive and returned fees are negative. On a payment, fee_money equals processing_fee_money, and net_money is amount_money minus fee_money. Refund, dispute, return, and standard payout transactions carry no fee_money, so theirs is 0. That is not the same as costing nothing: disputes, ACH returns, failed ACH payments, and instant bank verification carry separate event fees assessed against your merchant account, readable on merchant billing. See Processing fees.
Read endpoints here are useful for reconciliation: list balance transactions to tie settled funds back to orders, and list payouts to match deposits on a bank statement.