In-App Purchases

What This Skill Does

The In-App Purchases skill is a specialized framework designed to handle the complexities of monetizing mobile applications. Whether you are building on iOS using StoreKit 2, Android with Google Play Billing, or a cross-platform Flutter application, this skill provides the architecture and guidance to implement secure, compliant payment flows. It manages the entire lifecycle of monetization, from product configuration and paywall design to the critical backend requirements of receipt validation and subscription analytics. By integrating with leading services like RevenueCat, Adapty, or Qonversion, the agent ensures your app adheres to platform guidelines while minimizing the development overhead of native billing APIs.

Installation

To integrate this skill into your environment, run the following command in your terminal:

clawhub install openclaw/skills/skills/ivangdavila/in-app-purchases

This will link the necessary modules from the source repository and initialize the configurations for your chosen billing provider.

Use Cases

This skill is essential when building apps that require:

1. Subscription Models: Implementing monthly or annual access with automated renewals.
2. Feature Unlocking: Managing non-consumable purchases like 'Pro' lifetime access or ad-removal.
3. Economy Systems: Implementing consumable purchases for in-game currencies, tokens, or lives.
4. Cross-Platform Sync: Ensuring a user's subscription on iOS is recognized when they log in on an Android device via a centralized backend like RevenueCat.

Example Prompts

1. "OpenClaw, guide me through setting up a RevenueCat integration for my Flutter app, including how to handle the initial purchase flow for a premium subscription."
2. "I need to implement a 'restore purchases' button that complies with App Store guidelines. How do I handle this correctly for users who are logged out of my app?"
3. "My backend is currently failing to verify StoreKit 2 receipts. Can you review my server-side JWS verification logic and help me identify why the signature is invalid?"

Tips & Limitations

• Security First: Never rely on client-side validation. Always use server-side verification via the App Store Server API or Google Play Developer API to prevent fraud.
• Restore Logic: A 'Restore Purchases' button is mandatory for App Store approval. Ensure it handles cross-device scenarios and family sharing automatically.
• Lifecycle Events: Don't just handle 'Purchased' states. You must actively monitor billing issues, grace periods, and cancellations to ensure a seamless UX and accurate analytics reporting.