--- title: "The whole pass lifecycle, from design to retirement" url: https://getstell.com/platform description: "Stell sits between the systems you already run and the wallets your customers carry: pass creation, distribution, live updates, NFC identification and push." --- # The whole pass lifecycle, from design to retirement # Platform The whole pass lifecycle, from design to retirement Stell sits between the systems you already run and the wallets your customers carry: pass creation, distribution, live updates, NFC identification and push. /platform POS & payment terminals Existing NFC readers, no new hardware CRM / loyalty engine Member records, points, tiers E-commerce & app ESP / campaign tools Location & time relevance Expiry & revocation Add-to-wallet links & QR PKPass · VAS identification Pass objects · Smart Tap Till, turnstile, kiosk, standalone reader Relevance, updates, notifications The reader announces your program. The wallet presents the matching pass with the payment card, in one gesture. The payload is encrypted for your program alone. The terminal holds the private key and reads the member identifier itself. No lookup, no network. The POS gets the identifier with the payment result and posts the basket to your loyalty engine. Discounts can apply in the same tap. Your engine sends the new points, stamp or tier in one API call. The pass updates in Apple Wallet and Google Wallet. Your engine · Stell Reward unlocked? An automation sends a lock-screen notification through the pass. No extra channel. Pass creation & design Templates, both wallets, one payload Add-to-wallet links, QR, email Any field, in seconds Apple VAS · Google Smart Tap Lock screen, through the pass Campaigns & automations Segments, triggers, scheduled sends QR & barcode scanning QR, PDF417, Aztec, Code 128, EAN-13 and more Post-purchase sign-up, no form Analytics & reporting Installs, taps, redemptions From kickoff to the first live tap: a scoped launch, not a project. Apple & Google certificate setup, under your own developer account Stell + your team Day-to-day operation belongs to your marketing and ops teams. Segments, automations and campaign scheduling Install, tap and redemption analytics Your team, self-serve We stay on the hook for the parts customers never see. Certificate renewals, no downtime The pass type identifier and its certificates live on your account. We need only enough access to operate them, and how much is your call: Add a named Stell engineer to your account, scoped to certificates Or give us App Store Connect API credentials scoped to certificates, and renewals run with no named person on your account at all If NFC identification is in scope, the account also needs Apple's VAS entitlement. Stell is a VAS Provider and prepares that request with you Issue under your own issuer ID. We take service-account access to manage classes and objects, and the account, and the estate of passes on it, stay yours throughout. Already issuing Google passes? They migrate onto Stell under the issuer ID you already hold Existing objects keep working and start receiving updates from us, with nothing for members to re-add Your issuer ID, before and after The test of ownership is what happens if you decide to leave. When the accounts are yours, so is the estate: serial numbers, authentication tokens and device registrations export on request. No member deletes, re-adds, or notices anything Export rights in the contract, not on request Templates, artwork specs, both wallet renderings, previews for sign-off Logo, brand colors, hero artwork REST API, signed webhooks, staging keys, reference payloads Access to CRM/POS, a technical contact 1–2 days VAS and Smart Tap configuration, merchant IDs, test tooling Reader model list, acquirer contact Add-to-wallet links, QR posters, landing page, email snippets Rollout plan, staff one-pager, launch review / /platform #architecture #tap #capabilities #integrations #ownership #security / The whole pass lifecycle, one platform . /contact Architecture Three layers, one integration. Your stack keeps the customer record. Stell operates the pass: its schema, certificates, distribution and state. Wallets and readers are the last mile. Your systems Stell Pass lifecycle platform Wallets & readers Data flow Under a second, stretched out. The same tap that pays also identifies. The member is read at the terminal before the receipt prints. Stell comes in afterwards, to keep the pass in the wallet true. Your systems · Stell Capability map What the platform does. One engine, one API. These are the jobs that define a wallet pass platform , each available across the pass types it applies to. This is the matrix teams usually want in front of them before scoping a launch. Available today Not applicable to that pass type Apple Wallet and Google Wallet unless noted. Scope Who does what. The honest split, so nobody discovers a surprise in week three. Ownership Bring your own accounts. The accounts are yours. The operating is ours. Register the pass type identifier and the issuer ID under your own Apple and Google accounts, and Stell takes the certificate lifecycle off your team entirely: issuance, annual renewal, PKCS#7 signing, and spec changes when the platforms move. Moving an existing program onto Stell, or planning for the possibility of moving off one day? The mechanics, and the questions to ask a provider before you sign, are in switching wallet pass providers . Built on modern serverless cloud infrastructure. Capacity scales with your traffic, from a single store to peak season, with nothing for you to provision. Passes carry a token, not a profile. Your customer record stays in your systems. Built in Norway under European data protection law. A data processing agreement with every customer. Apple VAS Provider. Google Smart Tap enabled. Signing keys held in our vault, on the accounts you bring. Pass engine Template editor Certificate management Update service Push service Identity at the reader Barcode redemption Hosted join pages Enrollment at the till Post-purchase invite Notification history Phone meets reader Terminal decrypts the pass Sale linked to the member Balance written to the pass Push if it matters Real-time updates Push notifications Bring your Apple Developer Account Bring your Google issuer account The day you leave The platform The tap Stell sits between the systems you already run and the wallets your customers already carry. You send events; we handle pass creation, distribution, live updates, NFC identification at the reader, and push, for Apple Wallet and Google Wallet alike. Book a technical walkthrough Read the docs API · webhooks signed pass · NFC Technical walkthrough Bring your architecture. We'll map it. Forty minutes with a solutions engineer: your POS, your loyalty engine, your reader estate. You leave with a diagram and an honest scope split.