Stripe connection settings in Core Connections showing connection status and configuration
For initial setup instructions, see Connecting Stripe.
How billing works
Subscription billing flows between Stripe and Ghost directly. Outpost reads the same Stripe events to drive automation: Stripe is the source of truth for billing. Ghost owns the subscription and tier relationship with the member, and Outpost does not handle those payments itself: it reads the same Stripe activity to drive welcome flows, segmentation, label changes, and integration syncs. Outpost does run its own checkout for promotions, gifts, group subscriptions, and tips.Connection settings
Stripe is configured under Core Connections in the left navigation.Stripe data Outpost reads
What Outpost handles automatically
Once Stripe is connected, Outpost reacts to billing events in real time. Here’s what Outpost does for each scenario:New subscription
When a member subscribes through your Ghost site’s Stripe checkout:- Member status is set to active and assigned to the correct tier
- The welcome email flow triggers (if configured)
- Connected integrations are notified (HubSpot, Salesforce, podcast platforms, etc.)
- The subscription appears in the member’s Activity Log
Subscription upgraded or downgraded
When a member changes their tier or billing interval:- Member’s tier assignment and renewal date update automatically
- Any active retention flow for this member is ended
- Integration syncs fire for the updated tier
Member cancels auto-renewal
When a member cancels (but their current period hasn’t ended yet):- Subscription is marked as “scheduled to cancel at period end”
- The retention email flow triggers automatically: a configurable sequence that asks the member to reconsider before their access ends
- The member retains full access until their current billing period ends
- An admin notification is sent to the publication owner
Subscription expires
When the billing period ends after a cancellation:- Member is removed from the paid tier
- A “Former Paid Subscriber” label is added in Ghost (useful for segmentation and re-engagement)
- For group subscriptions, individual members may revert to complimentary status depending on configuration
Payment failed (dunning)
When a renewal payment fails (card declined, expired, insufficient funds):- Member status changes to past due: they keep access while Stripe retries
- Outpost triggers the failed payment flow: a configurable email sequence encouraging the member to update their payment method
- Stripe retries the charge according to your Stripe retry schedule
- If a retry succeeds: member returns to active status, dunning emails stop automatically
- If all retries fail: Stripe cancels the subscription, and the member is marked as cancelled with the “Former Paid Subscriber” label
Payment method updated
When a member updates their card, Outpost stops any dunning emails still in progress and triggers the thank-you action in your failed payment flow. If the failed payment left an unpaid invoice, Outpost pays it with the new card rather than waiting for Stripe’s next retry. No action is needed from you.Checkout completed (one-time payments)
For non-subscription purchases (gifts, group subscriptions, donations, and promotional checkouts), Outpost:- Finalizes the purchase (activates gift, seats, or records donation)
- Triggers matching email flows and automations
- Notifies connected integrations
Offers and coupons
When you create an offer in Outpost, it creates a corresponding Stripe Coupon. When a member redeems the offer via Ghost’s checkout, the coupon is applied automatically. Outpost tracks which members used which offers for reporting.Subscription schedules
Outpost supports two-phase pricing scenarios: for example, a discounted first year followed by full price. See Subscription Schedules for details.Test mode
Outpost supports Stripe test mode so you can try payments without real charges. Use your Stripe test keys in the connection settings, and use Stripe’s test card number4242 4242 4242 4242 to simulate successful payments.
Related features
Ghost Integration
Ghost handles the subscription billing relationship; Outpost reads the results.
Failed Payment Flow
Configure the dunning email sequence for failed payments.
Offers & Discounts
Create promotional offers backed by Stripe coupons.
Subscription Schedules
Set up two-phase pricing with Stripe subscription schedules.
FAQ
Does Outpost process payments directly?
Does Outpost process payments directly?
In some cases, yes. Your ordinary subscription billing, the recurring charges that renew a membership, runs between Ghost and Stripe. Outpost reads those payments to update member records and trigger automations, and does not charge the member itself.Outpost does take payments directly in two cases:
- Its own checkout pages, used for promotions, gifts, group subscriptions, and tips. These run through Outpost rather than Ghost’s checkout.
- The failed payment flow. When a member updates their card after a payment has failed, Outpost pays the outstanding invoice with the new card instead of waiting for Stripe’s next retry.
Can I use a different Stripe account than my Ghost site?
Can I use a different Stripe account than my Ghost site?
No. Outpost must connect to the same Stripe account as your Ghost site so that member and subscription data matches across both systems.
What happens if Stripe stops sending updates?
What happens if Stripe stops sending updates?
Member status updates will be delayed until the connection is restored. Check your Stripe dashboard for any delivery issues. Your Outpost connection URL is shown in Core Connections → Stripe.
How do I connect Stripe to Outpost?
How do I connect Stripe to Outpost?
Click “Connect to Stripe” in Core Connections. You’ll be taken to Stripe to authorize the connection, then redirected back to Outpost.