Flutter in-app purchases without building the billing layer yourself
A Flutter app that sells subscriptions has to do more than open a store sheet.
It must fetch products, complete a purchase, decide whether the buyer is entitled, keep that answer correct across iOS, Android and the web, and give support and marketing teams something they can act on. This overview covers what a Flutter purchase SDK plus a subscription backend provides, what the purchase call returns, and how to judge whether that scope fits your team.
What the Flutter purchase SDK covers
The SDK is the client side of a larger subscription system. In the app, you fetch products, start a purchase and read subscription status. Around it, products and pricing are configured remotely from a dashboard rather than hard-coded into a release, customer transaction histories are visible, and real-time events can be pushed to other systems through webhooks. The same customer status is intended to hold across platforms and third-party tools, so a subscriber who bought on one store is recognised elsewhere.
That split matters for planning. The SDK removes store-specific purchase plumbing from your Flutter code, but it does not replace your app's own access rules: you still decide which features sit behind which entitlement, and you still handle the case where a purchase attempt fails.
The purchase call, field by field
The captured Flutter example is short enough to read as a contract. It takes a package as input, awaits a purchase, and returns a PurchaserInfo object. The decision about access is then made from that object: the code looks up a named entitlement in entitlements.all and checks isActive before unlocking content. Anything thrown as a PlatformException is treated as no purchase having occurred.
Read that structure as three separate questions. Did the purchase call complete? Is the entitlement active? If neither, what should the UI show? The example answers the first two and leaves the third to your app. A purchase that throws and a purchase that completes with an inactive entitlement are different failures and usually deserve different messages: the first is an interrupted or rejected transaction, the second means the transaction did not grant the access you expected.
The exact snippet, including the entitlement identifier placeholder and the error branch, is preserved in the accompanying code module.
Reporting and customer visibility
Once purchases flow through the system, the dashboard becomes the operational surface. It reports revenue, churn and retention with filters and segments, and it lets you inspect an individual customer's purchase timeline and active subscriptions so support can debug a specific complaint. Promotional subscriptions can be granted from the dashboard without the user redeeming a promo code.
For growth work, results can be filtered by campaign creative to see what drives conversion, and referral sources can be compared by lifetime value. Attribution and analytics integrations feed the same event stream into tools your team already uses.
Events and integrations
The integration surface is organised around event types. Subscription lifecycle events such as initial purchase, trial start, trial conversion, trial cancellation, renewal, cancellation, uncancellation, billing issues, expiration and product change can be routed to analytics, engagement, support and data destinations. The integration catalogue is grouped into advertising and monetization, analytics, marketing and engagement, customer support, data management, and billing and payments.
Attribution tools include Adjust, Airbridge, Apple Search Ads, AppsFlyer, Branch, Meta Ads, Singular, SplitMetrics Acquire and Tenjin. Analytics tools include Amplitude, Firebase, Mixpanel, mParticle, PostHog, Segment and Statsig. Engagement tools include Airship, Braze, CleverTap, Customer.io, Iterable and OneSignal. Support tools include Discord, Intercom, Slack and Zendesk. Data destinations include Amazon S3, scheduled data exports, Google Cloud and webhooks. Billing and payments tools include Paddle, Stripe and the Stripe Dashboard App. Each destination has its own setup page in the integration registry.
Identity, entitlements and web data
Two cross-cutting features decide whether the system behaves correctly in production. Identity validation matches a subscriber to the right user and keeps that mapping consistent across devices. Cross-platform entitlements then unlock access for the right users wherever they sign in. For teams selling on the web as well as in the app, web purchase data can be connected to the same reporting and analytics stack through the billing and payments integrations.
Build or adopt: a decision checklist
Use these questions before committing either way.
- Do you need purchase state to agree across iOS, Android and web, or is a single store enough for now?
- Will pricing or product changes need to ship without a new app release?
- Does support need to see a customer's purchase timeline and grant access without a promo code?
- Do marketing and analytics teams need subscription lifecycle events in tools they already run?
- Can your team own receipt validation, renewal handling, billing-issue states and cross-device identity itself, and keep owning them through store policy changes?
- Do you need web purchases to appear in the same reporting as app purchases?
If several answers point to shared state and ongoing maintenance, adopting a subscription backend is the smaller commitment. If you sell one product in one store and never change it, the calculus is different.
Getting started
The Flutter SDK documentation covers installation and the first purchase. The dashboard is where products are configured and customers are inspected. The exact purchase snippet referenced above should be treated as the contract for the client call; the surrounding access rules remain your app's responsibility.
Frequently asked questions
Does the Flutter SDK handle purchases on iOS, Android and the web?
The SDK is described as covering in-app purchases and subscriptions across iOS, Android and the web, with reporting and data integrations alongside. Web purchase data reaches the same stack through the billing and payments integrations such as Paddle and Stripe. Exact platform coverage for your app should be confirmed against current SDK documentation.
What does purchasePackage return, and how do I know whether to unlock content?
It returns a PurchaserInfo object. Access is decided by looking up your entitlement identifier in entitlements.all and checking isActive. The identifier in the example is a placeholder that you replace with your own entitlement.
What is the difference between a thrown PlatformException and an inactive entitlement?
A thrown PlatformException means the purchase call did not complete, and the example treats that as no purchase. An inactive entitlement means the call completed but the access you checked was not granted. They call for different user-facing handling.
Can products and pricing be changed without releasing a new app version?
Products are hosted and configured remotely from the dashboard, which is presented as a way to avoid long release cycles for product and pricing changes.
Which third-party tools can receive subscription events?
The captured integration list spans attribution, analytics, engagement, support, data and billing tools, including Adjust, AppsFlyer, Amplitude, Firebase, Mixpanel, Segment, Braze, OneSignal, Zendesk, Amazon S3, Google Cloud, webhooks, Paddle and Stripe. Each has its own setup page in the integration registry.