What flo.space prepares with Stripe
Prepares payment links, invoices, and refunds with the amount and customer prefilled.
- Create a $4,200 payment link from a quote
- Prepare a refund for a returned order
- High dollar actions always need a human
What it reads, and what it can write
Reads · read-only to start
Only the Stripe data you connect, within the OAuth scopes you approve. flo.space reads the context it needs to prepare an action and nothing beyond it.
Writes · only on approve
Nothing writes back to Stripe until you approve it. On approval, flo.space performs the exact action you reviewed, and logs it to the audit trail.
A Stripe action, prepared and waiting
Every prepared action lands on one screen with its source, reasoning, and a risk level. You approve, edit, or decline.
Recommendation: Prepares payment links, invoices, and refunds with the amount and customer prefilled.
What flo.space drafts around your payments
The communication that surrounds money, drafted from live Stripe data: payment links prepared from an agreed quote or an open invoice, with the exact amount and customer prefilled; receipts and confirmations drafted into the original thread when a payment lands; failed-payment follow-ups that say what happened and carry the retry link, in a tone that keeps the customer; refund actions prepared with the reversing bookkeeping note and the customer message together; and dispute correspondence, where the drafted response assembles the evidence your records actually contain.
The sentence that matters most, stated without hedging: flo.space never moves money on its own. It reads payment events and drafts the actions and messages around them; every charge link, refund, and dispute response is a prepared action that waits for a person, and money-touching actions carry a high-risk flag by default on top of that.
Connecting Stripe, step by step
Authorize with Stripe’s standard OAuth from your workspace; your Stripe credentials never touch flo.space.
Payments, customers, invoices, and events, read-only. The queue can now understand your payment flow but cannot act on it.
Links, receipts, and follow-ups referencing real payments appear with their sources cited.
Money actions are flagged for deliberate review by default, and you can route them to a second approver with approval rules.
A worked example
A subscription customer's card fails on the monthly charge. flo.space drafts the follow-up in your voice: what failed, the one-click retry link, and no shame in the copy, queued at medium risk. Two days later the retry has not happened and the second, slightly firmer draft is waiting. The customer replies that the card was compromised and asks to pay by bank transfer; the prepared response includes the transfer details from your records, and the action to cancel the open payment link rides along with it. Every step was a ten-second approval, and no message about money left unread.
Limitations, honestly
flo.space is not a billing engine: subscriptions, metered billing, and payment processing itself stay in Stripe. It does not do accounting reconciliation on its own (pair it with QuickBooks for that; the Stripe + QuickBooks page covers the flow). Dispute responses are drafts assembled from your records; judging whether to fight or refund a dispute stays a human call, on purpose. And there is no threshold below which money moves unattended; a $5 refund gets the same approval as a $5,000 one, faster to review but never skipped.
Stripe + flo.space, answered
No. It prepares payment links, refunds, and related messages as drafts; a person approves every one, and money-touching actions are flagged high risk by default. It reads payment data; it never moves money unattended.
Payments, customers, invoices, and payment events, within OAuth scopes you approve, read-only at the start. Your Stripe login stays with Stripe; access is revocable instantly from either side.
It drafts the recovery sequence: the first notice with a retry link, the firmer follow-up, and the alternative-payment reply if the customer asks. You approve each send, which keeps dunning from ever outrunning a real conversation.
It drafts the response and assembles the evidence your connected records contain: the order, the correspondence, the delivery confirmation. Whether to contest or refund remains your decision, and the draft waits for it.
Stripe paired with the rest of your stack
Deep dives on what flo.space prepares between two connected tools.
Connect the rest of your stack
Put Stripe on approve
Connect Stripe read only and let flo.space prepare the first wave of actions. Nothing sends until you approve.