Adding Apple Pay, Google Pay, and PayPal to Your Store's Checkout

On this page 8 sections

1. Why Digital Wallets in Ecommerce Checkout Matter on Mobile
2. How to Add Apple Pay to Website Checkout: Domain Verification and Requirements
3. Google Pay for Your Online Store: Setup Through Your Gateway
4. PayPal Checkout Button and Venmo: Fees and Dispute Rules
5. How Wallet Tokenization Reduces Fraud
6. Placing Wallet Buttons for Express Checkout Conversion Without Clutter
7. Pre-Launch Checklist
8. Next Steps

Key takeaways

• Apple Pay and Google Pay usually run through your existing gateway and card pricing. PayPal and Venmo are a separate account with their own fees and dispute process.
• Apple Pay on the web requires domain verification, and Google Pay requires gateway support and a merchant ID. Confirm both with your gateway before you build.
• Wallet tokenization keeps real card numbers off your site and adds device authentication, but it does not stop friendly fraud or "item not received" disputes.
• Offer the wallets your customers actually use, and put them where mobile shoppers decide to buy. Don't stack every button on every page.

Mobile shoppers often leave at the point where they have to type a card number, billing address and shipping address on a small screen. Express wallets remove most of that typing. This guide explains how to add Apple Pay to website checkout, how to set up Google Pay and PayPal, what each one costs you in practice, how wallet tokenization reduces fraud, and where to place the buttons so they help sales without crowding the page.

Fees, program rules and technical requirements change. Treat this as a planning guide, and confirm current terms with your processor, gateway and each wallet provider before you launch.

Why Digital Wallets in Ecommerce Checkout Matter on Mobile

A standard online checkout asks a phone user to do several things on a small screen:

• Fill in a long form with name, email, phone, two addresses and card details
• Switch between keyboards for numbers and letters
• Correct autofill mistakes, such as an old address or the wrong apartment number
• Go through extra verification if the bank challenges the card

Each of these steps is a point where a shopper can give up. An express wallet replaces them with a single confirmation. The shopper picks a saved card and address, confirms with a fingerprint, face scan or password, and the order goes through.

For an online store, the benefits are practical:

• Fewer address errors. The wallet passes along the shipping address the customer already saved, which can cut down on misdeliveries.
• Faster repeat purchases. Wallets give guest shoppers much of the speed of a saved account without making them register.
• Impulse-friendly checkout. A buy button on the product page lets a shopper who arrived from a social ad purchase without ever opening the cart.

If you're weighing account creation against speed, our guide to guest checkout vs. forced accounts covers the trade-offs. Wallets often let you skip that choice.

Which Wallets to Prioritize

Your store doesn't need every wallet. Check your analytics for device and browser mix:

How to Add Apple Pay to Website Checkout: Domain Verification and Requirements

Apple Pay on the web runs through your payment gateway. Apple doesn't process the payment. It hands your gateway an encrypted payment token, and your gateway sends it through the card networks like any other card-not-present transaction.

What You Need Before You Start

• A gateway that supports Apple Pay on the web. Ask your provider directly. Support varies by gateway, by plan and by platform plugin.
• HTTPS on every page where the Apple Pay button appears.
• Acceptance of Apple's terms. This may happen through your gateway's dashboard or through an Apple developer account, depending on how your gateway integrates.
• A product catalog that fits Apple's acceptable-use guidelines. Some regulated categories may be restricted, so check before you build.

The Domain Verification Step

Apple requires proof that you control every domain where the button appears. The typical flow:

1. Register your domain, including any subdomain such as a separate checkout subdomain, in your gateway's Apple Pay settings or in Apple's developer portal.
2. Download the verification file your gateway or Apple provides.
3. Host the file at the exact path specified, on your live domain, without redirects.
4. Trigger verification and confirm the domain shows as verified.

Common reasons verification fails include a redirect from the bare domain to the "www" version, a firewall or bot-protection tool blocking the file, or a staging domain that was never registered. Many hosted platforms and plugins handle registration automatically. Verify anyway that your live domain appears as active.

Browser and Device Support

Apple Pay on the web was long limited to Safari on Apple devices, and Apple has expanded support over time. Don't assume every visitor will see the button. Your code or plugin should check whether Apple Pay is available on the visitor's device and show the button only when it is.

Google Pay for Your Online Store: Setup Through Your Gateway

Google Pay also works through your gateway. Google returns a payment token, and your gateway processes it as a card transaction.

Setup Steps

1. Confirm gateway support. Ask your gateway whether it supports Google Pay directly. Also ask whether it's offered through your platform, such as Shopify or WooCommerce, or through a custom integration.
2. Register as a merchant with Google. You'll create a business profile in Google's console and receive a merchant ID for production use.
3. Configure your gateway as the tokenization method. In most integrations, your gateway name and gateway merchant ID go into the Google Pay configuration so tokens are encrypted for your gateway.
4. Test in Google's test environment, then request production access. Google may review your integration and checkout screens before approving it.

One Important Detail: Two Kinds of Google Pay Cards

Google Pay can return either of two things:

• A device token with a cryptogram, from a card added to an Android phone. This is the more secure version.
• A card stored in the customer's Google account, used from a desktop browser or another device. Your gateway may treat it much like a card typed in by hand.

