Dodo Payments and Waffo Pancake
- The payment service now supports Dodo Payments and Waffo Pancake alongside Stripe and Creem. Both are integrated over their REST APIs without adding an SDK dependency.
- Checkout, customer portal links, and webhooks cover one-time credit packs, subscription activation and renewals, cancellations, and refunds. Credits are granted and revoked with the same idempotency rules as the existing providers.
- Webhooks must be signed: Dodo requests are verified with Standard Webhooks HMAC signatures, and Waffo requests with RSA signatures against the Waffo platform public keys. Unsigned or invalid requests are rejected.
- The official Nuxt, Astro, TanStack, and SvelteKit templates send checkout to whichever provider is bound to the project.
Where to configure
- Admin → Pay Channels: create a Dodo channel (API key, webhook signing secret, test or live environment) or a Waffo channel (Merchant ID and API private key).
- Admin → Projects → Edit project → Payment: bind the channel. Each project uses one provider.
- Admin → Price Config: fill in the Dodo product ID (
pdt_…) or the Waffo product ID (PROD_…). - In the provider dashboard, register the webhook URL
https://<node3>/dodo/webhookorhttps://<node3>/waffo/webhook. For Waffo, register it once for test and once for production.
Notes
- ZShip coupons are not applied to Dodo or Waffo checkout yet, so the pricing page hides coupon entry for those providers.
- In-app plan changes and cancellation remain Stripe-only. Dodo and Waffo subscribers manage their subscriptions in the provider portal.
- Self-hosted deployments need the node3 D1 migration
0015_dodo_waffo_providers.sqlbefore deploying the new code.