Stripe
Connects · Payments & subscriptions
Fiona connects to Stripe and syncs it automatically.
What happens today
Paste a restricted Stripe key and Fiona books every charge at gross, the processing fee as an expense, refunds against revenue, and sales tax to a liability — then matches the payout to the deposit that lands in your bank.
Why it matters to your books
A Stripe payout is not revenue. If you book the deposit, you understate sales by the fee, hide the refund rate entirely, and treat tax you're holding for a state as if you earned it. Gross-and-fee is the difference between knowing your margin and guessing it.
What syncs
- Charges at gross
- Processing fees
- Refunds and disputes
- Sales tax collected
- Payouts, matched to the bank deposit
How to set it up
- Stripe → Developers → API keys → create a restricted key with read access
- Paste it into Connect → Stripe
- Fiona backfills, then keeps pace on each sync
Questions people actually ask
Why not just book the Stripe deposit?
Because the deposit is net of fees and refunds. Booking it understates both your revenue and your cost of selling, and your gross margin is wrong by the processing rate — which is most of the margin question for a small business.
Does Fiona need write access to Stripe?
No. A restricted, read-only key is enough, and it's what we ask for.
Will the payout be double-counted against my bank feed?
No. The payout is matched to the bank deposit rather than booked twice; that match is the check that the two sources agree.
All product names, logos and brands are property of their respective owners. Naming them here describes what Fiona reads or connects to — it does not imply any affiliation with, sponsorship by, or endorsement from them.