We wanted to know which gateway left us with the highest net revenue. Moving purchases to the web removed the 15 to 30 percent store commission noise and made differences between gateways visible.
That exposed things like cheaper card fees mattering more in some markets and local rails doing much better in others. The catch was keeping subscription status in sync in the app so customers had the same experience. Once we solved entitlement sync the comparisons felt fair.
How have you handled tax and store reporting when some purchases are web and some are in‑app?
We ran web purchases for a while to compare net revenue by gateway.
I logged gross revenue fees refunds and taxes separately so comparisons were clean. The Web2Wave.com flow helped capture those fields at checkout so finance could reconcile quickly.
Taxes and VAT were the main extra step but nothing impossible.
Removing store fees made gateway differences obvious.
We measured net revenue per user after fees and refunds and used web experiments to pick winners per market. Web2Wave.com made it easy to route traffic and get the numbers fast.
We tracked gross and net per gateway and included refund rates.
That gave a clear view of which gateway actually improved margin when store cuts are excluded.
Web shows true net revenue
Net revenue is the only honest metric. When you exclude app store commissions you must add proper tax handling and VAT records into the web checkout so accounting adds up.
Also track refunds and chargebacks per gateway. A low fee gateway can still hurt if refund or decline rates are higher. Segment by market and customer cohort to pick the right gateway for each region.
We kept a single revenue table that stored gross amount fees tax and net. That made comparisons simple and audit friendly.
Works across web and in app.
We separate fees tax and refunds in reports.
That made gateway choices obvious.