Ask Kabbalist

You land in Delhi before dawn, connecting onward to Singapore, and the officer hands your passport back without reaching for a stamp. The camera above the desk already knows your face. Nobody sat you down and explained how to use DigiYatra, and at that terminal it has stopped being a choice you get to make. The queue moves faster. Your record of having been there moves somewhere you cannot see.

Why DigiYatra, and why the rush?

India's Bureau of Immigration stopped stamping international boarding passes on 1 September 2026, so the paper trail a traveller once carried home now lives entirely inside an app and an airline database. That is the real story, and it broke a week ago with almost no coverage joining the two changes together.

Two things happened this year, three months apart, and they only make sense read as one move. First the face scan became the default way through the terminal at the busiest international gateways. Then the ink stamp, the one artefact that proved you physically left and re-entered the country, was withdrawn. Visa officers asked for that stamp. So did tax officers, and employers running background checks. Now the answer is a PDF and a database query.

What is DigiYatra actually doing at the gate?

It matches a live camera image against an encrypted template built from your Aadhaar-verified selfie, then releases your boarding record to the checkpoint. Outlook Traveller reported the operational detail plainly: the selfie and the boarding pass go into the app before you reach the airport, and the gate does the rest. There is no counter and no second look. This is the same pattern as India's Android developer verification rules, where a convenience is announced first and the compulsion arrives later, quietly, in a circular.

The programme's governance is the part worth sitting with. DigiYatra Foundation is a private not-for-profit, and because it is private it sits outside the Right to Information Act, 2005. So the body holding a biometric template of every international flyer through four major airports cannot be asked, by an ordinary citizen, how long it keeps that template. The Internet Freedom Foundation has raised exactly this: privacy, surveillance, exclusion errors, and no institutional accountability. A Kerala High Court PIL alleging commercial misuse of passenger data is still live. None of that stopped the mandate.

That last figure is the one that should shape how you treat the app. It was measured while enrolment was still sold as voluntary, and it describes people who handed over a document at a counter and were signed into a biometric programme without registering that it had happened. A system with that much accidental enrolment in its optional phase does not suddenly grow better consent hygiene once it becomes compulsory. It just stops needing consent.

How to Use DigiYatra: What Each Step Demands

You enrol once in the DigiYatra app with an Aadhaar-verified selfie, attach each boarding pass to that profile before you travel, then walk to the e-gate where a live camera matches you against the stored template and opens the checkpoint.

The steps are simple. What sits behind them is not, and the table below is the version nobody prints on the airport signage. Read the Identity row first if you hold a foreign passport, and the Paper trail row before your next visa application.

The Ownership row is the one that changes how you should read every reassurance about deletion. A shareholding split between the state airports authority and the operators it regulates is a commercial arrangement wearing safeguard language, and the entity it created answers to neither a regulator nor a citizen with an RTI form. The 15-minute buffer in the Gate fallback row is not published anywhere either. It comes from the plain logic of the system: if the automated lane rejects you, you rejoin a manual queue that was sized for fewer people than it used to hold.

Can you register for DigiYatra without a boarding pass?

You can create the profile without one, since enrolment needs only the Aadhaar-verified selfie, but the boarding pass has to be added to that profile for every single trip before the gate hardware will recognise you and let you through.

Which means the app is two systems wearing one name. The identity half is permanent and lives with a private foundation. The travel half is per-journey and expires. Most of the friction people report sits in the second half: a pass added too late, an airline that issues the document only at the counter, a name spelt differently on the ticket and the Aadhaar record. The rollout is fine, mostly, if your face matches on the first attempt.

The camera is the least interesting part of this. What nobody has published is a retention window for the biometric template, and the body holding it is structurally unanswerable to the people it holds it on. That is a stance, not a finding, and it is the same gap that shows up whenever the rules land before the plumbing does, exactly as they did with AI shopping agents and India's missing payment rail.

• Download and store the e-boarding pass as a PDF the moment it arrives, because the immigration stamp that used to prove your trip no longer exists.
• Check that the name on your ticket matches your Aadhaar record character for character, including initials, before you add the pass.
• Ask for the manual counter if you do not want the scan. It still exists at these terminals for people the automated lane rejects, and staff will point you to it if you insist.
• Keep a printed pass in your bag. It looks absurd next to a face scanner, and it is still the cheapest insurance you can carry.

Do one thing this week. Open your last international e-boarding pass, save it somewhere that survives a lost phone, and do the same for every trip from here. The face scan is settled and arguing with it at the gate will only cost you your connection. The paperwork is what you can still control, and the day a consulate or a tax officer asks you to prove you left the country, that saved file is the whole of your answer.

You tell your AI browser to find the cheapest 65-inch TV under Rs 60,000 and buy it. It finds one in about eleven seconds. Then it stops. Not because Amazon blocked it, and not because a judge did. It stops because nothing in India's payment plumbing knows how to let a piece of software hold your wallet.

Why It Matters

On 9 March 2026, a federal judge in the Northern District of California ordered Perplexity to keep its Comet browser off Amazon. On 4 August the Ninth Circuit vacated that order in Amazon v. Perplexity, No. 26-1444, and the reasoning is the part worth keeping. Where the AI company's servers never speak to the retailer directly, and every request routes through the shopper's own machine, the panel held that it is the shopper who "accessed" Amazon's computers under the Computer Fraud and Abuse Act. Not the software vendor.

