Guide

14 min read

Creem reviews

Modern software companies face a fundamental decision when building their monetization stack: how to handle payments, billing, and tax compliance without diverting engineering resources from core product development. Merchant of Record platforms like Creem combine payment processing, tax remittance, and seller-of-record responsibilities in a single offering. For companies with usage-based billing needs, understanding where payment processing ends and billing infrastructure begins is important when choosing a monetization platform.

Key takeaways

  • Creem advertises a standard rate of 3.9% + $0.40 per transaction, with additional fees for specific scenarios including chargebacks, payouts, and optional services
  • Creem holds a 3.1/5 rating across 61 Trustpilot reviews as of November 2026, with customer feedback reflecting varied experiences
  • Creem's September 2026 product update (Creem 2.0) introduced expanded usage-based billing capabilities, including prepaid credits, custom usage meters, and multiple aggregation methods, while Orb provides SQL-based metrics and historical pricing simulations
  • Merchant of Record platforms handle tax compliance and seller-of-record responsibilities for covered transactions, while contractual terms determine merchants' financial obligations for disputes and product-related matters
  • Companies with complex usage-based pricing can benefit from dedicated billing infrastructure like Orb alongside their preferred payment processing services

Understanding online payment processing for modern billing

What payment processors actually do

Payment processing companies facilitate the movement of funds between customers and merchants. Their core functions include authorizing transactions, connecting to card networks, managing fraud detection, and settling funds into merchant accounts. The payment processing landscape ranges from processors focused on transaction services to Merchant of Record platforms that also manage tax compliance and act as the legal seller.

Creem operates in the Merchant of Record category, targeting indie developers and AI product builders seeking payment processing and tax handling in one platform. Its standard advertised rate is 3.9% + $0.40 per successful transaction, with additional charges applying to certain transaction types and services.

How the Adyen acquisition of Orb changes the landscape

Adyen completed its acquisition of Orb for $335 million on July 1, 2026, creating a strategic connection between usage-based billing infrastructure and global payment processing. The acquisition reflects growing demand for connected billing and payment experiences.

The combined capabilities create opportunities to connect billing information with payment data and risk signals, supporting the development of more integrated revenue operations. Orb continues to operate as a standalone product, and customers retain the flexibility to use their preferred supported payment processors.

Evaluating payment processing software for usage-based models

Creem's usage-based billing capabilities

Creem's September 2026 product update, Creem 2.0, expanded its usage-based billing capabilities, including:

  • Prepaid credit wallets with automatic refills and balance tracking
  • Postpaid metered subscriptions with configurable billing periods
  • Custom usage meters for tokens, API calls, compute, and other consumption metrics
  • Multiple aggregation methods including count, sum, average, minimum, maximum, and unique values
  • Usage-event ingestion through a public API with idempotency support
  • Free usage allowances and configurable spending caps
  • Credit balance and usage webhooks for usage monitoring

These capabilities support AI products with token-based pricing and other consumption-driven applications. For companies requiring SQL-based billable metrics, historical pricing simulations using actual usage data, or complex customer hierarchies, dedicated billing platforms like Orb provide additional capabilities.

Integrating billing logic with payment platforms

One approach to complex monetization is combining a dedicated billing platform with payment processing infrastructure. A dedicated billing platform can manage:

  • Metering and usage aggregation
  • Invoice calculation and generation
  • Revenue recognition and finance workflows
  • Plan versioning and migrations

Payment processors then execute payment transactions associated with billing activity. This arrangement allows companies to configure sophisticated pricing and billing workflows while maintaining flexibility in their payment processing relationships.

Creem pricing: transaction fees and additional costs

Standard transaction pricing

Creem's standard pay-as-you-go pricing is 3.9% + $0.40 per successful transaction, with no standard monthly subscription fee, setup fee, or minimum transaction volume. The base fee covers payment processing and the Merchant of Record services included in Creem's offering, such as applicable tax handling and invoicing.

The total amount deducted from a sale depends on its transaction value and any applicable additional charges.

For a $100 transaction, the standard fee calculation is:

  • Percentage fee: $3.90
  • Fixed transaction fee: $0.40
  • Total standard transaction fee: $4.30
  • Amount remaining before other applicable deductions: $95.70

