Skip to main content
The Wallet button element renders a native Apple Pay or Google Pay button that charges the customer in one tap. Because wallet buttons skip manual card entry, they reduce checkout friction and typically boost conversion rates by up to 30%.
Don’t confuse the Wallet button with the Apple Pay and Google Pay payment methods of the Checkout element. The Checkout renders wallets inside the full payment form, while the Wallet button is a standalone one-tap button you can place anywhere in the funnel.

​
How it works

Place the Wallet button on your paywall screen alongside the Plan picker, above the Checkout element. At runtime, the Wallet button:
  1. Detects which wallet the visitor’s device and browser support.
  2. Shows that wallet’s native button.
  3. Falls back to a regular button when no wallet is available.
Wallet availability depends on the visitor’s device and browser, and on the wallet configuration of your payment provider: If both wallets are available on the device, Apple Pay is shown.
In the Editor, the Wallet button is not rendered and always appears as a static placeholder.

​
Supported providers

Set up digital wallets for your payment provider before adding the Wallet button: Avoid showing wallets twice on one screen: for example, a Stripe Wallet button next to a Stripe Managed Payments Checkout duplicates Apple Pay, and Solidgate supports only one wallet source per screen.

​
Create Wallet button

To set up a Wallet button, configure digital wallets for your payment provider first, including Apple Pay domain verification, as described in Supported providers.
Prompt AI Chat in Editor to add and configure the Wallet button. Or open the Layers tab in your Editor, click + Add element and select Paywall Elements > Wallet button, and follow the steps below.

​
1. Payment provider

  1. Go to the Parameters tab of your Wallet button.
  2. Select your provider under Payment settings. The list shows only providers with wallet support. If you have a single wallet-capable provider, it’s selected automatically.
  1. Configure the settings under the payment provider:
  • When payment succeeds: Navigation action to trigger when payment is completed.
  • When payment fails or is declined: Navigation action that runs when the payment fails due to a decline or error, including 3DS.
    • Common reason: Navigation that runs when the payment fails for any unspecified reason.
    • Cancelled by user: Navigation action that runs when the user closes the payment sheet.
    • Add failure reason: Configure navigation based on a specific failure reason, such as insufficient funds, invalid card details or do not honor.
  • Account: Your Stripe account. Learn about multiple Stripe accounts in FunnelFox.
  • Total label: Text label shown next to the price in the browser’s native payment sheet.
Don’t place a Stripe Wallet button on the same screen as a Stripe Managed Payments Checkout. The Managed Payments checkout can already show Apple Pay, so the screen would display duplicate wallet buttons.

​
2. Product selection

Configure the product your Wallet button sells the same way you configured it in the Checkout element.

​
3. Fallback

If wallets are not available, a regular button appears with your fallback settings. The fallback triggers when the device or browser doesn’t support Apple Pay or Google Pay, and when the wallet button fails to load or initialize. Treat the fallback as the path for everyone else and always configure it:
  • Fallback text: Label for the fallback button. If empty, the Wallet button text value is used. Supports localizations.
  • Fallback action: Action to trigger when the fallback button is tapped, for example, navigate to your checkout screen.

​
4. Styling

Go to the Styles tab of your Wallet button and adjust the following:
  • Container: Margins, alignment, and other layout settings.
  • Button: Background, border, roundness, padding, size, and text styles.
  • Effects: Pulse animation to draw attention to the button.
With FunnelFox Billing, the provider renders its own native wallet button, so free-form styling is disabled. Choose Black or White under Button color instead.

​
Event triggers

The Wallet button triggers the same payment flow events as the Checkout element:
  • purchase_started: User taps the one-click Apple Pay or Google Pay button.
  • purchase_completed_success: User successfully completes a purchase.
  • purchase_completed_fail: User fails to complete a purchase.
The checkout_init_error event is not sent when a wallet can’t initialize on a device that doesn’t support it, for example, Apple Pay on Android.
Learn more about events and their parameters.

​
Troubleshooting

Check the following in order:
  1. Verify your domains for Apple Pay. Both your project domain and your custom domain must be added to your PSP, and the PSP must be selected under Apple Pay domain verification in Settings > Domains in FunnelFox. See the steps for Stripe, Solidgate, and FunnelFox Billing.
  2. Check the device and browser: Apple Pay requires Safari on iOS or macOS, and Google Pay requires Chrome or Android.
  3. Make sure digital wallets are enabled for your payment provider.
  4. Check where you’re testing: the Editor always shows a static placeholder. Test in Live Preview or on the published funnel.
Solidgate renders the Apple Pay button only in Safari. This is a limitation on the Solidgate side. Learn more in the Solidgate documentation.
For customers with slow internet connections, the linked wallet button may load before the related Checkout element. In this case, the wallet button won’t function, and the fallback button is triggered automatically.

​
Next steps