Payments • Stripe • Order Forms
Using Apple Pay and Google Pay in Order Forms
Apple Pay and Google Pay give eligible customers a faster way to complete purchases without manually entering card details during checkout. These digital wallets can be used on eligible One-Step and Two-Step Order Forms when Stripe is the payment provider. Wallet settings can be managed directly from the sub-account. This guide explains how to configure Apple Pay and Google Pay, understand checkout eligibility, and troubleshoot wallet visibility.
What You'll Learn

Learn how to manage Apple Pay and Google Pay from the Stripe integration, configure the correct Order Form and payment environment, understand Apple Pay domain verification, and troubleshoot wallets that do not appear at checkout.

Important

Enabling a wallet does not guarantee that every customer will see it. Wallet visibility can depend on the product area, Test or Live configuration, Stripe account eligibility, customer location, browser or device, wallet setup, and additional requirements such as Apple Pay domain verification.

1

What Are Apple Pay and Google Pay in Order Forms?

Apple Pay and Google Pay are digital wallet payment methods customers can use during eligible Order Form checkouts. They are available through Stripe and can appear alongside other enabled payment methods when the customer and checkout environment meet the applicable requirements.

Apple Pay and Google Pay can be used with eligible Funnels - One-Step Order Form and Funnels - Two-Step Order Form payment experiences.

2

Key Benefits of Apple Pay and Google Pay

Digital wallets can reduce the information eligible customers need to enter manually during checkout while giving businesses centralized control over where supported Stripe payment methods are available.

  • Faster Checkout: Eligible customers can use a saved wallet instead of manually entering card information.
  • Centralized Management: Manage supported Stripe payment methods directly from the sub-account.
  • Order Form Support: Configure wallet availability for eligible One-Step and Two-Step Order Forms.
  • Separate Environment Controls: Configure supported payment methods independently for Test and Live environments.
  • Subscription Controls: Review subscription-specific payment-method settings when the checkout includes recurring products.
3

Prerequisites and Limitations

Apple Pay and Google Pay only appear when the payment configuration and the customer's checkout environment meet the applicable requirements. Reviewing these conditions first helps prevent unnecessary Order Form troubleshooting.

  • Stripe must be connected to the applicable sub-account.
  • The wallet must be enabled for the applicable Order Form product area.
  • Confirm that you are configuring the correct Test or Live environment.
  • The customer's country, device, browser, and payment account must support the selected wallet.
  • The customer must have an eligible payment method configured in the applicable wallet.
  • Apple Pay requires completed domain verification before it can appear during eligible checkout experiences.
  • Subscription checkouts can have separate payment-method settings under Subscriptions.
  • The Subscriptions configuration becomes available after a subscription product has been added in Live Mode for the applicable sub-account.

Payment-provider scope: Apple Pay and Google Pay for the Order Form use case covered here are provided through Stripe. Other payment providers have their own supported payment methods and product-area availability.

4

How To Set Up Apple Pay and Google Pay for Order Forms

Stripe payment methods are managed from the Payments area of the sub-account. Configure the wallets for the applicable Order Form product area and payment environment before testing the customer checkout.

Step 1: Open the Stripe Integration

Start from the Stripe integration so you can access payment-method management and wallet-related configuration for the connected account.

  1. From the sub-account view, select Payments.
  2. Select Integrations.
  3. Locate Stripe.
  4. Click Manage.
Payments Integrations page showing Stripe as the default payment provider with the Manage button
Go to Payments → Integrations, locate Stripe, and click Manage.

Step 2: Open Manage Payment Methods

The Stripe management page provides access to payment-method settings and the domain-registration control used for Apple Pay and Link.

  1. On the Manage Payment Integration page, confirm the Stripe connection status.
  2. Review Register domains for Apple Pay and Link.
  3. Click Manage Payment Methods.
Manage Payment Integration page showing Manage Payment Methods and Register domains for Apple Pay and Link
Review domain registration for Apple Pay, then click Manage Payment Methods.

Apple Pay requirement: Apple Pay requires completed domain verification. If Apple Pay is enabled but does not appear at checkout, domain verification should be one of the first settings you review.

Step 3: Configure the Order Form Payment Methods

Payment methods are configured by product area, which lets you control whether a wallet is available for a One-Step Order Form, Two-Step Order Form, or another supported payment experience.

  1. Review the available Stripe payment-method configurations.
  2. Locate Funnels - One-Step Order Form or Funnels - Two-Step Order Form, depending on the checkout you use.
  3. Enable Apple Pay where available.
  4. Enable Google Pay where available.
  5. Save the changes.

Step 4: Verify Test or Live Mode

Test and Live payment-method configurations are independent. A wallet enabled only in one environment may not appear when the checkout is using the other environment.

  1. Confirm whether you are configuring Test or Live.
  2. Verify Apple Pay and Google Pay are enabled in the environment you plan to test or use.
  3. Save any changes before testing the Order Form again.

Step 5: Review Subscription Settings When Needed

Subscription products can use a separate payment-method configuration, so recurring checkouts should be reviewed independently from one-time Order Form settings.

  1. Open the Subscriptions payment-method configuration when it is available.
  2. Review the available wallet methods for subscription checkout.
  3. Enable the applicable wallet settings and save your changes.