Read the coverage and you would think agentic shopping just won outright. It didn't, quite. The panel left Amazon's contract and tort claims standing, terms-of-service breach included, and went out of its way to say it was not foreclosing liability for agents with greater autonomy, or for designs where the vendor's own servers hit the retailer. So the decision protects one narrow shape: a local agent driving your session, on your hardware, with your login. Build it any other way and you are back in front of a judge with worse facts. There is a second thing the ruling did not do. It did not stop Amazon from blocking agents by other means. Nothing in the opinion obliges a retailer to serve a request it can detect and refuse, and detection is a product problem rather than a legal one. A platform that loses on the statute can still rate-limit, fingerprint, challenge or quietly terminate the account, and none of that needs a judge's permission.

None of which is why your agent stalls at checkout in Bengaluru. The Reserve Bank of India's Digital Payments E-Mandate Framework, in force since 21 April 2026, requires your issuer to notify you at least 24 hours before any recurring debit lands. Sit with that for a second, with an agent in mind. The one rail built for automatic payments comes with a mandatory day of warning attached. It is the same instinct now shaping how platforms decide what software may act on your behalf, applied to money instead of apps, and it lands harder here. E-mandates were designed around a repeating charge whose amount and merchant you already know, on a date fixed well in advance. An agent's entire value is the opposite of that: an unpredictable amount, at a merchant you have never used, on the day it finally finds the thing. The rail and the use case were built for different worlds.

Four numbers frame the standoff: how long the ban actually held, what the retailer stands to lose, how fast agent buying is climbing, and how much of the open web is already machine traffic. Together they explain why Amazon spent five months fighting this, and why losing once has not ended it.

Take the order growth. Shopify's second-quarter 2026 earnings set it against a figure that matters more: 75% of AI-attributed purchases fell outside the company's top hundred product categories. Agents are not winning the things people already know how to buy. They are finding the awkward, badly-named, three-pages-deep thing you would have given up on by the second search.

Three Routes, One That Pays

So where does this leave an Indian shopper who actually wants the thing? Three routes exist right now, and the gap between them is not about how clever the model is. It is about who holds the authority to move money and who answers when the money moves wrongly. The third column deserves a note, because it is the one people picture when they hear the phrase. A delegated-payment agent is not an agent holding your password. It is an agent holding its own credential, one your bank recognises as separate from you, spending inside limits you fixed beforehand, leaving a trail that records which instruction came from a human and which from software. That is a great deal of new infrastructure, and not one piece of it is a model-quality problem.

Notice what the table does not contain. There is no column where an agent both chooses freely across the whole market and pays without you. That combination is the product everyone is describing, and in India it currently exists nowhere. The court fight was about the first half. The second half is a payments question, and payments questions in this country are settled by the regulator, not by the Ninth Circuit. It is tempting to read all this as a delay, as though the parts are on order and the launch is a scheduling matter. That reading is too generous. Granting payment authority to a non-human actor is a genuinely hard design question, and the countries working on it are not converging on a shared answer.

Friction Points

India does have an answer in progress. Business Standard reported in July 2026, citing industry sources, that the National Payments Corporation of India is building a Unified Agent Protocol to authenticate agents and set transaction limits without rebuilding UPI underneath. That is the right shape. It is also, as of today, a reported development rather than an announced product: no official NPCI statement, no timeline, no pilot, no published limits. The protocol is real, or at least the consultation is; the protocol itself is still slideware.

Which brings up the thing that irritates me about the current commentary. Specific per-transaction caps have been circulating as though they were policy. They are not. They come from one writer's proposal about what NPCI ought to do, and they have been repeated until they read like a specification. If you are planning around numbers nobody at the regulator has published, you are planning around fiction, and the correction will be expensive.

Then there is the hole nobody wants to own. An agent buys the wrong size, the wrong variant, the wrong seller. Under a card payment you dispute it. Under an agent-initiated debit, who is the counterparty: you, because a court just said the agent is your hands, or the vendor, whose model picked the listing? Reporting on the protocol work concedes that chargeback and dispute mechanisms will need to evolve. That concession is doing a lot of work. The same framework already obliges the issuer to send a post-transaction notification carrying its grievance redressal details, which tells you plainly how the regulator pictures recourse: a named human at both ends of every debit. An agent-initiated purchase breaks that assumption at the first step, and no amount of protocol design makes the question of who authorised the spend disappear.

• Check where the agent actually runs. If it drives your browser on your machine, the Ninth Circuit's reasoning covers you. If it calls the retailer from a vendor's cloud, that protection was explicitly not extended.
• Read the retailer's terms before you point an agent at it. Contract claims survived this ruling untouched, and account termination needs no court at all.
• Keep the final confirmation yours. The moment you hand over the button, your chargeback story gets harder to tell.
• Treat any agent asking for a standing payment mandate as premature. Nothing in India authorises it yet.

Use an agent to shop, not to pay. Let it hunt and fill the cart, then check the total yourself and press the button with your own thumb. That is not caution for its own sake, it is the only configuration where you keep both the legal cover the Ninth Circuit just described and the dispute rights India's payment rules already give you. Revisit it the day NPCI publishes an actual specification. Until then, the agent works for you right up to checkout, and that is genuinely useful on its own.