Customers and active subscriptions
RunwayCal reads supported customer and subscription fields and proposes new or existing deal mappings for review.
Stripe + RunwayCal
Connect a restricted or secret Stripe API key, inspect supported customers, subscriptions, charges, and balance data, then approve the records that belong in RunwayCal. Stripe remains the payment system; RunwayCal adds controlled planning context.
What connects
The Stripe connection combines a reviewable import workflow with a few narrower event-driven behaviors. It is not a general bank feed, an accounting reconciliation service, or permission for RunwayCal to create charges.
Succeeded charges
Historical charges can be staged as receipts for a linked deal. Duplicate provider IDs are checked before an approved receipt is created.
Stripe Balance
A dedicated Stripe Treasury account can refresh from the available Stripe balance when Mission Control loads. This narrow refresh is separate from bank connectivity.
Supported Stripe events
Invoice, subscription, and refund events can update linked records or enter an unmatched review queue. Unmatched activity does not silently become planning truth.
Without Stripe connected vs with Stripe connected
Without Stripe connected
- Export supported Stripe records before matching them to planning data
- Track the source of imported receipts outside the product
- Check Stripe separately when reviewing a linked subscription or payment
With Stripe connected
- Inspect Stripe data through a read-only connection
- Review proposed deal mappings before approving them
- Keep provider IDs on imported records for duplicate protection
- See unmatched supported events without silently accepting them
Who uses this connection
Subscription teams reviewing recurring revenue
Inspect active subscription context and decide how it maps to RunwayCal deals before it enters the planning model.
Operators reviewing collected revenue
Stage supported succeeded charges as receipts while keeping their Stripe source and duplicate protection.
Finance teams monitoring exceptions
Review supported events that could not be matched instead of letting them silently change the model.
Connection boundary
The connection is read-only on the Stripe side. RunwayCal stores an encrypted API key, reads supported objects, and writes only to RunwayCal after the relevant control path. Disconnecting removes the local key and Stripe-linked Treasury account; the key must also be revoked in Stripe to fully end provider access.
Restricted API key · review before import
Review Stripe data before it changes the planning model.
Stripe records payment activity. RunwayCal uses a controlled connection to bring supported revenue and payment context into the operating model without turning every provider event into an approved financial record.
The initial workflow reads customers, active subscriptions, recent charges, and balance information. RunwayCal proposes mappings to deals, and the user chooses whether to create a deal, link an existing one, import supported receipts, or skip the suggestion.
After a record is linked, supported Stripe webhook events can update subscription state, payment status, refunds, or staged receipt activity. Event IDs protect against replay, and activity that cannot be matched is retained for review.
Stripe Balance is a specific exception to the review-first import pattern. The product can refresh a dedicated Stripe Treasury account on Mission Control load with a cooldown. That behavior does not establish general bank feeds or automatic accounting reconciliation.
Use Stripe for billing and payment operations. Use RunwayCal to review how supported Stripe activity belongs in deals, receipts, Treasury context, and the next financial decision.
Review Stripe data in RunwayCal
Connect the supported account, inspect available data, and approve what enters RunwayCal.