Integration · Payments
Stripe revenue, in the forecastcharges, refunds, payouts and subscriptions, read-only.
Stripe knows what customers actually paid. Connect it with a restricted, read-only key and Replafin reads charges, refunds, fees, payouts, invoices and subscriptions, so revenue, receivables and deferred revenue in the model come from real collections rather than a typed run-rate.
What Replafin reads
The lines Stripe fills
We read charges, refunds, payouts, invoices and subscriptions; we never create or change anything in Stripe.
- Sales
- Cost of those sales
- Owed to you
- Paid up front by customers
- Kind
- Payments
- Connects by
- Paste a read-only key
- Time to connect
- about 4 minutes
How to connect
- 01Open dashboard.stripe.com and click Developers (bottom left), then API keys.
- 02Click "Create restricted key". Name it "Replace (read only)".
- 03Grant Read on: Balance, Balance transactions, Charges, Refunds, Payouts, Customers, Subscriptions, Invoices.
- 04Leave everything else at None, then click Create key.
- 05Copy the key. It starts with rk_live_… and is shown only once. Paste it here.
Free. A restricted key with Read only is enough; never paste your secret key.
What happens next
What the forecast does with Stripe
Collected revenue and fees become the revenue and cost-of-revenue actuals; open invoices feed receivables; annual plans paid up front feed deferred revenue, which is cash in before the revenue is earned. The subscription base gives the recurring-revenue driver its starting point, so churn and new-customer assumptions project from what Stripe shows rather than a guess.
Live connections refresh themselves when they are more than six hours old. Every row a sync writes lands on the changes log, and anything it cannot categorise with confidence waits for you in Review. The cash flow forecast guide shows how the months ahead are built from these actuals.
Questions
Stripe, answered
Do I have to paste my Stripe secret key?
No, and you should not. Create a restricted key with Read only on Balance, Balance transactions, Charges, Refunds, Payouts, Customers, Subscriptions and Invoices. It cannot create charges, refunds or payouts.
What if Stripe is not my only revenue?
Connect the bank or the books as well, or import a CSV for the rest. Each source fills the lines it knows about; the model reconciles them against each other and flags what does not tie.
Does Replafin write anything back?
No. Every connection is read-only by construction: restricted keys, read scopes or a Plaid link that cannot move money. Replafin reads balances, transactions and reports; it never posts, edits or deletes anything in the source.
How often does it sync?
Live connections refresh themselves when they are more than six hours old, and you can refresh on demand. Every row the sync writes lands on the changes log, and anything it cannot categorise with confidence waits for you in Review instead of being guessed.
Which plan includes integrations?
All of them. Connectors are part of the workspace on every plan; nothing about the bank, books or payroll links is gated by tier.
Other sources: QuickBooks Online, Xero, Mercury, Brex, Your bank, via Plaid, Otto HR, CSV or XLSX.
Connect Stripe.Forecast from real numbers.
Open the workspace, connect the source in minutes, and the model opens on the balances you actually have. Plans from $200 a month.