Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Laravel Mobile Pass

Laravel Mobile Pass Laravel Package

spatie/laravel-mobile-pass

Laravel package to generate Apple Wallet mobile passes (boarding passes, tickets, coupons, cards) with support for pushing updates to issued passes so they stay current on users’ devices. In development—don’t use in production yet.

View on GitHub
Deep Wiki
Context7

Generate mobile passes for iOS and Android

Frequently asked questions about Laravel Mobile Pass
Can I use this package for boarding passes with real-time flight updates?
Yes, this package supports real-time updates via Apple Wallet and Google Pay APIs. You can push changes like gate numbers or flight statuses instantly to users' devices. Ensure your Laravel queue system (e.g., Redis) handles high-frequency updates efficiently to avoid delays.
What Laravel versions does spatie/laravel-mobile-pass support?
The package explicitly requires **Laravel 10.x+** and PHP **8.1+**. Check the [GitHub repo](https://github.com/spatie/laravel-mobile-pass) for minor version compatibility notes, as it’s currently marked **IN DEVELOPMENT** and may evolve. Test thoroughly before upgrading Laravel.
How do I set up Apple Wallet integration? Do I need a developer account?
Yes, you’ll need an **Apple Developer account ($99/year)** to configure Wallet Web Service. The package requires your **Apple Wallet Merchant ID** and **private key** for signing passes. Follow Apple’s [Wallet documentation](https://developer.apple.com/documentation/passkit) and configure these keys in Laravel’s `.env` or the package’s config file.
Does this package support Google Pay passes? What are the prerequisites?
Yes, it supports **Google Pay passes** (Android). You’ll need a **Google Pay API key** and access to the [Google Pay & Wallets Console](https://pay.google.com/business/console). Configure your API credentials in Laravel’s config, and ensure your app meets Google’s [requirements](https://developers.google.com/wallet/digital) for pass types.
How do I customize pass templates (e.g., add barcodes or dynamic fields)?
Templates are defined using **JSON-LD** and can be customized via the package’s configuration. For barcodes, the package likely relies on `spatie/laravel-barcode` (check dependencies). Dynamic fields like expiration dates or loyalty points are added via Eloquent model attributes or pass metadata. Refer to the [examples](https://github.com/spatie/laravel-mobile-pass) for JSON-LD structure.
What happens if a user’s device doesn’t support Apple Wallet or Google Pay?
The package **does not natively support fallbacks** like PDFs or emails. You’ll need to implement a secondary delivery method (e.g., QR codes or SMS links) for unsupported devices. Document this limitation in your user flow and consider hybrid approaches for critical passes like boarding tickets.
How do I handle pass updates when Apple/Google APIs reject my payload?
The package uses **queues** for async updates, but you should validate passes locally before sending. Use Apple’s [PassKit Validator](https://developer.apple.com/documentation/passkit) or Google’s [test tools](https://developers.google.com/wallet/digital/test) to catch issues early. Log rejected payloads and implement retry logic with exponential backoff in your queue workers.
Is this package ready for production? What are the risks?
**No, it’s explicitly marked IN DEVELOPMENT** and not production-ready. Risks include breaking changes, undocumented edge cases, and potential API dependency issues (e.g., rate limits). Test thoroughly in a staging environment, monitor queue failures, and have fallback mechanisms for critical passes.
Can I generate passes offline or for air-gapped systems?
No, this package **requires server-side rendering** and relies on Apple/Google APIs for delivery. For air-gapped systems, consider generating **QR codes or PDFs** as an alternative and manually distributing them. Offline generation isn’t supported natively.
What are some alternatives to spatie/laravel-mobile-pass for mobile passes?
Alternatives include **custom API integrations** with Apple Wallet/Google Pay SDKs or third-party services like **PassKit.io** or **Trellis**. For simpler use cases, consider **PDF/QR code generation** with libraries like `dompdf` or `endroid/qr-code`. Evaluate based on your need for real-time updates and cross-platform support.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
davejamesmiller/laravel-breadcrumbs
artisanry/parsedown
christhompsontldr/phpsdk
enqueue/dsn
bunny/bunny
enqueue/test
enqueue/null
enqueue/amqp-tools
milesj/emojibase
bower-asset/punycode
bower-asset/inputmask
bower-asset/jquery
bower-asset/yii2-pjax
laravel/nova
spatie/laravel-mailcoach
spatie/laravel-superseeder
laravel/liferaft
nst/json-test-suite
danielmiessler/sec-lists
jackalope/jackalope-transport