How to Set Up Stripe and PayPal in WooCommerce the Right Way

Connecting a payment gateway takes minutes. Getting webhooks, express buttons, refunds and test orders right is what keeps the money flowing.
Stripe and paypal in woocommerce: a basket with a target and a target in it

Setting up Stripe and PayPal in WooCommerce looks like a five-minute job: install two plugins, connect two accounts, done. Most of the time the buttons appear and the first order goes through. The problems hide in the details: webhooks that stop working after a domain change, an Apple Pay button that never shows, two card forms confusing buyers, orders stuck in “Pending payment”. I’ll cover which plugins to use, the setup steps in order, the problems I see most often, and how to keep payments working after updates.

Why most stores offer both

Stripe and PayPal cover different buyer preferences, and together they serve most shoppers in the US, UK, Canada, Australia and Europe.

  • Stripe handles cards, Apple Pay and Google Pay, and, depending on your country, local payment methods and buy now, pay later options. The card form sits inside your checkout, so the experience feels like part of your store.
  • PayPal suits buyers who would rather not type card details on a store they don’t know yet, plus people who pay from a PayPal balance or use PayPal’s pay later options.

Offering both isn’t about more logos. It’s about not losing the buyer who trusts one and not the other.

Choose the right plugins, and only those

Payment problems often start with plugin choice. My rules are simple:

  • For Stripe, use the official WooCommerce Stripe Payment Gateway plugin, or WooPayments, WooCommerce’s own Stripe-based option in the countries where it is available. Do not run two Stripe plugins side by side.
  • For PayPal, use the official WooCommerce PayPal Payments plugin. The older PayPal Standard integration is outdated, and stores still using it should move.
  • Pick one card processor. PayPal Payments can also show a card form. If Stripe already handles cards, turn that off, so buyers don’t see two different card forms.

Every extra payment plugin is another thing that can conflict with an update. Fewer is safer.

How to set up Stripe and PayPal in WooCommerce, step by step

  1. Verify your business accounts first. Create or check your Stripe account and PayPal Business account, with correct business details and payout bank accounts. Unfinished verification is the most common reason payouts get held.
  2. Install on staging. Add the plugins on a staging copy of the store, not the live site.
  3. Connect through the plugin’s onboarding. Both official plugins offer a connect flow, which is safer than copying API keys around by hand.
  4. Start in test mode. Use Stripe’s test mode and PayPal’s sandbox, and place test orders for each payment method.
  5. Check the webhooks. Stripe uses webhooks to tell WooCommerce what happened after checkout: payment succeeded, failed, refunded or disputed. The plugin usually sets this up when you connect, but confirm in your Stripe dashboard that events are being delivered without errors.
  6. Turn on express buttons. Enable Apple Pay and Google Pay in the Stripe settings and choose where they appear: product pages, cart, checkout. Apple Pay needs your domain registered with Stripe. The plugin usually handles it, but check it on the live domain after launch.
  7. Configure PayPal buttons. Decide whether to show PayPal, pay later messaging, or both, and where. Keep the checkout tidy.
  8. Set a clear statement descriptor. Use a name buyers will recognize on their card statement. Unrecognized charges turn into disputes.
  9. Test strong customer authentication. UK and European cards often require an extra verification step. Stripe provides test cards that trigger it. Use them.
  10. Go live and prove it. Switch to live mode, place a real low-value order with each method, then refund it from the WooCommerce order screen to confirm refunds reach the gateway.

Common payment problems and how I fix them

Orders stuck in “Pending payment”

The customer paid, but WooCommerce never heard about it. This is nearly always a webhook problem: the endpoint points to an old domain after a migration, or a security plugin or firewall is blocking the gateway’s requests. Fix the webhook, then check recent orders against the gateway dashboard.

Apple Pay button missing

Check that the domain is registered with Stripe, that you’re testing in Safari on a device with a card in Apple Wallet, and that the site loads fully over HTTPS. Google Pay has similar requirements in Chrome.

A sudden wave of small failed payments

That pattern usually means card testing: bots using your checkout to check stolen card numbers. Tighten Stripe’s fraud rules, add rate limiting or a challenge on checkout, and talk to your host or Cloudflare about blocking the traffic. Left alone, it can get your account flagged.

Payouts held or delayed

Usually incomplete verification, or a sudden change in sales volume that triggers a review. Keep account details current and respond quickly to provider requests.

Checkout errors after an update

Plugin updates occasionally break payment fields or express buttons. If checkout is already failing, my WordPress error fixing service covers urgent repairs.

Keep payments working after launch

Payment setups don’t fail on launch day. They fail three months later, after an update nobody tested. A few habits prevent most of it:

  • Update payment plugins on staging first, then place test orders before updating the live store.
  • Check failed and pending orders once a week.
  • Glance at Stripe’s webhook delivery status after any hosting, domain or security change.
  • Keep one person responsible for the payment accounts, with up-to-date contact details.

If you would rather not think about any of this, my WordPress maintenance plans include tested updates, and payment setup is a standard part of my WooCommerce development work.

Quick checklist

  • Stripe and PayPal Business accounts verified, payout banks added.
  • One official plugin per gateway, one card form at checkout.
  • Test mode orders placed for every payment method.
  • Stripe webhooks delivering without errors.
  • Apple Pay and Google Pay tested on real devices on the live domain.
  • Recognizable statement descriptor set.
  • Real order and refund completed in live mode.

Related reading: how to set up pre-orders on Shopify for a product launch and an honest Shopify vs WooCommerce comparison.

FAQ

Do I need both Stripe and PayPal?

Not strictly, but most stores benefit from offering both, because some buyers strongly prefer one or the other.

Should I use the Stripe plugin or WooPayments?

Both run on Stripe. WooPayments manages payments inside your WooCommerce dashboard and is available in fewer countries. The Stripe plugin connects your own Stripe account directly. Either works well when set up properly.

Do card details touch my server?

No. With the official plugins, card details go into fields hosted by Stripe or PayPal. That keeps most of the card security burden with them, though your site still needs to be secure and updated.

Can both handle subscription renewals?

Yes, with WooCommerce Subscriptions, as long as the payment methods you enable support automatic renewals. Test a renewal on staging before launch.

Book a free website review, and I’ll check your gateway setup before it costs you an order.

Share this article

Shehzad Akram

About the author

Shehzad Akram

Senior WordPress and Shopify developer in Lahore, Pakistan, Top Rated on Upwork with 100% Job Success. I write these notes from real client work: what broke, what fixed it, and what I check every time.

Keep reading

More notes from real client work