Stripe payments foundation

v0.5.0.0 migrates Saperly’s payment processor to Stripe. The customer-facing API path /api/v1/billing/add-funds keeps the same request and response shape. The visible difference is the Checkout screen, which is now Stripe-hosted with Stripe’s branding.

What changed

• Stripe is the payment processor. New customers see Stripe Checkout when they add funds.
• Schema additions for an idempotent webhook audit trail: a stripe_events table, a payment_intents ledger, and a stripe_customer_id column on billing accounts.
• Webhook handler at /api/webhooks/stripe for payment_intent.succeeded, payment_intent.payment_failed, refund.created, charge.dispute.created, and subscription events. The handler is transactionally idempotent, so replaying a webhook does not double-credit.
• Refund correctness. Refunds debit credits proportionally instead of in raw cents, so a full refund collapses cleanly to the original credit grant.
• /api/health reports version: 0.5.0.0 post-deploy.

API compatibility

/api/v1/billing/add-funds accepts the same request shape and returns the same response shape it always has. Code that consumes the SDK does not need to change.

The legacy webhook path /api/webhooks/lemonsqueezy now returns 410 Gone with a year-long cache header, pointing integrators at /api/webhooks/stripe. If you had nothing subscribed to the legacy path, you can ignore it.

Top-up packs

Top-up pack pricing is unchanged from the prior processor:

• 1,000 credits = $13
• 2,500 credits = $30
• 5,000 credits = $55
• 10,000 credits = $100

These are documented for archival reference. v0.5.3 retired the credits unit on customer-facing surfaces. See Cents-honest pricing reprice for the post-reprice model.

What you need to do

Nothing on your side. If you saved Stripe billing portal links from the prior processor’s flow, they no longer apply. Stripe-hosted Checkout is the entry point now.