Google Wallet tickets with Motics support
Overview
This documentation describes how to issue Motics enabled QR-Code tickets in
Google Wallet.
In order to successfully implement support for Motics tickets, carefully review
the following:
- The Integration Steps are a summary of the main prerequisites and steps
required to complete a Google Wallet integration for Motics tickets.
- The Technical Details section contains a system architecture overview, a
detailed description of the necessary Google Wallet API changes and how to
implement the Activation Endpoint.
- The Move and Unlink Flow section contains the details for allowing users
to move or unlink their Motics ticket, within limits defined by the issuer.
- The Testing section provides more detail around the various testing phases
and exit criteria that must be met before proceeding to a full launch or
public pilot.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-03-06 UTC.
[null,null,["Last updated 2025-03-06 UTC."],[[["This documentation guides you on issuing Motics-enabled QR-Code tickets for Google Wallet, outlining the steps for seamless integration."],["Key sections cover integration prerequisites, technical implementation details including API changes and activation endpoint, user management for ticket moving and unlinking, and comprehensive testing procedures."],["By following these guidelines, transit agencies can effectively enable their Motics tickets for use within Google Wallet."]]],["The documentation details how to implement Motics-enabled QR-code tickets in Google Wallet. Key actions include reviewing integration steps, understanding technical details such as system architecture, API changes, and the activation endpoint. It also outlines implementing move and unlink functionalities for users, within issuer-defined limits. Additionally, it provides information on testing phases and the necessary criteria for moving to a full launch or public pilot.\n"]]
