Take a digital wallet payment
Your users can make payments with Google Pay and Apple Pay. This page tells you how to enable digital wallet payments, test digital wallet payments, and the restrictions around diigtal wallets.
Users can use digital wallets with:
- payment links
- payments created through the GOV.UK Pay API
Users can only use Google Pay if they’re making payments in a supported browser, such as Google Chrome.
Users can only use Apple Pay if they’re making payments on a compatible Mac, iPhone, or iPad in a supported browser, such as Safari.
If your payment service provider (PSP) is Stripe, digital wallets are enabled by default. You can still disable Apple Pay and Google Pay in the GOV.UK Pay admin tool.
There are no additional PSP fees if your service takes digital wallet payments.
If you have disabled any card brands through the GOV.UK Pay admin tool, these card brands will also be disabled for digital wallet payments.
Enable Apple Pay
If your PSP is Stripe, Apple Pay is enabled by default.
If your PSP is Worldpay, you’ll need to enable Apple Pay.
Sign in to the GOV.UK Pay admin tool.
Under Services, select the service where you want to enable Apple Pay.
Select Settings.
Change the Apple Pay setting.
You do not need to ask Worldpay to enable Apple Pay in your Worldpay account.
Disable Apple Pay
- Sign in to the GOV.UK Pay admin tool.
- Under Services, select the service where you want to disable Apple Pay.
- Select Settings.
- Change Apple Pay to Off.
Enable Google Pay
If your PSP is Stripe, Google Pay is enabled by default.
If your PSP is Worldpay, you’ll need to enable Google Pay.
To enable Google Pay on a Worldpay service, you need to get a Google Pay merchant ID from your Worldpay merchant admin interface
If required, speak to your Worldpay account manager to upgrade your Worldpay merchant admin interface to include Google Pay functionality.
Sign in to your Worldpay merchant admin interface.
Go to Integration and select the Pay with Google tab.
Under Generate unique merchant ID, select Generate.
Copy the generated merchant ID.
Sign in to the GOV.UK Pay admin tool.
Under Services, select the service where you want to enable Google Pay.
Select Settings.
Go to the Google Pay setting, select On and enter the merchant ID.
Disable Google Pay
- Sign in to the GOV.UK Pay admin tool.
- Under Services, select the service where you want to disable Google Pay.
- Select Settings.
- Change Google Pay to Off.
Test digital wallet payments
Test Google Pay
To test Google Pay, you need a Google account and you must add a credit or debit card to that account. You can add a real credit or debit card, or use Google Pay’s test cards.
We will not take any money if you use a real credit or debit card.
To test Google Pay:
In your test service, create a payment through the API or create a payment link through the GOV.UK Pay admin tool.
Open Chrome on a desktop or Android device.
Sign in to a Google account.
Visit the
next_url
you received when you created the test payment or visit the payment link.Complete the test payment using a real card or a test card. We will not take any money if you use a real debit or credit card.
You can see the payment in the GOV.UK Pay admin tool and through the API.
Test Apple Pay
To test Apple Pay, you must set up Apple Pay on an iOS or macOS device. You can use a real credit or debit card.
We will not take any money if you add a real credit debit card to test Apple Pay.
If your organisation has an Apple developer account, you may be able to use Apple’s test cards.
To test Apple Pay:
In your test service, create a payment through the API or create a payment link through the GOV.UK Pay admin tool.
On an iOS device, open a browser that supports Apple Pay, such as Safari, Chrome, or Microsoft Edge. If you’re using a Mac, open Safari.
In your chosen browser, visit the
next_url
you received when you created the test payment or visit the payment link.Complete the test payment using the credit or debit card you added to your Apple Wallet. We will not take any money.
Strong Customer Authentication (3D Secure)
Apple Pay requires your users to authenticate digital wallet transactions using a secure method such as a fingerprint scan. Your Apple Pay users do not need to complete a Strong Customer Authentication (SCA) method such as 3D Secure separately.
Google Pay supports, but does not require, your users to authenticate digital wallet transactions using a secure method. Your users who do not use Google Pay’s secure authentication may have to complete SCA separately.
See the GOV.UK Pay page on Apple Pay and Google Pay for more information.
Restrictions of digital wallet payments
GOV.UK Pay cannot apply corporate card surcharges to digital wallet payments made with a corporate card.
Users cannot make recurring payments with digital wallets.
Stored cardholder information in digital wallet payments
GOV.UK Pay stores different cardholder information for digital wallet payments than standard card payments. There are further differences between payments made through Apple Pay and Google Pay.
If you rely on cardholder information as part of your service, you should not collect this information through GOV.UK Pay. Cardholder information in digital wallet payments is unreliable because of how Google Pay and Apple Pay handle payment cards.
Cardholder information | Stored for standard payments? | Stored for Apple Pay payments? | Stored for Google Pay payments? |
---|---|---|---|
Cardholder name | Yes | No | Yes, but it may not match the name on the user’s card |
Billing address | Yes, if you enable billing address collection | No | No |
Card expiry date | Yes | Yes, but this may not match the date on the user’s card | No |
Card type (credit or debit) | Yes | Yes | No |
Card brand | Yes | Yes | Yes |
Last 4 digits of card number | Yes | Yes, but this may not match the 4 digits on the user’s card | Sometimes, but the digits may not be accurate |
First 6 digits of card number | Yes | No | No |
Email address | Yes, if you enable email address collection | Yes, if you enable email address collection | Yes, if you enable email address collection |
The GOV.UK Pay API returns a null
value for any cardholder information that we do not store for digital wallet payments.
For example:
"card_details": {
"last_digits_card_number": "4242",
"first_digits_card_number": null,
"cardholder_name": null,
"expiry_date": "10/25",
"billing_address": null,
"card_brand": "Mastercard",
"card_type": "debit",
"wallet_type": "Apple Pay"
}