Creem also offers custom pricing arrangements for qualifying higher-volume businesses.

Additional fees and payout costs

Certain payment events, payout methods, and optional services can generate charges beyond the standard transaction fee.

These include:

  • Chargebacks: A reported $25 fee per dispute, alongside applicable disputed amounts
  • Bank payouts: Published fee schedules have listed $7/€7 or 1% of the payout amount, whichever is higher
  • Stablecoin payouts: A reported 2% fee for applicable USDC payout methods
  • Abandoned cart recovery: A reported additional 5% charge on transactions recovered through the feature

These charges are conditional rather than fees applied to every transaction. Businesses comparing payment arrangements can account for transaction volume, dispute frequency, selected payout methods, and optional features when estimating overall costs.

Creem's subscription billing and developer features

Subscription management and checkout

Beyond one-time payments, Creem supports recurring subscriptions and checkout workflows for software and digital products. Its subscription functionality includes recurring billing, customer billing management, and payment-related lifecycle events.

Key capabilities include:

  • Recurring subscriptions with supported billing intervals
  • Hosted and customizable checkout for purchasing products and subscriptions
  • Customer billing portal for accessing subscription and payment information
  • Subscription lifecycle management for renewals, cancellations, and account updates
  • Payment links for launching checkout experiences

These features support businesses selling recurring access to applications, digital services, and subscription-based products.

Developer APIs and integrations

Creem provides APIs, SDKs, CLI tools, and webhooks for connecting payment and subscription workflows with applications.

Developers can use these capabilities to:

  • Create products and checkout sessions programmatically
  • Synchronize subscription status with application accounts
  • Receive payment, renewal, and cancellation notifications through webhooks
  • Connect subscription activity with authentication and access-control systems
  • Test payment-related workflows before production deployment

These tools support common software payment integrations, while dedicated platforms like Orb provide additional infrastructure for SQL-defined usage metrics, enterprise pricing configurations, pricing simulations, and finance operations.

International payment gateways and global monetization

Geographic coverage and tax remittance

Creem's published materials describe tax and compliance handling across more than 190 countries, while some pricing materials distinguish the jurisdictions where specific tax collection and remittance services apply. These figures may refer to different coverage categories, including supported customer locations and tax jurisdictions.

Creem generally schedules payouts on the 1st and 15th of each month. Its published payout conditions also include minimum withdrawal balances and clearing periods before certain funds become eligible for withdrawal. Actual settlement timing depends on the applicable payout method and account conditions.

Benefits of unified billing and payments infrastructure

The Adyen acquisition of Orb creates opportunities for connected billing and payment workflows. Organizations can potentially benefit from:

  • Billing signals informing payment timing and retry strategies
  • Payment performance information supporting revenue operations decisions
  • Streamlined integrations between billing and payment services
  • Connected reporting across the revenue lifecycle

These are opportunities associated with the combined infrastructure rather than guarantees that every capability is already available as a unified product.

What is a merchant account and why it matters for SaaS

The difference between merchant accounts and payment gateways

A merchant account is a financial account used to receive proceeds from electronic payment transactions before settlement to a business bank account. Payment gateways are the technology layer that securely transmits payment information between checkout systems and payment processing infrastructure.

Some payment architectures use a merchant account alongside a gateway and payment processor. Merchant of Record platforms like Creem manage the seller-of-record relationship and relevant payment arrangements, then remit proceeds to the businesses selling through the platform, subject to applicable fees and payout terms.

Choosing merchant services for different business models

The appropriate payment infrastructure depends on business requirements:

  • Simple digital products: Merchant of Record platforms can support one-time purchases and straightforward subscriptions
  • Seat-based SaaS: Subscription billing systems can manage per-user pricing
  • Usage-based models: Dedicated billing infrastructure can support complex metering and pricing calculations alongside payment processing
  • Enterprise contracts: Billing systems may need invoicing, payment terms, commitments, and contract-specific pricing

For companies with hybrid pricing models combining multiple pricing dimensions, flexible billing configurations can support more sophisticated commercial arrangements.

Modern merchant services for subscription billing

Automating subscription and usage-based billing cycles

