Rail tickets in Apple Wallet with custom passes in iOS 27

[James H]

The newly released iOS 27 includes the function to scan a barcode to create an Apple Wallet pass.

https://www.tapsmart.com/tips-and-tricks/create-a-pass-wallet/

Point your camera at the card’s barcode or QR code and Wallet copies it directly onto a new digital pass – no typing required for that part. Note that it also works from an image or screenshot – hit the Photos button in the corner to grab something from your camera roll. This is handy if you already have the code digitized in an email or another app and just want to move it to Wallet.

On an iPhone 17 Pro, 17 Pro Max, or Air, Wallet goes a step further: Visual Intelligence tries to read the printed text on the card too, pre-filling the name, location, and other details for you to check over before saving. On other Apple Intelligence-capable iPhones (15 Pro and later), you get the barcode scan but not the automatic text fill-in – you’ll fill in the rest of the fields yourself.

Anyone tried this with e-tickets from retailers that don't support automatic Apple Wallet pass creation? And what about PlusBus?
Any pitfalls?

Will guards and RPIs quibble if shown something not in the official format, even if the barcode is fine? Place your bets for the first case in disputes & prosecutions.

 

[mmh]

The newly released iOS 27 includes the function to scan a barcode to create an Apple Wallet pass.

https://www.tapsmart.com/tips-and-tricks/create-a-pass-wallet/


Anyone tried this with e-tickets from retailers that don't support automatic Apple Wallet pass creation? And what about PlusBus?
Any pitfalls?

Will guards and RPIs quibble if shown something not in the official format, even if the barcode is fine? Place your bets for the first case in disputes & prosecutions.

No, they won't quibble. Android has done this for a long time. If the code scans, nobody cares what the app or anything else around it looks like.

 

[Mattplans]

No, they won't quibble. Android has done this for a long time.

Really? We've seen plenty of cases on here where staff suggested a ticket was invalid because it was a screenshot of the QR (Aztec) code as opposed to the "official" pdf or other delivery method.

If the code scans, nobody cares what the app or anything else around it looks like.

Also seen many cases where members of staff incorrectly interpret the fields around the QR code. https://www.railforums.co.uk/thread...anytime-ticket-tied-to-specific-train.306413/ In this case, numerous members of southeastern staff incorrectly claim that an anytime ticket was only valid on a certain train.

 

[alistairlees]

The newly released iOS 27 includes the function to scan a barcode to create an Apple Wallet pass.

https://www.tapsmart.com/tips-and-tricks/create-a-pass-wallet/


Anyone tried this with e-tickets from retailers that don't support automatic Apple Wallet pass creation? And what about PlusBus?
Any pitfalls?

Will guards and RPIs quibble if shown something not in the official format, even if the barcode is fine? Place your bets for the first case in disputes & prosecutions.

Does it work with Aztec barcodes? QR codes are not used for rail tickets.

 

[mmh]

Really? We've seen plenty of cases on here where staff suggested a ticket was invalid because it was a screenshot of the QR (Aztec) code as opposed to the "official" pdf or other delivery method.

Implied contract terms - ticket delivery methods

Hi, In short, I purchased several tickets from a TOC. The TOC advertised that tickets could be added to Apple wallet, and this influenced my decision to purchase from them and thus became an implied contract term The Apple Wallet versions their app created for me were invalid as some displayed...

www.railforums.co.uk

CrossCountry demonstrates "astonishing contempt for fare-paying passengers"

In today's Guardian, https://www.theguardian.com/money/2019/jun/29/passenger-threatened-with-court-for-using-screenshot-of-e-ticket, is a report of a passenger attempting to use a screenshot of an "e-ticket" with a perfectly readable bar code, but being effectively compelled to pay £161.30 to...

www.railforums.co.uk

Also seen many cases where members of staff incorrectly interpret the fields around the QR code. https://www.railforums.co.uk/thread...anytime-ticket-tied-to-specific-train.306413/ In this case, numerous members of southeastern staff incorrectly claim that an anytime ticket was only valid on a certain train.

The first of those posts is a very old case where a retailer messed up, not a ticket checker.

The second post is a forum member stating something which isn't (and has never been) true.

 

[Wallsendmag]

Does it work with Aztec barcodes? QR codes are not used for rail tickets.

