Skip to content
AppDues
Log in
Contact salesSign up

Cordova In-App Purchases

Adding purchases to a Cordova app usually means wiring store billing on each platform, tracking who is entitled to what, and building a backend to keep it all consistent.

A managed purchase layer handles that plumbing so the Cordova SDK can fetch products, complete purchases, and report subscription status, while product and pricing changes happen remotely instead of through long release cycles. This page describes the capabilities of the Cordova SDK and dashboard as presented in the vendor's product overview; whether a given capability is offered under your own account or plan is owner-confirmed.

Decision checklist before you adopt

Use this checklist to judge fit before committing:

  • Do you need the same purchase and entitlement logic across iOS, Android, and other platforms rather than per-store code?
  • Do you want to change products and pricing without shipping a new app build?
  • Do you need a single customer-status record that other tools can read?
  • Do you need revenue, churn, retention, and segment reporting out of the box?
  • Do you need real-time events (webhooks) to trigger downstream actions?
  • Are you prepared to handle the purchase callback states — success, user cancellation, and error — explicitly in your Cordova code?

If most answers are yes, a managed layer removes backend work. If you only need a one-off purchase with no reporting or cross-platform status, a lighter approach may be enough.

How a purchase call works

The supplied purchase module shows two entry points. purchasePackage takes a package and returns a product identifier plus purchaser info; you then check whether the active entitlement you care about is defined before unlocking content. purchaseProduct takes a product ID and the same success/error callbacks. For Android in-app products, purchaseProduct needs an optional third parameter — the module notes you can use the package system to avoid that. The exact code is preserved in the accompanying code module and should be treated as the authoritative contract.

Cancellation versus error

The callbacks separate two outcomes that are easy to conflate. A user cancelling is not a failure — it is a deliberate choice and should not be logged or surfaced as an error. An actual error means the purchase did not complete for another reason and needs handling. Keeping these distinct avoids polluting error metrics and avoids showing alarming messages to users who simply changed their mind.

Example: unlocking a pro entitlement

Suppose your app has an entitlement identifier for pro content. After a successful purchasePackage call, you check whether that entitlement is active in the returned purchaser info. If it is, unlock the content; if the user cancelled, do nothing; if there was an error, show a retry path. The same pattern works for purchaseProduct, with the Android in-app product caveat noted above.

ConfigureTargetTest

Reporting and customer management

The vendor's dashboard is aimed at answering three practical questions: which plans and segments actually earn, where churn concentrates, and what a specific customer's history looks like when support needs to debug. It exposes key metrics with filters and segments, charts for revenue, churn, and retention, and a per-customer timeline of purchases and active subscriptions. Support can grant promotional subscriptions from the dashboard rather than issuing a promo code, subject to the owner-confirmed promotional policy. Campaign creative, keyword, and referral data can be filtered to see what drives conversion and lifetime value.

Integrations and data flow

The value of a purchase event depends on where it lands. The vendor routes events such as trial starts, renewals, cancellations, and billing issues to analytics, marketing, support, and data tools, and lets you filter attribution and campaign data by media source, creative, ad group, campaign, and keyword. Normalized cross-platform event data can be delivered to cloud storage, and webhooks notify you of key events in real time. Before adopting, map each downstream tool you rely on to the event it needs, so you can confirm the integration covers that event rather than assuming it does.

Identity and cross-platform entitlements

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 regardless of which device or platform they purchased on. The practical test is whether a user who buys on one platform sees the same entitlement on another without a separate purchase — if that consistency matters to your app, this is the capability to verify first.

Ready to grow?

The vendor's overview states that its full feature suite comes standard and that getting started is free, with a sales contact path for teams that need more. Those plan and pricing terms are owner-confirmed: check the current pricing page and sales contact before relying on any specific free-tier or plan guarantee. To begin, use the start-for-free signup or the talk-to-sales link below.

ConfigureTargetTest

Frequently asked questions

Do I need to run my own backend for Cordova in-app purchases?

The vendor describes the managed layer as letting you add purchases without managing servers or writing backend code: the SDK fetches products, makes purchases, and checks subscription status, while the dashboard hosts product configuration and reporting. Confirm current account and plan terms with the owner before relying on this.

What is the difference between purchasePackage and purchaseProduct?

purchasePackage takes a package and returns a product identifier plus purchaser info. purchaseProduct takes a product ID and the same callbacks. For Android in-app products, purchaseProduct needs an optional third parameter; using packages avoids that requirement.

How should I handle a user cancelling a purchase?

Treat cancellation as a deliberate user choice, not an error. The error callback exposes a userCancelled flag so you can branch: unlock on success, do nothing on cancel, and show a retry path on a real error.

Can I change products and pricing without a new app release?

The vendor describes products and pricing as manageable remotely from the dashboard, intended to avoid long release cycles for those changes. Confirm current dashboard capabilities under your account.

What reporting is available?

The vendor describes key metrics with filters and segments, charts for revenue, churn, and retention, and a customer timeline of purchases and active subscriptions. Support can also grant promotional subscriptions directly, subject to the owner-confirmed promotional policy.