Run wallet campaigns for every client — on one account you own

The problem with reselling wallet passes

Most wallet-pass platforms are built for a single merchant. For an agency that means one login per client, one credit card per client — and the platform bills your client directly, so there's no room for your margin. App-store loyalty suites make this structural: the app charges the merchant's own account, and you're reduced to a setup consultant.

Pass Studio inverts this. You hold the account. Each client is a brand workspace under your team. Credits live in one pooled wallet you buy centrally and allocate per client. There's no partner tier and nothing to negotiate — the public rates are already this low. What you charge for the program is between you and your client; the margin is yours.

Campaigns that outlive the ad spend

A wallet campaign is an offer that lives on the customer's phone. Design a branded coupon or offer pass, distribute it by QR, link, or embed — in the client's ads, email, packaging, storefront — and it sits in Apple or Google Wallet. Mid-flight changes are a push, not a reprint: extend the deadline, change the offer, and every issued pass updates in place.

And when the campaign ends, the audience remains. Every saved pass is a customer the next campaign reaches with a push — no re-targeting spend to find them again. Campaign one builds the audience; every campaign after pushes to it for pennies.

• Relevance. The audience opted in — every pass in a wallet was saved by choice. The wallet surfaces it on the lock screen at the right time and place, and a push keeps the offer current, so it's never a stale coupon.
• Immediacy. A push update lands on every issued pass in seconds — no inbox in between, no open-rate lottery, no algorithm deciding whether the customer sees it.
• Effective targeting. You push to exactly who holds what: each campaign's pass is its own audience, and first-touch attribution tells you which channel built it.

Together, that's the ROI case — and the next section is where you prove it to the client.

The attribution story that closes retainers

Every client eventually asks the question agencies fear most: "Your ads ran — did anyone actually come in?" Pass Studio answers it out of the box.

• First-touch campaign parameters (utm_source, utm_campaign, …) are stamped on the pass at issuance and preserved for its whole life.
• Every event — install, update, register scan, redemption — streams to Segment as a native source, named to spec (orders emit as "Order Completed" for e-commerce destinations).
• Three privacy modes (Events / Anonymous / Full Identity) so the pipeline matches each client's consent posture.
• A register scan weeks after the ad click lands in your client's warehouse already attributed. Offline ROI becomes a single SQL query — a report you can put in front of a client every month.

Two-minute setup: paste a Segment write key. No custom data engineering.

From campaign to relationship

The campaign ends; the wallet slot doesn't. Re-push seasonal offers to everyone who saved a previous pass and keep the client's brand on the lock screen between campaigns — engagement between bursts costs a push, not a media budget.

When a client is ready for always-on, the same passes become a full loyalty program — points, rewards, register scans, no customer app. The retention economics hold up too: a loyalty client with ~1,500 active members generating ~4,000 billable actions a month costs you about $120/month at the 10,000-credit rate — a rounding error inside a retainer.

How the economics work

Credits are pay-as-you-go and only consumed by actions — issuing a pass, pushing an update, a register scan. No per-active-pass fee, no monthly platform tax per client. A pass sitting in a customer's wallet costs you nothing; you pay when the program does something.

A worked example. A campaign that puts 5,000 passes into wallets, updates them all once mid-flight, and sees 2,000 scanned redemptions costs about 12,000 credits — roughly $360 at the 10,000-credit rate (design is a one-time 10 credits). That's a number you can build into the quote in the proposal before you pitch it — and it scales linearly, so a 50,000-pass flight prices out the same way. On subscription plans, bulk pushes and scans meter in blocks and cost less at volume.

Built multi-tenant from day one

• Brand workspaces. One team per client: separate passes, holders, analytics, and branding. Switch clients from the top bar.
• Pooled credits with allocation. Buy centrally, allocate per workspace, see consumption per client — or set a workspace to bill through your account entirely: plan inherited, one shared balance, released any time.
• Roles. Bring staff into the workspaces they work on.
• White-label signing. Passes sign under Pass Studio's certificate by default — no Apple Developer account, no .p12 wrangling. Clients who want their own issuer name can bring their own certificate.

Every rail your clients are on

• Shopify — auto-issue passes from paid orders, discount-code sync.
• Square — native register loop: scan the pass, member identified, discounts applied.
• Web POS — staff scan page for everyone else; works on any phone or tablet.
• REST API + webhooks + Zapier — idempotent, documented, built to be wired into whatever the client already runs.
• Forms & share links — no-integration issuance for the clients who just need a card in wallets this week.

Want all of this — economics, billing structures, attribution, and the due-diligence answers — on a single page you can forward? Partner terms on one page →

FAQ

Comparing platforms first? Best wallet pass platforms in 2026 → · Building on the API? Integration docs →

Ready to set up your first client workspace? Create your agency account — 50 free credits →