Creem review

Creem is a hosted merchant-of-record service, delivered as a SaaS dashboard and API rather than a payment library or self-hosted server. It sits between your product and its customers: Creem provides checkout and payment handling, and it takes responsibility for taxes, invoices, fraud screening and chargebacks on sales. You receive payouts on its schedule.

For a software stack, that puts Creem alongside your application and billing logic. You can configure products and pricing in the dashboard, use usage billing for metered products, and connect your application through the API and webhooks. Its credit wallets and custom meters can support prepaid balances or charges based on units such as calls or minutes. Affiliates, revenue splits and short links add sales and attribution functions to the same service. Creem says it supports payments in customers’ currencies and methods across 190+ countries.

Creem names an API, SDKs, CLI, webhooks and MCP server as integration surfaces. Its homepage directs developers to read https://creem.io/SKILL.md to get started and describes a CLI setup flow. It also says one command adds the MCP server to Claude Code, with the same configuration block for Cursor and Claude Desktop or other MCP clients.

The vendor describes using the API to create products, open checkouts and send usage events to custom meters. It also describes verified webhooks for connecting events to your application. The homepage does not name specific API protocols, SDK languages or package names, so confirm SDK support and webhook verification details in Creem’s docs before choosing an implementation path. The MCP option can let an agent manage store tasks, but production code should still handle credentials, event verification and failure paths explicitly.

Creem’s Pay as you go plan has no monthly fee or setup fee and charges 3.9% + $0.40 per successful transaction. That is a $0 monthly starting price, not free payment processing: your bill rises with successful sales. The listed payout schedule is the 1st and 15th.

The Partner plan has custom pricing and is aimed at higher-volume businesses. It includes lower transaction fees, weekly payments concierge meetings, personal phone support and Creem cards for your business; the vendor does not publish a fixed price for it. No add-ons are listed in the pricing details. Creem’s usage billing features let you charge your customers for units, credits or metered use, but the listed pricing does not give a separate platform fee for those meters. Model your own transaction volume against the per-sale fee, and ask Creem about any negotiated rates, reserves or other payout conditions before signing up.

Creem is presented as a hosted service. Its homepage does not list an open-source license or a self-hosting option, so teams should treat it as a vendor-operated dependency unless Creem confirms otherwise. The dashboard, API, CLI and MCP server are ways to operate the service, not evidence that its payment infrastructure can run in your environment.

The vendor does not publish data-export or migration details on the homepage. Before adopting it, ask how to export customer, product, subscription and transaction records, and what happens to active subscriptions if you leave. You will also need to plan a replacement for hosted checkout, tax handling and billing workflows. Your application can keep its own customer and usage records, but migration effort will depend on which system is authoritative for each piece of data.

Before routing live payments through Creem, confirm API rate limits, webhook retry and delivery behavior, uptime commitments, security controls and payout terms with the vendor. The homepage describes webhooks and verified events, but does not publish operational limits or service-level targets. It says Creem handles tax calculation and remittance across 190+ countries, along with fraud screening and chargeback liability; verify country coverage and eligibility for your business and payout location.

Merchant-of-record architecture also means Creem receives customer payments before paying you. In one Reddit thread, a commenter warned that this creates credit exposure and advised checking reserve, hold and suspension terms. Other Reddit users reported waitlists, while one said access arrived after roughly 14 days; these are individual reports, not a published onboarding policy. Ask about approval timing and payout holds before making Creem your only payment path.