Cleeng Standard Statement of Work

Version: May, 2026

This document presents a detailed scope of work for integrating Cleeng's payment and subscription management solutions into your digital infrastructures. Our aim is to enhance the efficiency and effectiveness of subscription services, making payment processes smoother and boosting subscriber engagement across web and mobile interfaces.

The primary objective is to empower Customer with the capability to efficiently manage and scale their subscription models using Cleeng's robust platform. This integration will facilitate a direct, streamlined path for users to engage with content, ultimately driving revenue growth and improving user satisfaction.

Expected outcomes include:

• Enhanced Subscriber Management: Leveraging Cleeng's platform for improved subscriber acquisition, retention, and management.
• Streamlined Payment Processing: Implementing a seamless payment system that supports various payment methods and gateways, reducing friction for subscribers.
• Comprehensive Integration Support: Providing detailed documentation and support for integrating Cleeng's API with your existing web and mobile applications.
• Data Migration and Merchant Setup: Assisting in the migration of legacy data to Cleeng's platform and setting up merchant accounts for transaction management.
• User Support Enhancements: Developing resources and tools to enhance user support capabilities, including FAQs, email templates, and chatbot functionality.

Through this integration, users will gain access to a powerful set of tools and services designed to optimize their subscription business model, enhance the user experience, and drive digital content consumption. The scope of work provided herein lays out the roadmap for achieving these goals through a collaborative, structured, and efficient integration process.

Project Overview

The primary goal of this project is to onboard and integrate Cleeng's payment and subscription services into your web and mobile applications. This integration aims to enhance the user experience by providing a smooth and secure platform for payment processing, subscription management, and in-app purchase functionality.

Overview of Responsibilities

Cleeng's responsibilities are detailed in the phase tables throughout this document. Customer will play a crucial role in the success of this integration. Specifically, Customer is responsible for:

• Developing and testing all front-end applications that will interface with Cleeng's services.
• Integration with Cleeng in-app purchase framework.
• Product configuration, including setting up offers, subscription upgrades and adding admin accounts.
• Integrating Cleeng's platform webhooks with your own backend services ensuring seamless communication and functionality across platforms.
• Planning and managing all migration and cutover activities.

Project Deliverables

These deliverables are designed to support all phases of the integration process, from initial setup to full deployment. Below is a detailed list of the project deliverables:

• Comprehensive Integration Guide: Detailed documentation outlining API endpoints, data formats, and a step-by-step guide for integrating payment and subscription services.
• Secure Payment Processing: Assistance in integrating Cleeng's platform into the selected payment gateway(s), facilitating secure and efficient payment transactions. This includes support for setting up payment methods, handling transactions, and ensuring compliance with security standards.
• Cleeng Core Integration: Support for integrating Cleeng's subscription management module (Cleeng Core), enabling users to easily subscribe, upgrade, and manage their subscriptions. This module will provide the tools necessary for managing subscriber lifecycles, from initial sign-up to renewal or cancellation.
• Seamless User Experience: Assistance in integrating in-app purchase functionality within the mobile application.
• Real-Time Updates and Notifications: Integration of Cleeng's platform webhooks with your backend services. This will enable you to receive real-time updates and notifications about subscription changes, payment transactions, and other critical events, ensuring that your systems are always in sync with Cleeng's platform.
• Cleeng Hi5 and Help Center: A comprehensive self-service platform designed to provide users with easy access to FAQs, troubleshooting guides, and helpful resources to enhance their experience with Cleeng's subscription management services. Applicable only when Customer is utilizing the Hi5 product module.

Implementation Strategy

This multi-phase approach is designed to address all critical aspects of the integration. By breaking down the process into distinct phases, we aim to provide clear guidance, support, and resources at each step.

Phase 1: Requirements and Planning

Phase 2: Setup & Configuration

Customer is required to confirm and validate each of the steps mentioned above within 3 business days of Cleeng notifying Customer that the steps have been completed. This collaboration ensures that both parties are aligned and satisfied with the setup before moving forward.

