WooCommerce Payment Gateway Configuration Guide

WooCommerce payment gateway setup looks simple: install plugin → paste API key → done. But Webhook callbacks, cross-currency settlements, and test mode switching are barely documented in official guides — and the same configuration that works on one store fails on another.

Stripe and PayPal dominate WooCommerce payment processing with a combined ~65% market share (Statista 2025). This article focuses on real pitfalls from actual setup, not generic "how to install a plugin" instructions.

---

Prerequisites

• WordPress installed (6.x recommended)
• WooCommerce plugin activated
• SSL certificate configured (HTTPS mandatory for both Stripe and PayPal)
• PHP 8.1+ (required by Stripe plugin)
• Stripe Payment Gateway for WooCommerce or PayPal Checkout Payment Gateway installed

---

Stripe Setup: Why Your Webhook Keeps Returning 404

Problem

Stripe Dashboard shows: 23 requests returned HTTP 404, indicating the URL doesn't exist.

Cause 1: Nginx Cache or Security Plugin Blocks /wc-api/

Stripe's Webhook endpoint is /wc-api/WC_Gateway_Stripe — a special WordPress REST endpoint. If your Nginx config has broad 404 handling (redirecting unknown paths to homepage) or a caching plugin (WP Super Cache, LiteSpeed Cache) returns an HTML page with non-200 status, Stripe receives 404.

Solution — Nginx config:

# Add to your server {} block
location = /wc-api/WC_Gateway_Stripe {
    proxy_pass http://127.0.0.1:8080;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    # Disable all caching for this path
    proxy_cache_bypass 1;
    expires -1;
    add_header Cache-Control "no-store, no-cache, must-revalidate";
}

For LiteSpeed Cache: go to LiteSpeed Cache → Cache → Excludes → Add URLs: /wc-api/*

Cause 2: REST API Broken by Security Plugins

Security plugins like Wordfence or Sucuri may block /wp-json/ and /wc-api/ as suspicious. Check Wordfence → All Options for rules blocking wp-json/*.

Verification command:

curl -I https://yourdomain.com/wc-api/WC_Gateway_Stripe
# Should return: HTTP/2 200
# Not: HTTP/2 404 or HTTP/2 302

Cause 3: Cloudflare or CDN Caching the Wrong Response

If you use Cloudflare, set /wc-api/* to "Bypass cache" — otherwise the CDN may cache a 404 or wrong HTTP status.

Complete Stripe Setup Steps:

1. WordPress Dashboard → WooCommerce → Settings → Payments → Stripe → Settings

2. Click "Configure connection" → Account details → Webhook settings

3. Confirm Webhook URL: https://yourdomain.com/wc-api/WC_Gateway_Stripe

4. Check Stripe Dashboard → Developers → Webhooks → Recent deliveries status

---

PayPal Setup: Why Your Cart Clears After PayPal Returns

Problem

Customer clicks "Pay with PayPal", completes payment at PayPal, returns to store — cart is empty, order status shows "Pending Payment."

Cause 1: PayPal Return URL Session Mismatch

WooCommerce passes a session token when redirecting to PayPal. When PayPal returns, WooCommerce needs that token to restore the cart. If the session parameter is lost in the return URL, WooCommerce can't find the original cart.

Common triggers:

• Mixed HTTPS/HTTP content (some resources still load over HTTP)
• Third-party theme or plugin overrides WooCommerce's return_url
• CDN inadvertently strips URL parameters

Check in WooCommerce → Settings → Payments → PayPal → Settings:

• **Enabled**: YES
• **PayPal Sandbox**: toggle based on testing vs production
• **Debug Log**: enabled (for troubleshooting)
• **Receiver Email**: your PayPal registered email
• **Return URL**: should be `https://yourdomain.com/checkout/order-received/`

Cause 2: PayPal API Credentials Misconfigured

For the legacy PayPal plugin (not WooCommerce's built-in PayPal Checkout), manually enter:

• **Client ID** and **Secret**: from https://developer.paypal.com/ → Dashboard → My Apps & Credentials → REST API apps
• Ensure App's Redirect URLs and Webhook URLs are correctly set in PayPal Developer Dashboard

Testing method:

Use PayPal Sandbox for testing. Enable "PayPal Sandbox" in WooCommerce → Settings → Payments → PayPal → Settings, then complete a payment with a sandbox account. Watch if order status updates correctly after return.

---

Stripe vs PayPal: Which Is Better for Cross-Border Ecommerce?

This is the most common dilemma. Here's the 2026 fee breakdown from official pricing pages.

Fee Comparison

Factor	Stripe	PayPal
Domestic transaction fee	2.9% + $0.30	2.9% + $0.30
International card fee	+1.5%	+1.5% (higher in some cases)
Currency conversion fee	+1% when settlement currency differs	Higher, variable
Checkout experience	Embedded (customer stays on your site)	Redirect (leaves to PayPal page)
Mobile experience	Better, smoother card input	Depends on PayPal mobile UX

Key insight: Stripe's embedded checkout reduces cart abandonment by 10-23% on average (Stripe case studies). PayPal's brand recognition still converts many EU customers who prefer paying with PayPal balance.

Best practice: Enable both — let customers choose. Stripe for card payers, PayPal as fallback.

---

My Final Configuration (After 2 Weeks of Testing)

• **Stripe**: enabled (primary gateway, handles USD/EUR/GBP)
• **PayPal**: enabled (fallback for PayPal-preferring customers)
• **WooCommerce Payments**: disabled (less feature-rich than Stripe)

Key steps:

1. WooCommerce → Settings → Payments → enable both

2. Stripe Webhook URL explicitly allowed via Nginx config, all caches disabled

3. PayPal Return URL manually verified as /checkout/order-received/

4. Test mode (Sandbox) confirmed working before going live

---

Quick Troubleshooting Table

Problem	Most Likely Cause	Fix
Stripe Webhook 404	Cache plugin blocking /wc-api/	Exclude from cache + Nginx config
PayPal returns with empty cart	Return URL session lost	Check for HTTPS mixed content
Order status unchanged after payment	Webhook undelivered	Check Stripe Dashboard deliveries
Customer can't complete payment	API credentials expired	Regenerate Client ID/Secret
International fees higher than expected	Wrong settlement currency	Set Stripe settlement to customer's currency

---

Recommended Actions

If you're configuring WooCommerce payments:

1. Set up Stripe first, test if Webhook delivers successfully (Stripe Dashboard → Webhooks → Recent deliveries)

2. Configure PayPal second, test if order status updates correctly after return

3. Enable both simultaneously, let customers choose at checkout

👉 If you want to automate your WooCommerce store — product publishing, order management, customer support — with AI agents, check out MiniMax's AI Agent workflow solution: Try MiniMax AI Tools

---

Summary

Payment gateway configuration is the most underestimated part of WooCommerce setup. Webhook failures, session loss, and fee miscalculations directly impact revenue. My recommendation: get Stripe working first, add PayPal as backup, then monitor actual fees. For cross-currency settlements, always check your actual received amount — not just the advertised rates.

---

*Information current as of May 2026. For latest fees, check Stripe Pricing and PayPal Merchant Rates.*

📌 This article was AI-assisted generated and human-reviewed | TechPassive — An AI-driven content testing site focused on real tool reviews