Dodo Payments review

Dodo Payments is a hosted Merchant of Record (MoR) and billing service, not a payment library or self-hosted server. Your application integrates with Dodo’s payment and billing services; Dodo handles transaction processing as well as the cross-border tax and compliance work included in its plans. That puts it between your product and its customers’ payments, rather than in your application’s database or infrastructure.

The service targets AI and SaaS billing patterns: credit balances, metered usage such as tokens and API calls, overages, subscriptions with addons, and one-time charges. It also offers global payments and digital product distribution, including storefronts and delivery. The homepage says it supports payments from 220+ countries and regions, with 80+ currencies and 40+ payment methods. Your application still needs to connect product events and customer state to its billing integration; Dodo’s role is to provide the monetization and MoR layer, not to replace your product backend.

Dodo advertises APIs and SDKs, but its homepage does not name an API protocol or enumerate SDK languages. It does list adapters for BetterAuth, Convex, Next.js, Nuxt, SvelteKit, Astro, Remix, TanStack, Hono, Express, and Fastify. For billing UI, it offers React and ShadCN components; for in-app payments, it lists payment links and a React Native SDK for iOS and Android. Confirm SDK language and API support in the vendor’s docs before choosing your integration path.

The hosted MCP server connects AI models to Dodo Payments, and the vendor says it can also be run locally in one command. Its Dodo Agent Plugin provides two MCP servers and seventeen skills, with support listed for Claude Code, Codex CLI, Cursor, VS Code, Kiro, and OpenCode. The homepage also describes plugins and integrations but does not enumerate their full scope. It references subscription and webhook flows for agent-assisted integration. Check the documentation for authentication, webhook retry behavior, idempotency, versioning, and rate limits before relying on those flows in production.

The Standard plan has no fixed cost and lists a 4% + $0.40 standard transaction rate. Enterprise has custom pricing. There is no free plan listed, and the vendor does not list monthly or annual plan prices. The pricing page also lists cross-border tax and compliance, billing, payments, and distribution in the Standard plan.

The bill can grow as you add features: subscriptions, addons, and usage-based billing are listed at +0.5%, while 0.7% per transaction is also listed; usage-based billing separately lists $1 per million events. Ask Dodo which usage and subscription rates apply to your setup. Invoicing is listed at 0.4% per transaction, tax management at 0.5%, analytics and reporting at $10 per month, and storefront transactions at 5%. BNPL adds 3%, PayPal adds 3%, and international cards and APMs add 1.5%. Refunds cost $1 each and disputes $30 each. Regular payouts are free, but payouts under $1,000 incur $5. Confirm the full fee combination in writing before forecasting margins.

Dodo presents its payment and billing product as a hosted service. The homepage offers a hosted MCP server and says the MCP server can also run locally, but that local option is not the same as self-hosting the Merchant of Record, payment processing, or billing platform. The vendor does not publish an open-source license or describe the platform’s source availability on the homepage; it does not list a self-hosted deployment option for the payment service.

The vendor also does not publish data-export details there. Ask what customer, subscription, credit-balance, and transaction data you can export, in which formats, and whether exports remain available after account closure. Moving away would mean replacing the payment and billing integration and arranging another provider for payment processing and MoR responsibilities. Your product should retain its own customer identifiers and usage records so it can reconcile billing state or migrate it if the provider relationship changes.

Before depending on Dodo, verify account eligibility and the handling of disputes, refunds, reserves, and payouts. Reddit users report products being rejected during compliance review, including after integration, and one thread alleges funds were withheld after a store was deemed outside the merchant acceptance policy. These posts are individual accounts, not proof of typical outcomes, but they make pre-approval and written payout terms important. A commenter also reports an upgrade flow that left a customer unable to complete an earlier payment or buy a new plan.

The homepage says Dodo is PCI DSS Level 1 certified and advertises tax compliance and fraud prevention. It does not publish API rate limits, uptime commitments, or detailed reliability terms on the homepage, so ask the vendor for current operational limits and service commitments. Test webhook retries, duplicate-event handling, failed-payment recovery, and subscription changes in your integration. The homepage’s country, currency, and payment-method counts describe broad coverage, but confirm availability for your target markets and product category before launch.