Prerequisites
To integrate the Dodo Payments API, you’ll need:- A Dodo Payments merchant account
- API credentials (API key and webhook secret key) from the dashboard
API Integration
Checkout Sessions
Use Checkout Sessions to sell subscription products with a secure, hosted checkout. Pass your subscription product inproduct_cart and redirect customers to the returned checkout_url.
- Node.js SDK
- Python SDK
- REST API
API Response
The following is an example of the response:checkout_url.
Webhooks
When integrating subscriptions, you’ll receive webhooks to track the subscription lifecycle. These webhooks help you manage subscription states and payment scenarios effectively. To set up your webhook endpoint, please follow our Detailed Integration Guide.Subscription Event Types
The following webhook events track subscription status changes:subscription.active- Subscription is successfully activated.subscription.on_hold- Subscription is put on hold due to failed renewal.subscription.failed- Subscription creation failed during mandate creation.subscription.renewed- Subscription is renewed for the next billing period.
Payment Scenarios
Successful Payment Flow When a payment succeeds, you’ll receive the following webhooks:subscription.active- Indicates subscription activationpayment.succeeded- Confirms the initial payment:- For immediate billing (0 trial days): Expect within 2-10 minutes
- For trial days: whenever that ends
subscription.renewed- Indicates payment deduction and renewal for next cycle. (Basically, whenever payment gets deducted for subscription products, you will getsubscription.renewedwebhook along withpayment.succeeded)
- Subscription Failure
subscription.failed- Subscription creation failed due to failure to create a mandate.payment.failed- Indicates failed payment.
- Subscription On Hold
subscription.on_hold- Subscription is put on hold due to failed renewal payment or failed plan change charge.- When a subscription goes on hold, it will not renew automatically until the payment method is updated.
Best Practice: To simplify implementation, we recommend primarily tracking subscription events for managing the subscription lifecycle.
Handling Subscription On Hold
When a subscription enterson_hold state, you need to update the payment method to reactivate it. This section explains when subscriptions go on hold and how to handle them.
When Subscriptions Go On Hold
A subscription is placed on hold when:- Renewal payment fails: The automatic renewal charge fails due to insufficient funds, expired card, or bank decline
- Plan change charge fails: An immediate charge during plan upgrade/downgrade fails
- Payment method authorization fails: The payment method cannot be authorized for recurring charges
Reactivating Subscriptions from On Hold
To reactivate a subscription fromon_hold state, use the Update Payment Method API. This automatically:
- Creates a charge for remaining dues
- Generates an invoice for the charge
- Processes the payment using the new payment method
- Reactivates the subscription to
activestate upon successful payment
1
Handle subscription.on_hold webhook
When you receive a
subscription.on_hold webhook, update your application state and notify the customer:2
Update payment method
When the customer is ready to update their payment method, call the Update Payment Method API:
You can also use an existing payment method ID if the customer has saved payment methods:
3
Monitor webhook events
After updating the payment method, monitor for these webhook events:
payment.succeeded- The charge for remaining dues was successfulsubscription.active- The subscription has been reactivated
Sample Subscription event payload
| Property | Type | Required | Description |
|---|---|---|---|
business_id | string | Yes | The unique identifier for the business |
timestamp | string | Yes | The timestamp of when the event occurred (not necessarily the same as when it was delivered) |
type | string | Yes | The type of event. See Event Types |
data | object | Yes | The main data payload. See Data Object |
Changing Subscription Plans
You can upgrade or downgrade a subscription plan using the change plan API endpoint. This allows you to modify the subscription’s product, quantity, and handle proration.Change Plan API Reference
For detailed information about changing subscription plans, please refer to our Change Plan API documentation.
Proration Options
When changing subscription plans, you have two options for handling the immediate charge:1. prorated_immediately
- Calculates the prorated amount based on the remaining time in the current billing cycle
- Charges the customer only for the difference between the old and new plan
- During a trial period, this will immediately switch the user to the new plan, charging the customer right away
2. full_immediately
- Charges the customer the full subscription amount for the new plan
- Ignores any remaining time or credits from the previous plan
- Useful when you want to reset the billing cycle or charge the full amount regardless of proration
3. difference_immediately
- When upgrading, the customer is immediately charged the difference between the two plan amounts.
- For example, if the current plan is 30 Dollars and the customer upgrades to an 80 Dollars, they are charged $50 instantly.
- When downgrading, the unused amount from the current plan is added as internal credit and automatically applied to future subscription renewals.
- For example, if the current plan is 50 Dollars and the customer switches to a 20 Dollars plan, the remaining $30 is credited and used toward the next billing cycle.
Behavior
- When you invoke this API, Dodo Payments immediately initiates a charge based on your selected proration option
- If the plan change is a downgrade and you use
prorated_immediately, credits will be automatically calculated and added to the subscription’s credit balance. These credits are specific to that subscription and will only be used to offset future recurring payments of the same subscription - The
full_immediatelyoption bypasses credit calculations and charges the complete new plan amount
Charge Processing
- The immediate charge initiated upon plan change usually completes processing in less than 2 minutes
- If this immediate charge fails for any reason, the subscription is automatically placed on hold until the issue is resolved
On-Demand Subscriptions
On-demand subscriptions let you charge customers flexibly, not just on a fixed schedule. Contact support to enable this feature.
on_demand field in your request body. This allows you to authorize a payment method without an immediate charge, or set a custom initial price.
To charge an on-demand subscription:
For subsequent charges, use the POST /subscriptions/charge endpoint and specify the amount to charge the customer for that transaction.
For a complete, step-by-step guide—including request/response examples, safe retry policies, and webhook handling—see the On-Demand Subscriptions Guide.