ดูข้อมูลเพิ่มเติมเกี่ยวกับวิธีสร้าง JWT ที่ลงนามแล้วที่จำเป็นในการสร้าง "เพิ่มลงใน Google Wallet" โปรดดูการทำงานกับโทเค็นเว็บ JSON
2. (แนะนำ) ใช้ปุ่ม "เพิ่มลงใน Google Wallet" ปุ่ม
สำหรับแพลตฟอร์มที่รองรับไฮเปอร์ลิงก์รูปภาพ เช่น เว็บไซต์และอีเมล ขอแนะนำให้แสดงไอคอน "เพิ่มลงใน Google Wallet" ลิงก์ไปที่ผู้ใช้ของคุณได้ด้วยลิงก์ "เพิ่มลงใน Google Wallet" สำหรับผู้ใช้ Google Wallet ปุ่มเป็นข้อความแจ้งที่คุ้นเคยซึ่งทราบว่าเป็นวิธีเริ่มเพิ่มบัตรลงใน Google Wallet
ชิ้นงานรูปภาพพร้อมให้ดาวน์โหลดในการวางแนวและภาษาที่หลากหลายเพื่อรองรับการผสานรวม Google Wallet API
[null,null,["อัปเดตล่าสุด 2025-08-29 UTC"],[[["\u003cp\u003eIssue passes to users via 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 is a dynamically generated URL containing an encoded and signed JWT representing the pass data.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends using the 'Add to Google Wallet' button, with downloadable assets, to visually guide users.\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, present users with an 'Add to Google Wallet' button or hyperlink, which saves the pass upon tapping. This link, formatted as `https://pay.google.com/gp/v/save/\u003csigned_jwt\u003e`, contains an encoded and signed JWT and can be embedded in various mediums like websites, email, or SMS. Before issuing, complete onboarding, create pass classes and objects, encode them in a JWT, and sign the JWT with a service account key. The recommended method is using the 'Add to Google Wallet' button.\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/transit-passes/qr-code/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/transit-passes/qr-code/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/transit-passes/qr-code/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/transit-passes/qr-code/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/transit-passes/qr-code/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/transit-passes/qr-code/resources/brand-guidelines)"]]
