Code Freeze
As previously announced, Cleeng is currently in its scheduled holiday code freeze period to ensure maximum platform stability.
Code Freeze Period: December 17, 2025 – January 7, 2026
What you can expect:
- No new features or major changes will be introduced to the codebase, unless they are critical fixes.
- We will continue to monitor systems to ensure smooth operations.
- Regular deployment of features and updates will resume after January 7, 2026.
Upcoming
📢 Taxes Collection for Australian Customers
We are rolling out an update for tax management in Australia. Starting January 1st, 2026, customers in this country will have an applicable Goods and Services tax (GST) of 10% added to their purchases.
If you use Cleeng’s Merchant (Cleeng acts as your Merchant of Record) and sell your digital content to customers in Australia, the following information is relevant to your content offers:
- Historically, prices of offer localizations for Australia were exclusive of tax.
- Starting January 1st, 2026, prices for Australia will be treated as inclusive of tax in the Cleeng platform.
- You may need to update your prices on any offers that target the Australian market that were created before January 1st, 2026.
What do I need to do?
The tax rate of 10% will apply to any purchases of your offers made in Australia and will be remitted on your behalf to the tax authorities. If you wish to update your prices, you can do so in the Cleeng dashboard.
You can also see the related article on Taxes Collection in Australia.
New
✨ Transactional Emails: Support for Dutch
We've added support for Dutch in our transactional emails.
What do I need to do
- If you have chosen Basic Customization, translations are automatically synced.
- If you have selected Advanced Customization (you use your own Mailchimp Account), you need to sync templates in the Cleeng Dashboard > Admin & Tools > Transactional Emails > Mailchimp Integration to take advantage of the newly added language version.
Learn more
For more information on transactional emails and translations, see What emails are sent to my customers?, and How to set up transactional emails?.
🚀 Support for Google Play Store Resubscribe Feature
We’ve improved how Cleeng handles re-subscriptions made directly from the Google Play Store, ensuring better continuity for subscribers and more reliable processing behind the scenes.
With this update, Cleeng more smoothly recognizes returning subscribers and automatically links new purchases to their existing Cleeng accounts, restoring access without interruption.
This update delivers a seamless and more convenient experience for returning customers, simplifying the re-subscription journey.
Learn more
To find out more, see our documentation on handling resubscriptions.
✨ Cleeng Dashboard - Favicon Update
We've updated the browser tab icon (favicon) for the Cleeng Dashboard. It now displays the Cleeng logo, replacing the former ChurnIQ icon.
This update ensures a consistent brand experience across all our platforms, including the Cleeng Dashboard, Help Center, Developer Portal, and the main Cleeng Website. Same powerful dashboard, now with a unified look!
🚀 Tax Rate in Transactions Report
The exportable Transactions Report now includes a Tax Rate column. It shows the tax rate applied at the time of the transaction, calculated as applicable tax divided by transaction net price.
Key benefits
This provides more detailed financial data, making it easier for publishers to handle accounting and financial reporting.
Where to find it
The new column is available in the Transactions Report, which you can export from the Cleeng Dashboard by navigating to Analytics > Data Export.
Learn more
For more information on the data included in exports, please see our documentation on how to understand exported data.
✨ "Unspecified" Direction for Apple Subscription Switches
We've introduced a new “unspecified” subscription switch direction to improve how subscription changes are handled and reported when the switch intent cannot be clearly identified.
This enhancement currently applies to Apple in-app purchases using StoreKit 2.
The “unspecified” direction is used when a subscription switch is initiated via Apple and the offer switch direction (upgrade or downgrade) is not configured or cannot be determined. We will record the switch as unspecified, ensuring accurate and transparent reporting while allowing the subscription change to be finalized immediately and without interruption.
Not Affected: Cleeng-managed web-based subscriptions are NOT affected by this change, as their offer switch direction is always defined as upgrade or downgrade.
Reporting impact
As a result of this change, you may see the unspecified value in reporting dashboards, specifically:
- The Upgrades and Downgrades dashboard
- The ‘Subscription Switch History’ tile on the Customer History dashboard
It will also be visible in the "Subscription Switch direction" column in the Transactions Report.
What do I need to do
This change only affects you if you use multi-channel billing with externally-managed subscriptions (i.e., subscriptions whose lifecycle is managed outside of Cleeng).
If this applies to you, you must prepare your system to handle the new unspecified direction.
Please see the detailed API updates related to "unspecified" direction below.
API Changes
API Updates Related to "unspecified" Direction
The direction property of the subscription switch resource now supports a new string value: unspecified.
Important: This is an additive change. While it does not remove existing functionality, integrations that read the switchDirection property must be updated to handle the new unspecified value to prevent potential errors or unexpected behavior in your system.
The unspecified value will be returned only when an external source starts using it to make subscription switches. If your implementation uses an Apple StoreKit 2 connector, it must be prepared to handle the unspecified switch direction in both requests and responses.
Core (3.1) API changes:
-
Switch subscription (POST /3.1/subscription_switches) - the unspecified value is available for the switchDirection body param and in the response
The unspecified value is available in the response of:
- List switches (GET /3.1/subscription_switches)
- Fetch switch details (GET /3.1/subscription_switches/{switchId})
- Update switch (PATCH /3.1/subscription_switches/{switchId})
MediaStore API changes:
-
Switch subscription (POST /customers/{customerId}/subscription_switches/{offerId}) - the unspecified value is available for the switchDirection body param and in the response
The unspecified value is available in the response of:
- List switches (GET /subscription_switches)
- Fetch switch details (GET /subscription_switches/{switchId})
- Update switch (PATCH /subscription_switches/{switchId})
Other API Updates
The following Core (3.1) API endpoints have a new paymentId field added to the request payload:
- Update switch (PATCH /3.1/subscription_switches/{switchId})
- Revive subscription (POST /3.1/subscriptions/{subscriptionId}/revive
MediaStore SDK Components Changes
The changes for MediaStore SDK Components version 5.23.0 have been released.
Important note: Due to a necessary update in the npm authorization process, these changes are only available in npm package version 5.23.4. To get the latest updates, please install this specific version.
->>><<<-
Click here to subscribe to our release notes emails and we will send them over to your inbox.