Upon the completion of these steps, Customer will have access to working test and production environments, setting the stage for the subsequent phases of application integration, payment and subscription management, and the enhancement of user support capabilities. This phase is critical for laying the groundwork for a successful integration, enabling Customer to proceed with confidence towards achieving a fully functional and integrated subscription management system.

Phase 3: App Store and Frontend Application Integration

In this critical phase, the integration of Cleeng's platform with your application is fully realized. Cleeng commits to providing robust support and capabilities to ensure that your applications are well-equipped to meet the demands of users across various platforms.

Cleeng will extend comprehensive support to the integration process with the following capabilities:

• Multi-Platform Subscription Purchases: Enable users to purchase recurring subscriptions or other entitlements through iOS, tvOS, Android (Google Play), Amazon Fire, Roku, Vizio, and Samsung ensuring a broad reach across devices.
• Entitlement Management: Maintain ongoing, up-to-date entitlements based on app store payment processing, ensuring users have access to what they've paid for without interruption.
• Restore Purchase Flows: Support restore purchase flows within apps, allowing legacy app store payments to be saved in Cleeng. (This is only needed if In-app Payment details cannot be provided from previous provider)
• Event and Notification Listening: Cleeng's ability to listen to events and server-to-server notifications from Apple, Android, Roku, Amazon and Vizio ensures real-time responsiveness to user transactions and activities.
• Receipt Management: Offers support for transferring receipts from one user to another for Apple and Android.

API Integration Guides

To support these integrations, Cleeng provides comprehensive API documentation and integration guides, crucial for your development team in implementing subscription management and payment processing functionalities:

• Apple Payments: Apple Payments Integration Guide
• Android Payments: Android Payments Integration Guide
• Roku Payments: Roku Payments Integration Guide
• Amazon Fire TV Payments: Fire TV Payments Integration Guide
• Vizio: Vizio integration
• Samsung TV: Samsung TV integration

These guides serve as essential resources for integrating Cleeng APIs with both applications and middleware, ensuring a streamlined and effective integration process.

Web Front-end app will leverage Cleeng’s Mediastore Hosted Customer Flows where possible. Use cases and flows that cannot be handled with Cleeng’s Mediastore Hosted Customer Flows, including account updates and offer listings, will be managed using Cleeng’s Mediastore and Core APIs listed in Appendix 1: Cleeng Mediastore APIs. 

The high-level project activities and responsibilities for this phase are listed below.

Phase 4: Transactional emails

This phase of the project concentrates on establishing the email communication framework. Customer is responsible for activating, customizing, and testing all email features, using the documentation and templates provided by Cleeng.

Phase 5: Webhook integration

This phase is designed to empower Customer with the tools and information necessary to expand their service capabilities through webhook integration. The responsibility for implementing and maintaining webhook integrations lies with Customer; Cleeng provides documentation and verification support as described in Appendix 3.

Phase 6 (optional): Merchant setup

This phase applies if Customer is utilizing Cleeng’s Merchant services. It focuses on the setup and configuration of merchant accounts to process payments seamlessly. The activities below delineate the responsibilities of both Cleeng and Customer in the merchant setup process.

By using our SaaS platform, Customer acknowledges and agrees to the specific countries in which we operate as the Merchant of Record, covering all merchant operations within those jurisdictions.

Phase 7: User and Data Migration

This phase is dedicated to the meticulous process of migrating legacy subscription and credit card payment details into Cleeng Core, ensuring a seamless transition from your existing systems to Cleeng's comprehensive commerce tools. 

The user migration process comprises multiple steps, each requiring tailored preparation and review to accommodate the specific migration case. This allows for adjustments to meet the unique migration requirements effectively.

This phase is designed to minimize the impact on the user experience while accommodating specific migration requirements through a series of well-defined steps.

Data Migration Steps:

