Skip to content
InfluToDocs

Purchases

Choose a purchase validation path

InfluTo verifies every purchase before it pays commission — through your RevenueCat webhook or directly with Apple and Google. How to choose, and why never both.

InfluTo never pays commission on a purchase it hasn't verified with the store. You connect that verification in one of two ways, chosen per platform in Settings → Validation: RevenueCat, or store-direct. Use exactly one per platform — two paths would report every purchase twice.

The short answer

  • You use RevenueCat → RevenueCat. Nothing to call at purchase time; RevenueCat sends InfluTo every purchase, renewal and refund.
  • You don't use RevenueCat → Store-direct. The SDK sends the store's signed proof of each purchase, and InfluTo checks it with Apple or Google.

Side by side

RevenueCat Store-direct
You need A RevenueCat project for the app An App Store Server API key (.p8) and/or a Google Play service account
How InfluTo hears about purchases RevenueCat's webhook, server to server The SDK reports each purchase; InfluTo re-checks subscriptions with the stores every hour
Code in your app Let the SDK tag the RevenueCat subscriber with the referral code Usually none — automatic capture, or reportPurchase if you prefer
Setup in the dashboard Setup & SDK → Webhook: connect automatically with a RevenueCat v2 secret key, or paste the URL and secret into RevenueCat Settings → Validation: upload the credentials and wait for the green check
Renewals and cancellations From RevenueCat events From the stores (hourly check; Google also via real-time notifications)
Refunds reversed Yes, from RevenueCat refund events Subscriptions on both stores and Google Play one-time purchases

Mixing platforms

The choice is per platform. An app can validate iOS directly with Apple and Android through RevenueCat, for example. The SDK learns the setting from InfluTo at startup, so automatic purchase capture only runs on platforms set to store-direct.

Testing either path

Sandbox and TestFlight purchases flow through the same pipeline and show up in Real-Time Events, but they never move money or change stats. How to run a full test: Verify the integration.