The Gift Card enrollment (sign-in) feature allows users to search for a gift card and add it to the Google Wallet. Users will be directed to your mobile-friendly website to complete the process, after which they can add their card to Google Wallet. This guide provides an overview of the implementation steps required to enable your gift card program for this feature. ## Overview To get started, make sure you have previously set up your project and have access to Google Wallet API. You must follow these four steps to implement the sign-in feature for your gift card program: 1. Set up a test class in Google Wallet for testing your sign-in flow. 2. Develop sign-in pages that use Google Wallet `SharedDataType`. 3. Implement push back of gift card to Google Wallet after sign-in. 4. Request verification and activation. ## Set up a test class in Google Wallet Determine the sign-in URL, your program logo. Then, use the `discoverableProgram` nested fields in the [`giftcardclass`](https://developers.google.com/wallet/reference/rest/v1/giftcardclass.md.txt) to set the appropriate values. Set the values in the `discoverableProgram` to create a draft version of your sign-in enabled gift card program. To make sure this is visible to testers, verify that the testers have access to your Google Pay and Wallet Console. For details on how to share your Google Pay and Wallet Console's access with other people, see [Learn about the Users page](https://support.google.com/googlepay/businessconsole/answer/10878869#zippy=%2Cinvite-a-new-user). To complete the verification of your implementation's functionality during the development process, reach out to us using the contact support widget in the Google Pay and Wallet Console. While in the console, select **Google Wallet API** in the topic, and select **Gift card sign-in** in the subtopic. ## Develop sign-in page that use Google Wallet user data When a user chooses to add your gift card, they are directed to a tailored page on your website in order to complete the sign-in process. You are required to provide a sign-in URL where a user can sign in to an existing account. Your sign in page must meet the following requirements: - Provide a mobile-friendly user experience. - Allow the user to complete sign-in within one single page. - Use `HTTPS` encryption with a valid certificate to ensure user data is transmitted securely. - Ensure at least 99.9% uptime of your sign-in page. When presenting the sign-in page, Google Wallet will create an Android WebView and a `POST` request is made to your provided URL. User data is provided in the parameter `SharedDataType` which is included in the `POST` request using the [application/x-www-form-urlencoded](https://www.w3.org/TR/html401/interact/forms.html#h-17.13.4.1) content type and `UTF-8` encoding. The value of the `SharedDataType` parameter is a Base64 encoded JSON object. > [!NOTE] > **Note:** The JSON string is first UTF-8 encoded and subsequently encoded using [android.util.Base64](https://developer.android.com/reference/android/util/Base64.html) with the options NO_WRAP and URL_SAFE. This corresponds with [RFC 3548 section 4](https://tools.ietf.org/html/rfc3548#section-4). ## Implement immediate push back of gift card to Google Wallet Once authenticated (sign-in), your page should immediately push back the user's gift card to Google Wallet. > [!NOTE] > **Note:** Don't implement a Google Wallet API button as users should be taken back to Google Wallet without additional user interaction. You can push back the gift card to Google Wallet by redirecting to a link that follows the structure ``` https://pay.google.com/gp/v/save/{jwt_generated} ``` > [!NOTE] > **Note:** Make sure to include the trailing '/' in the URL before the JWT. > [!NOTE] > **Note:** JWTs are unencrypted. Only include data in the deep link that is safe to share as plain text. The safe length for a URL is 2000 characters. Your links should remain under this limit. Objects encoded in JWTs should be small, containing only data that is specific to the user. Try to keep most data in the object's class, creating it before making the JWT. For larger objects that don't fit the limit, consider first creating the object in the **Google Wallet API** and sending only the object ID in the JWT. ## Typical Communication Flow The communication flow for a user completing sign-in is illustrated in the following image. All actions between "Your Server" are your responsibility to implement. ![Sign-in flows](https://developers.google.com/static/wallet/retail/gift-cards/images/giftcard-enrollment-flow.png) ## Request verification and activation After you complete the development work and test your sign-in flow, submit a request through the [Google Pay and Wallet Console](https://pay.google.com/business/console/) contact support widget. After a full review of your implementation that confirms correct feature in combination with the Google Wallet app, the gift card sign-in feature will be publicly launched for your gift card program. This will allow any user to see the program and make use of this feature. In order to ensure an optimal user experience, recurring checks of your sign-in implementation will be conducted to ensure ongoing compliance with the feature requirements. You will be notified in the event of discrepancies and the sign-in feature may be disabled until the issue is resolved. ## Frequently Asked Questions - **Are there any requirements for the images used in my gift card program?** - Yes, your images should be hosted on `HTTPS` location as they won't be visible in Google Wallet otherwise. - **Are there any tools that simplify the implementation and debugging of JWTs?** - Yes, platforms such as [www.jwt.io](https://jwt.io/) allow you to decode and debug your tokens during your development process, allowing you to verify the content you are submitting. Do note that Google has no affiliation and does not specifically recommend any of such third parties. - **How do we correctly handle the Base64 encoded SharedDataType data?** - Ensure that you are using UTF-8 encoding throughout your process. The JSON string is first UTF-8 encoded and subsequently encoded using [android.util.Base64](https://developer.android.com/reference/android/util/Base64.html) with the options NO_WRAP and URL_SAFE. This corresponds with [RFC 3548 section 4](https://tools.ietf.org/html/rfc3548#section-4).