[Music]
hi i'm kevin flanagan a partner engineer
at google and i'm petra cross a software
engineer at google
today we're excited to introduce the
google wallet for android which will
soon be available in over 40 countries
with plans to expand access to all
android users globally
i'll talk about how this will affect
existing integrations with the google
pay api for passes
then we'll explore new features that let
you create any type of paths and
visually group passes together
i'll also introduce you to the new
android sdk
updates we made to the business console
and some of the other integration
options using wallet api
but first kevin is going to give you a
general overview of what google wallet
has to offer over to you kevin
thanks petra
in the last couple of years the use of
digital wallets has grown significantly
initially they were just for credit and
debit cards but now they can manage so
much more than that
like a physical wallet they can store
all kinds of tickets and passes
but unlike a physical wallet there's
never any rummaging at the checkout line
for the right loyalty card or worrying
about leaving your passes behind at home
we're excited about the wallet we've
built and we think developers will be
too that's because with google wallet
we're building a common platform that
makes it easier for device makers to
provide a digital wallet on every
android device
and developers can enable their users to
have quick convenient access to wallet
objects across the android ecosystem
in the next few months google wallet
will be available in over 40 countries
across android phones and wear os
devices
and we'll expand access for millions
more users later this year as we
continue to add countries
we know that fumbling through your phone
at the checkout line or at a boarding
gate is stressful so google wallet will
be quickly accessible from the device
lock screen and from the pull down shade
your users will be able to quickly
access their passes when they need them
and your users will never have to worry
about selecting which cards to carry in
their google wallet they can store their
loyalty cards gift cards maybe some
special offers or event tickets how
about boarding passes transit tickets
they're vaccine cards
and soon users in select areas will be
able to store their driver's license in
the google wallet
in addition to these pass types we're
excited to announce a new api that
supports passes that don't fit into one
of these types
the new generic passes api will allow
developers to digitize passes of any
kind
we've partnered with aaa on the use of
this new api so aaa members will be able
to easily store their membership cards
in their wallet
you'll also be able to offer your users
a helpful grouping feature during those
moments when more than one item is
necessary
for example say you're going to a
concert and you have your entry ticket a
parking pass
maybe you have some food vouchers
in your passes list you'll see a pass
tile with a badge showing the number of
items in that group
when you tap on this tile a carousel
will appear allowing you to easily swipe
between all passes in the group so
everything you need for your night is in
one place
and in addition to being broadly
available to android users google wallet
allows you to share wallet objects with
other google apps when the sharing
option is enabled
for example users who have transit cards
saved to their wallet will be able to
see information about their card and
balance while searching for directions
using google maps
and users can easily save their cards
and passes from gmail and photos to
their wallet
it's really important to mention that
this sharing option doesn't apply to
sensitive objects like vaccine cards
those are private to the user and stored
only on their device
driving all of these features are
powerful privacy and security controls
while it brings all of the security
features that you're already familiar
with in android as its first line of
defense such as authentication
find my phone remote data wipe and more
your users can rest easy knowing that
their valuables stored in google wallet
are safe and secure
on top of that all payments made using
the wallet are encrypted and card
information is never shared with third
parties
privacy controls allow users to maintain
full control over their data with
transparency about what is shared and
who has access to it
now petra is going to show you how to
enable these features with an overview
of the google wallet api
thank you kevin
now that you've seen the vision
let's talk about the google wallet api
formerly known as google pay api for
passes the google wallet api lets you
digitize everything from boarding passes
to loyalty programs and engage your
customers with notifications and
real-time updates
all existing developer integrations with
the passes api will continue to work
once we launch google wallet the only
thing that has changed is the new look
of the gpa save to phone button which
now says add to google wallet so if your
integration is using buttons that say
gpa save to phone we ask you to please
update these buttons to reflect the
change in branding after google wallet
launches in a few weeks let's talk about
new features in our api
the google pay api for passes supported
seven types of passes offers loyalty
cards gift cards event tickets boarding
passes transit tickets and vaccine cards
but what if you want to issue passes or
cards that do not fit into any of these
categories you may want to issue your
users other things such as membership
cards or insurance cards
we do not have a pass type for each of
these other use cases so we added
support for generic passes to the google
wallet api it's for all the cards that
do not fit into the seven already
supported pass types
the options are endless if it is a card
and has some text and a barcode or a qr
code it can be saved as a generic card
and you will have the flexibility to
control the look and design of the card
itself
you do this by providing a card template
that may contain a maximum of three rows
with up to three fields per row
you can configure a number of attributes
such as the barcode qr code or a hero
image
while generic passes can be used to
emulate appearance of any existing
supported path type such as a loyalty
card
developers should continue to use an
existing path type when available for
type specific specializations
for example you should use the boarding
pass type for boarding passes in order
to receive the benefit of flight delay
notifications and other features that
only exist for boarding passes
generic cards are different from other
path types in that they contain most of
the past data on the object not the
class
class only contains template information
object contains most of the past data
which makes it easier to rapidly develop
generic passes
here you can see a generic object it has
a small set of self explanatory fields
and this is a generic class
you can add up to three rows and three
fields per row by populating class
template info with card template
override with up to three card row
template infos
we also implemented another cool feature
grouping of passes in user's google
wallet and mixing multiple path types
together
this feature lets you issue multiple
passes to the same user
and ensure they are all displayed
together in their google wallet
you can also use this feature if you are
issuing passes over a longer period of
time for example
your user saves your event ticket and
three days later you send them a voucher
to get a free drink at the event
you can include the same grouping id in
both saves and we will make sure to
group these two passes together in the
user's wallet
you also get to control the order in
which these passes get displayed within
the group
here is an example of json web token
payload showing one offer and one event
ticket mixed together and sharing the
same grouping id
the event ticket will be displayed
within the group first because it has
sort index 1.
you can use the same grouping id in
future passes you issue to the same user
if you want to keep adding more passes
to their group
if you need to update the grouping info
of a previously saved pass or separate
one pass from the rest of the group you
can use our rest api to update the
grouping id on the object
at the beginning of this video i
mentioned that there is a new android
sdk
as you might know our existing android
sdk only supports saving offers loyalty
cards and gift cards but you've been
asking us to add support for other path
types we heard you
that's why we created a new more
extensible android sdk that allows you
to save all existing path types and also
future pass types
it also lets you mix and match multiple
path types in a single save and supports
grouping passes
this sdk receives passes in json or json
web token aka jot format
if you have already integrated with one
of our job-based apis you are already
generating the same json and turning it
into a signed jot
please note that the android sdk allows
you to only save passes from your
android app if you do need to update or
edit previously saved passes you would
still need to integrate with our rest
api
if you have already integrated with the
old android sdk don't worry there is no
current plan to deprecate it but we do
encourage you to please use the new json
or jot based android sdk
using android sdk is very easy
first you create a json payload with the
path data you can either build it within
your android app or you can fetch it
from your server
you can pass this unsigned json directly
into our sdk
or you can first turn it into a signed
jot by signing it with your oauth 2.0
service account private key
you then call the api in this case pay
client save passes jot method like so
our sdk then takes over the user
experience and guides the user through
the save flow for this path allowing
them to preview the pass and save it
once the sdk completes or the safe flow
encounters an error your app will handle
the result by overriding on
activityresult method where you can
implement your own custom behavior
we've created an android sdk codelab
which you can follow to integrate with
an android app
the codelab has more code examples
showing you how to check for
availability of the pay api on the
android device
how to handle errors and how to add
android sdk button to your app
we have also redesigned our developer
documentation to make the content easier
to follow and added plenty of code
samples to reflect additional languages
that you commonly use including java php
python node.js c-sharp and kotlin
don't forget to play with our
interactive path builder tool which lets
you fill in the fields and create your
own custom pass prototype without
writing a single line of code
you can show this prototype to your
broader team and your company before
your company decides to invest in an
integration with the google wallet api
not only will you see what the path will
look like with your company's logo and
any additional details the tool will
also generate code samples that show you
how you would build the past data
structures which we call classes and
objects
you can manage your passes directly from
google pay and wallet console previously
known as google pace business console
find the new google wallet api section
in the console's left hand navigation
bar and from there you can access your
tickets loyalty programs offers and
other passes resources
the google pay and wallet console has a
more intuitive user interface and lets
you easily navigate and discover new
features
the new google wallet api section lets
you onboard
request access to the google wallet api
create and manage your passes
validate api calls
and onboard and manage smarttap
authentication keys
very soon
we're also going to launch a trial mode
for passes
where we give you instant access to the
passes sandbox environment so that you
can develop and test google wallet api
in a safe environment
while waiting for approval for your
service account
now let's talk about your integration
options
integrating with the wallet api does not
take much time at all in fact we've had
partners who integrated and went live in
two days
you can choose from multiple integration
methods depending on where you want your
customers to be saving your passes from
if you want your customers to save
passes from your android app
integrate with our new json and jot
based android sdk
if you want your customers to save
passes from your website integrate with
our javascript web button
and if you want your customers to save
your passes from sms email and or web
then you should integrate using jot
links
for sms email or web integration
if your pass data requires more than
1800 characters you would need to
pre-insert the paths to google servers
ahead of time using our rest api or jot
post method
after you pre-insert the pass object you
only need to include its object id in
the skinny jot link that you give to
your users
this will make the resulting url
much shorter
and acceptable by web browsers
share this link with your customers to
let them save your pass to their wallets
remember you can allow the same pass
object to be saved into multiple google
wallets of multiple users
users who saved your pass
own the association to the object you
pre-inserted but you the issuer on the
actual object only you can make changes
to the object or disable it
users can only delete the pass in their
wallet which only removes their
association to your
object that's all from me over to you
kevin
thanks petra
so let's summarize
we explored how we're making wallet more
accessible comprehensive and secure for
users
we introduced support for a new generic
passes api and a pass grouping feature
and we talked about the new json or jot
based android sdk
as well as additional integration
options
and finally we shared a preview of the
updated developer documentation with
useful samples and developer tools which
can simplify your integration
we're really excited to build a great
digital wallet experience with you and
we're here to guide you through the
process
check out our hands-on workshop called
digitize any wallet object with the
google wallet api during this year's i o
thanks for listening have a great rest
of your day
[Music]
you