Apple and Google Wallet
Create coupons, loyalty cards and tickets. The pass lives in the phone's wallet and updates whenever you change it. No push permission required.
Create coupons, loyalty cards and tickets. The pass lives in the phone's wallet and updates whenever you change it. No push permission required.
You manage it from the Wallet page in the dashboard or via the API.
1. Enter your credentials
Credentials are validated when saved, encrypted and never shown again. You only need to configure the platform you use.
Apple
In your Apple Developer account, create a Pass Type ID and its certificate, and download the WWDR intermediate certificate from the Apple PKI page.
Apple gives you a .p12. Pushizo requires PEM, so convert it with these commands:
openssl pkcs12 -in Sertifikalar.p12 -clcerts -nokeys -out pass.pem -legacyopenssl pkcs12 -in Sertifikalar.p12 -nocerts -nodes -out pass.key -legacyopenssl x509 -inform DER -in AppleWWDRCAG4.cer -out wwdr.pemThe certificate expiry date is shown in the dashboard. Renew it before it expires: once it expires, no new passes can be issued and existing passes stop receiving updates.
Get your Issuer ID from the Google Pay & Wallet Console. In Google Cloud, enable the Wallet API, create a service account and add that account to the Console as a user. Enter the service account's JSON key. New classes are visible only to test users until Google reviews them.
2. Create a template
| Field | Description |
|---|---|
kind | coupon, loyalty, event, generic |
slug | Short name used in messages; cannot be changed later |
design | Title, description, organization, colors, barcode format, fields |
images | icon (required for Apple), logo, strip. PNG, base64, at most 256 KB |
Images are served from a public URL so Google can access them: don't put confidential content in them. When you change the template, passes already issued are updated too.
3. Distribute the pass
Via a message
Add the tag to your template. Each recipient gets their own link, and the pass is created on the spot if needed:
Your coupon is ready: {% wallet_pass 'yaz_kuponu' %}For a subscription without a user, the tag returns empty. The link opens according to the device: iOS and macOS download a .pkpass, Android goes to Google Wallet.
Via the API
POST /v1/apps/{appId}/wallet/passes
Authorization: Bearer <key with notifications:write scope>
{ "template_id": "wlt_...", "external_id": "musteri-42", "barcode_value": "KOD-9", "values": { "oran": "%20" } }The url in the response opens the pass. A pass tied to a user is unique per template: a second request for the same user returns the same pass. The link opens only that pass and contains no personal data; still, don't post it publicly.
4. Update or void
PATCH /v1/apps/{appId}/wallet/passes/{id}
{ "values": { "puan": "1250" } }On Apple, registered devices are notified and download the new pass. On Google, the pass is written directly. POST .../passes/{id}/void invalidates the pass; this cannot be undone.
Permissions
| Operation | Dashboard permission | API scope |
|---|---|---|
| Read | analytics.read | users:read |
| Issue, update, void passes | campaigns.create | notifications:write |
| Templates | templates.write | admin |
| Credentials | channels.manage | admin |
Known limitations
- There are no location- or beacon-based pass suggestions.
- Instead of bulk pass issuance, use the tag in a message.
- The Apple web service is served from the
API_URLaddress and must be HTTPS: Apple won't connect to a web service with an HTTP address.
Product recommendations
Pick the right products from your product catalog for each recipient and show them in campaigns, journeys and emails. Recommendations are computed daily from your event data. Decision record: ADR-0063. A product catalog must be uploaded first…
Data Feeds
Data Feeds fetch data from an external JSON endpoint for each recipient at send time and make it available in templates as {{ feed.<name>.field }} (loyalty points, stock, cart, weather…). Decision record:…