1. Planning and preparation: Define scope, timelines, and data mapping requirements, and map your data to Cleeng required formats.
2. Environment setup for user and subscriber test migration (optional): Configure sandbox environment to validate process through dry runs.
3. Sandbox migration dry-run (optional): Validate process through dry runs in a sandbox environment. Conduct simulated migrations to troubleshoot and confirm data formats and processes.
4. Production environment setup: Prepare live environment for migration.
5. Production migration: Execute the actual migration of data.
6. Document final results: Confirm success, document outcomes and deviations.
7. Cutover and support: Transition the service live and provide post-migration assistance.

Credit card data will be migrated between payment service providers.

The migration of historical transactions, financial statistics, analytics and terminated historical subscriptions is not included in the standard migration process.

Payment Migration Process:

1. The migration of subscriptions precedes the migration of credit card. This ensures a seamless transition of payment methods for continued service access.
2. For credit card data, the migration output file, containing Cleeng user and subscription data, will be passed to Adyen by Cleeng for matching with payment data.

Data Security Measures:

For any sensitive Personal Identifiable Information (PII) involved, a secure solution involving SFTP transfer and PGP encryption will be provided by Cleeng. This ensures the utmost security of data both in storage and during transfer.

Phase 8: Hi5 implementation

This phase is designed to bolster user support capabilities, ensuring users receive timely, accurate, and helpful support. It applies where Customer is utilizing the Hi5 product module. Activities span from reviewing use cases to deploying advanced support tools like chatbots and CRM configurations, with responsibilities shared between Customer and Cleeng to optimize the support experience.

Documentation and Training

This section outlines the approach to ensuring that the Customer team is fully equipped with the knowledge and resources necessary for a successful integration and ongoing management of the Cleeng platform.

Documentation

1. Appendices: 
   • Detailed documentation related to the project's scope, including technical specifications, integration guides, and project plans, are appended to this Statement of Work for easy reference.
2. Online Resources: 
   • Cleeng maintains a comprehensive repository of documentation on its website, accessible here, in the Cleeng Broadcaster Help Center and Developer Portal. This repository includes user guides, API documentation, troubleshooting tips, and more, supporting a wide range of needs from technical integration to daily operation.
3. Onboarding Guide: 
   • Cleeng will share an onboarding guide document designed to facilitate self-service onboarding for Customer. This guide covers:
     • An overview of the onboarding process and what Customer can expect during each phase.
     • Specifics about the project, including timelines, key milestones, and deliverables.
     • Instructions on using the Cleeng dashboard for managing subscriptions, creating offers, analyzing performance metrics, etc.
     • Guidelines for escalating issues, including contact information for Cleeng support teams and resources for self-help.

Training

1. Knowledge Transfer Session: 
   • Cleeng will conduct a dashboard training session aimed at transferring essential knowledge to Customer’s team. This session will cover hands-on training on the Cleeng dashboard, emphasizing offer creation, subscriber management, and data analysis.

2. Continuous Learning: 
   • Cleeng encourages ongoing learning and will provide access to updated materials and resources as new features are released or updates are made to the platform. You are encouraged to regularly consult Cleeng’s online resources for the latest information on Help Center and Dev Documentation. 

Assumptions and Exclusions

This section outlines the assumptions made during the planning of this project and identifies any exclusions from the scope of work. These assumptions and exclusions are crucial for setting accurate expectations and defining the boundaries of project responsibilities and deliverables.

Assumptions

1. It is assumed that your technical environment is compatible with Cleeng's platform requirements. Any necessary adjustments or upgrades to ensure compatibility are your responsibility.
2. The success of data migration and integration processes is contingent upon Customer providing complete and accurate data. Cleeng assumes that all data provided by Customer, including user details and payment information, is accurate and in the required format.
3. It is assumed that Customer has the necessary internal resources and expertise, or access to such resources, to manage the implementation on Customer’s side, including any required development work and project management.
4. Project timelines are based on assumptions of timely reviews, approvals, and feedback from Customer. Delays in Customer responses may impact project delivery dates.