Subscriptions not visible? The Subscriptions configuration becomes available after at least one subscription product has been added in Live Mode for that sub-account.

5

How Wallet Availability Works at Checkout

Enabling a wallet makes it available to eligible checkout experiences, but the final payment options displayed to a customer are determined at checkout based on several configuration and eligibility factors.

FactorWhy It Matters
Product AreaThe wallet must be enabled for the specific checkout type being used.
Test or Live ModeThe method must be enabled in the same environment as the checkout being tested or used.
Stripe Account EligibilityPayment-method availability can depend on account activation, region, and Stripe eligibility requirements.
Customer LocationSome payment methods are only available in supported countries or regions.
Device and BrowserThe customer's checkout environment must support the applicable wallet.
Wallet SetupThe customer needs an eligible wallet with a supported payment method configured.
Apple Pay Domain VerificationApple Pay requires domain verification before it can appear on eligible web checkouts.

If a wallet does not appear, verify the payment configuration and customer eligibility before treating the missing payment option as an Order Form issue.

6

Troubleshoot Apple Pay and Google Pay

Wallet visibility is determined by several layers of configuration. Start with the Stripe integration and payment-method settings, then verify the checkout environment and customer eligibility.

Troubleshoot Apple Pay

Apple Pay requires an eligible Stripe configuration, the correct Order Form settings, and completed domain verification before it can appear on a supported checkout.

  1. Go to Payments → Integrations.
  2. Click Manage for Stripe.
  3. Open Manage Payment Methods.
  4. Confirm Apple Pay is enabled for the applicable One-Step or Two-Step Order Form.
  5. Verify the correct Test or Live environment.
  6. If the checkout contains a subscription product, review the Subscriptions payment-method settings.
  7. Confirm the Stripe account is activated and eligible for the payment method.
  8. Confirm Apple Pay domain verification is complete.
  9. Test from an eligible customer environment with Apple Pay configured.

Troubleshoot Google Pay

Google Pay visibility depends on the Stripe payment-method configuration and whether the customer's checkout environment is eligible to display the wallet.

  1. Go to Payments → Integrations.
  2. Click Manage for Stripe.
  3. Open Manage Payment Methods.
  4. Confirm Google Pay is enabled for the applicable One-Step or Two-Step Order Form.
  5. Verify the correct Test or Live environment.
  6. If the checkout contains a subscription product, review the Subscriptions payment-method settings.
  7. Confirm the Stripe account and payment method are eligible.
  8. Test from a supported customer environment with Google Pay configured.

Troubleshooting order: Check product area, Test/Live mode, payment-method status, Stripe eligibility, and customer environment before changing the Order Form itself.

7

Frequently Asked Questions

Q: Why does a wallet not appear even though I enabled it?
Wallet visibility also depends on the selected product area, Test or Live environment, Stripe account eligibility, customer location, browser or device, and wallet configuration. Apple Pay additionally requires domain verification.
Q: Can I configure Test and Live payment methods separately?
Yes. Stripe payment methods can be configured independently for Test and Live environments.
Q: Can Apple Pay or Google Pay be used with subscription products?
Subscription checkouts have separate payment-method settings. Review the Subscriptions configuration and enable the applicable wallet when available for that checkout.
Q: Why don't I see the Subscriptions payment-method configuration?
The Subscriptions configuration becomes available after at least one subscription product has been added in Live Mode for that sub-account.
Q: Will Apple Pay and Google Pay transactions appear in reporting?
Supported Stripe transactions continue to be recorded in the Payments area. Existing Order Submitted and Payment Received workflow triggers also continue to function for supported payment-method transactions.
Q: Are Apple Pay and Google Pay transaction fees always identical to card pricing?
Not necessarily. Stripe transaction fees can vary by country and payment method. Review the current Stripe pricing applicable to your account and region.
Q: Can I enable Stripe payment methods other than Apple Pay and Google Pay?
Yes. Additional Stripe payment methods can be available across eligible product areas. Availability depends on the product area, payment account, region, payment method, and any additional requirements.
8

Need Help?

  • Neither wallet appears: Confirm Stripe is connected, the correct product area is configured, and the wallet is enabled in the same Test or Live environment as the checkout.
  • Apple Pay is missing: Review Register domains for Apple Pay and Link, confirm domain verification is complete, and test from an eligible Apple Pay environment.
  • Google Pay is missing: Confirm Google Pay is enabled for the applicable product area and test with a supported customer environment that has an eligible Google Pay wallet.
  • Test Mode works but Live Mode does not: Review the Live payment-method configuration separately. Test and Live settings are independent.
  • Wallets are missing from subscription checkout: Review the separate Subscriptions payment-method configuration when available.
  • Subscriptions settings are not visible: Confirm that at least one subscription product has been added in Live Mode for the sub-account.
  • Still unresolved: Record the affected Order Form, product area, Test or Live environment, connected Stripe account status, wallet being tested, checkout URL, customer device/browser, and screenshots before contacting support. Do not include passwords, card details, API keys, or other sensitive credentials.