Google Pay vaulting

Google Pay subscribers who move with you

Google Pay tokens normally live with the processor that accepted them. Leave the processor and those subscribers have to check out again. PaymentKit captures Google Pay into an independent vault so they transfer with the rest of your base.

Independent vault. PCI Level 1. Works alongside the processors you already use.

The problem

The best Android checkout is also the hardest one to take with you

On Android and Chrome, Google Pay is frequently the highest-converting option. Google Pay payments are processed through a gateway integration tied to specific processor credentials, and the stored credential that comes out of it belongs to that processor.

Lose the processor, lose the Google Pay subscribers. For a business with a large Android audience that can be a third of the base with no way to rebill.

How PaymentKit handles it

Vault the credential, not the processor’s copy of it

The credential is stored before any processor owns it, so a route change is all it takes to move the subscriber.

  1. 01

    Google Pay on your PaymentKit checkout

    Google Pay is enabled on your PaymentKit checkout (hosted, embedded, or PaymentKit.js on your own domain).

  2. 02

    Customer confirms as normal

    The customer confirms payment in the Google Pay sheet as normal.

  3. 03

    Credential stored in our vault

    PaymentKit receives the Google Pay payment data and stores the resulting credential in our vault, independent of whichever processor runs the first charge.

  4. 04

    Rebills route anywhere

    Subsequent charges route through any processor in your route that accepts the credential.

What’s required on your side

Setup

  • A Google Pay merchant ID and merchant registration in the Google Pay Business Console. PaymentKit walks you through it.
  • Checkout through PaymentKit, not through a processor’s own checkout page.

Availability

Google decides who can offer it

Google Pay is enabled by the acquirer and governed by Google’s acceptable use policy. Some categories are excluded regardless of processor, including adult content. If you’re in a restricted category, we’ll tell you up front.

Who this is for

Merchants with a large Android or Chrome audience

Subscription businesses with a large Android or Chrome audience. Merchants in markets where Google Pay share is high. Anyone who has lost a processor and found out their wallet subscribers didn’t come along. Merchants planning a processor change.

Proof

  • Independent vaulting is how the brands in our own portfolio switch processors without a churn event.

  • 20+subscription brands in our own portfolio, run on PaymentKit.

FAQ

Google Pay vaulting, answered

Book a call