| name | sales-dodo-payments |
| description | Dodo Payments (dodopayments.com) platform help — developer-first Merchant of Record (MoR) for SaaS, AI, and digital products: sells on your behalf and handles global sales tax/VAT/GST across 220+ countries / 40+ payment methods, with subscriptions, usage/credit billing, one-time payments, embeddable checkout, and license keys. Full REST API (test/live.dodopayments.com, Bearer key) for payments/subscriptions/products/customers/checkout/license-keys/refunds/payouts, Standard-Webhooks-signed events, 9 SDKs, framework adapters, a CLI, and an MCP server. Per-transaction MoR fee, no monthly fee. Use when integrating payments/subscriptions via the API or SDK, verifying webhooks with the standardwebhooks library, choosing MoR vs a payment processor, handling tax/VAT as MoR, or issuing license keys. Do NOT use for merchant-of-record selection across vendors (use /sales-merchant-of-record), checkout-conversion strategy (use /sales-checkout), or general digital-product strategy (use /sales-digital-products). |
| argument-hint | [describe what you need help with in Dodo Payments] |
| license | MIT |
| version | 1.0.1 |
| tags | ["sales","payments","merchant-of-record","platform"] |
| github | https://github.com/dodopayments |
Dodo Payments Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Take a payment / create a subscription via the REST API or an SDK
- B) Build checkout — hosted Checkout Session, embeddable checkout, or a framework adapter
- C) Verify webhooks (Standard Webhooks) and react to payment/subscription events
- D) Sell digital products — license keys, entitlements, digital delivery
- E) Handle MoR concerns — tax/VAT/GST, refunds, disputes, payouts
- F) Decide MoR (Dodo) vs a raw payment processor, or compare to Paddle/Lemon Squeezy
-
API/SDK or no-code? Code → REST API + a language SDK / framework adapter. Low-code → hosted Checkout Sessions + short links.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Choosing a Merchant of Record across vendors (Paddle/Lemon Squeezy/Polar/Creem/Dodo) | /sales-merchant-of-record {question} |
| Checkout/cart conversion strategy across platforms | /sales-checkout {question} |
| General digital-product selling strategy across tools | /sales-digital-products {question} |
| Generic iPaaS wiring to a CRM/ESP | /sales-integration {question} |
When routing, give the exact command, e.g. "This is a selection question — run: /sales-merchant-of-record MoR vs Stripe for a global SaaS".
Step 3 — Dodo Payments platform reference
Read references/platform-guide.md for the full reference — the MoR model (what Dodo takes liability for), the billing models (subscriptions/usage/credit/one-time), the object map (what's API vs hosted vs SDK), pricing, and quick-start recipes (create a payment; verify a webhook; spin up a checkout session).
Read references/dodo-payments-api-reference.md for the integration surface — base test/live.dodopayments.com, Bearer auth (Developer → API Keys, read-only/read-write), tiered rate limits, the endpoint catalog (payments, subscriptions, products, customers, , , discounts, refunds, disputes, payouts, webhooks management), signing (// via the library), the 9 SDKs + framework adapters + + CLI.
