Pull all balance_transaction objects for the payout period using the balance transaction endpoint with the payout parameter, rather than assuming the payout amount equals the sum of that period's charges
Group transactions by reporting_category instead of the older type field, since Stripe consolidates and renames categories for clearer reconciliation (for example, the legacy reserve_transaction type maps to reporting_category connect_reserved_funds, and reserved_funds maps to risk_reserved_funds)
Expect two separate balance transactions for every reserve hold: one that debits the reserved amount out of the available balance, and a second, later one that credits it back when the reserve period ends
Match the reserve-related balance transactions against your internal ledger as their own line items rather than netting them silently into "unexplained" variance
Reconcile only after accounting for reserve debits and releases in the period, so a payout that looks short by exactly the reserved amount is correctly explained rather than flagged as a discrepancy
Known gotchas
Comparing payout totals directly to "sum of charges for the period" produces a false discrepancy whenever a reserve is active, since reserved funds are deliberately excluded from that payout until released
The renamed reporting_category values (connect_reserved_funds, risk_reserved_funds) differ from the older type field names (reserve_transaction, reserved_funds) that older integrations or exports may still reference, so a reconciliation script built against type alone can silently miss reserve activity
Reserve percentage and hold duration can change over the life of a connected account, so a hardcoded assumption about a fixed percentage held for a fixed number of days will drift out of sync with the account's actual current reserve configuration
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?