Why your bank never matches the Stripe dashboard
Stripe shows you gross volume the moment a charge succeeds. Your bank shows you net payouts days later. Those are two different numbers on two different calendars, and they will never line up by eyeball.
A single payout bundles every charge from a window of days, subtracts processing fees, then subtracts any refunds and disputes that cleared in the same window. So the $4,218 you watched come in over a weekend might land as one $4,061 deposit the following Wednesday. Or as two deposits. Or, if a dispute hit, as something that looks nothing like any number in your dashboard.
Add a rolling payout schedule (two business days for most US accounts, longer elsewhere), bank holidays, and the occasional failed payout, and manual reconciliation turns into a monthly hour of squinting at two browser tabs. That's the hour this workflow deletes.
What you need before you start
Two things. First, your business bank connected to BankBridge, which takes about two minutes and costs $5 a month per bank. If you haven't done that yet, start with the guide on connecting your bank to Claude; the same flow works in ChatGPT, Cursor, and any other MCP host.
Second, the Stripe side of the ledger. That's your Payouts page in the Stripe dashboard, a payout CSV, or a Stripe MCP server if your agent has one connected. BankBridge covers the bank half of the equation; Stripe covers its own half.
Everything on the bank side is read-only and fetched live. Nothing gets cached on BankBridge servers, so every answer reflects your account as it is right now, not a snapshot from last night.
Step 1: pull every Stripe deposit from the bank
Start by asking the agent for the raw material.
Search my business checking account for every deposit from Stripe since June 1. List the date and amount of each one, plus a running total.
Under the hood the agent calls search_transactions with the Stripe descriptor. Most banks label these deposits something like STRIPE or STRIPE TRANSFER followed by an ID, but descriptors vary. If the first search comes back thin, tell the agent to try variants; it can check ST- prefixes and partial matches in a second pass.
You'll get a clean list: every deposit, dated, totaled. That list alone answers the most common founder question, which is "did the money show up at all?"
Step 2: match deposits against expected payouts
Now hand the agent the other side.
Here are the payouts Stripe says it sent in June: [paste the list from your Payouts page]. Match each one to a bank deposit. Flag anything that hasn't arrived, landed on an unexpected day, or differs from the expected amount by more than a dollar.
This is the part that's miserable to do by hand and trivial for an agent. It matches amounts to the cent, notes timing offsets, and hands you a short exception list instead of a wall of numbers.
When something doesn't match, the cause is usually one of four things: a payout still in transit, a bank holiday shifting the landing date, a payout that failed and got retried, or a deposit that belongs to a different Stripe account than the one you're reconciling. The agent can't fix any of those, but it tells you exactly which payout to chase in the dashboard, and that's most of the battle.
Step 3: watch for fee drift
Fees are invisible in a payout. They're subtracted before the money ever moves, which is exactly why drift goes unnoticed. More international cards, a rising dispute rate, currency conversion, a new Billing or Tax add-on: each one quietly shaves the percentage of gross volume that reaches your account.
Total my Stripe deposits for each of the last three months. Here's my gross Stripe volume for the same months: [paste]. What percentage landed in the bank each month, and is it shrinking?
get_merchant_history gives the agent the deposit-side trend per month without re-running any searches. You supply gross volume, it computes your effective take-home rate. A slide from 97.1% to 95.8% sounds small and isn't: on $30k a month, that's about $390 a month walking out the door.
If the rate drops, the follow-up question is which lever moved. That answer lives in Stripe's own reporting, but now you know to go look, and you know which month to look at.
Make it a five-minute monthly close
Once the workflow works, save the prompt and run it on the first of the month.
Run my Stripe reconciliation for last month: pull every Stripe deposit from business checking, total them, match them against this payout list: [paste], and report matched payouts, missing payouts, and the effective fee rate versus the prior month.
Pair it with get_monthly_cashflow and the reconciliation becomes one line in a broader review: revenue that landed, versus revenue that should have landed, versus everything you spent. If you already run an agent-powered monthly money review, this slots in as the revenue check at the top.
Five minutes, once a month. The alternative is discovering in October that a payout failed in July.
What this workflow can and can't do
BankBridge sees the bank side only. It confirms what landed, when, and for how much. The expected side comes from Stripe, via your dashboard, a CSV, or a Stripe integration running alongside. The agent's job is joining the two, and it's very good at that job.
Access is read-only by design. The agent can't move money, can't retry a failed payout, and can't touch your Stripe account. What it replaces is the spreadsheet, the manual matching, and the part of your brain that was tracking whether Wednesday's deposit ever came.
And because BankBridge fetches live and stores nothing, you can run this the morning a payout is due and get an answer that's current to the minute.