#How Paytm opens a page
Paytm is a super app: payments, recharges, travel and shopping sit next to offers and partner services. Many of those partner experiences are Paytm Mini Apps, which Paytm describes as web applications or web URLs opened inside the Paytm Consumer or Business app, with extra abilities through Paytm's JavaScript APIs. In other words, they are web pages running in Paytm's own web view, not in Chrome or Safari.
So if your brand runs an offer inside Paytm, or a Paytm page links to your product, the tap happens inside that web view. Paytm's user agent doesn't name the app, so on its own it looks like any Android web view, or an iPhone web view with no Safari in it. On Android there is one more clue: Android's web view sends an X-Requested-With header with the host app's package name, net.one97.paytm. When that header arrives, the link server names Paytm's browser.
#What a tap gets
On Android, when the header names Paytm, the link server answers with the same page it gives Instagram or Facebook's browser instead of a redirect: an Open in app button carrying the hand-off Chrome would get, plus steps to open the link in the phone's real browser. Newer Android web view versions may stop sending the header; then the tap looks like any web view (the second card) and gets the plain hand-off. Whether Paytm's web view follows either is up to Paytm: web views only pass a hand-off to another app when the host app allows it, and many show an error or stay on the page instead. The third card is the cleaner path. Paytm's mini-app platform has an openInBrowser API that passes control to the phone's browser (Paytm documents it for files such as PDFs); once the link is in Chrome, it gets the normal hand-off. Your app opens at the deep link, or Google Play opens with the link in the install referrer so the right screen is waiting after install.
On iPhone, an embedded web view can't run our Get the app page, so the link server sends the tap directly to the App Store, which shows Open when the app is installed. Strait's Universal Links were tested on a real iPhone in October 2026, though not yet from inside Paytm; install matching after an App Store install is opt-in.
We haven't recorded a Paytm test on a real phone. Treat the cards as what the server sends, and test the real path before a campaign.
#Counting Paytm taps
When the tap comes from Paytm's web view with the header, or Android reports the Paytm app as the referrer, Analytics files it under paytm. A web view tap with neither counts as direct. Put utm_source=paytm and a utm_campaign on every link you place in Paytm so these taps get their own row.
#Making Paytm placements work
- Make the landing page complete on its own. Some people will stay inside Paytm, so let them see the offer and its terms without needing your app.
- Use a clear Open in app button rather than an automatic redirect. A tap is what lets most web views pass a link on.
- Put the offer code in the link's destination (
/offer/DIWALI50), so a user who installs from Paytm still sees the offer on first open.
- If you build a Paytm Mini App yourself, use Paytm's documented APIs to leave the web view, and test on the Paytm app version your users run.
#Sources and how we checked
The cards are the link server's real decisions for each user agent; the first card also carries the X-Requested-With: net.one97.paytm header. That header is standard Android web view behaviour, but we haven't checked on a real phone that Paytm's current app sends it. Paytm's description of Mini Apps is from its developer docs, Paytm Mini Apps overview, and the browser hand-off is its openInBrowser JS API. How Paytm's own pages open external links isn't documented and can change between app versions.