Deutschlandticket Apple Wallet: Which Providers Support It

Nearly 14 million Germans use the Deutschlandticket for unlimited regional transit. But getting it into Apple Wallet is frustratingly inconsistent. Some providers support it, others promise it is "coming soon" (and have for years), and some require monthly manual downloads.

This is the pillar guide. It covers how Apple Wallet support actually works for the Deutschlandticket in 2026, which Verkehrsverbund does what, and which child article to dive into for a specific Verbund or problem.

The Deutschlandticket Apple Wallet Situation

There is no single "Deutschlandticket app" with universal Apple Wallet support. Where you purchased your ticket determines whether Wallet export is available. The official Deutschlandticket App by HanseCom added Apple Wallet support in late 2024, after promising it since spring 2023. But even now, the feature is hidden deep in settings and doesn't work with all transport companies.

Providers with Apple Wallet Support

Providers Without Wallet Support

Verbund Comparison Matrix

A quick view across the Verbünde I see most often in my support inbox. Tap a guide for the full step-by-step.

Provider-Specific Instructions

Hamburg (HVV Switch)

Hamburg has the smoothest Apple Wallet experience. The hvv switch app supports automatic monthly updates directly in Apple Wallet. You need to enable this in the card details within the Wallet app after adding it.

On Android, updates happen automatically. On iPhone, you must manually toggle "Automatic Updates" in the pass settings for the ticket to refresh when the month changes. For the full HVV walkthrough see the HVV Apple Wallet guide.

Berlin (BVG)

Berlin requires two separate apps. The main BVG Fahrinfo app doesn't support Wallet export. You need to download the separate BVG Tickets app, log in with your account, then find your Deutschlandticket under "Ticketspeicher."

From there, tap the three-dot menu and select "Add to Apple Wallet." The catch: the export step has to be repeated every month. There is no automatic update. Step-by-step screenshots live in the Berlin BVG guide.

Munich (MVG)

Munich's MVGO app technically supports Apple Wallet, but with significant friction. According to MVG, the new ticket has to be re-downloaded each month under "Meine Tickets," then manually added to Wallet again. There is no automatic update within the Wallet app.

That defeats much of the point of having the ticket in Wallet at all. Full MVGO walkthrough plus alternatives are in the Munich MVGO guide.

West and South (VRR, VRS, RMV, VVS)

The big west-and-south Verbünde behave very differently from each other. VRR uses the Deutschlandticket App and the eezy.nrw flow. VRS ships its own ticket app. RMV in Frankfurt offers the RMV app and partial Deutschlandticket App support. VVS in Stuttgart leans on the Deutschlandticket App.

The mix of native pkpass, in-app passes, and missing Wallet support across these four Verbünde is the most confusing area for readers. The full breakdown lives in the VRR, VRS, RMV, and VVS guide.

Deutschlandticket App (Official)

The official Deutschlandticket App by HanseCom added Apple Wallet support, but it is not available for all transport companies. Supported providers include VBB (Berlin-Brandenburg), various Ruhrgebiet operators (DVG, Ruhrbahn Essen/Mülheim), and several smaller regional providers.

To find the Wallet option: go to Settings, then "My Contracts," and look for the Wallet export there. It is not visible on the ticket itself. Once added, the pass should update automatically as long as your subscription remains active.

Common Problems Across Verbünde

Five issues come back again and again, regardless of which Verbund issued the ticket. Each links to the deeper article for that specific symptom.

The Wallet ticket disappears or expires at month rollover

This is the single most reported issue. The pass simply stops working on the 1st because the underlying VDV-KA barcode has changed and the old pass was never refreshed. The pattern of which providers push automatically vs. require manual re-export is covered in the monthly update guide with a per-Verbund table you can scan in seconds.

The QR code is rejected by the inspector's scanner

Inspectors scan the VDV-KA barcode embedded in the pass. If the pass is from the previous month, or if it is a NeatPass screenshot of a dynamic barcode, the validation fails on the device. NeatPass works for Verbünde that issue a static monthly barcode. If a Verbund regenerates the code mid-month, only the native provider app stays valid. The list of content.commonProblems.scanner.supportedBarcodesLinkText explains which formats NeatPass can preserve cleanly.

The pass became invalid when the price changed

The Deutschlandticket jumped from 49 Euro to 58 Euro to 63 Euro. Each price change triggered a contract change, and several Verbünde silently invalidated old Wallet passes when the new subscription period started. The 2026 price update and what it means for active passes is covered in the 2026 price article including the cancellation deadlines that catch most subscribers off guard.

The pass works in Wallet but the provider app cannot find the subscription

This usually happens after a phone reset, a SIM swap, or a logout from the provider app. The Wallet pass keeps working as long as it has not expired, because content.commonProblems.disappear.offlineLinkText. But the next monthly refresh fails because the provider app cannot reach the subscription record. Reinstalling the provider app and signing back in restores the link, then the next month's pass exports cleanly.

Why Doesn't Every Provider Support Wallet?

The Deutschlandticket uses VDV-KA barcodes, cryptographically signed to prevent fraud. Creating these barcodes requires specific hardware and certificates. While the technical standard exists, implementing Apple Wallet integration requires additional development work that smaller Verkehrsverbund operators haven't prioritized.

Deutsche Bahn, despite being Germany's largest rail operator, has not implemented Wallet export for the Deutschlandticket in DB Navigator. DB Wallet support is limited to long-distance ICE/IC tickets, which use a different barcode system.

What NeatPass Can and Cannot Do

NeatPass can create Apple Wallet passes from supported barcodes. However, the Deutschlandticket presents a unique challenge: the barcode changes every month, and some providers regenerate it more frequently.

When NeatPass Works

• Static monthly barcodes: If your provider issues a barcode that stays the same for the entire month, you can screenshot it and create a Wallet pass with NeatPass
• Backup access: Having the current month's ticket in Wallet means you can show it even if the app crashes or won't load
• Offline reliability: Wallet passes work offline, unlike apps that may need to connect

When NeatPass Won't Help

• Dynamic barcodes: Some providers regenerate the QR code during the month for security. A screenshot won't stay valid.
• Automatic updates: A new pass has to be created each month when the barcode changes

How to Add Deutschlandticket to Wallet via NeatPass

For providers with static monthly barcodes, or if you want a Wallet backup even with manual monthly updates:

Frequently Asked Questions

Your Ticket, Always Ready

The Deutschlandticket is supposed to simplify transit across Germany. Apple Wallet integration would make that even smoother, but the fragmented implementation means you are stuck navigating provider-specific quirks.

For providers with native support, enable auto-updates and enjoy the convenience. For everyone else, NeatPass offers a workaround for static barcodes, though the pass needs a monthly refresh. Either way, having your ticket in Wallet means faster access at turnstiles and reliability when apps fail.