CREEM 2.0 is an all-in-one merchant of record and billing platform designed for software businesses, offering agentic store configuration, usage-based metering, credit wallets, and global tax compliance.
What the product does and how it is positioned
CREEM 2.0 operates as a global merchant of record platform tailored for software and digital product businesses. It combines checkout infrastructure, indirect tax management, invoice issuance, and fraud protection to allow developers to sell across more than 190 countries without establishing local tax entities.
Beyond standard checkout processing, the platform provides specialized billing models for AI and software applications, including prepaid credit wallets, seat-based subscriptions, and metered usage. It also integrates programmatic store management through an MCP server, CLI, and mobile monitoring applications.
Source-supported ways to use the product
Software developers configure prepaid credit balances that decrement based on user generations, API calls, or compute minutes, with optional auto-refill triggers.
Founders recruit affiliate partners, assign custom commission rates, and automatically split transaction revenue among collaborators without manual spreadsheet reconciliation.
Technical teams use MCP-compatible assistants such as Claude Code or Cursor to generate checkout links, configure webhooks, and manage store settings via natural language.
The documented workflow, where available
Add the Creem MCP server to an MCP client such as Claude Code, Cursor, or Claude Desktop, or set up the CLI.
Define products, credit packs, usage meters, or discount codes using agent prompts, the CLI, or the web dashboard.
Test checkout flows and verify incoming webhooks within the sandbox environment using test API keys.
Switch from test keys to production keys to accept global customer transactions and monitor sales in real time.
CREEM 2.0 integrates Model Context Protocol tooling into its commerce architecture, enabling AI development assistants to manage store configuration tasks. Developers can configure an MCP server within clients like Claude Code, Cursor, or Claude Desktop using skill files that outline platform functions.
Through API keys in test mode, connected agents can script dashboard operations, construct product catalogs, generate checkout URLs, and register verified webhooks. In production, agents can monitor lifecycle events such as failed renewals, scheduled cancellations, and new purchases to initiate recovery actions or discount offers.
Checks to run with your own material and workflow
What was checked and when
Answers based on the source-checked product record
Creem acts as the merchant of record for transactions, which means it processes customer payments, issues compliant invoices, handles fraud screening, assumes chargeback liabilities, and calculates, collects, and remits indirect taxes such as VAT, GST, and sales tax across supported countries.
Usage-based billing allows businesses to attach per-unit pricing to products with optional free allowances and usage caps. Developers define custom meters for metrics like tokens, API requests, compute, or active seats, send usage events to the API, and Creem aggregates and bills the activity.
AI agents can connect via the Model Context Protocol server, CLI, or direct API calls. After configuring an MCP client such as Claude Code, Cursor, or Claude Desktop, agents can create products, open checkouts, configure verified webhooks, and generate customer billing portal links.
Creem supports payments through credit and debit cards, PayPal, Apple Pay, and Google Pay, enabling buyers in over 190 countries to pay in their local currencies.
Store activity can be monitored via native mobile applications for iPhone and Android with real-time lock screen push notifications, agent notifications across platforms like Slack, or through the centralized dashboard.
