Emisión de pases para la Web, correo electrónico y SMS
Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Una vez que hayas creado un pase y lo hayas codificado en un JWT firmado, podrás emitirlo donde sea que se muestre el vínculo es compatible. Para ello, debes presentar al usuario el campo “Agregar a la Billetera de Google” o un hipervínculo, que guardará el pase en su Billetera de Google cuando lo presione. Entre los ejemplos de casos en los que puedes utilizar este método, se incluyen los sitios web, el correo electrónico y los SMS, entre otros.
Requisitos previos
Antes de intentar emitir un pase, asegúrate de hacer lo siguiente:
Codifica la clase Passes y el objeto Passes en un JWT.
Firma tu JWT con la clave de tu cuenta de servicio de Google Cloud.
1. Crea una cuenta “Agregar a la Billetera de Google” vínculo
Cómo emitir un pase con una “Billetera de Google” agrega el Objeto Pases a la Billetera de Google de un usuario y solo se puede iniciar en el contexto de una identidad de Google a la que se accedió.
Obtén más información sobre cómo crear el JWT firmado necesario para crear una cuenta consulta Trabaja con tokens web JSON.
2. (Recomendado) Usa la opción “Agregar a la Billetera de Google” botón
Para cualquier plataforma que admita hipervínculos con imágenes, como sitios web y correo electrónico, se recomienda presentar el botón “Agregar a la Billetera de Google” a los usuarios con un vínculo “Agregar a la Billetera de Google” . Para los usuarios de la Billetera de Google, el botón es un mensaje conocido que se reconoce como una forma de comenzar a agregar un pase a su Billetera de Google.
Los recursos de imagen están disponibles para descargar en una variedad de orientaciones e idiomas para admitir la integración de la API de la Billetera de Google.
[null,null,["Última actualización: 2025-09-03 (UTC)"],[[["\u003cp\u003eIssue passes to users through an 'Add to Google Wallet' link, which can be embedded in various platforms like websites, emails, and SMS.\u003c/p\u003e\n"],["\u003cp\u003eThis link contains an encoded and signed JWT representing the pass data.\u003c/p\u003e\n"],["\u003cp\u003eIt's recommended to use the 'Add to Google Wallet' button (with provided assets) to enhance user experience and recognition.\u003c/p\u003e\n"],["\u003cp\u003eBefore issuing passes, ensure completion of onboarding, class and object creation, JWT encoding, and signing.\u003c/p\u003e\n"],["\u003cp\u003eDemo passes will have "[TEST ONLY]" in the title until publishing access is granted.\u003c/p\u003e\n"]]],["To issue a pass, first ensure you've completed onboarding, created pass classes and objects, and encoded/signed them in a JWT. Then, generate an 'Add to Google Wallet' link containing the signed JWT. This link, usable in websites, email, or SMS, allows users to save the pass to their Google Wallet. For visual consistency, use the official 'Add to Google Wallet' button when hyperlinking is available. Demo passes will have \"[TEST ONLY]\" in their titles until publishing access is granted.\n"],null,["# Issuing passes for web, email, SMS\n\nOnce you've created a pass and encoded it in a signed JWT, you are ready to issue it anywhere that the 'Add to Google Wallet' link is supported. To do this, you will present your user with an 'Add to Google Wallet' button or a hyperlink, which will save the pass to their Google Wallet once they tap it. Examples of where you might use this method include websites, email, SMS, and more.\n| **Demo Mode / \\[TEST ONLY\\] passes**\n|\n| When you are still in [Demo Mode](../resources/terminology#demo-mode), all the passes that you create will have an additional text \"\\[TEST ONLY\\]\" in the title. This is to differentiate demo passes from live passes. Once you are granted [publishing access](../test-and-go-live/request-publishing-access), these demo mode passes will no longer have the additional text when the user reopens the wallet app on a connected device.\n\nPrerequisites\n-------------\n\nBefore you try to issue a pass, be sure you do the following:\n\n- Complete all of the steps in the [Onboarding guide](../getting-started/onboarding-guide).\n- Create at least one [Passes Class](../use-cases/create#creating_a_passes_class).\n- Create at least one [Passes Object](../use-cases/create#creating_a_passes_object).\n- [Encode](../use-cases/jwt#encoding-a-pass-in-a-jwt) your Passes Class and Passes Object in a JWT.\n- [Sign](../use-cases/jwt#web,-email,-and-sms) your JWT with your Google Cloud service account key.\n\n1. Create an 'Add to Google Wallet' link\n----------------------------------------\n\nIssuing a pass with an 'Google Wallet' link adds the Passes Object to a user's Google Wallet, and can only be initiated in the context of a logged-in Google identity.\n\nThe 'Add to Google Wallet' link is a dynamically generated URL that contains an [encoded and signed JSON Web Token (JWT)](/wallet/tickets/events/web/jwt).\n\nThe Add to Google Wallet link has the following format: \n\n```\nhttps://pay.google.com/gp/v/save/\u003csigned_jwt\u003e\n```\n\nFor example, a fully-formed 'Add to Google Wallet' link will look something like this: \n\n```\nhttps://pay.google.com/gp/v/save/eyJhbGci6IkpXVCJ9.eyJhdWQiO...6EkC1Ahp6A\n```\n\nThis link can be embedded into websites, email, chat, SMS, or anywhere else that supports hyperlinks.\n| The safe length of an encoded JWT is 1800 characters. If your JWT is less than this limit, the entire object can be included in the signed JWT. If the length is over 1800 characters, the save may not work due to truncation by web browsers. See this [FAQ](/wallet/tickets/events/resources/faq#my-jwt-link-url-exceeds-the-1800-character-limit-browser-restriction.-what-should-i-do) for more info.\n\nFor more information on creating Passes Classes and Passes Objects, see [Create Passes Classes and Passes Objects](/wallet/tickets/events/web/create).\n\nFor more information on how to create the signed JWT needed to create an 'Add to Google Wallet' link, see [Working with JSON Web Tokens](/wallet/tickets/events/web/jwt).\n\n2. (Recommended) Use the 'Add to Google Wallet' button\n------------------------------------------------------\n\nFor any surfaces that support hyperlinking images, such as websites and email, it is recommended to present the 'Add to Google Wallet' link to your users with an 'Add to Google Wallet' button. For Google Wallet users, the button is a familiar prompt that is recognizable as a way to initiate adding a pass to their Google Wallet.\n- \n- \n\n[Image assets](/wallet/tickets/events/resources/brand-guidelines) are available to download in a variety of orientations and languages to support your Google Wallet API integration.\n\n[Download the 'Add to Google Wallet' button](/wallet/tickets/events/resources/brand-guidelines)"]]
