Multi-Channel Billing: Overview

Cleeng manages subscription lifecycle events across all major app store platforms and normalizes them into a single, consistent entitlement model. This means you can manage entitlements, reporting, and customer experience through one unified system, regardless of how each platform delivers its data.

This article explains how Cleeng manages subscription lifecycle events across all major app store platforms. For platform-specific setup, see the individual Cleeng integration guide for each platform.

Why It Matters

Supporting subscriptions across app stores means dealing with different protocols, event schemas, and delivery models, each with its own lifecycle nuances. Cleeng removes this complexity by integrating natively with each platform and abstracting platform-specific notification formats into a unified subscription model.

This gives you:

• Subscription lifecycle tracking: every state change from activation to churn.
• Entitlement management: access granted or revoked based on subscription status.
• Revenue reporting: accurate billing and financial reconciliation.

Supported In-Apps

Cleeng integrates with six major app store platforms, each with its own delivery mechanism and event structure:

• Apple App Store
• Google Play
• Roku Channel Store
• Amazon Appstore
• Vizio SmartCast
• Samsung Checkout

Integration Models

Each platform delivers subscription data differently. Cleeng supports four integration models to ensure complete lifecycle coverage:

• Real-Time Server-to-Server: Platform pushes lifecycle events to Cleeng in real time (ASSN V2, RTDN, RTN via SNS, S2S notifications).
• Webhook: Platform-initiated HTTP callbacks delivered to a per-publisher Cleeng endpoint.
• Server-Side Receipt / API Check: Cleeng queries the platform's Application Programming Interface (API) to verify purchases and resolve current subscription state. Used at purchase time and as the source of truth alongside real-time signals.
• Scheduled Reconciliation: Proactive polling jobs that align Cleeng state with the platform. This is the primary mechanism where no real-time push exists, and a backstop everywhere else.

Regardless of the integration model, Cleeng runs scheduled reconciliation processes to verify subscription states and catch any missed or delayed signals.

Normalization Layer

Cleeng normalizes all platform signals — whether from real-time notifications, webhooks, receipt validation, or API polling — into a unified subscription model. This enables consistent entitlement management across all app stores.

For more information, see Subscription Lifecycle Flows.

Summary Matrix

The table below shows how Cleeng processes each lifecycle event across all platforms at a glance.

• Real-time: Event received instantly from the store.
• Reconciliation: Updated via scheduled sync.
• Kept in sync by Cleeng: Cleeng aligns status via receipt validation.
• Not available from store: Store does not provide this signal.

Coverage varies by platform because each app store exposes a different set of lifecycle signals.