Kartu Terbatas Akun
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Apa yang dimaksud dengan Kartu Dibatasi Akun?
Fitur baru yang memungkinkan developer mengaitkan beberapa objek kartu dengan Akun Google yang membatasi siapa saja yang dapat menyimpan kartu.
Bagaimana cara kerjanya?
Anda dapat menyetel alamat email pengguna di objek kartu menggunakan Google Wallet API. Saat pengguna
mencoba menyimpan kartu tersebut ke Google Wallet, kami memvalidasi bahwa akun yang ditetapkan di objek kartu
cocok dengan Akun Google pengguna Google Wallet yang menyimpan kartu.
Kedengarannya hebat! Bagaimana cara mendapatkan akses ke fitur ini?
Kami sedang menguji fitur ini dengan sejumlah kecil developer. Jika Anda tertarik,
hubungi dukungan
di Konsol Google Pay & Wallet dan
ajukan kasus dukungan berdasarkan Topik: “Integrasi Google Wallet API”, Subtopik: “Lainnya”
dan sertakan dalam deskripsi masalah: “Permintaan Akses Kartu Terbatas Akun”.
Kami akan memberi tahu saat Anda dapat mengaksesnya.
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-08-29 UTC.
[null,null,["Terakhir diperbarui pada 2025-08-29 UTC."],[[["\u003cp\u003eAccount Restricted Passes are a new feature allowing developers to link specific pass objects to Google accounts, restricting who can save them.\u003c/p\u003e\n"],["\u003cp\u003eThis feature works by verifying the Google Account of the user saving the pass against the account associated with the pass object using the Google Wallet API.\u003c/p\u003e\n"],["\u003cp\u003eThe feature is currently in limited testing, and interested developers can request access through Google Pay & Wallet Console support.\u003c/p\u003e\n"]]],["Developers can use Account Restricted Passes to link pass objects to specific Google accounts, limiting who can save them. This is done by setting the user's email on the pass object via the Google Wallet API. When a user attempts to save the pass, the system verifies that the pass's email matches the user's Google account. To gain access to this feature, developers must contact support through the Google Pay & Wallet Console, using the specified topic and subtopic, and requesting \"Account Restricted Passes Access.\"\n"],null,["# Account Restricted Passes\n\n#### What are Account Restricted Passes?\n\n\nA new feature that lets developers associate some pass objects with Google accounts which limits\nwho can save the pass.\n\n#### How does it work?\n\n\nYou set the user's email address on the pass object using the Google Wallet API. When the user\nattempts to save that pass to Google Wallet, we validate that the account set on the pass object\nmatches the Google Account of the Google Wallet user saving the pass.\n\n#### That sounds great! How do I get access to this feature?\n\n\nWe're testing the feature with a small number of developers. If you are interested,\n[contact support](https://support.google.com/google-pay-and-wallet-console/answer/10913634?zippy=%2Cbusiness-profile)\nin the [Google Pay \\& Wallet Console](https://goo.gle/wallet-console) and\nfile a support case under Topic: \"Google Wallet API Integration\", Subtopic: \"Other\"\nand include in the issue description: \"Account Restricted Passes Access Request\".\nWe'll let you know when you can access it."]]
