React Native内购开发咨询：订阅支付验证与Apple/Google Pay模块推荐

Hey there! Let's tackle your questions about subscription payment verification and reliable payment modules for your React Native + ExpoKit drinking game app. I've got you covered with practical, production-ready advice.

Let's break down each option you mentioned, along with their pros, cons, and real-world use cases:

AsyncStorage (Local Storage) #

• What it is: A simple key-value store for local device storage.
• Pros: Super easy to implement, no backend required—great for quick prototypes or mocking subscription flows.
• Cons: Extremely unsafe for production. Users can easily modify local storage (via jailbreaking/rooting or debug tools) to fake an active subscription status. Never rely on this as your sole verification method.
• Best use: Only as a temporary cache to avoid frequent API calls, but always cross-check with a backend or third-party service before unlocking premium features.

Self-Built Backend #

• What it is: Your own server that handles payment webhooks, stores user subscription data, and exposes an API for your app to verify status.
• Pros: Full control over your data and business logic. You can customize verification flows to fit your app's unique needs (like linking subscriptions to game progress).
• Cons: Requires backend development and ongoing maintenance—you'll need to handle webhook events from Stripe/Apple/Google (successful payments, subscription cancellations, failed renewals), secure data storage, and API endpoint security.
• Best use: If you already have backend infrastructure or need custom logic that third-party services can't provide.

Stripe as Your "Backend" (Highly Recommended) #

• What it is: Leverage Stripe's built-in Subscription API and webhooks to manage subscription statuses, without building a full custom backend.
• How it works:
  1. When a user signs up for a subscription, Stripe creates a subscription object tied to their customer ID.
  2. Your app stores the customer ID securely (use encrypted storage, not plain AsyncStorage).
  3. To verify status, your app sends the customer ID to a lightweight backend endpoint (you still need a tiny server here to avoid exposing your Stripe secret key publicly) that calls Stripe's retrieveSubscription API.
  4. Stripe returns the current subscription status (active, canceled, expired, etc.), which your backend relays back to the app.
• Pros:
  • Stripe handles all subscription lifecycle management: auto-renewals, payment retries, dunning (recovering failed payments), and status updates.
  • Webhooks notify you of status changes, so you can update your app's state in real-time.
  • Minimal backend code needed—just a few endpoints to proxy Stripe API calls.
• Cons: You still need a small server to handle Stripe API calls (never call Stripe directly from the frontend with your secret key).
• Best use: 90% of cases where you don't need custom backend logic. This is the most secure and low-maintenance option for subscription verification.

I feel your pain with the modules you've tested—many community-maintained packages fall behind on React Native/ExpoKit compatibility. Here's the most reliable, future-proof option:

Stripe React Native SDK (Official) #

• Why it's the best: It's maintained directly by Stripe, so it's always up-to-date with the latest React Native, ExpoKit, Apple Pay, and Google Pay changes. No more struggling with deprecated or unmaintained community packages.
• Compatibility: Works seamlessly with ExpoKit (you can link it as a native dependency since ExpoKit allows adding custom native code).
• Key features:
  • Full support for Apple Pay (including setup for recurring subscriptions) and Google Pay.
  • Built-in components for payment sheets that handle card inputs, Apple/Google Pay buttons, and error handling out of the box.
  • Direct integration with Stripe's Subscription API, so you can create and manage subscriptions directly from the app.
• Why your past attempts failed:
  • Tipsi-stripe is no longer actively maintained, so it's likely incompatible with newer React Native/ExpoKit versions.
  • React-native-payments has been deprecated for years—avoid it entirely.
• Quick setup steps:
  1. Install the SDK via npm/yarn.
  2. Configure Apple Pay: Register a Merchant ID in the Apple Developer Portal, enable Apple Pay for your app, and add the necessary entitlements to your ExpoKit project.
  3. Configure Google Pay: Set up a Google Pay Merchant Account, enable the Google Pay API, and add the required metadata to your Android manifest.
  4. Follow Stripe's documentation to implement the subscription flow—create a Payment Intent or Setup Intent, present the payment sheet, and confirm the subscription.

Important Final Notes #

• Never verify subscriptions solely on the frontend: Even if you use Stripe, always proxy API calls through a backend to keep your secret key secure.
• Test thoroughly: Use Stripe's test mode to simulate subscription renewals, failures, and cancellations before launching.
• Follow platform guidelines: Apple and Google have strict rules for subscription apps—make sure your app complies with their policies (e.g., clear pricing information, easy cancellation options).

内容的提问来源于stack exchange，提问作者Kérian Pelat