Subscription billing introduces requirements extending beyond transaction processing. Common capabilities include:

  • Plan versioning to maintain pricing versions and schedule migrations
  • Proration handling for mid-cycle upgrades and downgrades
  • Dunning sequences to support recovery of failed payments
  • Customer hierarchies for enterprise accounts with multiple divisions or subsidiaries

Orb's collections automation provides configurable dunning workflows and payment retry capabilities. These features connect billing operations with supported payment services and finance processes.

Reducing revenue leakage with robust billing systems

Revenue leakage can occur when usage is not captured accurately, incorrect prices are applied, or billing adjustments are missed. Orb's published Supabase case study reports processing more than 1.5 million invoices monthly, demonstrating high-volume billing operations.

Accurate usage-based billing at scale benefits from:

  • Idempotency controls to prevent duplicate event processing
  • Audit trails documenting billing activity
  • Reconciliation between usage, calculated charges, and invoices
  • Monitoring and alerting for billing anomalies

Understanding the Merchant of Record for global operations

Responsibilities of a Merchant of Record

When a company uses a Merchant of Record platform, the provider generally becomes the legal seller for covered transactions. Its responsibilities typically include:

  • Tax compliance: Calculating, collecting, and remitting applicable sales tax, VAT, and GST
  • Seller-of-record responsibilities: Managing the commercial transaction with the end customer
  • Chargebacks: Administering disputes and chargeback processes, subject to contractual allocation of associated costs
  • Currency conversion: Supporting applicable cross-border transactions and settlements

Creem combines these services with tools for selling digital products and managing recurring payments.

How MoR services simplify global expansion

For early-stage companies without dedicated international tax infrastructure, Merchant of Record platforms can simplify selling in supported markets. This model combines payment services with defined seller-of-record responsibilities, subject to the platform's terms and geographic coverage.

Moving from a Merchant of Record arrangement to direct payment processing may involve transferring billing records, establishing merchant relationships, configuring tax services, and updating customer payment methods. The effort depends on the existing integrations and transaction arrangements.

Why Orb's integration with Adyen stands out among payment solutions

Comparing payment processing approaches

The payment processing market includes several models. Payment processors like Adyen provide transaction infrastructure and related financial services. Merchant of Record platforms like Creem package payment processing with seller-of-record and tax responsibilities. Dedicated billing platforms such as Orb manage complex pricing, usage metering, invoicing, and revenue workflows while integrating with supported payment processors.

According to Trustpilot customer reviews, Creem holds a 3.1/5 rating across 61 reviews as of November 2026. Some reviewers describe straightforward onboarding and integration, while others report concerns involving account reviews, payout handling, and customer support. These are individual user reports and do not establish the frequency of such experiences across Creem's overall customer base.

The strategic advantage of billing and payments integration

Orb and Adyen bring together complementary capabilities in usage-based billing and global payments. Orb supports metering, SQL-based billable metrics, prepaid credits, flexible pricing configurations, and invoicing, while Adyen provides payment infrastructure.

Orb continues to support multiple payment processor integrations, allowing customers to retain choice in their payment processing arrangements as integration between the platforms develops.

Ensuring sales tax compliance with integrated software

The importance of accurate tax calculation in billing

Tax compliance is a central component of the Merchant of Record model. Managing sales tax across US states, VAT in Europe, and GST in other jurisdictions requires appropriate tax registration, calculation, collection, and remittance processes.

Businesses seeking direct billing and payment relationships can also use dedicated tax software and integration services to support these responsibilities.

Leveraging billing platforms for financial compliance

Orb integrates with tax providers, including Avalara, Anrok, Numeral, Sphere, Stripe Tax, and TaxJar, to support automated sales tax and VAT calculations. These integrations can help companies:

  • Maintain direct customer payment relationships
  • Use supported payment processors that align with business requirements
  • Connect specialized tax services with billing and invoicing workflows

For revenue recognition, Orb supports ASC 606-aligned recognized and deferred revenue reporting, alongside financial workflows and accounting integrations. These capabilities help finance teams manage revenue reporting associated with complex subscription and usage-based pricing.

Why Orb for usage-based billing and revenue design