Ask your gateway how it handles each type. Some stores run 3D Secure on online orders for the second type. Our guide to 3D Secure liability shift without lost sales explains when that extra step is worth it.

PayPal Checkout Button and Venmo: Fees and Dispute Rules

PayPal works differently from Apple Pay and Google Pay. It isn't a token passed through your card processor. It's a separate payment account with its own pricing, settlement timing and dispute process.

How PayPal Fees Work

PayPal sets its own transaction fees, which can vary by payment type, currency, cross-border status and account arrangement. Those fees are separate from your card processing pricing, so a PayPal sale and a card sale of the same size can cost you different amounts. Check PayPal's current merchant fee page and compare the effective cost against your card rates. Our breakdown of ecommerce credit card processing fees covers how to calculate your card side. To see what happens to those fees when an order is returned, read our guide on whether you get processing fees back on online refunds.

Apple Pay and Google Pay generally don't add a separate merchant fee. Those transactions usually price like other card-not-present card sales under your existing agreement. Confirm how your processor categorizes wallet transactions on your statement. If you take preorders, our guide to preorder payments: charging now or when the product ships compares the options for when to charge.

How PayPal Disputes Differ

• PayPal disputes opened by buyers go through PayPal's own resolution process, with its own deadlines and evidence requirements.
• Card chargebacks can still occur when a buyer funded a PayPal payment with a card and disputes it through their bank.
• Seller protection from PayPal comes with eligibility conditions, which commonly involve shipping to the address on the transaction and keeping proof of delivery. Read the current policy, because the details matter.

Funds in a PayPal account can also be subject to holds or reserves under PayPal's terms. If that has happened to you, see our guide on what to do when Stripe or PayPal froze your funds. If you run a dropship store, our guide to getting approved and staying live with dropshipping payment processors covers the shipping, refund and tracking practices that help keep your account active.

Venmo

Venmo usually appears as an option inside PayPal's checkout and is aimed at U.S. mobile shoppers. It follows PayPal's merchant terms. If your customers skew young and mobile, test it. If they don't, it may only add clutter.

How Wallet Tokenization Reduces Fraud

When a customer pays with Apple Pay or a device-based Google Pay card, your store never receives the real card number. Instead it receives:

• A token, which is a stand-in number tied to that card and often to that specific device
• A one-time cryptogram, which proves the payment came from the legitimate device and can't be reused
• Customer authentication, through a biometric check or device passcode, performed before the payment is released

What that means for your store:

Two cautions. First, wallets don't replace your other controls. Keep velocity limits and bot protection on the card form, as covered in our guide to stopping card testing attacks. Second, liability treatment for wallet transactions depends on network rules and how your gateway submits them. Ask your processor rather than assuming every wallet sale is chargeback-proof. For the broader picture, see network tokenization and higher approvals. If you're weighing extra protection, our guide asks whether chargeback guarantee services are worth it for your store.

Placing Wallet Buttons for Express Checkout Conversion Without Clutter

Buttons only help if they show up at the right moment and don't push the main path off the screen.

Where to Put Them

• Product page: One express button below "Add to Cart" works well for single-item, impulse-friendly products.
• Cart or cart drawer: This is the most common spot. Wallet buttons go above the standard checkout button.
• Top of checkout: Place an "Express checkout" row before the email field so returning wallet users never touch the form.

Placement Rules That Keep Checkout Clean

1. Show only available wallets. Hide Apple Pay on Android and Google Pay where it isn't supported.
2. Limit the row. Two or three express options is usually enough. Showing more can slow shoppers down.
3. Follow each brand's button guidelines. Apple, Google and PayPal publish rules on button size, color and wording.
4. Pass shipping and tax correctly. Make sure shipping options and tax update when the wallet shares the customer's address. Wrong totals on the wallet sheet cause abandoned orders and support tickets.
5. Capture the email. Make sure the wallet flow collects an email so order confirmations and tracking still reach the customer.
6. Test on real phones. Simulators miss layout problems, slow-loading scripts and checkout-page errors.

Illustrative Example

Illustrative scenario: A small apparel store finds that most of its traffic comes from phones via social ads. It adds Apple Pay and Google Pay to the product page and cart, keeps PayPal in the cart only, and leaves Venmo off. A month later, it reviews checkout completion by device, wallet usage and dispute rates. Then it decides whether Venmo or a product-page PayPal button is worth testing.

Pre-Launch Checklist

• [ ] Gateway confirmed for Apple Pay and Google Pay on your platform
• [ ] All live domains and subdomains verified for Apple Pay
• [ ] Google Pay production access approved
• [ ] PayPal fees, payout timing and dispute policy reviewed
• [ ] 3D Secure rules set for non-tokenized card flows
• [ ] Shipping, tax and email capture tested in each wallet
• [ ] Order data, including wallet type, passed to fulfillment and accounting
• [ ] Wallet transactions identified on your processing statement

Next Steps

Start with the wallets your traffic supports. For most U.S. stores, that means Apple Pay and Google Pay through your gateway, with PayPal added if your customers ask for it. Confirm requirements and fees with each provider, test on real devices, and review results by device and wallet before adding more buttons.

If you're reviewing your setup, MannyPay offers payment gateways for online stores and online payment processing for low- and high-risk merchants, with integrations including Authorize.Net and NMI. To discuss your checkout, request a free quote, and a MannyPay specialist will respond within one business day.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.