[MUSIC PLAYING] EDSON YANAGA: Hello, everyone. Welcome to the
very first episode of "What's in Your
Google Wallet?" My name is Edson Yanaga, and I'm
a developer relations engineer for Google Wallet. And I'm super happy to
be today here talking with you about Google Wallet,
and I can see some people here in the chat. I can see lots of comments, so
thank you so much for coming. Thank you so much for
watching this live. And just in case you're
watching it later, thank you. Thank you, too. Yeah, I hope you
enjoy the content that we'll be able to
present to you today. And if you're here watching
it live, please say hello, and please answer
our first question. Where are you watching from? And the second one is, well,
what's in your Google Wallet? And to show you what's
in my Google Wallet, I'd like to share
my screen here. So let's see what
we have to show. So in "What's in
Your Google Wallet," I'm going to show what do I
have in my Google Wallet first? And for that, let me
see my mobile phone. So I hope you all already
have Google Wallet installed in your phone. If you don't, you can just
install it from the Play Store. And if you open
it here, I usually have boarding passes,
event tickets, and other interesting
stuff in my Google Wallet. Here, for example, I have
an event ticket for an event that we had recently at
Google I/O in Shoreline that happened
almost a month ago. What else do we have? We also have here some
interesting collectible cards. For last year's Google I/O, we
partnered with the Flutter team. So they developed this
game called I/O Flip. I hope some of you
were able to check it. And during the game,
you were able to collect some interesting
collectible cards. For example, for some
of the characters, some of the special cards of
the game, we had a Phoenix Dash. And if you look here at
the back of the pass, you could see the
Phoenix Dash, the art that you had in the card,
in the physical cards or in the virtual cards. So we have some
interesting description. Dash the Phoenix,
director of tornadoes, is a creature of fire and wind. And it had 100
points in the game, and you would be able to do
some other interesting stuff with the cards if you
played the I/O Flip game. The I/O Flip game
is still available, so if you're interested,
you can just Google it-- I/O Flip-- and you will be
able to play that as well. And I can see people from
Bahrain, Germany, Austria, New York, India, Belgium. What else? Canada, Peru, Nigeria. Yeah, thank you so
much for watching us. I'm glad to see
you all here so I don't feel just alone by
myself talking to this screen. I can see a lot of people. Yeah, and some-- what else? [INAUDIBLE] is saying, "I'm
so happy Google Wallet is adding PKPASS support. Yes, now you can import some
passes from other formats into your Google
Wallet so you can have the benefit of having a
secure and easy-to-access way to access these digital
valuables in your Android phone. Isn't it nice? So Toby has like
vaccine certificates. That's-- glad to hear. Now you can easily access
that in your Google Wallet. Please keep saying hi here. I'm so happy that you're
here with me today. And since you're talking about
what you have in your Google Wallet, as a developer,
it's interesting for us to understand how
other developers were able to create these
things that you can add to your Google Wallet. And so we'll learn
how to do that today. But before I dig
into the details of the technical
implementation, let's do a very quick introduction to
Google Wallet for developers. So the world
definitely has changed. We want to do our things
virtually these days. And one of the things that are
part of this new world for sure are digital wallets. And when you think
about a digital wallet, the first thing for sure
that you think about is that, well, how can I put
my money in a digital wallet? How can I store my payment
methods in a digital wallet? And for sure, most
digital wallets allow you to do some sort
of payment with that. But I'd like to tell you
that digital wallets are much more, are more than
payments and certainly much more than payments because
consumers want to digitize their entire wallets
and other stuff that usually don't fit in a wallet
into their digital wallets. For example, a lot of users
want to digitize their car keys. They want to digitize
their hotel keys. They want to digitize
their corporate badges. They want to digitize even
maybe like your house key, so your event
tickets, your boarding passes, and other
interesting stuff into their digital wallets. And now that future
has arrived, and we're able to do a lot of
these different things. We're able to digitize a
lot of this different stuff into Google Wallet,
and that's what I'm going to share with you today. That's why we have
Google Wallet. So Google Wallet allows you
to easy and secure access to your everyday essentials. So you can just go to
your Android phone. You can quickly like tap an
icon in your lock screen, and you can access your digital
valuables in Google Wallet. And you have other benefits
like in digital wallets that you don't have. For example, if you're
using a physical wallet, if you'd like to board a plane,
if you have your boarding pass in Google Wallet and you
want to be notified when your-- when do you have
your upcoming flight? Google Wallet automatically
does that for boarding passes. So three hours, usually,
before your flight, you receive a notification. Your flight starts
in three hours, so you better hurry
up to the airport if you're not already on
your way to the airport. So if you have an event
ticket, for example, and your event ticket
has a location, well, wouldn't it be nice
if I just-- could just tap the address
in my event ticket and I already had the
directions to the venue? Well, with Google
Wallet, you can do that. So that's some of
the interesting stuff that you can do
with Google Wallet. And we made this announcement
a couple of weeks ago at I/O. But just in case
you missed it, I want to tell you right now
live that Google Wallet is soon going to be available in all
major countries and territories. So if you're just
wondering, well, when will I have Google Wallet
available in my country? Soon we will be providing Google
Wallet in all major countries and territories. And as our first
step in this race to be able to provide the best
digital wallets for Android worldwide, we made it
available in India last month. So until recently,
people from India, for example, they weren't
available to have access to digital wallet
like Google Wallet. Now they have Google
Wallet available so they can store their boarding
passes, event tickets, gift cards, offers, and other
interesting stuff in Google Wallet. And what can you do with
Google Wallet today? For example, if
you work on retail, you can create loyalty
cards for Google Wallet. So people can easily access
their loyalty information readily on their phones. You can also create gift cards. You can create offers
for your users. What else? You can also have event tickets. So you can have event tickets. You can send right now
notifications before the event. You can send directions. You can send useful information. For example, if your
event has a schedule, in the back of
your event tickets, you can put the
schedule of your event just in case there's some
change in the schedule or there's something that you
want to notify your users. If they added your event
ticket to their Google Wallet, you can send a push
notification and say to them, well, maybe the concert has been
delayed because it's raining, and it's an outside event. Maybe we will have to change the
date or maybe change the venue. So that's some of
the things that you can do with event
tickets in Google Wallet. And much more-- for example,
we also have this specific verticals for Google Wallet-- loyalty cards, event tickets,
boarding passes, car keys, and transit passes. But we also have a
generic pass API, which allows you to
create and digitize almost anything non-sensitive
and add that to Google Wallet. So the Google Wallet
API is super flexible, and you're able
to create and add a lot of different
stuff for your users to add to their Google Wallet. And now let's dig
into the details of how can I create these
things as a developer for Google Wallet? So I'm going to
switch from my slides, and I'm going to show you
some digital information here. So if you want to learn how to
integrate with Google Wallet, the best place on the
internet for you to do that is to go to our
developer documentation. So you just type
developers.google.com/wallets, and you'll be redirected
to our website. And if you want
to learn more, you can click here in the top of
the screen on documentation. You can see the
different verticals-- access, health, identity,
retail, tickets and transit, and generic. For today, because, well,
this is an event, right? This is the very first
Google Wallet live stream, "What's in Your Google Wallet?" And we're going to create
an event ticket so you can remember about it later. So if I go here into dig
into the documentation and click into
event tickets, you learn everything that you need
to know about event tickets, how passes, classes,
and objects work. For example, the
information that is the same for all your
event ticket holders should be contained
in a class definition. Some-- for example,
if you have an event, the venue is the
same for everyone. The date is the
same for everyone. The name of the event is
the same for everyone. The color of the tickets
is the same for everyone. So these kind of things
should be stored in a class. But for the information
that is specific to each one of your users, to each one
of your attendees, for that, you should be
creating an object. So the object would
represent each one of the individual
tickets that you're offering to your attendees. So we have these
different concepts that you need to learn to
be able to effectively use Google Wallet. So I strong
recommend you to read through the entire
documentation. And to get started, we have an
onboarding guide with the steps that you need to know to
be able to create that. But first step, if you want
to use the Google Wallet API to create your own event
tickets, loyalty cards, your own passes is to create
a Google Wallet API Issuer Account. So you want to issue
passes to your users. So let's create
an issuer account. If you do that, you can see
here through the documentation. But the basic steps I'm going
to just like walk you through. You go to the Google
Pay and Wallet console. You can click on the link. In my particular case, I already
have a lot of different accounts that are created for
myself, so I'm just going to click here in one of them. But if it's the first time
you're going through the Google Pay and Wallet
console, you probably see a screen like this one. The public business
name, which can be any name, the business
location where your business is located, you see that. Well, you probably read the
Terms of Service and the Privacy Policy before you click here. And you click here if you
want to get periodic emails about news or interesting stuff
happening in the Google Wallet worlds. And let's see what's
in your Google Wallets. And you continue, and that's it. I have another
business profile ready. So you can complete that. And once you created
your business profile, you see here that you have--
on the left side of the screen, you have the Google
Pay API option, and you have the Google
Wallet API option. If you're in the-- with
the Google Wallet API, you have here some-- build your first pass. If you agree with the terms
of service, which I do, which I strongly
recommend you to read before checking on this
one, and click Continue. Now we're enabling the Google
Wallet API access for you, and you're already in demo mode. So when you're first
integrating with Google Wallet, your account is what is
in what-- is in this state that we call Demo Mode. Demo Mode means that you
can't issue passes yet for everyone in the world
to use, so you restrict it. If you're in Demo Mode,
you can use the API, but you only be able to use-- to
issue passes to your own Google account and for the
other test accounts that you have here
in the console. So if you want to
set up test accounts, you would say here,
well, myaccount@gmail.com is another test account
that I want to use here with the Google Wallet API. If you do this, you'll be able
to issue passes to this account. So you have-- if your friend
or your colleague or you have a-- if you have
another Android phone, and that Android
phone is signed-- has this Google
account signed in, you would be able
to issue passes to that particular mobile
phone using this account. So in Demo Mode, you
can only issue passes to yourself and to
the test account that you add here
in the console. That's a very important
thing to note. So now we already have
an issuer account here in the Google Pay
and Wallet Console. The second step is you need to
enable the Google Wallet API in the Google Cloud Console. For you to be able to
do that, you can walk-- you can go and go
through the requirements in the documentation. I'm just going to tell here
live what you need to do. So the second step
that you need to do is for you to go to the
Google Cloud Console. Once you go to the
Google Cloud Console, you need to go here
and type wallets. Once you type wallets,
you'll be able to see here-- let's see-- Google Wallet API. You can create your Google
Cloud account for free. And actually, I think that you
can sign up for the first time, you will even get
some free credit so you can try
some other things. But it's very important to
tell you, so keep that in mind. Access to the Google
Wallet API is free. You don't have to pay anything
to be able to use the Google Wallet API. You don't need to pay anything
to start issuing passes to your users. So the requirements
are basically create the account on the
Google Pay and Business Console that I've just shown to you, and
go to the Google Cloud Console and enable the
Google Wallet API. And it's free. You won't be charged a penny if
you're using the Google Wallet API. So you click here-- Google Wallet API. And if you're going through
this step for the first time, this blue button
here will show-- will tell you Enable. So you would click here, and
you would enable the access for the Google Wallet API. In my particular case, I
already have a working account, so my API is already enabled. So that's why it's
telling me manage. But if it was the
first time for you, it would be written like--
the blue button would be saying Enable. So please have this in mind. And once you click that,
the Google Wallet API will be enabled in your
Google Cloud Console. Got it? So we already have an initial
account in the Google Pay and Wallet Console. We already have a
Google Cloud account. And we already enabled
the Google Wallet API in the Google Cloud Console. So what's the next step? The next step is required so
you can access the Google Wallet API from your code. For you to be able
to do that, we need to create a service account
and a service account key. And why do we need to do that? Well, think about it this way. The Google Wallet API exists
in the Google infrastructure. So we need to find a way
to authenticate you so we can be certain that you is you. And when you're calling
the Google Wallet API, we could have created
another entire authentication framework, another entire
authentication method. But guess what. Google Cloud already
has everything that we need to authenticate
ourselves against Google APIs. So that's why we're going
through the Google Cloud Console, and you need to
create a service account. Think about the service
account about an account for your service. In the end, it kind
of makes sense, right? So it's not an account that you
can log in into your console, but it's an account that you can
use to access Google services. And so now I'll have to
type here service account. And if I go through service
accounts, guess what. It's the first item that
I have here on the list. If you go through
the service accounts, you can see that I already have
a bunch of service accounts created because, well, I've
done a lot of Google Wallet integrations already. But if it's your first,
this list would be empty. So you can just go here and
click on the Create Service Account button. You're going to give
it a name, which is going to be What's
in your Google Wallet. Google-- the Google
Cloud Console is already creating a service
account ID because it's streaming all the spaces,
all the special characters, so you can use it later. You just need to note what
is this email address that is going to be created because
we're going to need it later in the next step. And you can do the other
stuff, but basically that's it. You just-- you can
click this button-- Create and Continue-- or you
can type-- click here on Done because all we need
on this step is to create the service account. So create the service
account, and it's created. So once you have it created, you
can see here that for me it's in the bottom of the list. And if you scroll it a
bit here to the right, you see that I don't have any
keys in my service account. Well, let's fix that. I'm going to click
here in the three dots on the right side of the screen. Click here and manage keys. My key list is empty, so
we're going to add a key. And because I don't
have any, I recommend-- you can upload an existing key,
but I recommend you to create a new one-- Create New Key. The type of the key that we
need for our Google Wallet, for the Google Wallet
API, is the JSON one. So let's create a JSON key. The key was created, and it
was downloaded to my computer. I can see here the ID, the file. And please save this
file and keep it safe because this is the
only time that you'll be able to access this key. Just in case you lose access
to this file or this file is compromised, you won't be
able to download it again. You have to create another
key and use the other one. And of course, you can go
here through the Console. You can expire your keys. You can create new ones. You can delete one of the keys
if it has been compromised. So you can do all the
security stuff here. And please be aware that
your key can expire. So just as a good
security [INAUDIBLE] you need to write it down when
your key is going to be expired. And you just go put a
notification in your calendar so you can tell, oh,
before your key expires, you need to move
that or else you won't be able to issue
your passes with an expired credential. So that file is going
to be used in our code to be able to issue
passes for Google Wallet. So what else? We have the key,
and remember that I mentioned that we need the email
from the service account key. Let's copy it now. So this is What's in Your Google
Wallet [INAUDIBLE]-- this email. I'm just going to click here. I'm going to copy the
email, the service account. And I'm going to go back here
to the Google Pay and Wallet Console, click on Users. And I'm going to invite a user. And I'm going to give
the email that I just copied from the service account,
and access level is developer. And I'm going to invite this
service account to my Console. So now, when I
use that file that contains the key to
my service account, that service account
is authorized to use the Google API-- the Google Wallet API-- for my issuer. And then we should
be good to go. And I did all of
these steps because I wanted to show how to onboard
with the Google Wallet API. But for demo purposes,
because I want to show that everything
would be fine when I'm showing you the
stuff that I'm doing here, I already have another key
that I know it's working. I already have another code
that should be ready to go. And the-- so I'm going
to use that in my code. And I don't know, which language
do you use for development? And you can tell me
here in the chat what is your favorite
programming language, but I'm a Java developer. I know some people
would complain. I might be making bad life
decisions, but I do enjoy Java. And I've been a Java
developer my entire life. That's why I'm going to show
you the code to create a Google Wallet pass using Java. But just in case you
use any other language, well, don't worry. Because it's a REST
API, technically you can use any programming language
to issue passes with the Google Wallet API. But also, if you want
to go the easier way, we also provide client libraries
for many different languages. So if you want to
learn more about how to integrate with
Google Wallet, you can go back here to the
developer documentation on the developer side. For example, go through
the client libraries. If you go here through
the client libraries, you can see that we have the
official Google API client libraries for Google Wallet. If you click here on this link,
you notice that we have already client libraries for the Google
Wallet API pre-built for you for Java, Python, PHP, .Net,
Javascript, Objective-C, Dart, Ruby, Node.js, and Go. And you're not limited to these
ones because as I said before, it's a REST API. So you can also go through
the REST documentation and just issue your passes
using plain HTTP plus JSON because the Google API uses-- the Google Wallet API
uses REST plus JSON as a form of communication. But as a Java developer,
I would click here on Java and say, oh, I have this. It's here, the how can I use it? And if you're a Java person
and if you're using Maven, it's just a matter of adding
this particular dependency to your Java project. So that's what I did in
one of my sample projects. Another thing that
I want to show you that makes it really easy to
create your first pass using the Google Wallet
API is that you can go here through the
developer documentation. And you see that I've clicked
here in the client libraries. You can say-- click here
in the pass builder. And you'll be able to
create your first pass using Visual Tools. Well, I know. JSON is fine. We can create our event
ticket definition using JSON. But I think it's
much easier for us to create our very first
pass using a visual builder. So you can see here that I have
a form, and I have some images. I can say, well,
the header is going to be Google Wallet,
and the event name, it's called What's in
Your Google Wallet? The name of the event, the date. Well, the date,
let's pick it today. It was today at noon,
at least my time. I don't know, it might be very
early or very late for you. But for me, it was
noon when it started. And I can customize the
other information here, for example, the gate, the
section, the row, the seat. Most of the information
is optional. You can go through the developer
documentation and the reference documentation and see
what are the mandatory and the optional fields. The barcode type, just
leave the default one. I can change the
background color. I don't know what kind of-- well, you can see
here the border of our screen is yellow today. So let me get a yellowish tone. Actually, I can try to reproduce
the same-- exact same color. I'm going to choose
here the color picker. And yes, this is
the exact same color that I have here
in our live stream. And you might be
wondering, how can I customize the color here of the
fonts in my Google Wallet pass? Well, we already have
a built in algorithm. So depending on the
properties of the color, if it's lighter or darker-- for example, if it's
a lighter background, the font will be black. If it's a darker background,
the color will be white. So it's automatically. And we could also be
defining here our image. We can find some interesting
Google Images to be used here. We can have the logo image here. We have some brand guidelines
that you need to follow. But for our very first
pass, it looks good. And guess what. When we use the pass builder, we
got the entire JSON definition of our objects and our
class already here. So if you're using, for
example, JavaScript Integrates, you should be good. If you're using the
Java client libraries, you would be able to
copy the properties and use that in
your own Java Beans to be able to create
your definition. But you're going to integrate
directly with the REST API. So if I go here
through my code, I want to copy that JSON
definition directly. So just go through
my screens, and I'm going to copy the
class definition. I just click here on this
button-- very practical-- and it's copied to
my clipboard and then go here for my screen class. I just copied the class here. Now I'm going to go here
for the object definition. I'm going to copy it,
paste, and I think I'm done. Yeah, let's run my code to see
if I can create a Google Wallet pass. So now my code is running. And yeah, it's done. When you run your code,
basically what you're doing is like you're creating
a jot with the definition of your pass, and
you're signing it with your service account key. When you do that, you
should be able to create an Add to Google Wallet URL. This Add to Google
Wallet URL is the one that you share with your users
with an Add to Google Wallet button. So when they click
on the button, they will be
redirected to the URL that you created with your code. So this code is a signed
jot, and I'm just going to click here on this link. And when I do that,
well, you can't see because it opened
in my other screen. But I'm going to copy
this link, copy this URL, and I'm going to open
here in my browser. So you can see that
it's a very long URL because it contains your pass
information and your pass signature. And you can see here that it's
available here in my browser. And I can view the ticket
because it was already added in the other screen. But what you didn't notice is
that once I clicked on the Add to Google Wallet, it-- and I did everything here
in my desktop computer. I clicked on the Add to
Google Wallet button, and it was
automatically added here in my Google Wallet
on my mobile phone. So just in case you
missed, I'm going to do this again because this is
a very cool thing about Google Wallet. So I'm going to go here
in my Google Wallet. I'm going to delete my pass. Remove it so it's not
available in my Wallet anymore. And now, I just want to do this. You can see here, left
side, my desktop browser. Right side, I have my
Google Wallet on my phone that I'm sharing
my screen with you. So when I click on the Add
to Google Wallet button, I should be redirected to
this screen on the left side. So when I click here
on the Add button, this ticket was added
to my Google account. And when I do that,
it is automatically shared with all my devices that
have my Google account sign in. So on the right
side of the screen, you've just seen that I
received a notification saying that a new event
ticket, a new pass, was added to my Google Wallet. And it's already available
here in my Google Wallet. So you can add
your event ticket. You can add your pass in your
Google Wallet in any device that you're already signed in. And for most types
of passes, they will be shared automatically
across your devices as long as they're signed in
in the same Google account. You can see I'm logged
in in the same Google account in both devices-- my desktop and my mobile
phone-- and the same pass is shared over there. And it's here. You know what's better? Let's try to make an
update to our pass. So what I'm going to do
here, I'm going to go back. I'm going to go back
here to my code, and actually, I'm going to
go here to my pass builder. And I didn't like
the background color. The background
color here, I think it was maybe too yellowish. So I'm particular--
I'm a blue person, so I like the blue color. So I'm going to pick here
this particular type of blue. So I prefer the blue
pass with white fonts, and think it feels better. It feels better my style. So what I'm going
to do, I'm just going to change the
background color of my pass. So I'm going to pick
this particular color in the hexadecimal-- in hex. I'm going to go back
here to my code, and I'm going to
find a property that defines the background color. See, I just changed it in my
code, the background color, and I'm going to run it. But I need you to pay attention
because I need to quickly move here, here to this screen. So I'm going to run the code. And I'll keep you running
while I'll switch the screens. Started it to run,
and so my code is running in the background. So in the background, I'm
sending a new pass definition to the Google Wallet API. And in this new
definition, I'm saying that the color of
the pass has changed. And once I do that, the color
definition that is already available in the Google
Wallet API will say that, well, your pass doesn't have a
doesn't have a yellow background anymore. Now it has a blue
background available. So the propagation
time, it varies depending on the network,
on the device, on the day. It depends on a lot
of different factors. But you can almost be certain
that if I as a developer change the pass definition in
the background using the API, it's very likely that
the next time your user accesses the pass,
it will already have an updated information. So let's try to click here in
my mobile phone in the pass that I just updated. So you can see here it still
has a yellow background on the main screen. But once I click
there, it's updated. So now it has the latest
information available. And this kind of-- it works
for any kind of information. I change the background
color because it's like-- it's nicer as a demo. But I could have changed the
location, the time, the title, the-- for example, I could have
gone through my system, and I bought an upgrade. So I want a better seat, but
I'm already at the event. I just go through the
website, I pick a better seat, and my event ticket is
automatically updated. How cool is that? And all you have to do is
just to send a put request to the Google Wallet API. Or you can go through
the client library and say update the
pass information, and all your users' passes
will be updated automatically. And just in case you have to
deal with millions of passes, just like some of our
partners, well, you also have the option of using
the bulk update API. So you don't have to
issue one HTTP request for each one of those tickets. In this particular case, I
changed the background color, which is a property available
on the class of the pass. This means that the property
is shared with all the passes that would have
created for all users. But just in case
you're creating-- you're changing an information
that is specific to multiple different users, you could have
used what we call the Bulk API, which allows you to batch-- I think it's up to 5,000
requests in a single HTTP request, which, of course,
improves your scalability a lot. So this is what I did
with the plain REST API. If you wanted to do
something, for example, with the client libraries,
you can do that as well. If you go here for the code,
of course, it's a lot of code. This one I have
typed in previously, but I downloaded the client
library from the developer documentation. I added here the
Java dependency. Remember, I'm a Java developer,
but if you're using node.js, Go, Python, PHP, Objective-C,
.Net, and many other different languages, you already have the
client library for your favorite programming language available. I just download it, added
it here to my project. I went through the code. I typed all the
information that I wanted. And in this particular
case of Java, I just said service, event
ticket objects, updates and then went through the API. So in the end, I
would have here, what? An Add to Google
Wallet link that I could have shared with my user
through SMS, through email, through an app, or
through a website. You can use multiple
different channels to share this information
with your users. So what else can we do
here with Google Wallet? And, of course, I
created an event ticket. You can do other different
stuff with Google Wallet. Let me maximize here. You could you create, for
example, generic passes. If you don't have
a particular use case that fits in the verticals
that you already have available, you could be using
a generic pass, or you could be creating
boarding passes. You could be creating
transit passes, loyalty cards, gift cards. You could-- health insurance
cards, COVID cards, campus IDs, car keys, corporate badges. Basically, your
imagination is the limit for when you're thinking
about the different use cases that you can use to add
stuff to your Google Wallet. And now that I've shared most
of the presentation with you, I think we covered the
basic steps of integration. By the way, I said when we are
integrating here in demo mode that you can only issue
passes to your own account or for the accounts that you
added here in test accounts. When you're ready,
you integrate it. Yes, my project is-- my software is
working great, and I'm ready to tell the world that
I have a Google Wallet API integration. How can you move to production? Well, once you do
that, you click here on the left side of the screen. You can contact support and
Google Wallet API integration and say that-- you can type, for
example, other and say I'm ready to go into production-- to production using
the Google Wallet API. And the support team will reach
back to you, and don't worry. Our support team
does a great job. You'll be contacted
very shortly. They will provide
you the requirements because we don't want people
issuing counterfeit passes. We want to make sure that your
business use case is legitimate. That's why we go
through this procedure that we need to validate what
you're creating with the Google Wallet API. And if you're doing
something like legitimate, you don't have to worry
about it because it's going to be a very smooth process. And in just a
couple of days, you will be ready to start issuing
passes with the Google Wallet API. And I think that's all. You've seen that I was able to
show you from zero to almost production environments
using the Google Wallet API in less than 30 minutes. So, of course, you need to learn
to go through the documentation. How does the properties work? You need to create
your own custom paths with your business
requirements, your own business logo, your hero. You have to go through
the design team. But for you as a developer,
it's super simple to integrate with
the Google Wallet API because we have very few steps,
and the API is super simple. You just create. You send a post
or a put request, and your resource is available. You sign the Jot
definition that you just created with your
pass information, and you share it
with your users. And they are ready to
add your beautiful pass, your super-useful pass,
to their Google Wallet. And now that I've been
through the technical part, let's see if we have some
questions that we can answer while we're live here. Zyolluax is asking here-- will Google Wallet get
a P2P payment option now that Google Pay
doesn't in the US? Well, I think that would
be a very good question to be answered by
the Google Pay team. To be honest, I don't know
what they have planned, and I'm not the right
person to answer it. Maybe when we have
another episode about, well, what's the difference
between Google Pay and Google Wallet, for example? I know that a lot of
you might be wondering, what's the difference? Well, guess what. We'll have an episode
just to answer these particular questions. So I'll pass it-- I'll save this question. And I'll be able
to answer that when we have the right people
here in the live stream. Let's see if we
have anything now. I'm going through the comments. You have a lot of comments. I'm going through the
questions as well. Let's see. Hardeep here is asking why is
Google Wallet not available on Wear os in India? Well, Google Wallet is already
available in Android phones. And I can't tell you when or if
it will be available in Wear os. But I have a team working
for India-specific features, so you can stay tuned. I don't know if we shared
the link here in the chat, but if you subscribe to the
Google Wallet newsletter, you'll be notified when
any new features arrive for Google Wallet in
your particular country and in other countries as well. So stay tuned. We're always making updates
to the Google Wallet API. We're always making updates
to the Google Wallet app. So maybe if your particular
feature or country or environment is
not available yet, it can be soon available because
we're constantly making changes and making new announcements. And what else? Let's see if I have
another question. Hasan AlDoy is asking
any countries roadmap? Well, I can tell that
the product team probably has a roadmap. But as I said
before, soon we will have Google Wallet available
in all major countries and territories. India was the first one launched
last month, in May 2024. And I can't answer because
I'm not the right person to be answering this question. But there is a
roadmap, and soon you should be seeing more countries. I think they're going
to do that in phases, but I don't know
which countries are going to be enabled in
which phase at least yet. But as soon as we have
any information about it, we'll be publishing this
information in the Google Wallet website. We'll be publishing this
information in the Google for Developers blog. We'll be posting that on
our social media channels, and very likely I'll be
announcing these countries in this very-- your new favorite
Google Wallet live stream. So if you just stay tuned, if
you subscribe to our channel-- so subscribe to our
social media accounts. And if you stay tuned with
the upcoming live streams, we'll for sure announce anything
that's happening here again. And Manjesh Singh is asking here
how to make a QR code for Google and how to work it. Well, I suppose you're
asking how can I create a QR code that you
can use with Google Wallet? And the fun thing is that
Google Wallet supports many-- I can't say for sure
if all of them-- but I'm sure that many different
types of barcodes and barcodes-- barcodes and QR
codes are already supported by Google Wallet. So most of the
time, for you to be able to use your QR
codes in Google Wallets, you just need to go through
the Google Wallet developer documentation. And when you type here,
for example, the barcode, you can choose which type
of format do you want. Here in my screen, if you
go to the Pass Builder, you can just go through
the barcode, the type, and you can type a QR code. And you can even type,
for example, a URL. And you can type something
here, and a barcode or QR code will be encoded automatically. So you don't have to
worry about creating an image for Google Wallet. The image will be created
automatically for you. So that's another interesting
feature about the Google Wallet API. Benovi Engineering
is asking here, I have heard of Google
implementing biometric passport option for Google Wallet. Will it be available worldwide? And the answer is
that I don't know. And even if I knew, I don't
know if I can comment on that. So I'm not authorized to discuss
like the launch of new features, but I'm here to tell you how
to use the existing features of the Google Wallet API. But again, if and
when it happens-- well, I can answer
neither of them. But if it happens
and when it happens, it's going to be announced in
all major channels, including this particular live stream. That's why I'm encouraging you
to subscribe and to stay tuned in this live stream
because we'll be telling about the new
features of the Google Wallet API. And what else? Rohit Saini is
asking us, will we be available to
contribute in it? Well, we're
accepting-- one thing that didn't show is that we
have a GitHub repository. So if you go to
github.com/google-wallet-- and I can even here post
in the chat for you. And I just posted it. It's just waiting to go through. If you go-- if you
look at our GitHub, you see that we have
many different repos, and they are all open source. And they're just waiting
for your collaboration. For example, we have a
REST samples repository. If you want to learn how to
code using the Google Wallet API in .net, Go, Java,
node.js, PHP, or Python, we already have samples
available here for you to try. And if you have
any other language that you'd like
to contribute to, if you found a bug, if you
have a new feature that you like to help us with, well,
please send a pull request. And I'll be more than happy
to review it and maybe probably accept it. And besides that, we also
have some other interesting like Flutter plugin. We have some code labs, we
have other interesting things in our GitHub repo. You can take a look at
everything that we're doing, and if you find anything
interesting, please help us. You create an issue-- create
issues, send pull requests. We're happy to have your help. Contactless
Connoisseur is saying that will you be updating
the Google Wallet website? Some of the information
there is outdated. We're constantly updating
the Google Wallet developer documentation. If you found any
outdated information, please report it to me so I can
work with the documentation team and have it up to date. We're-- like, we need your help. If you find anything that you
think that we can improve, we're more than happy to get
your feedback and work on it. Yeah, because, again,
Contactless Connoisseur is saying that claims IDs
are still only in Maryland and car keys are
only for BMW cars. Yes, it's out outdated because
mobile driver's license are already available
in other states, in states other than Maryland. I think in Arizona
it's already available, and I think we have
other two states also. So yes, we need to
have it updated. Let's see, what else
do we have here? Rohit Sahini is asking,
can we use it in web? Yes, and actually, what
I just did in the demo that I showed you is
that I used the REST API. When you use the REST
API, what you get back is basically a URL that
you can share anywhere. You can share it in a web. You can share it in emails. You can share it in SMS, and you
can share that in Android apps, too. So the-- other we have two
different types of integration. We have a REST API
integration, which means that it's a
back end integration. And for most purposes, this
is the recommended way for you to integrate with the
Google Wallet API. But just in case you're
an Android developer and you want to perform
the integration directly in your Android app, we
also have an Android SDK. So you can do that
using the Android SDK. But to be honest, I think most-- like I don't have
an exact number-- but I wouldn't be
surprised if more than 80% or 90% of the developers
integrating with the Google Wallet API are using the
REST API for the integration. So the default one-- REST. But just in case you
have some specific users, you can do that in the
Android SDK as well. And why I'm telling that? Because it's-- the more ways
you share your passes with your user, the better. I mean, super nice,
you should be doing, you should be sharing your
passes through your Android app. But you also should be sharing
your passes in your website. You should be sharing
your passes in the emails you send to your users. And if you integrate
with the Android SDK, you can only do that
for the Android app. If you integrate with the REST
API, you can do that anywhere. So there are advantages and
disadvantages for both methods, as everything we do in
software development. I just want you to be
aware of the benefits and downsides of using
each one of the approaches. And Bryson here is asking,
are there any security options we can implement
with Google Wallet to improve safety and security? I'd like to say that Google
Wallet is safe and secure by default. Your information
is already safe and secure with Google Wallet. What we do have
in some countries is that we have support for
more sensitive information. So if you're storing sensitive
data in Google Wallet, we add additional layers of
security to make sure that you and only you access
this information. And we have an API
specifically for that. I've shown you how to
create an event ticket. I could have created, for
example, a generic pass. But we also have what we
call generic private pass. With generic private passes,
we have additional layers of security to make sure that
your information is accessed only by you in your device. So if you want to learn more,
you can go to our website and read about the
generic private passes API, which is another
API that is supposed-- that is more secure, even more
secure than the default security that you have available
in the Google Wallet app. And I think we covered
most of the questions. And once again, I'm super
happy that you're here with us. I hope you enjoyed
our conversation. I hope you enjoyed our talk,
our content, because I certainly did. I hope it was useful to you. And we're almost in
the top of the hour. I'd just like to take these very
few last seconds to say once again, thank you so much for
joining us in this Google World Livestream, "What's in
Your Google Wallet?" I hope you learned what's
in your Google Wallet and what you can add to your own
Google Wallet as a developer. Please check our
developer documentation. Please subscribe to our channel. Please like stay tuned
for our next live stream. I believe our next live
stream is already scheduled. So if you go in the link that
is available in the comments and go there, please like ask to
be notified about it because we have a lot of new
and great content to be shared in the
next live stream. And I hope to see you again. Thank you so much. I'm Edson Yanaga,
and I hope to see you in two weeks in our
next live stream. Bye. [MUSIC PLAYING]
