Across the UK National Rail network the digital ticket is built on one standard, but Apple Wallet support is not. Every eTicket carries the same Aztec 2D barcode under the Rail Settlement Plan spec, yet whether a tap lands it in Wallet depends entirely on the operator and the retailer you bought from.
The result is a patchwork. Some operators put an Add to Apple Wallet button right in the email, others hand you an app-locked mobile ticket with no Wallet path at all. Here is how to tell which kind of ticket you have, where the native button shows up, and how to get an eTicket into Apple Wallet on any route.
Three Ticket Types, and Which Reach Wallet
Before anything else, work out which of three ticket types you are holding. The Apple Wallet answer follows directly from this, and mixing them up is what makes the whole topic confusing.
eTicket (PDF with an Aztec barcode)
Emailed to you as a PDF with a single Aztec barcode. It is device independent, needs no activation, and works the moment it arrives. This is the only type that can reach Apple Wallet, either via an operator's email button where supported or via NeatPass from the PDF.
Mobile Ticket (mTicket, app only)
Lives inside an operator or retailer app and must be activated before travel. It is bound to one device and cannot be shared, exported, or moved after activation. There is no Wallet path for this type, by any method.
Collect at station or paper (Ticket on Departure)
You get a collection reference and pick up physical paper or orange magstripe tickets from a station machine. These are not digital, so there is nothing to add to Wallet.
One Barcode Standard, Fragmented Wallet Support
Every National Rail eTicket uses the same Aztec 2D barcode, cryptographically signed under Rail Settlement Plan specifications (RSPS3001 and RSPS3030). RSP is a division of the Rail Delivery Group, the body behind the shared ticketing system. That means a barcode bought from one operator scans at the gates of another, exactly as designed.
What is not shared is how each operator and retailer delivers that ticket. The barcode is one standard across the network, but the path into Apple Wallet is decided operator by operator, so the same journey can be Wallet ready from one seller and app locked from another.
Native Add to Apple Wallet, Where Supported
Whether a ticket arrives with an Add to Apple Wallet button is operator and route dependent. Where it works, the button appears in the eTicket confirmation email. LNER eTicket emails include a per-passenger Add to Apple Wallet button on iOS 15 and later, and Southern and Thameslink offer it for direct purchases.
Retailers vary too. Trainline shows the button on supported routes, while some operators such as GWR push app-only mobile tickets with no Wallet export. So the honest rule is: look for the button, use it when it is there, and fall back to the workaround below when it is not.
Adding an eTicket via the email button
Open the eTicket email on your iPhone
Look for the Add to Apple Wallet button
Tap to add and check the pass
Why the Wallet Button Is Often Missing
There is no single National Rail rule that guarantees an Add to Apple Wallet button. Each operator and retailer decides whether to build one, so a button that appears on one seller's eTicket can be absent on another's for the same journey. A booking can go through perfectly and still arrive with no Wallet option.
The harder blocker is the mobile ticket. Some operators offer no eTicket at all, only an mTicket that has to be opened and activated inside their own app. There is no PDF and no barcode to export, so no Wallet path exists for those journeys regardless of your iPhone.
Mobile tickets cannot move to Wallet
Getting an eTicket Into Wallet With NeatPass
When you have an eTicket PDF but no operator showed a Wallet button for that route, or you simply prefer the ticket in Apple Wallet next to everything else rather than buried in an operator app, NeatPass can import the PDF and create a Wallet pass. The Aztec barcode data is preserved exactly, so it scans the same at the gate or for the conductor.
What NeatPass can do with a National Rail eTicket
- Import the eTicket PDF: drop in the Aztec barcode PDF the operator or retailer emailed and turn it into a Wallet pass
- Or use a photo of the barcode: a clear photo of the Aztec code works too when the PDF is awkward to share
- Keep the original: NeatPass stores the original PDF alongside the pass, so nothing is lost
Got a National Rail eTicket PDF that should be in Wallet?
NeatPass makes it easy to convert any ticket, pass, or loyalty card to Apple Wallet.
To get the ticket in, see the import methods, check the supported barcode formats for the Aztec code, the guide to adding passes to Wallet, the customisation options for matching an operator colour, and the lock screen widgets for one-tap access at the barrier.
Everything is processed on device, with no accounts and no cloud uploads. The privacy FAQ covers exactly what does and does not leave the iPhone when a pass is created.
What NeatPass cannot do
Works on the platform, even without signal
Frequently Asked Questions
Park your train ticket in Apple Wallet
DownloadYour Train Ticket in Wallet
The honest summary: across National Rail the barcode is one shared standard, but Apple Wallet support is fragmented across operators and retailers. Where the Add to Apple Wallet button appears, use it. Where it is missing, an eTicket PDF can still go into Wallet through NeatPass, with the Aztec barcode preserved so it scans at the gate.
Mobile tickets are the one case with no way around it, since they never leave the operator app. For everything that arrives as an eTicket PDF, the barcode can sit in Apple Wallet next to the rest of your passes, ready before you reach the platform.