Pillar
Education

Apple Wallet Pass Not Updating? Here's How to Fix It

Apple Wallet pass not updating? Learn what to check on iPhone and Apple Watch, when Wallet can refresh, and when the issuer backend must republish.

4 min readMar 29, 2026
A pass card paused on an update arrow while a phone and watch wait for fresh data from the issuer

When an Apple Wallet pass keeps showing old information, the issue is usually not the screen. Wallet can only display updates that the issuer publishes, and some passes only refresh when the issuer backend sends a new version.

If the same stale data appears on iPhone and Apple Watch, that usually points to the pass source, not just Wallet sync.

How Pass Updates Work

Apple Wallet does not invent new data on its own. The pass issuer has to publish the update, and the pass has to be able to accept it.

Issuer data first

Wallet updates come from the issuer's pass service. If that service does not send new data, Wallet stays on the old version.

Automatic Updates

Some passes expose an Automatic Updates option in Pass Details. If the issuer supports it, turn it on.

Apple Watch sync

Apple says passes added on iPhone are automatically added to a paired Apple Watch and update on both devices.

Hidden or expired copies

A pass can look stale if it is hidden, expired, or replaced by a newer pass that is not currently open.

If the same stale values appear on iPhone, Apple Watch, and the issuer app, the pass service is probably the bottleneck.

What to Try First

Work through these checks before assuming the pass is broken.

1

Open Pass Details

Look for Automatic Updates or any replacement or update prompt from the issuer.
2

Refresh the pass

Open the pass and use any refresh or update action that the issuer provides.
3

Check the issuer source

Open the app or website that issued the pass and look for a newer link, ticket, or balance.
4

Sync Apple Watch

If the watch is stale, open Wallet on iPhone first and re-add the latest issuer version if the pass was reissued.
5

Contact the issuer

If the same old data appears everywhere, ask whether the pass needs to be republished or reissued.

A stale pass is not always a broken pass

If the barcode still scans and only the text is old, the issuer may be the only thing that needs to change. Wallet cannot invent a new seat, balance, or ticket status on its own.

When It Is the Issuer

If the pass updates on one device but not another, or never changes after the issuer says it should, the pass service is probably the bottleneck.

That is common for tickets, stored balances, and time-sensitive passes. The app or website that issued the pass has to publish the new version first.

Where NeatPass Fits

NeatPass helps when the source is a static barcode or stored card that should live in Wallet without depending on a live issuer feed.

It does not force a merchant backend to update. It keeps the Wallet copy reliable when the source data can be imported cleanly.

See adding to Wallet, import methods, supported barcodes, plus offline mode.

For source handling and privacy, read View Original, data management, and privacy FAQ.

Keep passes current

NeatPass makes it easy to convert any ticket, pass, or loyalty card to Apple Wallet.

Frequently Asked Questions

Fix the source, not just the screen

Download

Keep the Right Data in Wallet

If the pass updates on the iPhone but not on Apple Watch, open the iPhone copy first and re-add the latest issuer version if needed. If the same stale data appears everywhere, the issuer backend is the part that needs attention.

NeatPass is useful when the pass is a static, barcode-based item that should stay usable in Wallet even when the original source is not behaving like a live pass.

Ready to migrate your cards?

NeatPass makes it easy to convert any ticket, pass, or loyalty card to Apple Wallet.