Apple Pay

Apple Pay lets your customers pay with a card they've already saved to their iPhone, iPad or Mac, confirmed with Face ID, Touch ID or their device passcode. There's no card number to type, no CVV to find and no form to fill in.

Apple 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, an Apple Pay button appears alongside card entry.
3. They tap it, check the amount, and confirm with Face ID, Touch ID or their device passcode.
4. The payment is confirmed and your customer returns to your site.

Enabling Apple Pay#

Card has to be enabled first. Apple 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.

Apple 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 Apple 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 Apple Pay on your own checkout page rather than an Ozow screen, that's a separate build using the Embedded Wallet, and you must verify each domain you'll display the button on. 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 Apple Pay. If you're building a standalone button, use card's; the Apple Pay button appears on the card payment screen alongside it.

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

Domain verification applies to your own checkout page. On the Ozow payment page there's nothing to verify. In the Embedded Wallet, Apple validates your top-level checkout domain, so each domain must host the association file Ozow supplies. See Apple Pay setup.

Outside Safari, the button hands off to a device. In Safari on macOS or iOS the native Apple Pay sheet opens. In Chrome, Edge and Firefox, including on Windows, the button opens a QR code sheet and your customer completes the payment on an iOS 18 or later device.

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 Apple Pay#

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

• Redirect to Ozow
• Embedded iframe
• Embedded modal
• No code payment requests
• Plugins and platforms

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.

→ Embedded Wallet

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

Also here#

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