Gatemi Stripe for WooCommerce FAQ and Troubleshooting

Do I need a Stripe account?

Yes. The plugin talks to Stripe with your own API keys. There is no Gatemi account, no shared platform account and no middleman, and no payment data is sent to Gatemi.

No Stripe method shows at checkout

Check in this order:

  1. Are keys saved for the current mode? The status pill on WooCommerce → Stripe must read Connected — Test mode or Connected — Live mode. A mode counts as connected only when both its publishable and its secret key are present. Until then, no method is offered.
  2. Are the keys for the right mode? If you see These keys are for the other Stripe mode, live keys are in the test boxes (or the other way round). Stripe rejects every payment until they match.
  3. Is the method switched on? Methods are switched on under Payment methods on WooCommerce → Stripe — not on WooCommerce's Payments tab.
  4. Does the order fit the method's limits? A method is shown only when the store currency fits its currencies and, where it has a country limit, the customer's billing country fits. iDEAL needs EUR and a Dutch billing address; BLIK needs PLN and Poland. This is deliberate: a method offered outside Stripe's limits fails at the last step of checkout, after the shopper has typed everything.
  5. Is there a product rule? A product's Payments tab can block or allow-list methods, and a rule on any item applies to the whole cart.
  6. Is it enabled in Stripe? Most methods other than cards must also be turned on in the Stripe Dashboard under Settings → Payment methods.

A method is listed but Stripe refuses it

The method is switched on in the plugin but not in your Stripe account, or Stripe has not yet approved your business for it (common for buy-now-pay-later methods). Turn it on in the Stripe Dashboard. With Log Stripe requests on, Stripe's own error message is in WooCommerce → Status → Logs under the source gmstripe. Errors are logged even with logging off.

Webhooks are failing in the Stripe Dashboard

Stripe shows the response code for each delivery.

  • 401 — there is no signing secret saved for the current mode, or the signature did not match. Copy the Signing secret (whsec_…) of this endpoint into Test signing secret or Live signing secret, matching the mode the endpoint was created in. A test-mode endpoint and a live-mode endpoint have different secrets.
  • A delivery more than five minutes old is refused. The signature carries a timestamp; replays outside the tolerance are rejected. If your server's clock is wrong, every event fails — check it.
  • 404 — the URL is wrong. The endpoint is /wp-json/gatemi-stripe/v1/webhook; copy it from the settings screen.
  • A security or firewall plugin blocks it. The endpoint is public by design (Stripe cannot log in) and is trusted only after the signature check. Allow POST requests to that path.

A copy of an event already handled is answered Already processed. and not applied twice, so Stripe's retries are safe.

Do I have to set up webhooks if I only take cards?

A card payment is complete before the shopper leaves the page, so the order is right without them. Set them up anyway: refunds made in the Stripe Dashboard, disputes and Radar reviews only reach the order through webhooks, and so does every bank debit, voucher and redirect method whose shopper does not come back.

An iDEAL or Klarna order stayed "Pending payment"

The shopper went to their bank and did not come back to your site — they closed the tab, or their connection dropped. The order is settled by the payment_intent.succeeded or payment_intent.payment_failed webhook. If it stays pending, your webhook is not reaching the site; see above.

Apple Pay does not show

Apple fails silently: no button and no error. Check that:

  1. Apple Pay is switched on under Payment methods, and the page is in one of the Express checkout locations you ticked.
  2. The site is on HTTPS.
  3. The domain is registered: the association file is pasted under Apple Pay domain verification and Register this domain with Stripe was pressed — once in test mode and again in live mode, and for each domain (with and without www) shoppers use.
  4. You are testing in Safari on a device with a card in Wallet.

Google Pay needs HTTPS and a browser signed into a Google account with a card.

The express button disappeared on one product

When Product Add-Ons, TM Extra Product Options or Advanced Product Fields put priced options on a product, the express button is removed from that product page. Pressing it would buy the base product without the options the shopper chose. With German Market or Germanized active, express buttons are switched off everywhere, because German law requires a confirmation step a wallet button skips.

Express checkout on the Cart and Checkout blocks takes me to the checkout

That is how version 1.0.0 works on the blocks: after the shopper confirms in the Apple Pay or Google Pay sheet, they are taken to the checkout page to finish rather than the order being placed from the sheet. On classic pages the order is placed straight from the sheet.

Does it work with the Cart and Checkout blocks and HPOS?

Yes. The plugin declares compatibility with High-Performance Order Storage and with the Cart and Checkout blocks, and the blocks run the same Stripe flow as the classic checkout.

Does it work with page caching?

The checkout, cart and My Account pages should never be cached — every cache plugin excludes them by default. Product pages with express buttons can be cached: the amount charged is always worked out on the server from the cart at the moment of payment, never taken from the page.

An authorised order was not captured in time

With Authorise now, capture later, card authorisations expire after about a week. Capture from the order's Order actions menu before then. After expiry the money is released back to the shopper and the order must be paid again.

I refunded in the Stripe Dashboard, but WooCommerce does not show a refund

That is intended. The charge.refunded webhook adds an order note with the total refunded at Stripe, but does not create a WooCommerce refund, because one created at the same moment as an admin's own refund would be recorded — and restocked — twice. Record it in WooCommerce yourself if you refunded in Stripe. Refunds made with WooCommerce's Refund button go through Stripe and are recorded once.

I switched to live mode. Can I still refund test orders?

Yes. Each order remembers the mode it was paid in (_gmstripe_mode), and refunds, captures and voids use that mode's keys. Keep your test keys saved until you no longer need them.

I am moving from another Stripe plugin

Use the same Stripe account's keys. Past orders and live subscriptions taken by WooCommerce Stripe Gateway, WooPayments, Payment Plugins for Stripe or FunnelKit's Stripe gateway are read through a gateway-id map, so they can be refunded and keep renewing. Nothing is rewritten. Deactivate the old plugin first: nothing is adopted while it is still active. See Moving from another Stripe plugin.

What happens when I uninstall?

Deleting the plugin removes gmstripe_settings, gmstripe_version, every gmstripe_seen_* webhook claim, the per-method gateway settings (woocommerce_gmstripe_*), the daily cleanup event and the Stripe customer ids on user profiles. Order meta is kept: an order is a financial record, and the payment intent id on it is how you reconcile a payment that happened. Saved cards stay at Stripe, in your account. Deactivating removes nothing.

Are card details stored on my site?

No. They are typed into Stripe's own iframe and exchanged for a payment method id before the checkout is submitted. Your server only ever sees that id.

Shopping Cart
Scroll to Top