Fictura
Stores

Google Play

Fictura reads Google Play's refunds and chargebacks. Here's exactly what Android support does and doesn't include today.

Honest scope

Fictura reads one thing from Google Play: refunds and chargebacks, below. There is no product management, no Play billing webhooks (RTDN) and no Play-side configuration. Android billing events reach Fictura the same way iOS ones do — through RevenueCat webhooks, which report PLAY_STORE purchases like any other.

Refunds and chargebacks

Dashboard → Tools → Google Play. RevenueCat reports a Google refund only when it also removed access, and doesn't report chargebacks at all, so this reads them from Google directly. It keeps your revenue right, and takes back affiliate commission paid on that sale.

You need a robot key invited in Play Console with View app information and View financial data, and your app's package name.

Turning it off asks first, because Google only keeps the last 30 days. When you turn it back on, it catches up that far. Anything older is lost.

What Android gets today

  • The SDK. @fictura/sdk is React Native — paywalls, onboarding, events, error tracking and config refresh all run identically on Android. Device identity uses the SSAID via expo-application.
  • App Links. The links platform serves /.well-known/assetlinks.json for your domains — add your android_package and SHA-256 signing fingerprints on Dashboard → Links → Domains and Android deep links verify properly.
  • Exact install attribution. A link with a Play Store URL rides the Play Install Referrer, so creator and campaign installs on Android match exactly (gp_referrer), not by a modelled guess. The Meta Install Referrer adds exact matches for Meta ads.
  • Web checkout targeting can include Android, though the default is iOS-only — Play billing's ~4-point spread rarely justifies the flow change (see eligibility).
  • Store numbers. Google Play downloads, revenue, ratings and reviews come through Appfigures, not from the Play Console directly.

Push on Android works through the same Expo token flow as iOS — registerForPush() and done.

On this page