Wallet Configuration Guide

Choose the correct wallet type based on your integration with Verifone. This guide maps each option in the Create Wallet screen to the right integration path.

---

Integration types at a glance

Verifone supports three integration paths. The wallet type you select must match the integration your storefront uses.

💻

Checkout / HPP

Verifone-hosted checkout page. Transactions are routed through the Checkout API.

Apple PayGoogle PayVippsMobile Pay

⚡

eComm API

Direct API integration. Your backend communicates with Verifone's eComm API.

Apple PayGoogle PayVippsMobile Pay

📱

In-App SDK

Native mobile integration using Verifone's iOS or Android SDKs.

Apple Pay

---

Which wallet type should I select?

Follow the decision flow below based on your integration method.

Apple Pay

Apple Pay has three distinct configuration paths depending on your integration.

🖥️ Checkout API / HPP

You use Verifone's hosted checkout (Checkout API / HPP).

Select "Apple Pay for Web" as the wallet type. No additional checkbox is needed. Transactions will be routed through the Checkout API automatically.

→ Select: Apple Pay for Web

⚡ eComm API

📱 Mobile SDKs

What you'll see in the portal

Create Wallet - Wallet type

🔵 Apple Pay for Web

Checkout / HPP integration

Leave the checkbox below unchecked. Apple Pay transactions route through Verifone's hosted checkout.

---

Enable Apple Pay for web via direct API

eComm API / Server-to-Server

Check this box if your backend calls Verifone's eComm API directly.

⚪ Apple Pay in App

In-App SDK integration

Select this for native mobile apps using Verifone's iOS or Android SDK.

Google Pay · Vipps · MobilePay

These wallets share the same configuration. Both Checkout and eComm API integrations are supported with a single selection.

Select the wallet you want to enable

Google Pay / Vipps / MobilePay

Simply select the wallet type. The same wallet configuration works for both the Checkout API / HPP and the eComm API / server-to-server integration. No additional checkbox or flag is needed.

Checkout/HPP eComm API

Key difference: Apple Pay requires you to distinguish between Checkout and eComm API integrations using the "Enable Apple Pay for web via direct API" checkbox. Google Pay, Vipps, and MobilePay do not — a single selection covers both integration paths.

---

Complete configuration reference

Use the table below as a quick lookup when configuring wallets.

Apple Pay

Your integration	Wallet type to select	Additional setting
Checkout / HPP	Apple Pay for Web	None
eComm API / S2S	Apple Pay for Web	☑ Enable Apple Pay for web via direct API
In-App SDK	Apple Pay in App	None

Google Pay

Your integration	Wallet type to select	Additional setting
Checkout / HPP or eComm API / S2S	Google Pay	None

Vipps

Your integration	Wallet type to select	Additional setting
Checkout / HPP or eComm API / S2S	Vipps	None

MobilePay

Your integration	Wallet type to select	Additional setting
Checkout / HPP or eComm API / S2S	MobilePay	None

---

Apple Pay — Domain verification (eComm API)

When using Apple Pay with the eComm API / server-to-server integration, you must complete domain verification with Apple before transactions can be processed. This is required when the Enable Apple Pay for web via direct API checkbox is checked.

⚡ Applies to: eComm API / Direct API integration only

If you use the Checkout / HPP integration, domain verification is handled by Verifone automatically. You do not need to follow these steps.

1

Set your Merchant URL

In Verifone Central, navigate to your Organization details and make sure the Merchant URL is set correctly. This is the domain where Apple Pay will be presented to your customers.

Critical: The domain must not include the https:// protocol prefix. Use only the bare domain format. Apple will reject the onboarding if the protocol is included.

Correct www.yourdomain.com	Incorrect https://www.yourdomain.com

2

Download the domain verification file

From the Wallet information section of the Create Wallet screen, click the "Download verifyDomain.txt" button. This file is provided by Apple and is unique to your merchant configuration.

3

Host the verification file on your domain

Upload the downloaded apple-developer-merchantid-domain-association file to your web server so that it is publicly accessible at the following path:

# The file must be reachable at exactly this URL: https://[YOUR_DOMAIN]/.well-known/apple-developer-merchantid-domain-association

For example, if your domain is www.paybylink.com, the file must be accessible at:

https://www.paybylink.com/.well-known/apple-developer-merchantid-domain-association

Make sure the .well-known directory exists on your web server and that the file is served without any redirects. Apple's verification bot will perform a direct GET request to this URL.

4

Verify the domain in Verifone Central

Once the file is hosted and publicly reachable, go back to the Wallet view in Verifone Central and trigger the domain verification. Verifone will communicate with Apple to confirm the file is accessible. Once verified, your Apple Pay wallet is active and ready to process transactions via the eComm API.

---

Apple Pay — Checkout / HPP integration

If you selected Apple Pay for Web without checking the "Enable Apple Pay for web via direct API" checkbox, you are using the Checkout / HPP integration. In this case, Verifone handles the Apple Pay domain verification and certificate management on your behalf. No additional onboarding steps are required — simply click Add Wallet to complete the setup.

---

Apple Pay — In-App SDK

If you selected Apple Pay in App, the integration is handled through Verifone's native mobile SDKs. Domain verification is not applicable for in-app integrations. Refer to the iOS SDK documentation or Android SDK documentation for setup instructions specific to your platform.