@dodopayments/sveltekit package gives your SvelteKit app three route handlers. Checkout returns checkout URLs, CustomerPortal sends a customer to the Customer Portal, and Webhooks verifies webhook events and routes them to your code.
Checkout Handler
Create checkout URLs from your SvelteKit app.
Customer Portal
Let customers manage their subscriptions and details.
Webhooks
Receive and verify Dodo Payments webhook events.
Installation
1
Install the Package
Run this command in your project root:The package lists SvelteKit 2 (
@sveltejs/kit 2.20.3 or later) and zod 3.25 or later as peer dependencies.2
Set Up Environment Variables
Create a Create the API key under Developer → API Keys. Add your webhook endpoint under Developer → Webhooks and copy its signing secret into
.env file in your project root:DODO_PAYMENTS_WEBHOOK_KEY. DODO_PAYMENTS_RETURN_URL is where customers land after checkout. If you don’t pass an environment, the handlers use live_mode.Route Handler Examples
The examples are SvelteKit
+server.ts endpoints under src/routes/api/. They import your credentials from $env/static/private, which SvelteKit keeps out of client-side code.- Checkout Handler
- Customer Portal Handler
- Webhook Handler
Use this handler to add Dodo Payments checkout to your SvelteKit app.
Checkout returns a GET handler for static checkout and a POST handler for checkout sessions, or for dynamic checkout when you set type: "dynamic". Export GET from a handler created with type: "static" or no type, because the GET handler of a session or dynamic handler returns 400.POST comes from a handler created with type: "dynamic". With type: "session", as in the example route, send the checkout session request.Checkout Route Handler
The checkout handler supports all three ways to take payments with Dodo Payments:- Static Payment Links: Shareable URLs that collect payments without code.
- Dynamic Payment Links: Payment links you generate with custom details. They use deprecated endpoints.
- Checkout Sessions: Hosted checkout with a product cart, customer details, and customization options. This is the recommended flow.
Checkout takes these options:
Static Checkout (GET)
Static Checkout (GET)
Supported Query Parameters
string
required
Product identifier, for example
?productId=pdt_nZuwz45WAs64n3l07zpQR.integer
default:"1"
Quantity of the product.
string
Customer’s full name. Ignored if
firstName or lastName is provided.string
Customer’s first name.
string
Customer’s last name.
string
Customer’s email address.
string
Customer’s country, as an ISO 3166-1 alpha-2 code.
string
Customer’s address line.
string
Customer’s city.
string
Customer’s state or province.
string
Customer’s ZIP or postal code.
boolean
Set to
true to disable the full name field.boolean
Set to
true to disable the first name field.boolean
Set to
true to disable the last name field.boolean
Set to
true to disable the email field.boolean
Set to
true to disable the country field.boolean
Set to
true to disable the address line field.boolean
Set to
true to disable the city field.boolean
Set to
true to disable the state field.boolean
Set to
true to disable the ZIP code field.string
Payment currency, for example
USD.boolean
default:"true"
Show or hide the currency selector.
number
Fixes the amount charged, in major currency units, for example
12.5 for $12.50. Works with Pay What You Want products only, and is ignored if it’s below the product’s minimum price.boolean
default:"true"
Show or hide the discounts section.
string
Any query parameter that starts with
metadata_ is passed as metadata.returnUrl from its config to the link as redirect_url.Response Format
Static checkout returns a JSON response with the checkout URL. In test mode, the URL usestest.checkout.dodopayments.com.Dynamic Checkout (POST)
Dynamic Checkout (POST)
- Send the parameters as a JSON body in a POST request.
- Supports both one-time and recurring payments.
billingandcustomerare required.- For every supported body field, see:
Response Format
Dynamic checkout returns a JSON response with the checkout URL:Checkout Sessions (POST)
Checkout Sessions (POST)
Checkout sessions create a hosted checkout for one-time purchases and subscriptions, with full control over customization.
product_cart is the only required field. If the body has no return_url, the handler uses returnUrl from its config.For more details and every supported field, see the Checkout Sessions Integration Guide.A session created with payment_method_id returns no checkout URL, so the handler responds with 400. To charge a saved payment method, create the session with the SDK instead.Response Format
Checkout sessions return a JSON response with the checkout URL:Customer Portal Route Handler
The Customer Portal route handler creates a Customer Portal session for the customer you pass and redirects the browser to it with a 302 response.Query Parameters
string
required
The customer ID for the portal session, for example
?customer_id=cus_123.boolean
If set to
true, Dodo Payments also emails the portal link to the customer.Webhook Route Handler
The webhook route handler verifies each request before it runs your code:- Method: Only POST requests are supported. Other methods return 405.
- Signature Verification: Verifies the raw request body and the
webhook-id,webhook-timestamp, andwebhook-signatureheaders withwebhookKey, following the Standard Webhooks specification. Returns 401 if verification fails. - Payload Validation: Validates the payload with Zod. Returns 400 for an invalid payload.
- Error Handling:
- 401: Invalid signature
- 400: Invalid payload
- 500: Internal error during verification
- Event Routing: Calls
onPayloadfor every event, then the handler for the event’s type, and returns 200.