Orb approaches billing as revenue infrastructure for companies with sophisticated monetization needs. Its platform brings together metering, pricing, invoicing, and finance workflows to support evolving business models.

  • Raw usage event architecture: Orb retains granular raw usage events in its standard architecture to support historical analysis, billing adjustments, and pricing calculations. This allows teams to recalculate eligible draft invoices and use supported correction workflows for finalized invoices. Hosted Rollups are also available for configured high-volume event streams.
  • Pricing simulations: Orb enables teams to model proposed pricing changes against actual historical usage data before launch. Product and finance teams can preview per-customer revenue impacts and compare different pricing scenarios.
  • AI product monetization includes token-based pricing, prepaid credit drawdown, threshold billing, and configurable spend alerts. These capabilities support AI businesses managing variable consumption and customer spending.
  • Finance-first design: Orb supports engineering, product, and finance teams with invoicing, A/R aging reports, financial reporting, and integrations with NetSuite and QuickBooks, alongside developer APIs and SDKs.

Orb pricing: The Business tier starts at $6 per credit, with volume discounts and 100 free starting credits for new sign-ups. Credits are consumed across separate usage meters:

  • Billing volume: 1 credit per $1,000 in billings processed
  • Raw usage events: 1 credit per 200,000 events ingested
  • Data exports: 2 credits per 500,000 rows exported

The Enterprise plan offers custom pricing and includes capabilities such as customer hierarchies, NetSuite and Salesforce integrations, and a 99.9% availability SLA. The optional Enterprise Support Bundle provides additional services and a 99.99% SLA commitment. See Orb's pricing for further details.

Vercel reported implementing Orb in three weeks and reducing engineering time to build billing for new products by 80%. Replit reported implementing Orb with one engineer and achieving substantial revenue growth following adoption. These are customer-reported results and are not guarantees of future performance.

For companies evaluating Merchant of Record services alongside dedicated billing infrastructure, the decision depends on pricing complexity, finance requirements, and the desired payment arrangement. Creem supports subscription and usage-based billing within its Merchant of Record offering. Orb provides additional capabilities for SQL-based billable metrics, historical pricing simulations, enterprise commitments, customer hierarchies, and revenue operations.

Ready to build more flexible usage-based billing and automate revenue workflows? Explore Orb's revenue design platform to see how granular metering, pricing simulations, and finance automation can support SaaS and AI businesses as they scale.

Frequently asked questions

What fees should I watch for when evaluating Creem?

Creem advertises a standard transaction fee of 3.9% + $0.40, with additional fees for certain services and payment scenarios. These may include chargeback fees, stablecoin payout charges, bank payout fees, and abandoned cart recovery fees. The total cost depends on which services apply and the business's transaction and payout patterns.

How do custodial fund models affect risk?

Merchant of Record arrangements may involve holding transaction proceeds until scheduled settlement or payout dates. Creem generally uses scheduled payouts on the 1st and 15th of each month, with eligibility subject to account conditions, minimum balances, and applicable clearing periods. Settlement delays, reserves, and account restrictions can also exist under other payment processing arrangements.

Can I migrate away from Creem if my billing needs outgrow the platform?

Migration from a Merchant of Record platform can involve changes to customer payment arrangements, integrations, subscription records, and tax responsibilities. The effort depends on how billing data is stored, which integrations are in place, and whether payment credentials can be transferred under the applicable arrangements. A dedicated billing platform like Orb can support sophisticated pricing and subscription management as companies establish or update their payment processing infrastructure.

How does Creem handle account reviews?

Merchant accounts may undergo additional review when information changes, verification requirements apply, or transaction activity triggers a risk assessment. The timing and outcome of individual reviews depend on the platform's policies and the circumstances of the account. Public customer reviews describe a range of onboarding and account review experiences.

What billing capabilities distinguish Orb from Creem?

Creem supports usage-based billing through prepaid credits, custom usage meters, and several aggregation methods. Orb provides a dedicated revenue design platform with SQL-based billable metrics, historical pricing simulations, hybrid and dimensional pricing, enterprise commitments, customer hierarchies, and comprehensive finance workflows. Orb also retains granular raw usage events, supporting historical analysis and billing adjustments. These capabilities help SaaS, AI, and infrastructure companies manage sophisticated monetization models while connecting billing with their existing financial systems.

Ready to try a billing platform built for modern growth?

See how AI companies are removing the friction from invoicing, billing and revenue.

Creem Reviews: Pricing, Fees, Features and Pros & Cons