Offer configuration stays visible
Use Offers to decide what Stripe receives: product, price, buyer, checkout mode, invoice, and automation context.
What it does
- Cards, wallets, and 135+ currenciesPayment optionsCurrencies
- Built-in fraud protection
- Subscriptions and invoicingSubscription pricesInvoices
Product surfaces
Where Stripe fits in the buying workflow
Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before Stripe receives checkout, payment, tax, or workflow context.
Checkout layout and selling blocks stay editable
Before Stripe enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.
Purchase events can start follow-up
Stripe should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.
Payment methods and processor setup
Stripe handles the charge while Plandalf keeps checkout, payment state, invoice, tax, and follow-up context together.
Builder paths
Stack guides that use Stripe
Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.
Substack ShopSell a template, report, workshop, membership, or paid download from a Substack post while Plandalf owns the offer, checkout, invoice, and purchase event.The Affiliate Tax LaunchConnect affiliate sales, payment options, live tax calculation, and post-purchase reconciliation.The API-First ProductSplit transactional email from lifecycle email so each tool does what it's good at.The Checkout Optimization LabTest checkout layouts, sessions, mobile flow, and recovery without turning the sales page into a custom app.The CoachTake deposits and recurring retainers without re-platforming your existing site.The Coupon Deadline FunnelRun a deadline offer with coupon rules and follow-up paths that stay attached to the checkout.
Stripe stack recipes
Find full stack guides that pair Stripe with checkout, payment, automation, fulfilment, records, and downstream integrations.
Offers overview
Use Offers to package products, prices, checkout pages, invoices, coupons, payment options, and follow-up context.
Hosted checkout
Use hosted checkout when Stripe should hand the buyer to a branded Plandalf checkout page.
SDK checkout
Use SDK checkout when Stripe belongs inside an app, custom site, or API-first stack.
Webhooks
Route checkout events, purchase events, payment state, invoices, and customer context into another tool.
Checkout completed fulfilment
Turn a completed checkout into access, receipts, CRM updates, support context, and records.
Plandalf vs Stripe
Compare how Stripe fits beside Plandalf Offers, checkout, payment state, invoices, automation, and integrations.
Stripe alternatives
Compare how Stripe fits beside Plandalf Offers, checkout, payment state, invoices, automation, and integrations.
Overview
Plandalf’s primary payment processor. Connect your Stripe account once and every offer in your org can take cards, Apple Pay, Google Pay, Link, and Stripe-supported wallets without any per-offer wiring.
The connect flow is OAuth — you’ll be sent to Stripe to pick the account to link, then bounced straight back. We never see your secret key.
Automation graph
Connecting Stripe
How Stripe participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.
Triggers from Stripe
Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.
stripe.payment_succeeded- Fires when Stripe confirms a successful charge.
stripe.payment_failed- Fires when a charge is declined or fails.
stripe.subscription_canceled- Fires when a customer cancels a recurring subscription.
Actions on Stripe
Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.
trigger: stripe.payment_succeeded
actions:
- plandalf.grant_entitlement: ${product_slug}
- email.send_receipt:
to: ${customer.email}
- notify_team:
channel: "#sales"Pair it with
Connect Stripe with…
Platforms whose roles complement Stripe inside a Plandalf sequence.
Stripe + HubSpot
Sync paying customers into HubSpot the second checkout completes.
Stripe + Kajabi
Sell a course through Plandalf, drop the student into Kajabi.
Stripe + ActiveCampaign
Sync paying customers into ActiveCampaign the second checkout completes.
Stripe + beehiiv
Sync paying customers into beehiiv the second checkout completes.
Stripe + Kit (ConvertKit)
Sync paying customers into Kit (ConvertKit) the second checkout completes.
Stripe + Customer.io
Sync paying customers into Customer.io the second checkout completes.
Integration methods
How Stripe connects to Plandalf
Each method below is the minimum viable setup. Pick the one closest to how you already use Stripe with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.
- Method 1
Connect your account
Plandalf links to Stripe via OAuth — pick the Stripe account to use, accept the scopes, and you'll be bounced back. Plandalf never sees your secret key, and every offer in your org can charge through that account without per-offer wiring.
Plandalf → Settings → Integrations → Stripe → Connect ↳ Redirects to https://stripe.com ↳ Authorize Plandalf ↳ Redirected back, account live
FAQ
Common questions about the Stripe integration
Do I need a paid plan to use Stripe with Plandalf?
Stripe has its own account requirements — Plandalf doesn't add any. Any Stripe plan that supports OAuth + the Charges/Subscriptions API will work, which is every paid plan.
How long does setup take?
Under 10 minutes — paste a webhook URL into Stripe, point it at the Plandalf endpoint, and trigger a test event to confirm.
Can I disconnect Stripe later without losing data?
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Stripe's own records are untouched. You can reconnect any time and resume from the last seen event.
Does Plandalf store Stripe data?
Plandalf stores the Stripe customer ID, the charge IDs, and the metadata needed to reconcile orders. Card numbers never touch Plandalf — they go straight from the customer to Stripe.
What if my payment need isn't covered by the actions or triggers listed here?
Drop into the Plandalf REST API and call Stripe directly from your sequence's HTTP action. Anything Stripe's public surface exposes is reachable.
Is there a usage limit?
Plandalf doesn't rate-limit Stripe calls beyond what Stripe itself enforces. Your Stripe plan's API rate limit is the practical ceiling.
Where do I find Stripe's own documentation?
Stripe's homepage at https://stripe.com links to their developer docs. For Plandalf-side questions about the Stripe integration, see the Plandalf docs.
Sequences for Stripe
Sequence
Affiliate sale tax reconciliation
Attach affiliate attribution, tax calculation, payment context, and reporting records to the same completed checkout event.
Sequence
Checkout completed → fulfillment
Fire fulfillment actions the moment a Plandalf checkout completes.
Sequence
Invoice issued record sync
Send invoice, customer, and payment records to email, CRM, and operations systems after checkout or renewal.
Sequence
Price plan changed lifecycle
Route product, price, plan, and subscription changes into lifecycle messaging and internal records.