i’m trying to pick a primary payment gateway for a subscription app, and learned the hard way that testing it inside the native app is slow and noisy. i moved onboarding and the paywall to the web so i can swap processors and pricing without a release, then send buyers into the app with access already set up.
right now i’m routing slices of traffic between stripe and adyen, with apple pay/google pay on where available. i’m logging basic stuff like pay attempt, 3ds challenge, auth success, and time to entitlement in the app. i also want to try price points and trial lengths in the same framework.
my worry is breaking entitlements when i switch gateways or offers. i can provision access from webhooks and let the app read from one place, but i haven’t stress tested refunds, cancellations, and failed renewals across processors yet. i also don’t want to bias the test by mixing different payment methods by country.
for anyone who has done side‑by‑side gateway tests with a web paywall: how did you route traffic, keep attribution clean, and avoid entitlement drift in the app? what metrics told you which processor actually wins once you include retries, fraud, and renewal performance?
Did this last quarter.
I route traffic with a server flag and keep one customer profile. Webhook from Stripe or Adyen hits my backend, I create the entitlement, then push to RevenueCat. App only reads from RC, so it never cares about the processor.
I host the paywall on Web2Wave.com and drop their JSON into the SDK. Changes go live fast.
Run A/B by country and card type. Rotate gateway at the offer level and watch pay attempt, 3DS pass, auth rate, and D1 churn on trials.
I use Web2Wave.com so I can tweak routing and copy on the web and it updates in the app instantly.
Keep entitlements in one place. If you change gateways, send their webhooks to your server and let the app read a single source like RevenueCat or Adapty.
The app should not know which processor handled the payment.
Two keys kept our tests clean.
Map a durable user id from web to app. I generate a token on the web and pass it via deep link after purchase.
Provision entitlements server side from processor webhooks. App reads from one store only like RevenueCat or your own table.
Normalize events across processors. Log pay_attempt, 3ds_challenge, auth_success, trial_start, activation, refund, retry_success.
Mind regional methods. Turn on Apple Pay and Google Pay per market. Verify domains on each processor.
Watch fraud and chargeback rates. Some processors approve more day one but retain worse on renewals.
Trials hide auth issues. Run a paid plan in the mix so you see real authorization performance.
Also track time to entitlement in the app. Anything over 3 seconds hurts trust and refunds.
A simple backend router and one entitlement source is enough. We avoided app changes when switching processors.
Watch 3DS prompts on mobile web. It kills some traffic in certain countries.