You don’t need to register with Google. You can play with the API yourself. And integrate into your site In this case we do show users’ real data. However, whenever they make a selection We will return you a fake token If you are working with one Of the supported processors, we will return you a token which you can use in their TEST environment. Remember your real card details are never used when in environment TEST, but you must add at least one chargeable card to your Google account before you proceed Once you complete.
The integration And you are ready to handle real payments, come and register with us. Through our self-service portal and then flip the environment to PRODUCTION, You can apply for production access. On g.Co/pay/sign-up, Now that you have Your PaymentsClient constructed the first API you will call is is ReadyToPay With is ReadyToPay. You can determine whether the user Has a valid payment method on file and is on a supported browser.
The Google Pay API Supports all major browsers, including Safari, Opera, Firefox, Chrome, UC, Browser and soon Microsoft Edge At Google. We focus On optimizing for conversion, so, if is ReadyToPay returns false, we highly recommend that you do not render The Google Pay button Now that you know that the user Is ready to make a payment? You will call our second API createButton. We recommend that you use this API To ensure the Google Pay branding is used correctly per our latest guidelines In the future.
We will also Automatically translate the button text based on the user’s location. Once you add the button to your site, And the user clicks on the button, you will call the loadPaymentData To open up the payment sheet, You can construct The paymentDataRequest object, which is a set of payments configurations, Used for this particular transaction, You can specify and request The following information: in addition to the payment credentials, email phone number Shipping address billing address.
We recommend that you collect As little information as necessary to prevent users from typing Additional information which might not be stored, In their accounts, One more point to call out in this object is the payment request. Tokenization parameters: Google, encrypts information, About a shopper’s selected card for secure processing, By a merchant’s gateway or directly on a merchant’s, secured servers Be sure to check your processor’s Integration guidelines to find out what they need: To finalize the payment Now that you’ve constructed The request object: you will pass it to loadPaymentData, an async call which will open Our payment sheet, Once the user, makes a selection, we will return to you a paymentData object which consists of metadata About the user’s selection, It also includes the payment token, which you can use.
To complete the transaction, Now you can send The final production-ready app to Google for a final test: Google tests, the apps with real cards And informs you if everything is correct, The app is then cleared to launch. You can find additional information. In our developer, documentation on g.Co/pay/api Don’t miss any future articles. About Google Pay, Chrome and Web and subscribe to the Google Chrome Developers blog If you’re reading on a mobile tap the little bell to receive New upload notifications See you soon: ♪ ( music ends ) ♪,