AI coding assistants have turned a basic Apple Wallet or Google Wallet pass into a small project. A capable developer can ship one in days, and we won’t pretend otherwise.
That shifts the build-versus-buy decision away from the initial development effort. What matters now is what your team owns after the first pass is issued.
Issuing a Pass Is One Thing. Running a Wallet Program Is Another.
A basic wallet pass can contain little more than a logo, customer information, and a barcode. If that is all you need, such as a few hundred membership cards that never change, building in-house may be the practical choice.
Most programs don’t stay there. A restaurant group launches a loyalty card, then wants point balances on the pass, then rewards, then offers by location. Each step means the pass has to change after it is already on a customer’s phone, and that is where the work begins.
By then, marketing wants to run campaigns without filing tickets, operations wants reporting, and engineering is keeping two wallet platforms in sync with the loyalty system. You are running customer-facing software.
What You Own After Launch
Creating a pass and keeping it current are separate problems, and Apple and Google handle the second one differently.
Apple Wallet
- Every pass is signed with a Pass Type ID certificate that expires. If nobody renews it, new passes cannot be signed and updates to existing passes are disrupted.
- Updating a pass requires a web service you host. Wallet communicates with it to register devices, check which passes have changed, and download updated versions.
- You trigger updates by sending notifications through Apple’s Push Notification service, using the appropriate pass certificate.
- Your service maintains device registrations and handles registrations that are no longer valid.
Apple documents these requirements in its guide to updating Wallet passes.
Google Wallet
- Passes are built from classes (shared configurations) and objects (individual passes), a different architecture from Apple’s signed pass files.
- Passes can be issued through signed JSON Web Tokens associated with a Google Cloud service account and an issuer account you manage.
- Updates go through Google’s API rather than a web service you host. That means maintaining separate update integrations for Apple and Google.
Google explains this architecture in its documentation on classes and objects.
Both platforms
- A balance that doesn’t update or a card showing outdated information lands on your team to diagnose, across two platforms with different technical requirements.
- Every new pass type, location, or business unit can introduce additional templates, integrations, and testing.
A capable engineering team can manage all of this. The problem is that the responsibility doesn’t end after launch.
What AI Changes, and What It Doesn’t
AI shortens the build. It can help write signing code, develop update services, create tests, and debug integrations.
It does not take the pager.
Customer data still has to be protected, certificates still have to be renewed, and platform changes from Apple and Google still have to be tested against existing passes. When a pass breaks in a customer’s hand, someone on your team owns the fix.
AI can substantially reduce the initial development effort, but ongoing operational responsibilities remain. Judge an internal build on what it costs in year three, not just month one.
The Comparison Most Teams Skip
Most comparisons set a development estimate against a vendor’s annual fee. That leaves out much of the build column and part of the buy column.
Before deciding, fill in every row below with your own figures over a three-year period.
| Cost factor | Build in-house | Buy a platform |
|---|---|---|
| Initial development | Pass generation, signing, update services, and admin tools | Platform setup, configuration, and integration |
| Integration with existing systems | Internal development and maintenance | Integration work, potentially supported by vendor tools |
| Hosting and monitoring | Your infrastructure and operating costs | Typically included in the platform service |
| Certificates and platform changes | Your team’s responsibility | Generally managed by the provider |
| New pass types and features | Internal development backlog | Existing features, configuration, or vendor roadmap |
| Day-to-day changes | Internal admin tools or engineering involvement | Managed through platform tools where supported |
| Technical support | Your engineering team | Vendor support, subject to the service agreement |
| Recurring costs | Infrastructure, maintenance, and staffing | Subscription fees and applicable service costs |
| Long-term dependency | Internal codebase and the people who maintain it | Vendor reliability, data ownership, and exit terms |
The row that rarely gets a meaningful number is engineering time.
Hours spent on wallet infrastructure are hours not spent on personalization, claims automation, or whatever sets your business apart. The underlying wallet infrastructure serves largely the same purpose for you as it does for your competitors, so owning it rarely creates a competitive advantage on its own.
That doesn’t mean buying is automatically cheaper. An organization with established infrastructure, available engineering capacity, and limited requirements may find that internal development is economical.
But a proper comparison must account for the full cost of operating the technology, not just creating it.
When to Build, and When Not To
Build if:
- You issue a small number of passes that rarely change.
- You already operate wallet infrastructure that meets your requirements.
- You have specialized needs that available platforms cannot support.
- You require full control over the architecture and have the resources to maintain it.
Buy if:
- Passes update frequently with balances, status changes, offers, or ticket information.
- You need to support both Apple Wallet and Google Wallet.
- Marketing or operations will regularly change designs, offers, and campaigns.
- The program will expand across locations, customer segments, or business units.
- Your engineering team has higher-value development priorities.
The more of these requirements your program has, the stronger the case becomes for an established platform.
Where Bambu Wallet Fits
Bambu Wallet provides the infrastructure described above, already built.
The platform supports pass creation, distribution through links, QR codes, and landing pages, dynamic updates, notifications, automation, and reporting for Apple Wallet and Google Wallet. It supports loyalty cards, offers, memberships, event tickets, insurance cards, and other digital wallet use cases.
Your engineers can focus on connecting the platform to existing systems and developing functionality specific to your business. Marketing and operations teams can manage pass designs, offers, and notifications without waiting on a development release for every routine change.
For companies evaluating an internal build, this changes the investment. Instead of recreating the underlying wallet infrastructure, you can direct engineering resources toward the integrations and customer experiences that create value for your organization.
If you’re weighing an internal build, book a demo and bring your estimate. We’ll show you how the same program would run on Bambu Wallet so you can compare the two properly.
Follow us on LinkedIn for more insights on digital wallet technology, customer engagement, and operational efficiency.