Integration tips with Google Pay #AskGooglePayDevs

Key Takeaways

[Music] hi everyone and welcome to our very first episode of ask google paydevs a series of videos where we'll address commonly asked questions about integrating google pay to make it easier for us to find your questions make sure to use the ask google paydev's hashtag across twitter youtube stack overflow or any other site where you enjoy asking questions i'm jose a developer relations engineer at google pay and i'll be your host today before we start and in case this is the first time you're taking a look at the online apis for google pay i'd like to share with you three reasons for integrating google pay in your applications and websites first when you add the google play button to your website or mobile application you are simplifying the checkout flow for your customers reducing the number of steps to pay to as few as two clicks or taps this not only makes your checkout process faster but it also has an impact on your conversion performance second there are hundreds of millions of cards that have already been saved to google accounts during the phone setup process or from previous transactions with google including google play chrome and other apps and websites that have already integrated with the google pay apis what does this mean for you your users don't need to log into their accounts to pay in your website or mobile application ensuring a fast checkout process and third security when a user chooses a form of payment through google pay the payment credentials are encrypted before they leave the google servers and send to your application it is not until you send those credentials to your payment service provider that they will be decrypted to the original form to complete the payment this makes your application resilient to external vulnerabilities when you are ready to integrate you can create a business profile and submit your integration through google pays business console okay now we are ready to dive into your questions let's get to our first question of the day how to collect payments for an application listed in google play should i use playbillin or google pay there are two primary ways to accept payments if you are distributing your android application through google play google plays billing system and google pay google plays billing system is required when you're selling digital items or services within an app on google play while google pay can be used when you're selling physical items or services that will be used or deliver outside of your app such as groceries retail merchandise or food delivery note that you can use google pay to make payments easier in your application regardless of whether your app is listed on google play or somewhere else should i integrate directly with the google pay libraries or should i use the libraries from my psp you can go with the libraries which are most suitable to you to complete the integration use the google pay online libraries if you like to integrate the different payment providers separately or if you prefer to remove intermediate layers in the code and the dependencies you use using the google pay libraries directly is also useful if you want to quickly swap payment configurations and payment providers take a look at the payment data request object in the documentation to learn more on the other hand if you are using multiple features from a single psp in your application and prefer to use one library that encompasses most of the functionality and apis available many psps offer complete packages that help you with just that take a look at the documentation for your specific payment provider to find out more how to integrate google pay using a mobile or web library or framework we want to provide you with the right set of tools to help you integrate google pay in the most familiar and convenient way for you and your team if you are using generic stacks for your applications like javascript on the web and java or kotlin on android you can use our vanilla libraries to get started on both platforms take a look at g.col slash pay api to learn more we've also added support for the google play button for many popular web frameworks like react angular vue spells and many others there are framework-specific libraries for react and angular while the general purpose web component version can be used for other frameworks check out the repository on github where discussions issues and pull requests are welcome where to place the google pay button inside your checkout form add the google pay button to the product page to provide an express checkout options for users who are likely to check out with only one product we recommend placing digital wallets like google pay above your checkout form the reason is that google pay makes it easy for your customers to choose from their existing payment details like their car details and shipping addresses placing the button first means that customers won't start filling in the form before realizing that a faster alternative is available the google pay button should be the same size as other buttons on the page by default the google play button will wrap to the size of the text inside this can be customized on the web by setting the button size mode property to fill and on android what happens after i receive a payment token from google pay after a form of payment is successfully selected a result is returned back to your application or website in response to the payment data request this result contains information about the payment request and the payment method itself which in turn includes what we refer to as tokenization information this object contains an opaque payload in stream format that you need to relate to your payment processor or gateway of choice this payload holds details about the form of payments selected by your users and is encrypted using keys shared between google pay and your psp in other words only your psp can decrypt and access the contents of the encrypted payload if you are integrating google pay and hence operating in test mode you are sent back a dummy token in string format as in in the example to learn more about the payment data response returned by the load payment data requests take a look at our documentation using the link for this question in the description below how do i complete my integration with the psp the way to handle the pain and payload received from google pay will depend on how you are completing the operation with your payment processor it's important to remember that the result returned by google pay contains the payment method selected by your user the most common procedure is to use this payment method to create the order through your backend servers and from there initiate the payment transaction with your psp some psps offer alternative flows to complete a payment process one of them separates the creation of the payment method and the order allowing you to use the google pay result to create the payment method directly from your client using client libraries provided by your psp once the payment method is created you can initiate the payment transaction from your backend servers without attaching the payment method information and simply passing a reference to the object created previously all in all make sure to only issue requests containing sensitive information like or the price from your backend servers how to test my integration before publishing my application or website testing your integration before pushing them live is key to ensure a reliable checkout experience for your customers and a robust payment stack for your business to help you test your payments flows holistically we have created a set of test cards authentication methods and billing and shipping addresses that you can associate to your test accounts and use them to complete payment transactions while operating in test mode you can enable test cards quickly by flipping a switch directly from the developer documentation i have completed my integration what do i need to do next if you have already integrated google pay in your web or android application you are one step away from collecting payments with google pay in production to do that you'll need to submit your integration using google pays business console which will guide you through the process of creating a business profile and submitting and managing your web and android integrations once your integration is cleared for production all you need to do is change the environment to production and publish or deploy your application you can access google pays business console in this link what security implications are there after integrating google pay the term security in payments is present at various stages in a transaction and they all need to be considered separately let's use a familiar example to help explain the concept suppose that you develop an application that allows users to create information that only they can see like their shopping list through a password-protected user account for these accounts to be secure the overall service needs to meet a minimum set of requirements like using an encrypted connection between your application and your servers storing credentials securely or prompting your users to use a strong password among others if any of the previous requirements is not adopted correctly your system may become vulnerable and your user's information can get exposed a payment transaction also has multiple security layers which are required in order to ensure a safe payment experience for your users like encrypting payment information in transit token s card details cardholder authentication payment authorization or storing payment details securely some of these security requirements are handled by pci dss compliant third-party service providers or gateways while others are embedded as part of the payment processing stack in cad networks and other payment methods keeping that in mind your service is responsible for collecting payment details and securely forwarding them to your psp or processing stack this is where google pay can help when your customers use google pay in your application or website their payment credentials are encrypted before they're shared with you to create the order with your payment processor this means that even if your service gets compromised the user payments information is still safe in addition to that make sure to continue running your existing risk checks through your payment processor or existing in-house infrastructure when the order is created what's the difference between gateway and direct integration which one should i be using with a gateway integration you are benefiting from the work your payment service provider or psp has done to support google pay in this case the payment information returned by google pay can only be decrypted and used by your psp as mentioned earlier if your service is compromised your customers payment details are kept safe if your psp is offering a google pay gateway integration it is recommended that you use it this significantly streamlines your integration and ongoing maintenance requirements the direct integration is designed for businesses who are pci dss compliant and work with the psp that does not offer the google pay gateway integration direct payment tokens are securely shared with you the merchant because of this direct integrations are required to provide ongoing evidence of pci dss level 1 compliance and regularly rotate encryption keys and these were topics for today's session i hope that your questions were answered and if they weren't make sure to post them on twitter youtube and stack overflow using the ask google paydevs hashtag so we can feature them on one of the upcoming episodes thank you for watching and i'll see you next time