Creem

The API covers product creation, checkout session generation, subscription management, and webhook events for payment and subscription lifecycle notifications. Agents can create checkout links for products and subscriptions, manage customer portal access, and receive webhook notifications for successful payments, subscription renewals, and cancellations. The merchant-of-record model means the payment and tax flow is handled by Creem, simplifying the agent's billing logic.

Reliability is appropriate for a production payments platform. Creem's merchant-of-record structure means their reliability commitments cover the full payment processing chain, not just the API layer. Teams launching with Creem as their primary payment infrastructure should understand the MoR model implications for dispute resolution and refund handling.

Creem is a merchant-of-record (MoR) payments platform targeting SaaS and digital product teams who want global tax compliance without registering for VAT/GST in every jurisdiction where they sell. As the merchant of record, Creem assumes the legal seller status and handles tax collection and remittance globally — the key benefit for digital product teams expanding internationally who want to avoid the complexity of multi-jurisdiction tax registration. The REST API provides checkout, subscription, and webhook management.

Authentication uses API keys for REST API access, following standard bearer token conventions. The key model is simple and developer-accessible. Teams should store API keys as server-side secrets given their control over checkout and subscription creation operations.

Documentation is developer-friendly and covers the checkout and webhook patterns clearly. The merchant-of-record model explanation is useful context for teams evaluating Creem versus Stripe + tax software alternatives. Teams choosing Creem for simplified global sales will find the documentation covers the integration patterns adequately for the launch use case.