Digital Wallets Overview
An overview of how digital wallets (Apple Pay, Android Pay, Google Pay) work with the Gateway, and which of the deeper wallet guides applies to your integration.
In one sentence: a wallet produces a secure payment token instead of raw card details; what changes between integration methods is how that token reaches the Gateway.
1. What the Gateway supports
The Gateway supports the Apple Pay, Android Pay and Google Pay digital wallets. Each produces a secure payment token, sent to the Gateway instead of the cardholder's actual card details. Wallets work on any merchant account configured to accept them.
Account-level prerequisites:
- Digital wallet support is not available with all acquirers, and must be enabled on your merchant account first (referred to as your "mass boarding" wallet setup).
- Contact the Gateway/acquirer to confirm support, enable a wallet, and get details on accepting the resulting payment tokens.
2. The three ways a wallet payment can reach the Gateway
| Method | How it works | Guide |
|---|---|---|
| Hosted Payment Page | Wallets boarded on your account appear automatically as buttons on the Gateway's own hosted page. No extra fields, no extra code — see §12 of the Hosted Payment Pages guide. | Already documented |
| Hosted Payment Page in an iframe | Same as above, but the hosted page is embedded in your own page via an iframe instead of a redirect/lightbox — requires Apple-specific domain/iframe configuration. | Apple Pay — Hosted (iframe) |
| Direct Implementation | You collect the wallet token yourself (from your own Apple Pay / Google Pay button) and submit it server-side via the Direct Integration. | This page, §3 below, plus Apple Pay — Direct / Gateway Merchant Validation for the Apple-specific merchant validation setup |
3. Direct Implementation — the token fields
If you collect the wallet token yourself (e.g. from an Apple Pay / Google Pay button in your
own page) and submit it server-side, send these two fields alongside the standard request
fields (merchantID, action, amount, type, currencyCode, countryCode, signature,
etc.):
| Field | Mandatory | Value |
|---|---|---|
paymentMethod | Yes | The token type: applepay, androidpay, or googlepay |
paymentToken | Yes | The secure payment token produced by the wallet-enabled application |
No additional response fields are required — read the outcome exactly as for any other
transaction (responseCode == 0 = success).
(Source: Gateway Integration Guide — Digital Wallet Transactions → Direct Implementation.)
4. Apple Pay — getting the token without your own Apple Developer account
Normally, embedding Apple Pay requires your own Apple Pay Merchant Identifier and associated certificates. The Gateway offers an alternative: use the Gateway's own credentials (a "Reseller"-level setup) so you don't need your own Apple Developer account at all. See Apple Pay — Direct / Gateway Merchant Validation for the full setup.
5. Google Pay — status
This is the one wallet without a dedicated setup guide right now. For Google Pay Direct, the merchant's own domain must be added directly to the Google Pay portal (not the Gateway's MMS), and it's unconfirmed whether Google enforces a domain limit — this should be checked before rolling it out to merchants. See Google Pay for details.
6. Quick reference
Wallets supported: Apple Pay, Android Pay, Google Pay
Token model: wallet produces a token, sent instead of raw card data
Hosted: wallet buttons appear automatically on the Gateway's hosted page
Hosted (iframe): same, but the hosted page loads inside your own iframe (Apple Pay: needs domain config)
Direct: paymentMethod=applepay|androidpay|googlepay + paymentToken
Apple Pay w/o own dev account: Gateway/Reseller-level Domain Verification File (DVF) flow
Google Pay: merchant registers own domain in Google's portal — no Gateway doc yet
Hosted Payment Fields Integration
Build your own tailored checkout page while the sensitive card inputs stay hosted by the Gateway — full layout control, same low PCI scope as Hosted Payment Pages.
Apple Pay — Hosted Payment Page (iframe)
Enabling Apple Pay on a Hosted Payment Page that is embedded in your own site via an iframe, instead of a redirect or lightbox.