Retrieve the current platform balance via GET /v1/balance; the response shows available, pending, and reserved amounts per currency.
Fetch balance transactions via GET /v1/balance_transactions with optional filters: type, created, payout, and currency.
Each balance transaction has a type (charge, refund, transfer, payout, application_fee, etc.), amount, fee, net, and reporting_category — use these to categorize activity.
To reconcile a specific payout, filter by payout: {payout_id} or use the Payout object's balance_transaction field to find the debit entry representing the bank transfer.
Use automatic pagination (has_more + starting_after) to iterate through large result sets.
Export data to your accounting system by mapping balance transaction types to journal entry categories; Stripe's Sigma or Data Pipeline products provide SQL-queryable versions of this data.
Known gotchas
Available balance ≠ payout amount — Stripe may hold reserves or have pending items; always use balance transactions to trace exact fund flows.
Balance transactions for the same event can appear across multiple payouts if funds were partially paid out — reconcile at the balance transaction level, not the charge level.
The fee field on a balance transaction is Stripe's processing fee, not your application fee — both appear as separate line items; do not double-count.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp