Next up

In Progress

Done

Product Roadmap

We would greatly appreciate the integration of PayPal or Klarna into the checkout

Planned

PayPal or Klarna integration

User

Tiered Batch Coupons. For example: <ul><li>Batch 1: Apply Coupon A automatically for the first 200 users.</li><li>Batch 2: Once Batch 1 is exhausted, apply Coupon B automatically for the next 300 users.</li><li>Final: Default to the base price once all batches are filled.</li></ul> This "Scarcity-as-a-Service" logic would be perfect for 'Early Bird' launches. It would also be very helpful to receive alerts for coupons via webhook when a specific coupon is exhausted. That way we can trigger changes in our landing pages.

Automatically apply discount codes

Gabriel Ferraz

I want to be able to support true multi-currency pricing where a single product can have different fixed, "clean" prices per currency (e.g., $14.99 for US users and €9.99 for European users) instead of relying on real-time conversion rates. This is important for marketing and UX to ensure price transparency and intentional pricing across different markets.Workaround: The same can be achieved today by using the 3rd party integration evendeals: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="link" href="https://docs.creem.io/integrations/evendeals">https://docs.creem.io/integrations/evendeals</a>

True Multi-Currency Pricing (Fixed Prices per Currency) (CREEM Native)

lara

SummaryAdd support for recovering <code>instance_id</code> after network failures during license activation. Either make <code>activate</code> idempotent, or allow <code>instance_name</code> as an alternative to <code>instance_id</code> in the <code>validate</code> endpoint. ProblemWhen calling <code>POST /v1/licenses/activate</code>, if the network drops before the response reaches the client, the <code>instance_id</code> is lost. Since <code>/v1/licenses/validate</code> requires <code>instance_id</code>, there's no way to recover.I've tested and confirmed that calling <code>activate</code> again with the same <code>key</code> + <code>instance_name</code> creates a new instance (not idempotent), which increments <code>activation_usage</code>. Proposed Solutions<ol><li>Idempotent activation If <code>activate</code> is called with the same <code>key</code> + <code>instance_name</code>, return the existing instance instead of creating a new one. (This might be a breaking change)</li><li>Allow <code>instance_name</code> in validate (less invasive) Accept <code>instance_name</code> as an alternative to <code>instance_id</code> in the validate endpoint.<pre><code>POST /v1/licenses/validate { key, instance_name } </code></pre>This would be non-breaking since it just adds a new optional parameter.</li></ol> Reference<ul><li>Discussion: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://discord.com/channels/1262843562140241952/1467467311320666258/1467467311320666258">https://discord.com/channels/1262843562140241952/1467467311320666258/1467467311320666258</a></li><li>LemonSqueezy has the same issue: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://lemonsqueezy.nolt.io/733">https://lemonsqueezy.nolt.io/733</a></li><li><a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Keygen.sh">Keygen.sh</a> handles this with fingerprint scope: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://keygen.sh/docs/choosing-a-licensing-model/floating-licenses/">https://keygen.sh/docs/choosing-a-licensing-model/floating-licenses/</a></li><li>Creem Activate API: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://docs.creem.io/api-reference/endpoint/activate-license">https://docs.creem.io/api-reference/endpoint/activate-license</a></li><li>Creem Validate API: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://docs.creem.io/api-reference/endpoint/validate-license">https://docs.creem.io/api-reference/endpoint/validate-license</a></li></ul>

License activation recovery: Allow instance_name in validate endpoint

I’d love to see an auto payout option “ENABLE” like Stripe has. So I set it to the 1st of every month. Once a custom amount is met - the payout will be started/made automatically.

Automatic Payouts on Schedule (Not Manual)

The user wants usage-based proration. Currently, Creem only supports time-based proration. If a user consumes all their plan's credits (usage) and then switches plans, the time-based proration still gives them a credit for the remaining time, which doesn't account for the consumed usage. The user wants the system to account for consumed credits when calculating proration.

사용자는 사용량에 따른 일할 계산 방식을 원합니다. 현재 Creem은 시간 기반 비례 배분만 지원합니다. 사용자가 요금제의 크레딧(사용량)을 모두 소진한 후 요금제를 변경할 경우, 시간 기반 비례 배분 방식에서는 남은 기간에 대한 크레딧이 여전히 제공되지만, 이미 소진된 사용량은 반영되지 않습니다. 사용자는 비례 배분을 계산할 때 이미 소진된 크레딧이 반영되기를 원합니다.

사용량 기반 비례 배분 지원

Usage-based Proration Support

박지환

I am experiencing a critical issue where customer-initiated chargebacks are being approved by Creem's system without giving us the opportunity to defend ourselves. We provide a service and have proof of delivery, yet the system consistently approves these chargebacks. We need this issue addressed and resolved to ensure a more seller-friendly chargeback process.

Chargeback approvals without opportunity to defend

Miguel Bandeira

I want to be able to sell multiple distinct license keys within a single sale/transaction. Currently, Creem only issues one key per purchase, but for my SaaS product, I need the ability to bundle or sell multiple keys at once.

Sell multiple license keys in a single sale

I want Creem to support SEPA Direct Debit and WERO as payment methods at checkout. This is very important for German customers to improve conversion rates and provide preferred local payment options.

Support SEPA Direct Debit and WERO payment methods

michael

It would be great if Creem supported hybrid pricing, where a subscription can have both a fixed recurring base price and a per-unit charge. Example: - $29/month base subscription - + $5 per seat (or +$0.10 per API call) Currently, it seems you can choose either a flat subscription or unit-based pricing, but not combine both. This is a common SaaS pricing model and would make Creem usable for many additional billing scenarios.

