Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Alguns cartões criados com a Carteira do Google podem conter dados sensíveis do usuário. Eles têm mais proteção para manter os dados dos usuários seguros e são gerenciados de forma diferente na API Wallet. Os cartões pessoais genéricos precisam ser usados nos casos em que dados sensíveis (conforme definido na Política de Uso aceitável da API Wallet) são incluídos no cartão.
Os cartões pessoais genéricos são compatíveis com os seguintes casos de uso:
Cartões de seguro de saúde
Documentos de identidade nacional
Outros documentos de identificação oficiais
Alguns países e jurisdições exigem que os dados sensíveis sejam gerenciados de uma forma específica. Sendo assim, a lista de casos de uso destacada aqui pode variar dependendo do seu país ou de outras regulamentações. Se os dados do usuário estiverem sujeitos à regulamentação legal no seu país de origem (por exemplo, a Lei de Portabilidade e Responsabilidade de Seguros de Saúde dos Estados Unidos), eles vão precisar usar os cartões pessoais genéricos e poderão estar sujeitos a uma análise adicional.
O que mudou?
Os cartões pessoais genéricos usam um método independente para definir e distribuir o cartão. Como desenvolvedor, você define o layout e o conteúdo do cartão em um único JSON Web Token, que é distribuído diretamente ao usuário para que ele salve o cartão na Carteira.
Os cartões que processam dados sensíveis (cartões pessoais genéricos) podem estar sujeitos a outros controles de privacidade durante a integração. Não permitimos que as APIs sejam usadas para processar dados sensíveis na Carteira sem permissão explícita do Google, conforme descrito na Política de Uso Aceitável da API Wallet.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Não contém as informações de que eu preciso","missingTheInformationINeed","thumb-down"],["Muito complicado / etapas demais","tooComplicatedTooManySteps","thumb-down"],["Desatualizado","outOfDate","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Problema com as amostras / o código","samplesCodeIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-04 UTC."],[[["\u003cp\u003eGoogle Wallet has extra protection for passes containing sensitive user data, like health insurance or national ID cards, using the generic private pass vertical.\u003c/p\u003e\n"],["\u003cp\u003eThese passes are managed differently, requiring developers to define the layout and contents in a JSON Web Token distributed directly to the user.\u003c/p\u003e\n"],["\u003cp\u003eUsing the Google Wallet APIs for sensitive data requires explicit permission from Google and may involve additional privacy controls during onboarding.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers must request access through Google Pay and Wallet Console support and provide verification documents to be eligible to issue generic private passes.\u003c/p\u003e\n"],["\u003cp\u003eAfter approval, developers can begin implementation by referring to the provided 'Get started' resources.\u003c/p\u003e\n"]]],["Generic private passes, designed for sensitive user data like health insurance or national IDs, require a specific approach within Google Wallet. Developers define the pass layout and content in a JSON Web Token distributed directly to the user. Access to create these passes is restricted and requires explicit permission from Google. To request access, submit an eligibility document, logo URL, and website URL via the Google Pay and Wallet Console. Once approved, developers can implement the pass using the provided guidelines. Passes that use private information may be subject to additional privacy controls.\n"],null,["# Overview\n\nSome passes that you can create with Google Wallet may contain sensitive user data. These passes have extra protection to help keep your users data safe and are managed differently in the Wallet API. The generic private pass vertical should be used in cases where sensitive data (as defined in the Wallet API [Acceptable Use Policy](https://payments.developers.google.com/terms/aup)) is included in your Pass.\n\nThe generic private pass vertical supports use cases such as:\n\n- Health Insurance Cards\n- National Identification Cards\n- Other Government IDs\n\nSome countries and jurisdictions require that sensitive data is managed in a particular way. As such, the list of use cases highlighted here may vary depending on your country or other regulations. If your user data is subject to legal regulation in your country of origin (e.g. the Health Insurance Portability and Accountability Act in the United States), it will have to use the generic private pass vertical and may be subject to additional review.\n\n### What is different?\n\nGeneric private passes use a self-contained method for defining and distributing the pass. As the developer, you define the pass layout and contents in a single JSON Web Token that is then distributed directly to the user for them to save it into their Wallet.\n\nPasses which process sensitive data (known as generic private pass) may be subject to additional privacy controls during onboarding. We do not allow the APIs to be used for processing sensitive data in Google Wallet without explicit permission from Google, as described in the as defined in the Wallet API [Acceptable Use Policy.](https://payments.developers.google.com/terms/aup)\n\nRequest access\n--------------\n\nIf your pass contains sensitive data, [contact support](https://support.google.com/google-pay-and-wallet-console/answer/10913634) in the [Google Pay and Wallet Console](https://pay.google.com/business/console/) and request for access. If you are unsure if your pass contains sensitive data, please contact support.\n\nYou will be required to provide the following:\n\n- Eligibility Document verifying your identity and attesting you are a valid entity\n- A URL to your logo\n- A URL to your website\n\nGet started\n-----------\n\nAfter you have received approval to issue generic private pass, get started with your implementation to add passes to Google Wallet.\n\n[Get started](/wallet/generic-private-pass/guides)"]]
