Save to Google Pay API
The Save to Google Pay API is a simple platform that lets you connect your business to millions of Android users by adding your Loyalty program, gift cards, and offers to Google Pay. You can engage with your customers anytime through location-based notifications, real-time updates, and messaging. Plus, it's easy to manage updates at scale through the cloud.
1. Apply for Save to Google Pay API access
All applications that access a Google API must be registered through the API Console. The result of this registration process is a set of values that are known only to Google and your application (client ID, email address, private key). (If you have already done this, you may skip this step).
Go to Save to Google Pay API access Sign up page. Enter all the details such as Name, company name, Title, Phone number, and email address. Select the desired redemption method and type of objects company would like to integrate into Google Pay. Refer below
Click on the "Submit" button.
Note: Once the above application has been submitted, Google will be in contact with the provided email address and guide through the creation of the Save to Google pay account.
A sample email trace from previous Save to Google pay account setting up is provided below:
FROM: s2ap-support@google.com RE: [0-9834000017954] Thank you for your interest in the Save to Google Pay API Hi, Thanks for your interest in the Save to Google Pay API! My name is Nayana and I’ll be guiding you through the onboarding process. In order to accurately gauge whether the Save to Google Pay API can meet your needs, please provide us with the following: A description of your use case The country from where you will be developing The country of your target user base For your reference, our Save to Google Pay API documentation can be found at https://developers.google.com/pay/passes. I’m looking forward to learning more about your use case. Once we have this information, we’ll be able to evaluate if the Save to Google Pay API is a good fit for your business. Warm regards, Nayana The Save to Google Pay Support Team |
FROM: yao.li@tractiondigital.com RE: [0-9834000017954] Thank you for your interest in the Save to Google Pay API Hi Nayana, Thanks for your response. Getting back to your questions: A description of your use case: Our client (an international shoe retailer brand) wants to use our marketing platform to deliver their digital offers/coupons to their customers’ Google Pay on mobiles. They want us to be able to distribute up to 200K digital cards. They also have high interest in sending their membership cards in this way. Once we developed this function, we will sell it to a wider range of businesses. The country from where you will be developing: We are from Australia The country of your target user base: At this stage, our target users are mainly in Australia I look forward to hearing back from you soon. Thanks for your help. Regards, Yao Li |
FROM: s2ap-support@google.com RE: [0-9834000017954] Thank you for your interest in the Save to Google Pay API Hello Yao, Thank you for your email. The Save To Google Pay API is designed for use in retail stores in which customers who have the Google Pay app on their phone can show a barcode that can be scanned at the register at checkout. You can digitize loyalty cards, offer cards, and gift cards. More info can be found in our documentation here (https://developers.google.com/pay/passes). Would you be interested in any of those aspects of the API? If so, may you be able to explain in more detail about your use case? Warm regards Nayana The Save to Google Pay Support Team |
FROM: yao.li@tractiondigital.com RE: [0-9834000017954] Thank you for your interest in the Save to Google Pay API Hi Nayana, We (TractionDigital) are developing digitize loyalty cards, offer cards and gift cards for our clients. At this stage, our client (an international shoe retailer brand) wants to use our marketing platform to deliver their digital offers/coupons to their customers’ Google Pay on mobiles. They want us to be able to distribute up to 200K digital cards per month. They also have high interest in sending their membership cards in this way. We also plan to sell this function to a wider range of businesses. Thanks. Regards, Yao |
FROM: s2ap-support@google.com RE: [0-9834000017954] Thank you for your interest in the Save to Google Pay API Hello **, Thank you for providing your use case. I will present it to my team and update you our next steps. Sincerely, Nayana The Save to Google Pay Support Team |
FROM: s2ap-support@google.com RE: [0-9834000017954] Thank you for your interest in the Save to Google Pay API Hello, In order to grant Save To Google Pay API access, we will need an email address that has a Google account associated with it. You can associate a Google account with an existing email address here (https://accounts.google.com/SignUpWithoutGmail?dsh=6121473328314604542&continue=https%3A%2F%2Fappengine.google.com%2F_ah%2Fconflogin%3Fcontinue%3Dhttps%3A%2F%2Fmap.googleplex.com%2F&service=ah#FirstName=&LastName=) , or provide an @gmail.com email address. Let us know what email address you would like us to use. Sincerely, Nayana The Save to Google Pay Support Team |
FROM: yao.li@tractiondigital.com RE: [0-9834000017954] Thank you for your interest in the Save to Google Pay API Hi Nayana, I have created a google account with email: yao.li@tractiondigital.com. Would you please help proceed? Thanks. Regards, Yao |
FROM: s2ap-support@google.com RE: [0-9834000017954] Thank you for your interest in the Save to Google Pay API Hello, I've created a Save to Google Pay Merchant Center account for TractionDigital. Your Merchant Center ID is 3220040669650182707. You can now access the Merchant Center at https://wallet.google.com/merchant/walletobjects/ using the following account: yao.li@tractiondigital.com. Below are some steps to help you through the initial setup. Step #1: Accessing the API documentation You can now access the documentation website at https://developers.google.com/pay/passes. Step #2: Accept the TOS and creating the authentication credential This page (https://developers.google.com/pay/passes) provides a straightforward step-by-step process to generating the authentication credential, during which you'll have the opportunity to click-to-accept the API Terms of Service. Step #3: Associate your authentication credential with your account At the end of the setup process you'll receive a Google-generated service account address in the format XXXXXXXXXXX@developer.gserviceaccount.com. In the merchant dashboard, you must add this address to your account by clicking on the “Share” button and adding it with “Edit” permissions. From this point on, you can access the API using your authentication credential. Please feel free to reach out to me at any time if you need assistance with the Save to Google Pay API! Sincerely, Nayana The Save to Google Pay Support Team |
Note: Please take note of the Google account mentioned in the last google email, in the sample's case - "yao.li@tractiondigital.com". This is the account name to access API Console in Step 2 and Save to Google Pay Merchant Console in Step 3.
2. Create Google APIs Service Account
Access the API Console. click on an existing project name (for example MobileWalletProduction in below screenshot); If there is no existing project, select Create a Project from the drop-down arrow located at the top of the page.
It will display 'Select a project' pop-up, Click on 'New Project'
The New project page appears. Type in a new project name, select the location and click Create button
When the configuration is complete, a notification appears in the top right corner. Click on this notification to navigate to the project's home page.
Click APIs & Services → Credentials from the left-hand menu.
Click the Create Credentials button then select Service Account Key.
If there has no available Service Account from the dropdown list, you need to create a new service account.
Give the Service account a name (e.g. document-test-admin) and make it's Role "Project Owner". (How to assign role to Service Account), refer the information added below at this page)
Note: Take note of the auto-generated Service account ID. It will be used later.
Select the Service Account and Create a Service Account Key using the Key Type- P12
Choose p12 as the key type and then click Create. Once you click on the 'Create' button, it will display the message and a .p12 file will be downloaded to your computer. Refer below...
Note: This .p12 file is the only copy of this key and you are responsible for keeping this key file in a secure location. You will use this key later.
Click on the 'close' button, it will display as below...
A new Service Account has been added to your list of accounts and a private key is downloaded to your local file system.
3. Tie your Service account to your Save to Google Pay account
Your Save to Google Pay account should have been created for you by your Google point of contact. The Save to Google Pay Merchant Console is a web site you can use to manage your account and all your associated classes and objects.
Access the Save to Google Pay Merchant Console. Click Account Management on the left-hand navigation. The Account Info page is displayed.
Note: Make a note of your Issuer ID (also called a Merchant ID). You will use this later when making API calls.
3a. From this page, you will see the all available / created Issuer IDs approved by Google listed as shown below:
3b. From the list, click on the Issuer ID that was created for this Mobile Pass project and click on Share account:
The Share settings popup appear for the selected Issuer ID.
Enter the Service account ID(which was created in step 2)and paste it in the Invite People field.
Make sure the permissions dropdown is set to can edit then click Save Changes.
Your service account is now tied to your Save to Google Pay account
4. Upload the certificate in TractionNext
Login to TractionNext and go to ‘Account Settings’. Under the ‘Integrations’ menu, Look for the ‘Pass Certificates’ option and click it.
Select Upload Certificate For Google Pay.
Get Service account ID, Issuer Id and .p12 file ready and fill in the fields accordingly.
5. After successfully adding the required certificates, you can now try to create the Passes in the TractionNext platform and test. You can create them by following the Article from here.
NOTE:
1) How to get Service account ID, refer below steps...
2) click on an existing project name (for example MobileWalletProduction in below screenshot);
Now click on 'Credentials' and then on 'Manage service accounts'.
A screen appears below. Click on Action icon and then select 'Edit' from the dropdown.
Edit screen will display. Value showing in the email (below screen) is your 'Service account ID'. Copy it.
2) How to assign role to Service account, refer below steps...
2) click on an existing project name (for example MobileWalletProduction in below screenshot);
Now click on 'Credentials' and then on 'Manage service accounts'.
A screen will display, Click on 'IAM' menu on the left hand side of the page, service account list will displayed. click on 'pencil/pen' icon displayed on the extreme right of the screen.
It will display a popup as below...
click on 'Role' dropdown and select the role as project owner, refer below screen,,,
Comments
0 comments
Please sign in to leave a comment.