Digital wallets
Digital wallet payments through Ozow.
On this page4 sections
Apple Pay and Google Pay let your customers pay with a card they've already saved to their phone, confirmed with Face ID, a fingerprint or their device passcode. There's no card number to type, no CVV to find and no form to fill in.
Digital wallets are card payments underneath, so everything on the Card page applies to them too.
How your customer pays
- Your customer reaches the payment step.
- If they're on a device and browser that supports it, an Apple Pay or Google Pay button appears alongside card entry.
- They tap it, check the amount, and confirm with Face ID, a fingerprint or their device passcode.
- The payment is confirmed and your customer returns to your site.
Enabling digital wallets
Card has to be enabled first. Digital wallets sit on top of card, you can't have them without it. If card isn't enabled on your account yet, start there: see Card.
Wallets are then enabled separately. They aren't switched on automatically with card. Speak to your account manager to have them added to your account.
Once both are enabled, the wallet buttons appear on the Ozow payment page for customers whose devices support them. You don't need to change your integration.
If you want wallets on your own checkout page rather than an Ozow screen, that's a separate build using the Embedded Wallet, and Apple Pay requires you to verify each domain you'll display it on. The integration guide covers the setup.
Things to know
They behave like card payments. 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 they are. See Card and Refunds.
There's no separate institutionId for Apple Pay or Google Pay. If you're building a standalone
button, use card's; the wallet buttons appear on the card payment screen alongside it.
Apple and Google set their own button rules. How the Apple Pay and Google Pay buttons look, how big they are and where they sit are governed by Apple's and Google's published brand guidelines, not by Ozow. Follow theirs. Ozow can't grant an exception.
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 digital wallets
On the Ozow payment page, there's nothing to build. Once card and wallets are enabled, the buttons appear automatically wherever your customers reach the Ozow payment page:
On your own checkout page, use the Embedded Wallet. It renders Apple Pay, Google Pay and card entry in an iframe on your page. This is a separate build with its own requirements, including Apple Pay domain verification and 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.
Apple Pay and Google Pay button artwork must come from Apple and Google directly, under their brand guidelines. Icons for Ozow's other payment methods are in Brand assets.
Last updated