Digital Wallets
Digital wallets are secure applications or services that enable users to electronically store payment details, such as debit or credit cards.
Digital wallets such as Apple Pay and Google Pay are accessible with smartphones, computers, or directly in web browsers. Digital wallets allow customers to pay for goods and services both online and in physical stores without a physical card, often using biometrics, a device passcode, or a wallet login, and approve the payment in a few clicks.
For online transactions, the wallet securely passes a payment token to the merchant or payment processor. You do not handle sensitive customer data directly. This reduces friction at checkout, improves conversion rates, and enhances security through built-in authentication and tokenization.
Wallets are best suited for one-time online purchases and express checkout experiences. Support for subscriptions and recurring payments varies by wallet, so you must confirm compatibility if future charges or merchant-initiated transactions are required.
Unified Checkout supports these wallet-based payment options:
- Apple Pay
- Google Pay
- Click to Pay
- Paze
Apple Pay
Apple Pay is a digital payment solution that enables your customers to make secure and convenient purchases without entering their card details or shipping information. This section describes how to accept Apple Pay payments with your Unified Checkout integration.
Board Merchants with Apple Pay
Before you can accept Apple Pay payments, your account must be boarded for Apple Pay. Portfolio users can board and enable their merchants for Apple Pay using the API.
Send a POST request to the Boarding Registration API to board Apple Pay:
POST /boarding/v1/registrations
POST /boarding/v1/registrations
If your organization is already boarded, you can add Apple Pay as a product using the PECS API instead:
POST /products/v1/product-setups
POST /products/v1/product-setups
Include these required fields in the Boarding Registration API request:
Required Fields for Enabling Apple Pay Using the BRS API
organizationInformation.organizationIdorganizationInformation.businessInformation.nameorganizationInformation.businessInformation.websiteUrlorganizationInformation.businessInformation.merchantCategoryCodeproductInformation.selectedProducts.payments.unifiedCheckout.subscriptionInformation.enabled: set totrue.productInformation.selectedProducts.payments.unifiedCheckout.subscriptionInformation.features.applePay.enabled: set totrueto enable Apple Pay on Unified Checkout.productInformation.selectedProducts.payments.unifiedCheckout.subscriptionInformation.features.portfolioAccessofSensitiveData.enabled: set totrueto enable portfolio access to sensitive data.
Include these required fields in the PECS API request:
Required Fields for Enabling Apple Pay Using the PECS API
organizationIdpayments.unifiedCheckout.subscriptionInformation.enabled: set totrue.payments.unifiedCheckout.subscriptionInformation.features.applePay.enabled: set totrueto enable Apple Pay on Unified Checkout.payments.unifiedCheckout.subscriptionInformation.features.portfolioAccessofSensitiveData.enabled: set totrueto enable portfolio access to sensitive data.
{ "organizationInformation": { "organizationId": "stuartwickedfasteatz01", "parentOrganizationId": "apitester00", "type": "MERCHANT", "configurable": false, "businessInformation": { "name": "StuartWickedFastEatz", "address": { "country": "US", "address1": "123456 SandMarket", "locality": "ORMOND BEACH", "administrativeArea": "FL", "postalCode": "32176" }, "websiteUrl": "https://www.StuartWickedEats.com", "phoneNumber": "6574567813", "businessContact": { "firstName": "Stuart", "lastName": "Stuart", "phoneNumber": "6574567813", "email": "[email protected]" }, "merchantCategoryCode": "5999" } }, "productInformation": { "selectedProducts": { "payments": { "unifiedCheckout": { "subscriptionInformation": { "enabled": true, "features": { "applePay": { "enabled": true }, "portfolioAccessofSensitiveData": { "enabled": true } } } } } } }}{ "organizationId": "stuartwickedfasteatz01", "payments": { "unifiedCheckout": { "subscriptionInformation": { "enabled": true, "features": { "applePay": { "enabled": true }, "portfolioAccessofSensitiveData": { "enabled": true } } } } }}Enrolling in Apple Pay
Apple Pay is a digital payment service that enables users to make secure and convenient transactions using their Apple devices. Users can add their credit or debit cards to the Wallet app and use them to pay online or in apps.
To enable Apple Pay, you must first host a public certificate on your web page and then pass your merchant name and domain name to Apple. Apple crawls your web page to validate the presence of this certificate to confirm the web page is properly vetted and registered with Apple.
Follow these steps to validate your domain and enroll in Apple Pay:
Navigate to Payment Configuration > Unified Checkout.
In the Apple Pay section, click Set Up.
Follow the link to download the certificate.
Upload the apple-developer-merchantid-domain-association certificate file to your web server at:
/.well-known/apple-developer-merchantid-domain-associationYou must verify that the file is accessible through HTTPS. You can validate this by visiting
https://<your-domain>/.well-known/apple-developer-merchantid-domain-association.Click Verify Domain.
Enter the domain name where you are hosting Apple Pay. This must be the same domain to which you uploaded the public certificate.
Your domain is now verified for Apple Pay.
Preparing a Test Device
To run an end-to-end test of the Apple Pay service on Unified Checkout, you must prepare an Apple test device by loading Apple Pay test cards onto the device.
Follow these steps to prepare your Apple test device for end-to-end testing:
- Confirm your Apple Developer account is configured for Apple Pay.
- Register your Apple Pay test device with Apple.
- Load Apple Pay test cards onto your Apple test device. The Apple Developer center provides instructions on the Sandbox Testing page for Apple Pay:
- Follow the steps described in Create a Sandbox Tester Account.
- Follow the steps described in Adding a Test Card Number.
Google Pay
Google Pay is a simple, secure in-app mobile and web payment solution. This section describes how to accept Google Pay payments with your Unified Checkout integration.
Board Merchants with Google Pay
Before you can accept Google Pay payments, your account must be boarded for Google Pay. Portfolio users can board and enable their merchants for Google Pay using the API.
Send a POST request to the Boarding Registration API to board Google Pay:
POST /boarding/v1/registrations
POST /boarding/v1/registrations
If your organization is already boarded, you can add Google Pay as a product using the PECS API instead:
POST /products/v1/product-setups
POST /products/v1/product-setups
Include these required fields in the Boarding Registration API request:
Required Fields for Enabling Google Pay Using the BRS API
organizationInformation.organizationIdorganizationInformation.businessInformation.nameorganizationInformation.businessInformation.websiteUrlorganizationInformation.businessInformation.merchantCategoryCodeproductInformation.selectedProducts.payments.unifiedCheckout.subscriptionInformation.enabled: set totrue.productInformation.selectedProducts.payments.unifiedCheckout.subscriptionInformation.features.googlePay.enabled: set totrueto enable Google Pay on Unified Checkout.productInformation.selectedProducts.payments.unifiedCheckout.subscriptionInformation.features.portfolioAccessofSensitiveData.enabled: set totrueto enable portfolio access to sensitive data.
Include these required fields in the PECS API request:
Required Fields for Enabling Google Pay Using the PECS API
organizationIdpayments.unifiedCheckout.subscriptionInformation.enabled: set totrue.payments.unifiedCheckout.subscriptionInformation.features.googlePay.enabled: set totrueto enable Google Pay on Unified Checkout.payments.unifiedCheckout.subscriptionInformation.features.portfolioAccessofSensitiveData.enabled: set totrueto enable portfolio access to sensitive data.
{ "organizationInformation": { "organizationId": "stuartwickedfasteatz01", "parentOrganizationId": "apitester00", "type": "MERCHANT", "configurable": false, "businessInformation": { "name": "StuartWickedFastEatz", "address": { "country": "US", "address1": "123456 SandMarket", "locality": "ORMOND BEACH", "administrativeArea": "FL", "postalCode": "32176" }, "websiteUrl": "https://www.StuartWickedEats.com", "phoneNumber": "6574567813", "businessContact": { "firstName": "Stuart", "lastName": "Stuart", "phoneNumber": "6574567813", "email": "[email protected]" }, "merchantCategoryCode": "5999" } }, "productInformation": { "selectedProducts": { "payments": { "unifiedCheckout": { "subscriptionInformation": { "enabled": true, "features": { "googlePay": { "enabled": true }, "portfolioAccessofSensitiveData": { "enabled": true } } } } } } }}{ "organizationId": "stuartwickedfasteatz01", "payments": { "unifiedCheckout": { "subscriptionInformation": { "enabled": true, "features": { "googlePay": { "enabled": true }, "portfolioAccessofSensitiveData": { "enabled": true } } } } }}Enrolling in Google Pay
Google Pay is a digital payment product offered by Google through Chrome browsers and Android devices.
Follow these steps to enroll in Google Pay on Unified Checkout:
Navigate to Payment Configuration > Unified Checkout.
In the Google Pay section, click Set Up.
Enter your business name.
Click Submit.
You can now accept digital payments with Google Pay.
Managing Google Pay Authentication Types
Additional controls are available for Google Pay on Unified Checkout. When you enable Google Pay on Unified Checkout, you can specify optional parameters that define the types of card authentication you receive from Google Pay.
To manage the types of credentials that Google Pay sends, use this expanded payment type object within the allowedPaymentTypes section of the session request:
{ "paymentConfigurations": { "GOOGLEPAY": { "allowedAuthMethods": ["PAN_ONLY", "CRYPTOGRAM_3DS"] } }}The expanded payment type object has these parameters:
type: defines the type of payment option.options: contains payment-type-specific parameters. For Google Pay, use theallowedAuthMethodsdata element withinoptionsto specify the authentication type you receive from Google Pay:PAN_ONLY: Google returns primary account number (PAN) values.CRYPTOGRAM_3DS: Google returns fully authenticated network token values.
By default, Google sends both authentication types.
This session request example specifies that Google Pay is to send only PAN values:
{ "allowedPaymentTypes": ["GOOGLEPAY"], "paymentConfigurations": { "GOOGLEPAY": { "allowedAuthMethods": ["PAN_ONLY", "CRYPTOGRAM_3DS"] } }}This session request example specifies that Google Pay can send all authentication types alongside other payment options. For information about configuring your allowed payment types, see Configure Unified Checkout.
{ "allowedPaymentTypes": ["PANENTRY", "GOOGLEPAY", "CLICKTOPAY", "PAZE", "CHECK"]}Click to Pay
Click to Pay is a secure online checkout method that enables customers to make purchases without entering their payment details for every purchase. This section describes how to accept Click to Pay payments with your Unified Checkout integration.
Board Merchants with Click to Pay
Before you can accept Click to Pay payments, your account must be boarded for Click to Pay. Portfolio users can board and enable their merchants for Click to Pay using the API.
Send a POST request to the Boarding Registration API to board Click to Pay:
POST /boarding/v1/registrations
POST /boarding/v1/registrations
If your organization is already boarded, you can add Click to Pay as a product using the PECS API instead:
POST /products/v1/product-setups
POST /products/v1/product-setups
Include these required fields in the Boarding Registration API request:
Required Fields for Enabling Click to Pay Using the BRS API
organizationInformation.organizationIdorganizationInformation.businessInformation.nameorganizationInformation.businessInformation.websiteUrlorganizationInformation.businessInformation.merchantCategoryCodeproductInformation.selectedProducts.payments.unifiedCheckout.subscriptionInformation.enabled: set totrue.productInformation.selectedProducts.payments.unifiedCheckout.subscriptionInformation.features.clickToPay.enabled: set totrueto enable Click to Pay on Unified Checkout.productInformation.selectedProducts.payments.unifiedCheckout.subscriptionInformation.features.portfolioAccessofSensitiveData.enabled: set totrueto enable portfolio access to sensitive data.
Include these required fields in the PECS API request:
Required Fields for Enabling Click to Pay Using the PECS API
organizationIdpayments.unifiedCheckout.subscriptionInformation.enabled: set totrue.payments.unifiedCheckout.subscriptionInformation.features.clickToPay.enabled: set totrueto enable Click to Pay on Unified Checkout.payments.unifiedCheckout.subscriptionInformation.features.portfolioAccessofSensitiveData.enabled: set totrueto enable portfolio access to sensitive data.
{ "organizationInformation": { "organizationId": "stuartwickedfasteatz01", "parentOrganizationId": "apitester00", "type": "MERCHANT", "configurable": false, "businessInformation": { "name": "StuartWickedFastEatz", "address": { "country": "US", "address1": "123456 SandMarket", "locality": "ORMOND BEACH", "administrativeArea": "FL", "postalCode": "32176" }, "websiteUrl": "https://www.StuartWickedEats.com", "phoneNumber": "6574567813", "businessContact": { "firstName": "Stuart", "lastName": "Stuart", "phoneNumber": "6574567813", "email": "[email protected]" }, "merchantCategoryCode": "5999" } }, "productInformation": { "selectedProducts": { "payments": { "unifiedCheckout": { "subscriptionInformation": { "enabled": true, "features": { "clickToPay": { "enabled": true }, "portfolioAccessofSensitiveData": { "enabled": true } } } } } } }}{ "organizationId": "stuartwickedfasteatz01", "payments": { "unifiedCheckout": { "subscriptionInformation": { "enabled": true, "features": { "clickToPay": { "enabled": true }, "portfolioAccessofSensitiveData": { "enabled": true } } } } }}Enabling Click to Pay
Click to Pay is a digital payment solution that allows customers to pay with their preferred card network and issuer without entering their card details on every website. Customers can use Visa, Mastercard, and American Express cards to streamline their purchase experience. Click to Pay provides a fast, secure, and consistent checkout experience across devices and browsers.
Follow these steps to enable Click to Pay on Unified Checkout:
Log in to the . If you are unable to access this page, contact your sales representative.
In the , go to the left navigation panel and choose Payment Configuration > Unified Checkout. The Unified Checkout customer experience page appears:
Unified Checkout Customer Experience In the Payment Options section, click Manage. The Payment Options page appears.
Click Manage next to Click to Pay. The Click to Pay configuration page appears.
Enter your business name and website URL.
Click Submit.
Contact your implementation contact or technical account manager to request that you be enabled for tokenization within Click to Pay. Your implementation contact or technical account manager confirms that you were configured successfully and that you can now accept digital payments with Click to Pay.
Customer Authentication Setup
These authentication methods are available for Click to Pay. Authentication methods differ in each region and depend on the issuer, the cardholder device, and the Click to Pay configuration:
- 3-D Secure
- FIDO
- Card verification value (CVV)
- One-time password (OTP)
Follow these steps to enable customer authentication through Click to Pay in the :
Log in to the . If you are unable to access this page, contact your sales representative.
In the , go to the left navigation panel and choose Payment Configuration > Unified Checkout.
You must have Click to Pay enabled as a digital payment method to use this method of authentication. Click Manage to view the digital payment methods that you have enabled.
If Click to Pay is not enabled, click On next to Click to Pay.
Click Set up under Value Added Solutions. The Value Added Solutions page appears.
Click Set up to configure 3-D Secure. The 3DS page appears.
In the Merchant Details section, enter the required information. You must enter the information that is provided to you by your acquirer or processor.
This completes the authentication setup for the entered acquirer merchant ID and BIN. If you do not know these values, you must contact your acquirer. Completing this information enables to send Visa the information that is required for authentication.
Click to Pay Customer Authentication
When you enable customer authentication through Click to Pay, you give permission to send Visa the required authentication information for each transaction. When the customer completes a transaction using a Visa card that is already stored in Click to Pay, authentication is managed within Click to Pay.
Click to Pay authentication is available only for Visa-branded cards that are tokenized with Click to Pay. If Click to Pay does not authenticate the transaction, but you are using the complete mandate with the consumerAuthentication field set to true, authentication is attempted as part of that request. When you do not use the complete mandate, you must check the result of the cardholderAuthenticationStatus field in the transient token and request payer authentication directly when it is required.
Authentication Flow
Click to Pay UI
Click to Pay UI Guidelines
The UI that is built in Unified Checkout for Click to Pay follows the EMV Click to Pay XC Guidelines V1.1. Unified Checkout has simplified the integration of the UI. The only UI work that you must complete is the placement of the payment option.
Unified Checkout captures all card details that are manually entered by the cardholder. This enables the cardholder to enroll in Click to Pay and removes the requirement for the cardholder to manually enter their card details the next time they check out.
Unified Checkout provides a standard payment label in the Unified Checkout JavaScript that is loaded on your checkout page. One of these scenarios occurs when the cardholder selects the button:
- The cardholder is recognized.
- The cardholder is not recognized but has a Click to Pay account.
- The cardholder does not have a Click to Pay account.
You can also trigger the Unified Checkout flow using a custom button. If you use your own custom button, your payment button or widget must display the Click to Pay image for the cardholder. For information about custom triggers, see Integration Examples.
Unrecognized Click to Pay Customer
When the cardholder has a Click to Pay account but is not on a registered device, they receive a one-time password to their registered email address and phone number to authenticate their identity before their stored Click to Pay credentials are shown:
No Click to Pay Account
When the cardholder does not have a Click to Pay account, they can provide a new email address to perform a new lookup or they can choose to enter their card details manually. The cardholder can make a one-time payment or complete the payment and choose to create a Click to Pay account for future use:
Click to Pay UI Examples
This section contains UI examples of how you should display Click to Pay on your payment page. For information about how to display the UI, see Integration Examples.
Click to Pay Replaces PAN Capture
Click to Pay is the card entry payment option within your payment page:
For information about how to configure this UI, see Integration Examples.
Click to Pay as Radio Button
Click to Pay is a radio button for the card entry payment option within your payment page. When the cardholder selects this option, the Click to Pay payment flow loads.
Click to Pay Icon on Radio Button
You can host the radio selection option for card payment with the Click to Pay icon displayed on the payment label. The Unified Checkout flow loads when the cardholder selects this option. For information about customizing how to trigger Unified Checkout, see Integration Examples.
Load Click to Pay Automatically From Trigger
You can load the Unified Checkout JavaScript flow within your payment page without requiring the cardholder to select a card payment option. A recognized user's payment information can be shown automatically next to the other payment methods hosted within your payment page. For information about customizing how to trigger Unified Checkout, see Integration Examples.
Card Payment Options with Click to Pay in UI
Do not present the Unified Checkout payment button as a separate payment method from the card payment button. If you do, the cardholder is not prompted with their Click to Pay cards and must manually enter their payment details. They also do not have the option to store their card within Click to Pay for future use.
This example shows multiple card payment options and Click to Pay in a UI:
Paze
Paze is an online checkout option, or digital wallet, that enables you to offer customers a fast and secure way to make purchases online. This section describes how to accept Paze payments with your Unified Checkout integration.
Paze UI
Related Payment Methods
Thanks for your feedback!
Last published: September 29, 2026