The offer record connects the stack
Use Offers to define the product, price, checkout mode, invoice, and automation context before Stripe and Kit (ConvertKit) receive events.
Integration pair
Stripe + Kit (ConvertKit)
Use Stripe and Kit (ConvertKit) together with Plandalf as the layer that ties checkout, payments, invoices, integrations, and lifecycle automation together.
Common setup
Most teams use Stripe as their payment layer and Kit (ConvertKit) as their email layer, with Plandalf in the middle handling the checkout, Offers, invoices, integrations, and the events that fire after a purchase.
See Stripe and Kit (ConvertKit) docs for connection details.
Product surfaces behind this integration
This legacy integration URL now points builders toward the same product reality as the canonical app-pair guide: Offers, payment options, invoices, integrations, Automations, API docs, and webhooks.
Payment options stay tied to checkout
Stripe and Kit (ConvertKit) should not split payment state from invoices, tax settings, or post-purchase events.
Purchase automation carries the details
Automations and webhooks let Stripe and Kit (ConvertKit) receive buyer, product, payment, invoice, coupon, and deadline context.
Use the richer guide from here
Keep moving from this page into canonical integration docs, platform pages, stack guides, and sequence recipes so every Stripe or Kit (ConvertKit) mention has a useful next step.
Open canonical app-pair guide Use the richer Stripe and Kit (ConvertKit) implementation guide. Stripe platform page Roles, capabilities, and setup notes for Stripe. Kit (ConvertKit) platform page Roles, capabilities, and setup notes for Kit (ConvertKit). API-first stack SDK checkout, API keys, webhooks, payment processors, and invoices.