Wallet passes - Masivo

A wallet pass is a coupon code packaged for Apple Wallet and Google Wallet. Masivo issues the pass through the Storefront API. The phone stores the pass. Masivo stays the source of truth for whether the code can still be used. Claiming a pass assigns it to a customer. It does not redeem the coupon. Redemption still uses POST /coupons/redeem.

How it works

Save Apple and Google credentials.
Design a template and enable it on a coupon campaign.
Call issue once per campaign and share the same claim_url. Each visitor gets a code.
Redeem the code with the customer_id. The pass is linked to that customer on its first redeem.

Status

Status	Meaning
`ISSUED`	Created, not linked to a customer yet
`CLAIMED`	Linked to a customer who still has uses left
`REDEEMED`	The coupon code was redeemed
`EXPIRED`	The campaign end date passed
`REVOKED`	Invalidated manually or because the customer was deleted

What the pass shows

Templates live in Settings → Wallet passes → Templates. Apple Wallet and Google Wallet only support their own layouts, so templates fill those slots. They are not HTML.

Slot	Template field
Title next to the logo	Header
Large offer	Offer label + offer text
Coupon code	Code label + allocated code
State	Status label + current status
Barcode	QR or Code 128 of the code
Colors	Background, foreground, label
Images	Logo (top-left), icon (stacked list), illustration (right)

Credentials are per account: an Apple Pass Type ID certificate and a Google Wallet issuer service account. See Wallet pass credentials.

Detecting a pass without reading the phone

Apps cannot list passes stored in Apple Wallet or Google Wallet. Detection uses Masivo records:

Passes linked to a customer_id, from GET /customers/{id}/wallet-passes. A pass is linked on its first redeem.
Every pass of the account, filtered by campaign, customer, status, or code, from GET /wallet-passes.

See the dashboard guide and the Storefront API guide.