Connect Stripe to Well

Pick Stripe in Well's Connections panel and start the connect step. Well reaches the Stripe MCP server at mcp.stripe.com, reads its published OAuth metadata, and registers itself on the spot through Dynamic Client Registration, so there is no client_id or secret for you to copy across. You approve the read scopes on Stripe's own screen and land back in a live connection a minute or so later.

Charges, payouts, subscriptions, and the customers behind them come across as workspace records. A charge lines up against the invoice it pays, a payout settles into the bank deposit it becomes, a subscription rolls into a recurring revenue line, and each customer enriches the matching company. The Stripe object id rides along on every record, so a workspace row always points back to its origin in Stripe.

Well opens the payout into the individual charges, fees, and refunds it carries, then lines each charge up with the invoice or order it settles. When the net payout hits your connected bank account, the per-charge breakdown is already attached, so the deposit reconciles without anyone rebuilding it in a spreadsheet. Currency-converted charges keep both the original and the settled amount so the math holds across regions.

A refund or dispute arrives as its own workspace record wired to the charge it reverses, and the original invoice is credited so the books show the money you actually kept. Disputes carry the Stripe case id and its response window so a deadline never goes quiet. Each charge keeps its fee amount and type alongside it, which makes your effective Stripe rate answerable from a question rather than a fee export.

Well reads recent Stripe activity through the MCP connection and folds new charges, payouts, and subscription changes into the workspace as it catches them, while the first connect backfills your earlier history in the background. You can already query the records that have arrived while the rest are still filling in. Stripe stays the system of record; Well holds a queryable mirror beside the rest of your stack.

Open the Stripe connection in Well and disconnect, and Well stops calling the Stripe MCP server immediately and drops the token it was issued. Stripe is read-only throughout, so there was never any write to unwind. The charges, payouts, and customers Well already mirrored stay in your workspace so historical questions keep answering; ask Support if your retention policy needs them purged.