Exclusions

1. In the event that Customer cannot provide App Store receipts matched to user data, the migration of Apple users cannot be performed. Cleeng is excluded from responsibility for any data loss or migration failure resulting from incomplete or inaccurate data provided by Customer.
2. Any custom development work required outside the scope of the standard integration solutions provided by Cleeng, including but not limited to custom features, bespoke analytics, or unique user interface designs, is excluded from this statement of work unless explicitly agreed upon in a separate document.
3. Integration with third-party services not covered under the Cleeng platform's standard integration capabilities is excluded. You are responsible for managing any additional integrations, including the associated costs and technical support.
4. Provisioning of hardware, networking infrastructure, or any other physical technology resources required for the implementation or operation of Cleeng’s platform within your environment is excluded from Cleeng's responsibilities.
5. Extensive training for Customer’s staff beyond the standard onboarding and knowledge transfer sessions outlined in the Documentation and Training section is excluded. Additional training can be provided upon request, subject to separate terms and conditions.

Appendices

Appendix 1: Cleeng Mediastore APIs

All Cleeng Mediastore APIs:

• Getting Started: Getting Started with Cleeng APIs
• List Customers: List Customers API - With externalID parameter to check if the account exists and retrieve user details.
• Register Customer: Register Customer API - For creating user accounts in Cleeng.
• Update Customer: Update Customer API
• Update Customer Email: Update Customer Email API - For updating user email.
• Delete Customer: Delete Customer API - To delete user accounts.
• Retrieve Customer Entitlements: Retrieve a Customer's Entitlements - Submit the entitlement check to Cleeng.
• Is Trial Allowed: Is Trial Allowed API - To check if the trial was already used.
• Submit Consent: Submit Consent API - To submit user consents.
• Update Broadcaster Specific Personal Data: Update Broadcaster Specific Data API - To submit users' answers to custom questions.
• SSO Login: SSO Login API - Generate tokens for components.
• Fetch Offers: Fetch Offers API - To list the offers.
• List Offers: List Offers API - List all offers.
• Fetch Offer Details: Fetch Offer Details API - Fetch specific offer details.

Other Cleeng APIs endpoints available on the Cleeng platform and included in the documentation can be also used by you in case required. However in order to ensure that the final solution will meet the performance and functional requirements, you will notify Cleeng about the intent to use other APIs and obtain Cleeng’s approval.

Appendix 2: Emails

The standard emails, possible configurations, supported languages and standardizations are documented here.

Appendix 3: Webhooks

Webhooks play a crucial role in the real-time synchronization of events between Cleeng's platform and your servers, facilitating automated notifications and actions based on specific occurrences within the platform.

Structure

Webhooks are structured as real-time HTTP POST requests sent to specified endpoints, carrying JSON payloads with event-specific data. This mechanism ensures immediate notification and action upon events occurring within Cleeng's platform, such as new transactions or updates to user profiles.

• broadcasterId: Identifies the broadcaster for whom the webhook is sent.
• topic: Specifies the topic or event type that triggered the webhook.
• data: Contains event-specific information or payload.

See here for webhook specific topics.

Webhooks Verification

To ensure the security and integrity of webhook data, Cleeng offers verification based on Hash-based Message Authentication Code (HMAC) signatures. You can opt into this verification mechanism during the webhook subscription process, providing an additional layer of security through a shared secret between you and Cleeng. 

A shared secret between you and Cleeng should not be divulged to any 3rd party. It's your responsibility to store/remember its value. For security purposes, Cleeng does not provide any mechanism to display its value to you in case it was forgotten.

Appendix 4: Migration Templates

Specific templates provided for facilitating the migration of legacy data into Cleeng’s platform. These templates are designed to ensure data integrity and smooth transition from existing systems to Cleeng Core.