Skip to main content

Documentation Index

Fetch the complete documentation index at: https://documentation.outpost.pub/llms.txt

Use this file to discover all available pages before exploring further.

Outpost connects to the same Stripe account as your Ghost site to read subscription events and use them to drive automation, segmentation, and retention tools. Ghost handles the billing relationship with Stripe directly — Outpost reads that data and acts on it.
Stripe integration settings with connection status, public key, secret key, webhook URL, and currency configuration
For initial setup instructions, see Connecting Stripe.

How billing works

Billing flows between Stripe and Ghost directly. Outpost reads the same Stripe events to drive automation:
  1. A member subscribes via your Ghost site’s Stripe checkout
  2. Stripe creates the subscription and notifies Ghost
  3. Ghost activates the member’s tier access
  4. Outpost receives the same event from Stripe
  5. Outpost updates member data and triggers any matching automations (welcome flows, segmentation, label changes)

Connection settings

Stripe is configured under Core Connections in the left navigation.
FieldDescription
Connection statusShows whether Stripe is connected. Use the Connect to Stripe button for Stripe Connect setup (recommended).
Public KeyYour Stripe publishable key (starts with pk_live_ or pk_test_). Only needed for manual configuration.
Secret KeyYour Stripe secret key (starts with sk_live_ or sk_test_). Only needed for manual configuration.
Default CurrencyThe currency for subscription pricing (e.g., USD, GBP, EUR).
Webhook URLRead-only URL that Outpost provides for Stripe to send events to.
Return URLURL where members are redirected after completing Stripe checkout.
Invoice mailing addressAddress included on Stripe invoices sent to members.

Stripe data Outpost reads

Stripe DataHow Outpost uses it
CustomerLinked to an Outpost member record
SubscriptionDrives member status, tier assignment, and renewal tracking
InvoiceTracks renewals, payment failures, and revenue
CouponCreated by Outpost when you configure offers and discounts
Subscription ScheduleCreated by Outpost for subscription schedules (two-phase pricing)

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):
  1. Member status changes to past due — they keep access while Stripe retries
  2. Outpost triggers the failed payment flow — a configurable email sequence encouraging the member to update their payment method
  3. Stripe retries the charge according to your Stripe retry schedule
  4. If a retry succeeds: member returns to active status, dunning emails stop automatically
  5. If all retries fail: Stripe cancels the subscription, and the member is marked as cancelled with the “Former Paid Subscriber” label
Configure your dunning email sequence in Autoresponder.
Members in “past due” status still have access to your content while Stripe retries their payment. This grace period helps prevent unnecessarily locking out members who just need to update an expired card.

Payment method updated

When a member updates their card in Stripe, Outpost logs the event for your records. 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 number 4242 4242 4242 4242 to simulate successful payments.

Ghost Integration

Ghost handles the 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

No. All billing flows between Stripe and Ghost. Outpost reads Stripe events to update member records and trigger automations, but it does not initiate charges or manage subscriptions in Stripe.
No. Outpost must connect to the same Stripe account as your Ghost site so that member and subscription data matches across both systems.
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.
Click “Connect to Stripe” in Core Connections. You’ll be taken to Stripe to authorize the connection, then redirected back to Outpost.