Google Pay | Q&A

Key Takeaways

[Music] welcome to our ask me anything for what's new in google pay my name is arshna malhotra and i have here with me socks yang and rajiva panda to help answer some of your questions hi i'm sak i'm a developer ad with google pay hi i'm rajiv apana and i lead product for both google pay merchants and online so we want the session to be as helpful as possible for you so please don't forget to post your questions just tap on the q a icon to the right side of the line livestream video on the i o website to post or vote we will choose the top voted questions and try and answer as many as we can in the session so now let's get started the first question is from mike why should i as a developer implement gpa apis how do i benefit from it that's a great question mike uh arsenal i can take this one sure look today if you if you are a merchant if you are a developer you're spending inordinate amount of time trying to optimize your checkout flows right especially mobile checkout flaws are especially hard multiple steps what we do with google pay is provide you with one click checkout experience right so there are over 150 million users who use google pay today in 40 countries they have not just a credit card information store but they also have their billing and shipping addresses all stored with google pay essentially we allow the user to click one one with one click they can share their payment information their shipping information and their billing information directly with you the merchant and the checkout experience gets really really fast so what does that mean specifically for you as a merchant it means improved conversion it means that guest checkouts will be fewer in number and they'll be much faster and then finally you can also add google page account directly to the product page so that the checkout can take place from the product page itself so removing many many steps in the entire checkout funnel so these these are some of the reasons you should use google play uh on android specifically it's a very it's a it's a native experience and it's very powerful cool thanks rajiv uh the next question is from anders is there any plan for or does that already or or does there already exist a method of using google pay on both android and ios i can take this one sure um so google pay the web integration already works for android and ios so it's available on you know modern browsers checking checking out using google pay provides a native experience on android and on ios it's an equally you know usable experience as well if we're talking about like native integrations one of the things that we've announced recently is an open source flutter plugin and while that isn't google pay specifically on ios what it will do is it will support um google pay on android devices and apple apple pay on ios devices additionally we've also made some changes um to the google pay application so that's now been rewritten in flutter and that's available on both ios and android so yes depending on what you're referring to google pay is available on both ios and android thanks zak uh so moving on to the next question uh it's from fernanda here in brazil pix is a new means of instant payment released in 2020 with picks people and companies can make transactions in less than 10 seconds 24 hours seven days a week using only mobile applications will gpa enter in this market and why rajiv do you want to take that yes i can take that uh look fernando at the end of the day brazil is a very important country for us it's a strategic priority for us as google pay in fact just in the last few years we have introduced things like support for combo cards allowing merchants to access cards that have bought the debit and credit functionality directly on the card right so what we are doing now is as we are working with the regulators to understand the functionality that pix has and understanding what needs that the marketplace might have we're trying to figure out what that means for google play and how we can support the merchant and issuer ecosystem to adopt picks so that's what we're doing now it is a strategic priority we are working with the regulators and you're going to see some interesting things come out because we are going to be investing in helping both issuers and merchants thanks rajeev um so moving on to the next one is from julia if i have already integrated with autofill for my checkout form should i still be integrating with google pay i can help you so i can add a few thoughts here suck then feel free to add more uh a few things here is so autofill basically is trying to help the user for a seamless checkout you know we try and fill in securely the car details to allow fast checkout the gpa button at the same time is helping a secure fast checkout but also goes a step forward further to help the merchant to process the transaction so in either case you need to effectively efficiently use and implement the tags or the api to get the most out of it so it's more towards the use case that you are wanting or the requirement that you're trying to accomplish to implement either or so feel free to add more yeah i mean i would just add that well done for integrating with what i feel not enough people do um and by doing that i think you you benefit from making your checkout forms a lot faster for your customers um that means that their safe details will be available and autofill i should note is different across different browsers so it's up to the browsers to implement autofill as they see fit um so the experience may vary from browser to browser what i can say is that for google pay um we we take every attempt to make sure that your card details uh and and other details uh easily available and fillable in with autofill um i think one thing to add um with autofill is is that it does make things easy um but sometimes the experience i'm sure people have experienced this as well but um because not auto not all forms implement water fill correctly the experience varies a bit so you might have an experience where some fields are order filled correctly and some aren't and you have to go through and double check with google pay you cut you can have that expectation that because we're returning the payload in a standard format that developers will handle that format correctly and therefore the details um don't need to be verified by by the user um and as as ashana mentioned um the having implemented um google pay uh the the payment credentials and the details will be encrypted and they won't be available for others to see so they're safe from prying eyes true yeah just just one last thing right uh i think the way to think about it is you have to provide customers choice right customers might want to use guest checkout they might want to log in they might want to use google pay ideally as a as a developer as a merchant you providing choice is a great thing and to and to solve what saks sock said you know autofill might not work in many cases in in some cases the checkout itself the number of steps are introduced but with the gpa api like we had talked about earlier one click checkout is possible sure you can see how passionate we are about this topic so moving on to the next question from amanda what's the difference between google play in app billing and the google pay api yeah i'm happy to take this one so the google google pay i'm sorry google play in-app billing is used for android apps that are downloaded from the google play store and it's used primarily for things like um digital purchases or um or items that are meant to be used within the app so some examples that might include unlocking certain features of the application going from like a free version to a premium or some other digital goods like if you're downloading movies and videos for use within the app um that's um that's a good use of the google play billing services um and and it goes beyond that because it's it's actually a requirement it's part of the policies when offering these apps on google play on the other hand if you're selling physical physical goods um or making purchases for things that are meant to use meant to be used in the outside world the real world other payment options are available including credit cards and um google google pay and that's so that's in the android space outside of android when it comes to web um yeah you're free to use any payment method we we strongly encourage using google pay for purchases because it makes the checkout checkout experience a lot easier but at the same time there are some apis being released on web that might suit your needs better so an example of that is the digital goods api um that allows you to use the digital goods api and the the payment methods in the paid billing services on android to be used to pay for um digital goods thanks zak um moving on uh the next question is from unis what are the plans for expanding gpa contactless payments into new regions rajiv you want to get that yeah i think i think the way to think about it is we're always expanding we expanded last year we're going to continue to expand into new new regions uh there's a lot of factors that we'll look at right the android penetration nfc font penetration as well as the number of nfc terminal penetration and those are those are the things that we'll look at while we're looking at um looking at where we want to expand i can't specifically comment on the countries that we are going to be expanding in the near future sure sure yeah um okay moving on next one is from renin is the google pay api an alternative to stripe or is it something else i'll take this one suck yeah so um google play sorry google pay api versus stripe they're they're both involved in payments but they're not exactly the same so strike for example is a payment service provider and they'll process your payments um as well as providing an api for you to use within your apps and websites so the difference between um stripe and google pays google pay will facilitate the payment so we'll we'll connect businesses with users that have card details already saved to their google account and we'll make that available across a number of different partners so we've got something like 160 over 160 different payment service providers that have partnered with us that can then take a google pay payment token to be used with um to be processed with the different payment service providers so i think stripe stripe as an example among others um will process the payment and if they do provide a library um sometimes they'll do it and provide say google pay as a payment payment method um i think you should feel free to use use them as a payment service provider with their libraries if it makes the integration easier um if you find that there's a feature that the stripe libraries don't support um then an alternative is to integrate directly from google pay pass those payment tokens payment credentials over to stripe and process the payment directly via their apis so yeah they're they're both involved in payments they're slightly different they cover different spaces but um stripe is a partner of ours and so just to add do we have developer documentation and all that we can point people to in this area yeah so we've got our development documentation site um it's got some general information there but i think the best source if you are interested specifically integrating with stripes stripes um offer really good documentation and um that's probably the the best starting point if you want to integrate google pay and strive happens to be your payment service provider great cool thanks doc oh so the next one is an interesting one uh does gb plan to support cryptocurrencies oh this is for you yes this this certainly is for me uh look in some sense we do it today right uh cryptocurrencies uh it's the hot topic it's all all over the news in some sense we do it today and the way we do it today is there are these products that exist in the market either a visa card or a mastercard that essentially pulls from your crypto balance and your use you can pay pay merchants with that right so one set of network is sought because visa and mastercard bring that multitude of merchants to the table you can now take those cards tokenize them and add them to your gpa wallet either to use for in-store or online payments so in that sense we already support crypto now for us the the next question is what about native support of crypto right that's an area that is a little more challenging we're thinking about it we're looking at it uh we want to find out it's the right use case for the user it's the right use case for the merchant and there needs to be you know broad adoption from a merchant perspective a and there needs to be a broad adoption from the ecosystem perspective and when i say ecosystems are our big partners are the psps or the payment service providers once they start supporting it you know we would we would consider adding crypto into uh into gpa as as the thing that as a sort of payment method that you as the user can add and then seamlessly pay with the merchant so complicated topic we do a little bit today with with what we have um we're expanding we're looking for ecosystem readiness before we start implementing something right right an exciting one for our roadmap right of course okay um moving on the question is from jesus uh greetings guys as is possible is it possible to integrate google pay with flutter apps is through a plugin or native code from or maybe it means is it through a plugin or native code from api yeah i can take that one so today we announced support well we announced the new um flutter plugin for for google pay you can find out more about it on pub.dev um it's also available on github so the support includes um a federated plug-in providing support for both ios and android so you can choose the the relevant bits that are important to you on on android you'll use google pay as your payment method whereas on and sorry on android you will use google pay on ios it will use apple pay and it's just been released today do check it out on github raise any issues that you have there or feel free to raise a um pull request if you're if you're so inclined cool thanks sir the next question is around subscriptions can google pay be used for subscriptions yes yes the the simple answer is yes google google pay can be used for subscriptions in fact a lot of our merchants do it today so it's not not necessarily a new use case right so the essentially what google pay does if you look at it from the back end perspective is we take the payment credential that the user stores with us we then tokenize it with the processor and we hand it to the merchant and the merchant then can send transactions to their payment service provider and capture funds from from the user on a regular basis the best way to figure out how you can you can enable google pay for subscription is to talk to your payment service provider and follow their guidelines that that that would be my sort of direction to point you in cool cool okay so the next one is sca which is a strong customer authentication one of our passionate topics which multiple you know teams have been following and working on this to get compliance so the question is is google pay compliant with ps d2 regulations for strong customer authentication which is seo as i can take that as mentioned this is one of our passionate topics we have a lot of effort that we have done on this and yes google pay is compliant with psd2 requirements it is the the cryptogram 3ds payment credential is with dynamic linking and that is true for mx visa mastercard so and also to add to that that this payment token does not need a step up from the merchant side so that basically prevents or helps uh conversion it helps reducing friction um so it and is of course secure so yes it is compliant uh and um yeah okay uh anything else to add rajiv saw yeah on this yeah i think maybe just i'll give like 30 second overview of the psd regulation for folks who don't know it uh because i'm assuming folks are joining from different parts of the world sure pst to sca is a regulation based out of europe uh essentially it means that you need to have two factors of authentication it is knowledge it's something you know it's something you have uh or uh it's something you know you something have and then what we want to do is is from a google pay perspective enable that so the way we do that is we have something called device binding which essentially means we take the the card number of the user we step it up with the merchant and we store it on the device securely so that step step one and then dynamically at the point of uh find a transaction we are able to take that we're able to pull that credential up generate a new cryptogram that essentially encrypts not just the card information but encrypts how much the user wants to spend and the merchant information so this cryptogram when we hand it back to the merchant now they don't need to do a step up they sure doesn't need to step up so it eliminates a ton of steps in that in that process yeah it makes for a much much quicker user experience yeah and just to add we're also trying to leverage biometric as much because that's something that the user is used to has it as a platform authenticator so i think like you know we're basically trying to reduce as much friction but be compliant with as much security guidelines that are being raised okay okay the next one is an interesting one how much does it cost to use google pay essentially the product that we have in market right now uh does not cost anything for you as the developer to use right uh we're different from other wallets in the sense that we don't essentially charge you as a developer you get integrating google pay essentially gets you the credentials encrypted along with like we talked about billing and shipping address when applicable will give it to you in a secure way now ultimately for you to process the payment with your payment processor there could be fees there will be fees involved and that is something for you as a developer or the merchant to negotiate with your payment processor but the google pay integration costs nothing yeah and i think to your point rajiv payment different payment providers will have different fees associated with them they also bring different things in terms of offerings as well so for example you might have some that prioritize the developer experience you might have some that prov you know prioritize the ease of integration and some that might support multiple currencies you know all over the world versus some that um some that will deal with like bricks and mortar as well as online so you need to weigh up your requirements when choosing the the payment service provider and therefore um you know the the fees associated with that it's a great point yeah sure um okay moving on a question from raj i'm using an e-commerce platform for my online store how do i enable google pay yeah i can take this one so um first some of the so there's a whole um i suppose spectrum of different e-commerce platforms you've got some that are you know fully hosted and fully managed through to what some others that you host and deploy yourself and it really depends on their setup so some some e-commerce platforms will have google pay integration out of the box um it might be even enabled by default for you some others you might have to take some extra steps to enable um including maybe downloading or enabling a payment plugin so many payment many e-commerce platforms have like a rich extension or plug-in ecosystem and um they allow other payment providers to plug in we rely mostly on those payment providers and the plugins supporting google pay but in addition to that we have recently released a a plug-in for magento community edition which allows you to enable google pay and um integrate it with i think it was something like seven different payment service providers that's something to look into but they're supported if you're really adventurous and you've got the technical ability you can also do a bespoke implementation which is you know a typical javascript backend implementation yourself provided the e-commerce platform enables that type of customization um let's take a couple of more i think we have time for that uh the next one is from cam my psp has a client library that includes support for google pay should i use my psp's library or the google pay library sock i think it's you yeah i can take this one so i i alluded to this in the previous answer around straight um so yeah i think the the short answer is yes you should be using the the pspe um library because they'll probably make for an easier integration because it will not only handle the back integration for you but also the front end um that said there there are occasions where you may want to do a direct integration even if the psp supports it so some examples for that would be if there's a feature that that's been released a new one is the custom button where we displayed the last four four digits of a user's um card if that's a feature that you want and the psp doesn't provide it one option is to do a direct integration with the google pay libraries another one might be to actually ask the psp to include support for it because it will not only benefit you but a number of other customers down the line there is also another scenario it's not too common but some some businesses may want to have support multiple psps so they might want to choose pspa for whatever reason here and pspb over there and it's hard to get those psps to play together so you might want to do a direct integration into google pay and then in the back end switch between which payment service provider you you want to target so again in short use the psps libraries if the if they work for you if you need anything a bit custom um by all means do the direct integration and call the psp when you're processing the payment thanks unk sock for the detailed answer we might be able to squeeze in the last one uh is from amanda how can i promote google pay acceptance in my app suck ticket okay so um i think there are a number of ways to do it so one of them is we've got a um the google pay mark so this is something that you can find on our developer site where um you can download the the branded artifacts to put into your your application um and the other one is actually just making use of the button like the presence of the button is a good way to to promote it and um again with the recent changes that we've made to allow the last four digits of the user's card to appear in the button it's now even more obvious to to users that they've got a payment card ready to use and you know checkout is just a couple clicks away so i think the just including it and using it is a good way to highlight the fact that google pay is available yeah just just one last one last comment there i think for android think about using google play as the default checkout that's the best practice default checkout option especially because there are so many users who already have the payment credentials stored and vaulted with us on android devices so that's been the best practice that's where we've seen merchants get the maximum success in improved conversion rates thank you rajeevan sakh we are now going to wrap up our live q a we you know just to summarize in our talk with what's new in google pay you did hear different exciting launches that we have had we are continuing to work and we will continue to focus on areas where we can provide secure transactions for both our customers and merchants we will continue to work on improving our ux we are trying to work to tr get different button strings for integrations improve our integrations for which developers can benefit and also try and improve our conversion rates for merchants by adding more value to our consumers it could be offers loyalty passes and much more so you are going to hear more from us and we are really excited that you were able to join us for our ask me anything uh for what's new in google pay so there is also there is also documentation on our on our website so please look at the developer docs reach out for any questions that you need and we will try and help you out so hope this session has been informational and useful thank you so much for joining us uh for google i o 2021 what's new in google pay thank you thank you [Music] you