Stripe Payment for WooCommerce

In test mode, use Stripe’s specific test card numbers — not real card numbers. The standard test card is 4242 4242 4242 4242 with any future expiry and any 3-digit CVC. If even 4242… declines: (1) verify test mode is active in both the plugin settings and Stripe dashboard simultaneously; (2) check the webhook configuration — a misconfigured webhook can cause payment intent status mismatches; (3) review the Stripe dashboard → Developers → Logs for the specific API error message.

Apple Pay requires: (1) your site to use HTTPS; (2) domain verification with Stripe — in the Stripe plugin settings, click “Verify Domain” which registers your domain with Apple Pay via Stripe’s API; (3) the customer to be using Safari on an Apple device; (4) the Apple device to have a payment card configured in Apple Wallet. If all conditions are met but Apple Pay still does not show, verify the domain verification was successful in Stripe Dashboard → Settings → Payment Methods → Apple Pay.

Stripe webhooks notify WooCommerce of payment events asynchronously. If orders stay pending: (1) in the Stripe plugin settings, find the webhook endpoint URL (typically yoursite.com/wc-api/stripe-webhook); (2) go to Stripe Dashboard → Developers → Webhooks and verify this URL is registered and receiving events; (3) check Stripe webhook logs for delivery failures — a 404 or 500 response from your site causes failures; (4) if the URL returns 404, flush WordPress rewrite rules (Settings → Permalinks → Save) and test again; (5) verify your hosting firewall does not block Stripe’s webhook IP range.

Klarna requires the Premium plugin. In WebToffee Stripe settings → Payment Methods, enable Klarna. Klarna availability depends on your store’s country and currency (available in US, UK, EU, and several other markets). Ensure your Stripe account has Klarna enabled (Stripe Dashboard → Settings → Payment Methods → Klarna). At checkout, Klarna appears as a payment option with monthly installment display. Klarna handles the payment terms directly with the customer — your store receives the full amount immediately from Stripe.

Saved payment methods require Premium. In WebToffee Stripe settings, enable “Save Payment Methods.” Customers must be logged in to save their card — guest checkout does not support saved cards. On checkout, logged-in customers see a “Save card for future purchases” checkbox. Returning customers see previously saved cards listed at checkout for one-click payment. Saved card data is stored securely in Stripe, not on your server.

Both are maintained and reliable. The official WooCommerce Stripe plugin (by Automattic) is deeply integrated with WooCommerce and receives updates alongside WooCommerce releases. WebToffee’s plugin is often preferred by users who report better support responsiveness and a more complete free tier. The choice often comes down to specific feature needs — check both plugins’ current feature lists before deciding.

No — Stripe’s standard transaction fees (2.9% + 30¢ in the US for card payments, varying by country) apply regardless of which plugin is used. The WebToffee plugin itself charges no per-transaction fees — only its annual license fee. Check stripe.com for your specific country’s fee schedule.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.