- Organizations that require enterprise-grade compliance documentation before procurement
- If buyers require SOC 2 Type II reports, ISO certificates, penetration test summaries, or detailed security architecture before vendor selection, Creem's public disclosures (based on the sources captured here) appear limited. Buyers in this situation should request documentation directly from the vendor.
- Organizations that cannot accept MoR platform risk controls
- Businesses that cannot tolerate potential account reviews, reserve placements, payout holds, or transaction blocks should avoid MoR models or require explicit contractual protections. Community reports include at least one anecdote describing unexplained declines, which highlights a category-level operational risk.
- Organizations that need maximum ownership of billing relationships
- Exiting an MoR often requires subscribers to re-authorize payment methods; organizations that require portability of payment credentials and billing relationships may find MoR arrangements restrictive.
- Organizations selling very low-priced items
- The fixed $0.40 per-transaction component increases the effective cost for very low-ticket transactions.
- Affiliate-heavy or margin-sensitive businesses without tolerance for splits surcharge
- The splits feature incurs an additional 2% fee, which can substantially affect margins in affiliate-heavy models.
- Current limitations acknowledged by the vendor / policy constraints
- Vendor documentation references prohibited-product categories, indicating policy-based restrictions common to MoR providers.
- Roadmap / beta signals
- Some vendor features are labeled as beta in public materials (for example, affiliate tooling). Buyers should confirm production readiness and support scope for beta features.
- Scale limitations
- No explicit public limits (API rate limits, maximum transaction volume, or region-specific method availability) were located in the captured sources. Buyers with high-volume requirements should request performance and scaling documentation.
- API limitations / integration constraints
- The vendor publishes API documentation and references LLM-indexable documentation endpoints, but detailed constraints (rate limits, pagination limits, retry semantics) were not evaluated in this pass and should be validated during technical due diligence.
- Operational risk limitations (category-wide but relevant)
- As a Merchant of Record provider, the platform inherits category-level risks: account reviews, reserves, delayed payouts, and transaction blocking. Prospective customers should request written payout schedules, reserve policies, and terms for handling funds in flight.