Connect with a restricted key.
Use the documented Stripe key permissions. RunwayCal reads supported objects and does not create charges, change subscriptions, or write provider-side records.
Stripe revenue review
Bring Stripe revenue data into a controlled financial review.
Connect Stripe with a restricted, read-only key. Inspect supported customer, subscription, charge, invoice, and balance context, then review suggested mappings before approved records inform RunwayCal. Stripe activity stays distinct from bank cash, accounting reconciliation, and recognized revenue.
- Access
- Restricted and read-only
- Mapping
- Reviewed before approval
- Direction
- Stripe to RunwayCal
Restricted read-only connection- 01ConnectRestricted key
- 02InspectSupported records
- 03Review + mapHuman approval
- 04Refresh + useApproved context
Conceptual workflow, not a product screenshot or a promise of automatic reconciliation.
The job
Keep source activity and financial truth on the right sides of the review.
Stripe records commercial and payment activity. That source context can be useful, but a charge, invoice, subscription, balance, and bank deposit do not all mean the same thing.
- 01What did Stripe record?
- Inspect the supported customers, subscriptions, recent charges, invoices, and Stripe Balance context available through the connection. The integration does not write changes back to Stripe.
- 02What money actually reached the business?
- A successful payment amount is not automatically the same as a bank deposit. Fees, refunds, disputes, and payout timing can change the cash that ultimately lands.
- 03What can enter the financial plan?
- Review, modify, approve, or skip suggested customer-to-deal mappings. Supported receipts and events follow their documented control paths instead of silently becoming financial truth.
From context to decision
Use a controlled path from connection to approved context.
Inspect the source records.
Review the Stripe customers and supported activity found by the connection. Source records remain source records until a person decides how they relate to the plan.
Review each suggested mapping.
A person can approve, modify, skip, or match a suggestion to an existing deal. Unmatched activity does not silently become canonical revenue or cash.
Refresh and use approved context.
A supported refresh can update RunwayCal records through the documented workflow. Availability and refresh behavior depend on the current integration configuration and plan.
Evidence boundary
The evidence here is the workflow boundary, not a fabricated Stripe dashboard.
No product screenshot is presented on this page. The conceptual sequence is labelled and the claims are limited to the current integration contract.
SourceSupported Stripe recordsControlReview and mappingUseApproved financial context
Keep the meanings separate
Related numbers can still answer different questions.
- Stripe activity
- Provider records such as customers, subscriptions, charges, invoices, and balance context.
- Payment
- A Stripe event that is not automatically equal to the net cash deposited in a bank.
- Received cash
- Money recorded through a supported receipt path after the applicable review and duplicate checks.
- Revenue recognition
- An accounting judgment that this integration does not determine.
- Connection
- Read-only provider access, not a general bank feed, two-way sync, or automatic reconciliation.
Stripe integration
Bring Stripe context into the plan without skipping the review.
Connect the supported source, inspect what arrived, and approve the mappings that belong in RunwayCal while the distinctions around cash and revenue remain visible.