Ozow Hub

Google Pay

Google Pay payments through Ozow.

  • payment-methods
  • money-in
  • card
  • google-pay
3 min read
On this page5 sections

Google Pay lets your customers pay with a card they've already saved to their Google account, confirmed with a fingerprint, their screen lock or their device passcode. There's no card number to type, no CVV to find and no form to fill in.

Google Pay is a card payment underneath, so everything on the Card page applies to it too.

How your customer pays

  1. Your customer reaches the payment step.
  2. If they're on a device and browser that supports it, a Google Pay button appears alongside card entry.
  3. They tap it, check the amount, and confirm with a fingerprint, their screen lock or their device passcode.
  4. The payment is confirmed and your customer returns to your site.

Enabling Google Pay

Card has to be enabled first. Google Pay sits on top of card, you can't have it without card. If card isn't enabled on your account yet, start there: see Card.

Google Pay is then enabled separately. It isn't switched on automatically with card. Speak to your account manager to have it added to your account.

Once both are enabled, the Google Pay button appears on the Ozow payment page for customers whose devices support it. You don't need to change your integration.

If you want Google Pay on your own checkout page rather than an Ozow screen, that's a separate build using the Embedded Wallet. The integration guide covers the setup.

Things to know

It behaves like a card payment. Chargebacks, refunds and settlementSettlement Ozow paying the money you have collected into your bank account. Payins arrive at Ozow first and are settled to you on a schedule, so what a customer paid you today and what has been settled to you today are different amounts. all work the same way as card, because that's what it is. See Card and Refunds.

There's no separate institutionId for Google Pay. If you're building a standalone button, use card's; the Google Pay button appears on the card payment screen alongside it.

Google sets its own button rules. How the Google Pay button looks, how big it is and where it sits are governed by Google's published brand guidelines, not by Ozow. Follow theirs. Ozow can't grant an exception.

There's no per-domain onboarding with Google. Google validates the Ozow iframe origin, pay.ozow.com, which is already approved. Enabling Google Pay on your Ozow merchant profile is what the Embedded Wallet needs from you. See Google Pay setup.

The Embedded Wallet is a web SDK. It isn't supported inside native iOS or Android applications. For payments in a native app, use Redirect: One API or web view.

Integrating Google Pay

On the Ozow payment page, there's nothing to build. Once card and Google Pay are enabled, the button appears automatically wherever your customers reach the Ozow payment page:

On your own checkout page, use the Embedded Wallet. It renders Google Pay, Apple Pay and card entry in an iframe on your page. This is a separate build with its own requirements, including content security policyContent Security Policy A response header listing the origins a page is allowed to load scripts, frames and other resources from. A policy that does not name Ozow's origin blocks an embedded checkout, and the browser reports it in the console rather than on the page.MDN allowances.

→ Embedded Wallet

Google Pay button artwork must come from Google directly, under their brand guidelines. Icons for Ozow's other payment methods are in Brand assets.

Also here

Apple Pay works the same way and is enabled on the same basis: see Apple Pay.

Last updated