Skip to content
TixFin

Wallet

Tickets that live in the phone

Apple Wallet and Google Wallet passes are generated from the same ticket design you configured, and a verified transfer flow moves a ticket to a new owner without a screenshot.

In short

How do wallet tickets work?

Tickets can be delivered as an Apple Wallet pass and a Google Wallet pass. Apple .pkpass files ship as an email attachment and can be downloaded through the /tickets/{id}/pass endpoint; the Add to Google Wallet link is generated through /tickets/{id}/google-wallet and embedded as a button in the confirmation email. Both formats automatically adopt the configured ticket design — colours, logo, background image and token labels — so the pass in the phone matches the ticket everywhere else.

  • Apple Wallet .pkpass by email and API

  • Add to Google Wallet link in the confirmation mail

  • Both formats inherit the configured ticket design

Wallet

One design, every surface

Because the wallet passes, the email ticket and the PDF attachment all render from the same design record, a rebrand is a single change rather than four. The QR code stays the credential the scanner validates at the door.

Capabilities

From purchase to phone

  • 01

    Apple Wallet passes

    A .pkpass file is attached to the confirmation email and remains downloadable through a dedicated ticket endpoint.

  • 02

    Google Wallet passes

    An Add to Google Wallet link is generated per ticket and embedded directly in the confirmation email as a button.

  • 03

    Design consistency

    Colours, logo, background image and token labels from the ticket designer are applied to both wallet formats, the email ticket and the PDF attachment.

  • 04

    Verified transfer

    A holder starts a transfer by recipient email with an optional message; a 48-hour token and secure accept link move ownership on acceptance.

  • 05

    Cancel and revoke

    Senders can cancel, admins can revoke, and pending transfers expire automatically after 48 hours.

  • 06

    Full audit trail

    Every transfer action is written to the audit log and the ticket event history, with bilingual email templates and in-app notifications.

Specifications

Key facts

Apple Wallet
.pkpass as email attachment and via GET /tickets/{id}/pass
Google Wallet
Add to Google Wallet link via GET /tickets/{id}/google-wallet
Design inheritance
Colours, logo, background image and token labels
Transfer verification
48-hour email token with a secure accept link
Transfer permission
TICKET_TRANSFER_MANAGE for admin access

How it works

Getting a ticket into a wallet

  1. 01

    Design the ticket

    Set colours, logo, background and token labels once in the ticket designer for that ticket type.

  2. 02

    Sell

    On purchase, the confirmation email carries the .pkpass attachment and the Add to Google Wallet button.

  3. 03

    Add to wallet

    The buyer adds the pass in one tap and no longer depends on finding the email at the gate.

  4. 04

    Transfer if needed

    If plans change, the holder transfers the ticket to a verified recipient and ownership moves on acceptance.

Use cases

Built for

FAQ

Wallet questions

Ask the team
  • Yes. Both Apple and Google Wallet passes automatically adopt the configured ticket design, including colours, logo, background image and token labels, as do the email ticket and the PDF attachment.
  • The confirmation email carries the Apple .pkpass as an attachment and an Add to Google Wallet button. Both are also available through dedicated ticket endpoints.
  • Yes. The holder starts a transfer using the recipient's email address. The recipient receives a 48-hour verification token with a secure accept link, and ownership is rewritten on acceptance.
  • The sender can cancel, an admin can revoke it through the event transfer overview, and any pending transfer expires automatically after 48 hours. Every action is recorded in the audit log.

Put your tickets in the wallet

Design the ticket once and let every buyer carry it in Apple Wallet or Google Wallet.