I'll have a look now and try scanning one, seems to work although I wouldn't rely on it as I'm fairly sure you will run into problems onboard as the format is nothing like the offical template

 

[James H]

I created a pass using my most recent Aztec code but the resulting barcode in Apple Wallet looks different to the one in the pdf

 

[Mattplans]

The first of those posts is a very old case where a retailer messed up, not a ticket checker.

The second post is a forum member stating something which isn't (and has never been) true.

In this case, the member (although they didn't return to answer further questions by the forum) that they were issued a penalty fare notice because their partner screenshotted a ticket and then sent it to them.
In this case, reported in the media, CrossCountry reject a ticket because the customer screenshotted it. (Also here: https://www.railforums.co.uk/threads/pdf-tickets-screenshots-acceptable.256319/#post-6459457)

I think it's pretty clear that rail staff have done quite a bit more than 'quibble' about it. Making up imaginary rules yet again such as “A photo of a ticket is not a valid ticket held.” (which Transport Investigations, acting on behalf of XC, in the aforementioned case claimed to a customer)

It says enough that the advice in numerous threads on the topic is just to use the PDF in case you run into a troublesome member of staff.
So, I'm not sure it can be said with such certainty that staff won't react to being shown something in a different format. They have a poor track record for this and it's reasonable to assume there might be some resistance as a result

 

[kacper]

What about people using this for railcards

 

[blimmo]

I have used a 3rd party ticket wallet (on android) to display an e-ticket. The app rendered the ticket significantly differently to Google wallet. On my first train (Greater Anglia) the inspector was unable to scan it but accepted it anyway! Turns out the app had a bug that was rendering the Aztec differently. The bug has now been fixed and I have used it regularly with no problems.

== Doublepost prevention - post automatically merged: 15 Sep 2026 ==

What about people using this for railcards

Railcards have regularly changing barcodes (and a photo for that matter)

 

[James H]

On a related note, I have both an Android phone and and iPhone and I've had difficulty with the automatically generated Flixbus tickets that Gmail puts in Google Wallet, with the code not scanning successfully.

 

[MrJeeves]

Railcards have regularly changing barcodes

No, they don't.

 

[blimmo]

No, they don't.

Ah I was confused by the animated logo (?) I've seen on some of them I think. Makes the argument against providing them as pdfs even weaker...

 

[Buzby]

the format is nothing like the offical template

So? My Aztec code appears on my watch in isolation - no ‘template’ evident (or required). After hundreds of scans only two instances of a hiccup. The first on XC when the staffer (sans reader) wanted to see the ‘real’ ticket, and I challenged her that it was as real as she was going to get. When I enquired where her scanner was, she just moved on. The other, on ScotRail the guy explained he hadn’t seen many watches being used… then went on to say if it was that clever, where was my Railcard? I fished it out and he went away happy (first time ever a ScotRail bod asked to see it) - I must be looking less decrepit these days!

 

[CyrusWuff]

Ah I was confused by the animated logo (?) I've seen on some of them I think. Makes the argument against providing them as pdfs even weaker...

The logo on Digital Railcards is indeed animated, with device sensors as an input. If one is presented without that animation, it should be rejected.

Another reason for RDG requiring Digital Railcards to be shown in an app is so they can be cancelled if required.

 

[MrJeeves]

Another reason for RDG requiring Digital Railcards to be shown in an app is so they can be cancelled if required.

Alternatively, they could be scanned instead!

 

[CyrusWuff]

Alternatively, they could be scanned instead!

That would also help. Though cancellation messages can take a while to be distributed.

I look forward to the Railcard Validation Service breaking everything.

 

[81A]

Would this work for PRT (Paper Roll Tickets)? And would it be accepted (I think some tickets are issued on PRT and not available as E-tickets as PRT is "security paper", which obviously is little use if the ticket is presented digitally)...

 

[davp]

Would this work for PRT (Paper Roll Tickets)? And would it be accepted (I think some tickets are issued on PRT and not available as E-tickets as PRT is "security paper", which obviously is little use if the ticket is presented digitally)...

Yes, I can create a pass based on PRT.

However it’s a faff as I had to create it manually and it otherwise looks nothing like a rail ticket. It can't create it automatically yet as it requires activating (more) Siri intelligence first. Maybe it’ll look better too.

 

[skyhigh]

In this case, the member (although they didn't return to answer further questions by the forum) that they were issued a penalty fare notice because their partner screenshotted a ticket and then sent it to them.
In this case, reported in the media, CrossCountry reject a ticket because the customer screenshotted it. (Also here: https://www.railforums.co.uk/threads/pdf-tickets-screenshots-acceptable.256319/#post-6459457)

I think it's pretty clear that rail staff have done quite a bit more than 'quibble' about it. Making up imaginary rules yet again such as “A photo of a ticket is not a valid ticket held.” (which Transport Investigations, acting on behalf of XC, in the aforementioned case claimed to a customer)

It says enough that the advice in numerous threads on the topic is just to use the PDF in case you run into a troublesome member of staff.
So, I'm not sure it can be said with such certainty that staff won't react to being shown something in a different format. They have a poor track record for this and it's reasonable to assume there might be some resistance as a result

Both those cases are a number of years old. Back then m-tickets were much more common and were only valid via the app - screenshots were specifically banned (presumably because fewer onboard staff had scanners to actually validate tickets).

Now, pretty much only e-tickets are issued, which are valid displayed in any format as long as the Aztec code can be scanned.

 

[Mattplans]

Both those cases are a number of years old.

It doesn’t really matter. All it shows is that railway staff have reacted poorly when showed a valid code but in a different format.

Therefore it follows, as per post #1, that staff might “quibble” and show resistance towards them.

 

[James H]

On balance I think I would be happy to use a ‘homemade’ wallet pass for barriers but probably wouldn’t present it for inspection

 

[davp]

Now, pretty much only e-tickets are issued, which are valid displayed in any format as long as the Aztec code can be scanned.

Can you clarify this? Does this mean that it can be shown to staff in any format, ie phone, tablet, printout etc?

Or that it doesn't matter what the rest of the ticket looks like as long as there is a scannable Aztec barcode? In which case the user created pass in post 19 would be fine.

This might seem like a trivial question, but given some people's experience with rovers printed on PRT I would be tempted to use a user created pass for my rover wherever possible (whilst carrying the original ticket safely if required).

 

[Buzby]

Or that it doesn't matter what the rest of the ticket looks like as long as there is a scannable Aztec barcode?

Absolutely - if shown on a Watch only the code is visible - never had an issue.

 

[davp]

Absolutely - if shown on a Watch only the code is visible - never had an issue.

Thanks - I'll give this a go.

 

[OscarH]

Though cancellation messages can take a while to be distributed.

Although of course they shouldn't

 

[Adam Williams]

There is no reason not to accept an Aztec code printed on a cup-cake, frankly. The barcode, provided it can be scanned, should be all that matters.

The nonsense around PRT somehow being "special" and therefore being more secure when I have seen people buy PRT stock on eBay is exactly that: nonsense. If it can be issued on PRT it should be possible to issue electronically.

 

[davp]

There is no reason not to accept an Aztec code printed on a cup-cake, frankly. The barcode, provided it can be scanned, should be all that matters.

The nonsense around PRT somehow being "special" and therefore being more secure when I have seen people buy PRT stock on eBay is exactly that: nonsense. If it can be issued on PRT it should be possible to issue electronically.

What stops someone sharing an Aztec barcode with someone else then? Or will the scanner pick up it has already been scanned (somewhere else)?

 

[OscarH]

There is no reason not to accept an Aztec code printed on a cup-cake, frankly. The barcode, provided it can be scanned, should be all that matters.

The nonsense around PRT somehow being "special" and therefore being more secure when I have seen people buy PRT stock on eBay is exactly that: nonsense. If it can be issued on PRT it should be possible to issue electronically.

Before we even get to the plain white PRT stock being trialed, and yet they still won't just link (non-sTicket) barcode fulfilment to a single RCS type

What stops someone sharing an Aztec barcode with someone else then? Or will the scanner pick up it has already been scanned (somewhere else)?

A functioning scanner will pick this up. An aztec is an aztec, so it's just fundamentally not possible to have user-side security against copying it - the security is that the tickets get scanned and the scanners do their job and highlight existing scans

 

[Haywain]

the security is that the tickets get scanned and the scanners do their job and highlight existing scans

And the weakness is that gates correctly reject them and gateline staff just look at the details and let people through, rather than using a scanner to find out why it was rejected.