Tag Archives: Google Pay

Wallets, APIs and Trust

Posted on by
1

6 Page Blog

Top of mind today are Wallets, Identity and Application Program Interfaces (APIs). APIs are the core concept behind many new business models investors must decipher:

  • Software as a Service (SaaS)
  • Payments as a Service (PaaS)
  • Banking as a Service (PaaS)
  • Open Banking – PISP, AISP, ..etc
  • Account Aggregation – FDX, Plaid, Akoya, … etc
  • Payment Service Provider (PSP) – Stripe, Adyen, PYPL/Braintree, … etc

Previously, I’ve covered this topic in Open Banking and Open Payments and Trust Networks (2020)  Part 3 – Internet 2.5 (2022), Modularity and Trust (2022) and Evolution of V/MA – Moving Beyond Cards (2021). Summary points from these previous blogs:

Continue reading →

Google’s Browser Tokens Payments

Posted on by
2

Short Blog – Chrome AutoFill 

I missed a key development 6 months ago: Google’s Chrome autofill began using network tokens in May 2022 (see article) after the Google Wallet relauch which was announced as part of Google I/O. Google now allows issuers to provision cards to the mobile device and to the browser desperately (see Web Push Provisioning) using network tokenization services (VTS/MDES).  I discussed this in detail in my 2016 post Browser Tokens. 

A Correction to previous blogs. Google’s Chrome autofil has network tokens, but (within the US) does not obtain a liability shift. For Google autofill to get a liability shift (within network rules), they would need to enable the 3DS 2.2 authentication features. Exceptions to 3DS 2.2 are where Issuer has provisioned card with Cryptogram (ie ApplePay card provisioned into wallet by bank). See Mastercard API doc for detail.

Continue reading →