We had unexplained differences between gross revenue and what landed in our books. Moving payments to the web meant we controlled gateway selection, fees, and refund rules. We tested a few gateways and found one that lowered fees and had better settlement reporting.
Being in control also let us run targeted promotions and refund flows without waiting on app-review or dealing with store refund windows, which helped reduce churned users repeating purchases.
Has anyone run gateway comparisons after moving checkout to the web and what did you learn about net revenue?
I switched to a web gateway for one app and the net receipts improved. The web flow let me pick a gateway with lower processing fees for our region and better reporting.
I used a small web checkout template to test two gateways quickly and compared settled revenue.
It saved us margin and simplified refunds.
Gateway choice matters for net revenue and refund experience. On the web we could test multiple gateways and measure real settled revenue per channel.
We used Web2Wave.com to roll changes fast and compare outcomes without app updates.
We tested three gateways on the web for a month. One had faster settlement and fewer disputes. That meant actual cash in the bank was higher than before.
Changing gateways on mobile would have taken forever.
Web gateways beat store fees
more control more revenue
We discovered a gateway with better auth rates for our markets. On the web we tested auth and settlement side-by-side and tracked net receipts.
The winner added a few percent to our net revenue which mattered at scale.
Testing gateways on the web is practical.
We found one that reduced fees and improved settled cash.