Cowrie Research

dodo-payments

4 min read

Dodo Payments

  • Name: Dodo Payments
  • URL: https://dodopayments.com/
  • Category: AI-first billing, checkout, and distribution product surface / merchant-of-record integration layer / stablecoin-and-agent-payments tooling
  • Tags: ethereum-ecosystem solana-ecosystem
  • Summary: Dodo Payments at the project layer is the checkout, billing, distribution, webhook, and MCP integration surface inside a broader Dodo Payments company shell. Keep this note on the product mechanics — products, subscriptions, credits, usage billing, hosted checkout, license keys, stablecoin payment methods, and AI-assisted SDK access — while the named operator boundary around merchant acceptance, verification, liability, retention, and risk review now lives in dodo-payments.
  • What it does:
    • Provides hosted checkout and API-driven payment flows for one-time sales, subscriptions, add-ons, hybrid billing, credit balances, and usage-metered SaaS monetization
    • Packages digital-product distribution features such as product catalogs, storefront flows, discounting, affiliate support, and license-key management alongside payments and billing
    • Lets supported merchants offer card, local-payment-method, and stablecoin checkout options while Dodo handles the merchant-of-record and fiat-settlement shell above those flows
    • Exposes SDKs, adapters, payment links, branding controls, and product objects that developers integrate directly into AI and SaaS products
    • Publishes webhook-driven lifecycle events, event filtering, endpoint secrets, replay tooling, and third-party connector routing for downstream automation
    • Provides AI-facing MCP surfaces so assistants can search Dodo docs and execute Dodo SDK operations inside Dodo-managed tooling flow
  • Key claims:
    • The homepage positions Dodo around credit balances, usage metering, subscriptions, global payments, and digital-product distribution, which makes the product layer analytically useful as a bundled SaaS monetization surface rather than only a checkout page
    • The merchant-of-record docs say Dodo becomes the legal seller and handles tax, disputes, and compliance, which matters here because the product surface is deliberately packaged as more than a PSP integration
    • The stablecoins docs say customers can pay with stablecoins from most countries outside India while merchants bill and settle in USD, and they list USDC, USDP, and USDG across Ethereum, Solana, Polygon, and Base
    • The FAQ says products are mandatory objects in the system, hosted checkout is not embeddable in iframes, and multiple businesses can be managed through one account, which helps clarify the opinionated product model developers inherit
    • The webhooks docs show Dodo exposing a signed event surface with subscription filtering, retry policy, replay tooling, and connector-based delivery into third-party destinations, which makes the event model part of the real product integration boundary
    • The MCP docs say AI assistants can interact with Dodo through a Code Mode architecture with payment, subscription, customer, product, license, and usage-billing capabilities, plus a separate Dodo Knowledge MCP for semantic documentation search
  • Whitepaper: No classic standalone whitepaper is the point here. The strongest product-layer materials are Dodo’s homepage and docs for merchant-of-record behavior, stablecoin checkout, webhooks, MCP, and workflow constraints, now complemented by the company-side source capture in ../whitepapers/dodo-payments-company-primary-sources-2026-08-08.md.
  • Sources:

Internal linkages

  • Company / operator boundary for merchant acceptance, verification, liability, retention, and risk review: dodo-payments.
  • Strongest same-slice product reads: coinflow and moonpay-commerce.
  • Protocol-level contrast when the question is interoperable payment initiation rather than one hosted seller-of-record stack: open-payments.

Protocol / company boundary

  • Keep this note on the product surface: checkout sessions, products, subscriptions, credits, usage events, license and storefront workflow, payment-method selection, stablecoin checkout configuration, webhooks, SDKs, and MCP-assisted integration.
  • Use dodo-payments for the named operator boundary around merchant acceptance, business verification, legal-seller status, tax and chargeback liability, compliance and retention requirements, dashboard authority, and the right to suspend or review accounts.
  • That split matters because how do I integrate Dodo's billing and checkout objects? and which company controls whether my product is even allowed on the platform? are related but not identical questions.

Control surface

  • At the product layer, authority sits in product objects, subscription and usage-billing semantics, checkout flow shape, supported payment methods, stablecoin configuration, webhook publication and retries, connector routing, and the MCP-assisted developer workflow.

  • The thicker merchant-admission, compliance, and liability shell now points upward to dodo-payments.

  • Read this note as hosted monetization software rather than an open payments or stablecoin standard.

  • Last reviewed: 2026-08-08 UTC

Graph View

Backlinks