flutter-in-app-purchases
Use for App Store and Google Play billing in Flutter, including store products, verified transactions, entitlements, subscriptions, restoration, and sandbox testing.
How do I install this agent skill?
npx skills add https://github.com/thienqo/flutter-skills --skill flutter-in-app-purchasesIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides security-focused guidelines for implementing Flutter In-App Purchases, emphasizing backend verification and transaction safety. No malicious behaviors or risks were identified.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Flutter In-App Purchases
Model store billing as an asynchronous reconciliation system, not a button callback. Preserve the project's current store package, subscription service, backend, account model, and state management unless migration is explicitly requested.
Do not create products, change pricing, upload builds, or mutate live store configuration without explicit authorization.
Preflight
Read pubspec.yaml, SDK constraints, supported platforms, store package and native configuration, product identifiers, purchase listener ownership, entitlement source of truth, backend verification, authentication, persistence, tests, flavors, and sandbox setup. Distinguish consumables, non-consumables, and subscriptions before editing the flow.
Keep three concepts separate:
- Store catalog: products, localized price, availability, offers, and store metadata.
- Transaction: pending, purchased, restored, cancelled, failed, consumed, acknowledged, or finished as supported by the store.
- Entitlement: the product capability the application currently grants to an account or device.
Never grant an entitlement from a button tap, client assertion, unverified payload, or pending transaction. Persist verified transaction identity, deliver entitlements idempotently, and follow the store and product-specific ordering for acknowledgement, consumption, or finish.
Load references conditionally
- Read purchase lifecycle and entitlements for listener ownership, verification, idempotency, pending transactions, acknowledgement, consumption, and account attribution.
- Read subscriptions and restoration for renewals, grace and hold states, expiration, restore or reconcile flows, upgrades, downgrades, and account switching.
- Read store testing and release for sandbox accounts, product readiness, interrupted flows, platform matrices, and release evidence.
Boundaries
flutter-payments-checkoutowns order payments through external gateways for physical goods or services delivered outside the app.flutter-authenticationowns account sign-in and session lifecycle; this skill binds verified transactions to the correct account and prevents entitlement leakage during account switching.flutter-networkingowns generic transport; this skill owns store and entitlement protocol semantics.flutter-persistenceowns durable local storage; cached entitlement state must expose freshness and never override authoritative revocation.flutter-securityowns broad threat review; this skill requires trusted verification and minimizes purchase-token exposure.flutter-product-analyticsmay observe purchase funnel events but must not become the entitlement source of truth.flutter-build-releaseowns signed application artifacts and uploads. Store publication remains an explicit external action.
Verification
Use fakes for deterministic state-machine tests and store sandbox or test tracks for end-to-end evidence. Cover success, cancellation, failure, pending completion after restart, duplicates, recovery between delivery and the store operation in the selected flow, restore, account switching, offline reconciliation, subscription state changes, and unavailable products.
For sandbox-readiness work, do not stop at a scenario checklist. Explicitly require inspection of application and bundle identifiers, flavors and environments, Android and Apple signing, entitlements or manifests, existing store products, test accounts, and backend routing before changing configuration. Provide concrete reproducible cases with preconditions, actions and interruption point, expected store and entitlement states, acknowledgement or finish outcome, and observable pass/fail evidence. Include at least one interrupted purchase and one restore or reconciliation case when those flows are in scope.
State which store, product type, account mode, platform, and backend path were exercised. A successful purchase sheet or client callback alone does not prove verification, entitlement delivery, acknowledgement, cross-device restoration, or renewal handling.
Sources
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/thienqo/flutter-skills/flutter-in-app-purchases">View flutter-in-app-purchases on skillZs</a>