set up Buttondown paid subscriptions backed by Stripe and read a subscriber's Stripe subscriptions via API
domain: docs.buttondown.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Connect a Stripe account (existing or new) to Buttondown from the newsletter's Paid Subscriptions settings
Configure content access, product selection, currency, and pricing model (fixed, pay-what-you-want, or per-email) in the dashboard
Once a subscriber pays, their subscriber type becomes "premium" and stripe_customer_id/stripe_customer populate on the subscriber object
Query GET /v1/subscribers/{id_or_email}/stripe-subscriptions to list that subscriber's Stripe subscription records (amount, cadence, status)
When creating subscribers programmatically from a Stripe webhook handler, pass X-Buttondown-Bypass-Firewall: true since you won't have the buyer's IP address
Known gotchas
Stripe connection, product, and pricing setup is dashboard-only — there is no API endpoint to create the Stripe integration itself
Buttondown takes no platform commission on Stripe-based paid subscriptions (you only pay Stripe's fees)
The bypass-firewall header is rate-limited to five requests/hour/newsletter, so reserve it for trusted server-to-server calls like payment webhooks
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?