Dodo Payments

Install corsair and @corsair-dev/dodopayments, add the Dodo Payments plugin, and connect with an API key. Then call methods like corsair.dodopayments.api.customers.create() from your app. Corsair verifies webhooks, and syncs data per tenant.

Yes. Dodo Payments requires an API key from your Dodo Payments account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Dodo Payments, GitHub, Notion, Stripe, and the rest. Trigger Dodo Payments from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for payment processing platform for subscriptions, checkout, and global merchant transactions. Common builds include sync jobs, admin tooling, and agents that call Dodo Payments APIs from your backend. Webhook handlers react to Dodo Payments events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced Dodo Payments records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Dodo Payments API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/dodopayments in the open repo. When Dodo Payments ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Dodo Payments data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Dodo Payments data on your behalf.