Changelog

This week, we are rolling out a major localization update for our Checkout. As your Merchant of Record, Freemius supports selling not only in international markets, but also in your buyers’ local markets. This is why our Checkout supports local languages and currencies out of the box.

With today’s deployment, we are opening our Checkout for RTL (right-to-left) languages.

Hebrew is the first RTL language we are releasing. It is currently available in beta while we gather feedback from our makers. We expect to move it to production mode very soon.

In the meantime, if you want to use it, simply add the language parameter with the value he.

Once the translation is finalized, it will automatically show up for buyers from Israel when you use language=auto in your Checkout configuration. You can learn more about it in our documentation.

We also fixed a Checkout bug that could affect products without USD pricing configured. In some cases, the Checkout could fail to load when an explicit currency parameter was not passed. This has now been fixed.

This week, we are rolling out a few bug fixes around the Settings page of a product.

• Newly created products did not show the bearer token on the Settings page immediately. It would only appear after a full page refresh. This has been fixed.
• We noticed that adding or deleting plans for a product could, in some edge case scenarios, break the settings form. We found the root cause and have deployed a fix.

We saw a bug in the Checkout where preloading a bundle checkout with a license key for manual renewal or upgrade did not work in some cases. The Checkout incorrectly reported that the license key was invalid.

We found the root cause and have deployed a fix. This now allows bundle renewal and upgrade flows to correctly preload the Checkout with the relevant license key.

This week, we are rolling out the following quality-of-life improvements to the Developer Dashboard.

Fixed Payments Table

We noticed that in some cases, the payments table was not loading all available payments.

We found the root cause and have deployed a fix for the same.

Events Menu in the Store Context Is Back

We noticed a regression where we accidentally removed the Events menu from the store context. It is now back. The events page shows all triggered events for all products under the store and is a great way to debug webhooks with store-level visibility.

Fixed Layout Glitch in the Earnings Page

Our earnings page has a currency filter that shows your earnings based on the selected currency. It came to our notice that it was not visible properly.

With today’s deployment, it has been fixed.

As part of improving our compliance and payout process, we have rolled out an update that now requires you to set your billing information before you can set up your payout method.

Setting up your billing information is simple, and you can refer to our documentation to learn how. It should only take a few minutes. If anything is unclear, feel free to contact our support.

This update ensures that all new makers complete their billing setup before receiving payouts. For existing makers, we have already started sending emails to notify you about this upcoming change. If you have already set your billing information, no further action is required on your side.

If you have not yet set your billing information, your payouts will continue as usual for now. However, please note that you have until May 31st, 2026 to complete the setup. Failing to do so may interrupt the payout process for your account. We will send a few more email reminders before this takes effect.

Once again, if you are unsure about anything, please contact our support. We will be happy to help.

We fixed a minor UI glitch in the subscriptions & payments tables where the tax tooltip was not rendered properly due to an unnecessary whitespace after the + sign.

The issue has now been resolved.

Freemius supports offering trials to your customers. It is a great way to market your product by letting customers try it before they purchase. Freemius handles both cases, whether a payment method is required or not.

It came to our attention that the Checkout title in trial mode did not include the product name, which could make the flow less clear for buyers. This has been fixed with today’s deployment.

Over the past few days, we noticed degraded performance in our Checkout for PayPal payments. Many Checkouts were failing and could not connect to buyers’ PayPal accounts. We immediately began investigating the issue and worked closely with the PayPal team to resolve it.

While the issue has now been resolved through a joint effort between Freemius and PayPal, we are also rolling out several redundancies to reduce the risk of similar outages. Our system is now better equipped to handle similar issues more gracefully in the future. Our team members will also be notified much earlier if such an issue occurs or if there is an increased risk of it happening.

We understand the past day has been frustrating. With these new safeguards in place, we expect to handle similar situations much more smoothly going forward. Thank you for your patience while we worked through this.

This week we’re rolling out a useful improvement to our analytics. You can now click any chart legend item to filter the chart by the selected items only.

This makes it easier to inspect your data in more detail. For example, if you want to view only a single country or just a few countries in the payments breakdown chart, you can now select those countries directly from the legend and the chart will render only the relevant data.

We hope you enjoy this new feature. If you have more suggestions, please let us know in our feature board.

We identified a regression in the bundle flow where the new product form could not render the product type field in the UI when adding a product to a bundle. This has now been fixed.

In addition, we have improved the UX of the dialog used while adding products to a bundle to make the flow clearer.

It is now more obvious how to add an existing product to the bundle or create a new product within the bundle flow.

Our Checkout supports license renewals even when the original pricing (quota) has been deleted. In such cases, the Checkout intelligently selects the closest pricing the license can be migrated to, based on its quota and activation count. When this happens, the Checkout also shows a notice to the buyer explaining the change.

However, we identified a regression in this flow where the notice could appear in unintended cases, especially for licenses whose quota had been changed from the Developer Dashboard. We found the root cause and deployed a fix. In addition, we improved the UX of the notice so it is clearer for buyers.

We have made the following updates to our backend and API servers.

License API Improvements

We have enhanced our license activation API doc to document the various error codes the endpoint might return and how to handle them. This should make it easier to build more reliable application license integration logic.

Additionally, all our endpoints now return an X-API-Server-Time header to help protect against local time tampering when validating a license’s expiration on the client side.

Fixed Free Plan Identification

We identified an edge-case bug where our system was incorrectly treating some plans as “Free” plans. This led to some unintended side effects. For example, some of the transactional emails were being sent with “Thanks for upgrading” instead of “Thanks for subscribing”, even when no Free offering was involved.

We found the root cause and fixed the issue.

This week we’re deploying a few small quality-of-life fixes to our Checkout.

The back button now aligns properly within the vertical space around the Checkout area. Previously, it was incorrectly pushing the Checkout form downward.

The Checkout also now correctly identifies an edge case in bundles where buyers try to upgrade a child license from a child product’s context. We now block this path and prompt the buyer to use the correct Checkout instead, helping avoid a confusing upgrade flow.

We have deployed the following quality-of-life updates to the Developer Dashboard.

We identified cases where the horizontal scrollbar was not visible, especially on pages with long tables. This made it harder to inspect wider datasets. The issue has now been fixed.

We also noticed a few UI glitches and alignment issues in the recently released Email History feature. Those have now been fixed as well.

We identified a UI inconsistency where the default profile picture in the Customer Portal was still referencing older assets from before our rebranding.

This has now been updated to ensure visual consistency across the Customer Portal, Developer Dashboard, and Checkout.