MOJA — Wallet Pass QR Codes

Wallet Pass QR Codes

A wallet pass QR code is a link to the pass file, which is how Apple Wallet and Google Wallet passes are actually distributed. The code does not contain the pass — it points at it, and the phone does the rest.

Premium

QR Generation lives in our app

Create unlimited QR codes — right from your phone, anytime, anywhere. Free to download.

Experience this feature seamlessly in our mobile app. Download it today to enjoy the full mobile experience

Download Free App

How to create a Wallet Pass QR code

Host the pass file somewhere over HTTPS A .pkpass for Apple Wallet, or a save link for Google Wallet. The code cannot carry the file itself, so this step is the actual work.
Check the file is served with the right content type Apple Wallet needs application/vnd.apple.pkpass. Served as a plain download, iOS shows a file it does not know what to do with instead of the Add to Wallet sheet — and the QR code will look like the thing that is broken when it is not.
Test on both an iPhone and an Android phone The two wallets take different files. A link that adds a pass on iOS may do nothing useful on Android, and the code cannot tell them apart.
Generate the code from the link In the app under Events & Access — or, since the payload is just the URL, with the free Website URL generator on this site.

What a Wallet Pass QR code is for

Wallet passes are files, and files are far too large for a QR code — a small .pkpass is tens of kilobytes against a practical ceiling of a few hundred characters. So every wallet-pass QR code in the world is a link, and this one is no exception: the payload is your HTTPS address and nothing else.

That is worth stating plainly, because it means the code is not doing anything clever and you should not expect it to. What makes a wallet pass work is the file and the server serving it. The code is transport.

You can build the same code here for free. Because the payload is a plain URL, the Website URL generator on this site produces an identical pattern. The app's version is a convenience — it keeps the pass link with your other passes — not a different kind of code.

Where a Wallet Pass QR code earns its place

Boarding-pass-style entry to an event

The pass lands in the wallet, where it surfaces on the lock screen at the right time and place. That behaviour comes from the wallet, not from the code.

Store cards and coupons that need to update

A wallet pass can be pushed changes after it is installed — a new balance, a changed gate. This is the one thing a static QR code cannot do on its own, and the reason to bother with a pass at all.

Handing out a pass on printed material

A poster or a flyer where the reader has no app installed and you want the thing to end up somewhere they will find it again.

Wallet Pass format notes and limits

The code is only a link, so everything a link suffers from applies. If the host goes away, the printed code is dead. Point it at an address you control and redirect, rather than at a signed URL from a service you may stop using.

The content type decides whether it works. Apple Wallet expects application/vnd.apple.pkpass; the wrong header produces a download that goes nowhere. This is the most common reason a wallet pass "does not scan" when the scan is fine.

Signed pass URLs expire. Some services hand out links with a token that dies after a period. Printing one of those produces a code with a shelf life, and nothing about the code will warn you.

One code cannot serve both wallets unless the page behind it detects the device and serves the right file.

Length matters as it does for any link: a long signed URL makes a dense code. Measured with this site's encoder, a 40-character address is 29 modules across and a 98-character one is 41 at the same error correction.

Wallet Pass QR codes — questions people actually ask

Does the QR code contain my pass?

No. It contains a link to it. Passes are tens of kilobytes and a QR code holds a few hundred characters in practice, so every wallet pass code is a link — including this one.

Can I just use the free URL generator instead?

Yes. The payload is a plain HTTPS address, so Website URL produces exactly the same code. The app version is a convenience for keeping the pass link alongside your others.

The code scans but nothing is added to the wallet.

Almost always the file is served with the wrong content type — Apple Wallet needs application/vnd.apple.pkpass. The scan and the code are fine; the server is answering the wrong way.

Will one code work on both iPhone and Android?

Only if the page behind the link decides which file to serve. The two wallets use different formats and the code carries no device information.