Support hybrid pricing (base subscription + unit pricing)

Micha

It would be great to have the ability to use our own domain for the checkout page. This would help maintain brand consistency and build more trust with customers during the payment process.

Completed

Custom Domain for Checkout Pages

Alipay Support

We are currently integrating your payment system into our website. However, we noticed that payments are processed exclusively through a hosted checkout session on your domain, and there is no option for embedding the payment flow via an iFrame on our site.For a more seamless user experience and better control over the checkout process, we would like to request support for an iFrame-based payment integration. This would allow users to complete their payments without being redirected away from our platform.

Şu anda ödeme sisteminizi web sitemize entegre ediyoruz. Ancak, ödemelerin yalnızca sizin alan adınızda barındırılan bir ödeme oturumu aracılığıyla işlendiğini ve sitemize iFrame aracılığıyla ödeme akışını yerleştirme seçeneğinin olmadığını fark ettik.Daha sorunsuz bir kullanıcı deneyimi ve ödeme sürecini daha iyi kontrol edebilmek için, iFrame tabanlı ödeme entegrasyonu için destek talep etmek istiyoruz. Bu sayede kullanıcılar, platformumuzdan yönlendirilmeden ödemelerini tamamlayabilecekler.

iFrame Ödeme Entegrasyonu Desteği Talebi

Request for iFrame Payment Integration Support

I’d love to see Creem support a hybrid billing model where a customer is charged a one-time fee upfront, followed by a recurring subscription (e.g., monthly or yearly). This is especially useful for digital product sellers like me, who offer both lifetime deals and update/maintenance subscriptions. My Use Case:I sell a digital product (a boilerplate) with two variants:<ol><li>Lifetime Deal:<ul><li>One-time payment (e.g., $30)</li><li>No updates or support in the future</li></ul></li><li>Ongoing Updates Access:<ul><li>One-time setup fee (e.g., $30 for the product itself)</li><li>Plus a recurring subscription (e.g., $10/month) for access to future updates, support, or new features</li></ul></li></ol>Currently, there's no way to implement this cleanly in Creem. Other platforms like LemonSqueezy support this out of the box Why This Is Important:This pricing model is becoming increasingly common among indie developers and product creators. It allows us to:<ul><li>Monetize the core product fairly with a one-time fee</li><li>Sustain long-term development and support through recurring revenue</li><li>Offer clear and flexible options to customers</li></ul>Feature Request:Please consider enabling the ability to:<ul><li>Charge a one-time setup fee </li><li>Start a recurring subscription immediately or after a delay (configurable per product/variant)</li></ul>This could be built as part of the product setup, where creators can add both a one-time charge and a recurring plan in the same offer.Thanks for considering — I believe this would unlock a ton of flexibility for creators like me and make Creem a great fit for many digital product businesses.

Support for One-Time Fee + Recurring Subscription for Digital Product Variants

It would be nice to clone a product so that it would be fast to create subsequent products and variabtions

Add ability to clone a product

We’d love to have the ability to upload and offer completely free products ($0) directly—without relying on discount codes. Currently, we’ve been told to apply a 100% discount code to make a product free, but that’s not an ideal long-term solution. Most platforms allow setting the price to $0 natively. For example, LemonSqueezy has a "Lead Magnet" pricing option that lets creators easily offer free downloads. Something similar would be super helpful for us too. Especially since free products are a core part of our marketing and customer experience, this would make a big difference. We’d really appreciate it if this could be considered!

할인 코드에 의존하지 않고 직접 완전 무료($0) 제품을 업로드하고 제공할 수 있는 기능이 있으면 좋겠습니다. 현재는 100% 할인 코드를 적용하여 제품을 무료로 제공하지만, 이는 장기적으로 이상적인 솔루션이 아닙니다. 대부분의 플랫폼에서는 기본적으로 가격을 0달러로 설정할 수 있습니다. 예를 들어, 레몬스퀴지에는 크리에이터가 쉽게 무료 다운로드를 제공할 수 있는 "리드 마그넷"( ) 가격 옵션이 있습니다. 저희도 이와 비슷한 기능이 있으면 큰 도움이 될 것입니다. 특히 무료 제품은 마케팅과 고객 경험의 핵심적인 부분이기 때문에 큰 도움이 될 것입니다. 검토해 주시면 정말 감사하겠습니다!

크리에이터의 무료($0) 제품 제공 허용

Allow Creators to Offer Free ($0) Products

if a business takes out a SaaS subscription, and they create the subscription on a staff member email, and that staff member leaves, we need to be able to change the email address on an active subscription to a new staff member. IDEALLY on update subscription API, but if the customer can do it in the customer login, and we can say, hey you can login there, thats fine also

Customer able to update their email address on an active subscription

Ability to split revenue from a product or store.

Revenue Splits

Similar to <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Polar.sh">Polar.sh</a> allow the customer to pay what they want for helping contribute to the product.

Product: Customer can choose to pay what they want

I want to be able to perform full CRUD (Create, Read, Update, Delete) operations for products, discounts, and prices via the public API. Currently, management of these entities is manual in the dashboard, which is inefficient for automated workflows. Full API support for these entities is important for scaling and integrating with other systems.

Full CRUD API for Products, Discounts, and Prices

Help Center

Improved

Fixed

creem

Payment declined that needs further information