framework-adapters

Framework Adapters

Use this skill when you need to integrate Dodo Payments into a web framework using the official adapter packages. Framework adapters handle route plumbing, environment configuration, and handler setup so you don't build checkout, portal, and webhook routes from scratch.

When to use this skill

• You're building a checkout flow in Next.js, Express, Fastify, Hono, Astro, Remix, SvelteKit, Nuxt, TanStack, Bun, or Convex.
• You need to set up a customer portal session endpoint.
• You're adding webhook handlers that verify signatures and dispatch events.
• You want framework-idiomatic route placement and environment variable handling.
• You need to choose between static, dynamic, or session checkout modes.

What framework adapters do

Dodo publishes @dodopayments/* packages that wrap the core SDK with framework-specific route handlers. Instead of writing your own HTTP handlers, you import the adapter's handlers and mount them directly in your routes.

Each adapter exposes three handler families:

• Checkout: static (GET only), dynamic (POST with cart), or session (POST with pre-built session).
• CustomerPortal: generates a time-bound portal session link.
• Webhooks: verifies webhook signatures and dispatches typed events.

Export names are not uniform across adapters. Most export Checkout / CustomerPortal / Webhooks, but two differ, and the return shapes differ as well. Check this table before writing imports:

Adapter	Checkout export	Portal export	Handler shape
nextjs, hono, astro, bun, remix, tanstack	Checkout	CustomerPortal	returns a request handler
express	checkoutHandler (lowercase)	CustomerPortal	returns (req, res)
fastify	Checkout	CustomerPortal	returns { getHandler, postHandler }
sveltekit	Checkout	CustomerPortal	returns { GET, POST } / { GET }
nuxt	checkoutHandler (auto-imported)	customerPortalHandler	no import statement
convex	DodoPayments component	—	createDodoWebhookHandler