New
✨ Google Play Billing - One-Time Products Supported
The recently released version of our Google Play connector now supports one-time (non-subscription) products. A one-time product purchase made in Google Play is handled as a pass in Cleeng, so you can now sell one-off access alongside subscriptions.
What you need to do
- If you are already using the new version of our connector and want to support one-time products, use the relevant API endpoints with the new value for the
productTypeparameter:one_time_product. - If you are about to start integrating Google Play in-app purchases using the new version of our connector, please follow our dedicated integration tutorial.
- If you have been using our legacy integration, you can use our simple migration path to move to the new connector. For more details, reach out to your dedicated account manager or our Technical Support Team.
Learn more
For integration details, see our Google Play Billing integration tutorial, and for related API changes, see the API Changes section below.
✨ Hosted Customer Flows: Custom Cancellation Reasons
We have upgraded our unsubscribe experience within Hosted Customer Flows. To give you more precise retention insights, we have introduced the Custom Cancellation Reasons feature. Now, you can completely customize the survey options to align with the unique retention categories of your business.
The cancellation survey configuration has its own dedicated Cancellation Reasons section, where you can toggle a new setting to replace default survey choices with your own custom, localized feedback options.
Key benefits
- Tailored churn insights: Capture real-time feedback using specific reasons that matter directly to your subscription model.
- Fully customizable: Replace standard options with your own tailored cancellation reasons. Decide in which order these options should be displayed to your customers.
- Multi-language capabilities: Define your custom reasons in English and translate them into any language supported by your portal to ensure a localized experience.
Where to find it
Navigate to your Cleeng Dashboard, go to Admin & Settings > Hosted Customer Flows, and select the User Account tab. Locate the new, dedicated Cancellation Reasons section that features:
- Show cancellation survey: Lets you turn the cancellation survey step on or off.
- Enable custom cancellation reasons: The brand new feature toggle that replaces default reasons with your customized list.
What you need to do
- By default, the Show cancellation survey option is enabled. If you wish to completely disable it, toggle this setting to No.
- Customize your reasons: Configure your new cancellation reasons and their translations. Then turn Enable custom cancellation reasons to On to show them in the unsubscribe experience in the User Account.
- If you ever want to revert to Cleeng’s standard questions, simply set the Enable custom cancellation reasons toggle to Off. Your custom-configured reasons will be kept, so you won't lose your work.
Learn more
To learn how to configure this and other user account behaviors, please visit the Configure Web User Account Widget Behavior section in our Hosted Customer Flows documentation.
Improvements
🚀 Improved Retention on Apple Pay
Following an upgrade released in early August 2026, Apple Pay subscriptions are now linked to the subscriber's Apple account instead of their physical device. Thanks to this upgrade, renewals now continue to be processed smoothly when a subscriber replaces or loses their device, or removes a card from Apple Wallet.
Subscribers now also see the price, billing cycle, and trial period directly in the Apple Pay payment sheet before confirming.
Key benefits
This upgrade makes Apple Pay a more resilient payment method for subscription billing, ensuring you don't lose active customers simply because they get a new phone:
- Seamless renewals: Subscribers can change devices without interrupting their active subscriptions.
- Lower involuntary churn: Fewer renewals fail for reasons unrelated to the subscriber's intent or funds.
- Protected revenue: You avoid the customer friction of asking subscribers to re-enter payment details, keeping them active and retaining your revenue.
Expect a gradual decline in involuntary churn and higher lifetime value for your Apple Pay subscribers over the coming renewal cycles. Our estimations show a 55-65% reduction in involuntary churn once this upgrade has reached its full potential. Based on current Apple Pay recurring performance across all customers, this means an uplift of 6% in recurring revenue coming from Apple Pay.
What you need to do
No action is required. The change is live from early August 2026 onward and applied automatically to any new recurring transaction.
Learn more
For questions on this upgrade, contact your account manager.
🚀 Analytics: "Active Subscriber Movement" and "Active Subscription Movement" Renamed
We’ve refined the naming for two of our key analytics metrics to provide a cleaner, more user-friendly interface and make them easier to scan in the side navigation menu.
- Active Subscriber Movement is now Subscriber Movement.
- Active Subscription Movement is now Subscription Movement.
Where to find it
Look for Subscriber Movement and Subscription Movement in your Cleeng Dashboard > Analytics.
What you need to do
- No configuration is required. This update has been applied to your dashboard automatically.
- Update your bookmarks: Because the page URLs have been updated to reflect the new names, if you have previously bookmarked the old links in your browser, you may need to navigate to the new pages and re-save the updated URLs.
Learn more
To find out more about the metrics, see the Subscriber Movement and Subscription Movement articles.
🚀 Hosted Customer Flows: Expanded offerId Support in Payment Events
We have enhanced our Checkout widget's event tracking to further enrich your transaction data. With this update, the offerId parameter is now included in both payment success and payment failure events across our supported payment gateways.
The onWidgetEvent callback now consistently passes the offerId for both payment-succeeded and payment-failed events, ensuring full data parity across all payment methods.
Key benefits
- Streamlined analytics: Identify exactly which offer a user successfully purchased (or failed to purchase) directly from the event payload.
-
Simplified integration for developers: Front-end teams listening to the
onWidgetEventcallback for custom integrations can now rely on theofferIdbeing present universally.
What you need to do
No action is required. This enhancement has been automatically rolled out to the Checkout widget.
Learn more
To learn more about widget event handling, please see: Cleeng Hosted Widgets: Global Communication Methods.
API Changes
🚀 Updated
The following API endpoints for Google Play in-app purchase integration have been updated to support one-time product purchases:
-
Register Google Play purchase (
POST /purchases) - theone_time_productvalue is accepted for theproductTypebody parameter. -
Transfer Google Play purchase (
POST /purchases/transfers) - theone_time_productvalue is accepted for theproductTypebody parameter. -
Check Google Play purchase synchronization status (
GET /purchases/synchronizations/{synchronizationId}).
->>><<<-
Click here to subscribe to our release notes emails and we will send them over to your inbox.