Next up
21Committed and queued
PayPal or Klarna integration
We would greatly appreciate the integration of PayPal or Klarna into the checkout
Automatically apply discount codes
Tiered Batch Coupons. For example: Batch 1: Apply Coupon A automatically for the first 200 users. Batch 2: Once Batch 1 is exhausted, apply Coupon B automatically for the next 300 users. Final: Default to the base price once all batches are filled. 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.
Support SEPA Direct Debit and WERO payment methods
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 hybrid pricing (base subscription + unit pricing)
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.
Multi-currency pricing: support GBP, AUD, NZD, CAD (or local-currency display at checkout)
Products can currently only be priced in USD or EUR. For merchants with customers in the UK, Australia, New Zealand, or Canada, that means those customers check out in a foreign currency: the price looks unfamiliar, their bank converts it at card rates, and many pay a 2 to 3 percent foreign transaction fee on top. It measurably hurts conversion outside the US and EU, and other MoR platforms already support per-currency pricing on a single product. Requests, in order of preference: Per-currency price points on a single product, so one subscription product can carry USD, GBP, EUR, AUD, NZD, and CAD prices and checkout picks the right one by customer location. Failing that, support for creating products in GBP, AUD, NZD, and CAD, so merchants can run one product per currency and route customers server-side. As a lighter interim step, local-currency display at checkout: keep billing in USD but show an approximate converted amount in the customer's own currency before they pay. Happy to beta test any of these.
License activation recovery: Allow instance_name in validate endpoint
Summary Add support for recovering instance_id after network failures during license activation. Either make activate idempotent, or allow instance_name as an alternative to instance_id in the validate endpoint. Problem When calling POST /v1/licenses/activate, if the network drops before the response reaches the client, the instance_id is lost. Since /v1/licenses/validate requires instance_id, there's no way to recover. I've tested and confirmed that calling activate again with the same key + instance_name creates a new instance (not idempotent), which increments activation_usage. Proposed Solutions Idempotent activation If activate is called with the same key + instance_name, return the existing instance instead of creating a new one. (This might be a breaking change) Allow instance_name in validate (less invasive) Accept instance_name as an alternative to instance_id in the validate endpoint. POST /v1/licenses/validate { key, instance_name } This would be non-breaking since it just adds a new optional parameter. Reference Discussion: https://discord.com/channels/1262843562140241952/1467467311320666258/1467467311320666258 LemonSqueezy has the same issue: https://lemonsqueezy.nolt.io/733 Keygen.sh handles this with fingerprint scope: https://keygen.sh/docs/choosing-a-licensing-model/floating-licenses/ Creem Activate API: https://docs.creem.io/api-reference/endpoint/activate-license Creem Validate API: https://docs.creem.io/api-reference/endpoint/validate-license
Automatic Discounts without Code
Currently, we can add discount using discount code. It would be better if we could just pre-apply the discount, again without any code. No code field will be required, and discount will be applied automatically to the products selected.
improve customer portal UI
the current customer portal UI is soo clunky even though it works. a little layout redesign and tabs addition would really help.
Usage-based Proration Support
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.
Sell multiple license keys in a single sale
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.
In Progress
2Actively being built
True Multi-Currency Pricing (Fixed Prices per Currency) (CREEM Native)
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: https://docs.creem.io/integrations/evendeals
Automatic Payouts on Schedule (Not Manual)
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.
Done
82Recently shipped
Custom Domain for Checkout Pages
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.
Alipay Support
Support Alipay or WeChatPay
Request for iFrame Payment Integration 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.
Support for One-Time Fee + Recurring Subscription for Digital Product Variants
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: Lifetime Deal: One-time payment (e.g., $30) No updates or support in the future Ongoing Updates Access: One-time setup fee (e.g., $30 for the product itself) Plus a recurring subscription (e.g., $10/month) for access to future updates, support, or new features 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: Monetize the core product fairly with a one-time fee Sustain long-term development and support through recurring revenue Offer clear and flexible options to customers Feature Request: Please consider enabling the ability to: Charge a one-time setup fee Start a recurring subscription immediately or after a delay (configurable per product/variant) 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.
Add ability to clone a product
It would be nice to clone a product so that it would be fast to create subsequent products and variabtions
Allow Creators to Offer Free ($0) Products
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!
Customer able to update their email address on an active subscription
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
Revenue Splits
Ability to split revenue from a product or store.
Product: Customer can choose to pay what they want
Similar to Polar.sh allow the customer to pay what they want for helping contribute to the product.
Full CRUD API for Products, Discounts, and Prices
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.