Docschargebeedocs

HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Developer Resources
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee


  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

AI in Chargebee


  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model context protocol)

Product Catalog


  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions


  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers


  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Invoices, Credit Notes and Quotes


  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes


  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities


  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Managing payments with ChargebeeJS
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Reports and Analytics


  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations


  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Order Management
  • Mobile Subscriptions (Legacy)
    • Legacy Vs New Solution
    • What do you need to know
    • What are the Limitations
    • Apple App Store
    • Google Play Store
    • Multiple Apps Connection
    • Frequently Asked Questions
  • Other Integrations
  • Articles and FAQ

Data Privacy & Security


  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations


  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  2. Integrations
  3. Mobile Subscriptions (Legacy)
  1. Billing
  2. Integrations
  3. Mobile Subscriptions (Legacy)

Mobile Subscriptions (Legacy)

We've stopped giving access to the legacy solution due to the limitations mentioned here. Please request access for enabling the new Omnichannel Subscriptions solution.

Introduction

If you are offering digital products/services in Apple or Google stores, then you are mandated to use in-app payment methods offered by these respective stores. While standalone solutions can manage in-app purchases and recurring billing, they often fail to handle the complexities of businesses operating across multiple platforms. To handle this complexity, a mobile subscription solution was launched in 2022, and this helped to create a single source of truth for subscriptions and one-time purchases made across Apple, Google, and Chargebee.

This solution was built on the premise that in-app subscriptions of app stores can be represented as Chargebee's subscription. This means that the billing engine of Chargebee can renew the subscriptions, generate invoices in the payment due state, and mark the invoices as paid upon receiving notification from the respective stores. However, post-launch, we learned from our EAP customers that the approach of retrofitting app store subscriptions to Chargebee leads to subscription state mismatches and has limitations, as stated here.

Hence we have decided not to treat in-app subscriptions as regular Chargebee subscriptions. Instead, they will be classified as Omnichannel subscriptions, managed directly by their respective sources, such as Apple or Google. Learn more

Was this article helpful?