Where the Stripe hour goes
For a lot of small businesses Stripe is where the money shows up first, and the dashboard is good at showing it. The hour goes on what comes after: copying last week’s payouts into the bookkeeping sheet, working out which orders a $1,843.20 payout actually covers once refunds and fees have come out, and noticing a dispute while there’s still time to answer it.
dassi is for the owner whose orders live somewhere else, like an online shop, a booking tool or a sheet of invoices someone started three years ago, and who is tired of stitching CSVs together on Monday mornings. It works in the Stripe dashboard you’re already signed into, in the browser you already use, so there’s no API key to create.
Reconciling last week’s payouts
We’d teach this one first, because nothing in it changes anything.
- dassi opens Balances, then Payouts, and picks the payouts that arrived Monday through Sunday.
- It opens each one and copies the transactions inside: charge, refund, fee, net, customer email, description.
- Those land in the “Stripe” tab of your sheet, a row per transaction, tagged with the payout ID.
- Each charge is matched to your orders tab by order number when the description carries one, and by amount plus a date within a day when it doesn’t. Anything that could match two orders is marked ambiguous and left for you.
- It opens Disputes, lists the open ones with amount, reason and response deadline, and writes a summary line at the top of the sheet.
Scheduled for 9 on Monday, the reconciliation is waiting when you open the laptop. You can tack on a step that posts the totals to Slack, or one that types them into an accounting portal that won’t accept a file, and before long it’s one piece of a longer Monday routine.
We’re not sure the matching rule in step 4 holds up for a business with lots of identical orders on the same day. A $25 class sold forty times on a Saturday will produce a lot of “ambiguous”, and the real fix is getting the order number into the Stripe description at checkout, which whoever set up your checkout can probably do in an afternoon.
Read-only, unless you say otherwise
Everything above is reading. Refunds, dispute evidence, cancelled subscriptions and edits to customer records go on your approval list, and when a refund is the right call dassi prepares it, shows you the charge and the amount, and waits. We’d keep bank details and API keys out of any workflow altogether.
For a hard fence rather than an approval rule, Stripe lets you invite a team member with a view-only role; sign a separate browser profile into that user and run the reporting there, where a refund isn’t possible no matter what anyone types.
Sign-in, schedules and the model
The browser has to be open when a scheduled run comes due. If you’re signed out, dassi uses whatever your password manager fills in, and the two-step code is yours to type. What the dashboard shows (customer names, emails, amounts, cards only by their last four digits) goes to the AI model you picked when dassi reads it, through dassi’s relay on included credits, or stays on your machine with a local model.
Past a few thousand charges a week, reading page by page stops being sensible, and Stripe’s own payout reconciliation report is the tool to use.