The card method does not show at checkout
Check in this order:
- Are the keys saved for the current environment? The badge on the Connection tab must not read Not connected. Remember a fresh install starts on Sandbox, so the sandbox keys are the ones it uses until you switch to Live.
- Is Enable Credit / Debit Card on (Credit card tab)?
- Is the store currency supported? The card method is offered only in AUD, CAD, DKK, EUR, GBP, NOK, NZD, PLN, SEK or USD. eCheck and Google Pay are offered only in USD.
- Is the Public Client Key stored? Without it Accept.js cannot tokenize the card. See the next question.
"We could not automatically retrieve your Public Client Key"
Your Authorize.Net account has no Public Client Key yet. In Authorize.Net go to Account → Settings → Security Settings → Manage Public Client Key, create one, then press Save changes on the Connection tab so the plugin can read it.
"Authorize.Net credentials are invalid for the selected environment"
The API Login ID and Transaction Key do not match the environment chosen. Sandbox keys come from sandbox.authorize.net, live keys from account.authorize.net, and they never work in the other. A Transaction Key also stops working the moment a new one is generated in Authorize.Net.
"Please enter API Login ID, Transaction Key, and Signature Key"
All three are needed for the environment you are saving. The Signature Key is not used to take payments, but without it no webhook can be trusted.
Webhooks are failing
- 401 in Authorize.Net's webhook log — the Signature Key saved here is not the account's current one (a new key was generated), or is missing for this environment. Generate a new Signature Key, paste it and save.
- 400 — the request had no signature header or no event; usually a proxy or firewall stripping headers. Allow POST to
/wp-json/gatemi-authnet/v1/webhook. It is public by design and trusted only after the signature check. - Nothing arrives at all on
localhostor a staging site behind a login: Authorize.Net cannot reach it.
The webhook is registered when you save the connection. Saving again updates its event list if it is missing any.
Why can I not make a partial refund?
The transaction has not settled yet. Before settlement Authorize.Net only allows voiding the whole transaction. Refund the full amount to void it now, or wait for settlement (usually within 24 hours) and refund part of it.
Why can an eCheck not be refunded after it settles?
The plugin does not keep customers' bank account details, and Authorize.Net needs them to send money back. Refund it in the Authorize.Net merchant interface; the refund webhook then records it on the WooCommerce order.
An order is "On hold — held for review by Authorize.Net fraud filters"
Your Fraud Detection Suite filters held the payment. Approve or decline it in the Authorize.Net merchant interface. The webhook then completes the order or marks it failed. If the webhook is not working, the order stays on hold.
Where is the Capture button?
Order actions → Capture Authorized Payment, on an order paid with Authorize only that is still On hold. It is not shown for other statuses.
Google Pay does not show
Google Pay must be enabled in Authorize.Net (Account → Digital Payment Solutions) and here, the store currency must be USD, the site must be on HTTPS, and the Gateway ID must be filled in (it is detected when you save the API keys). For live payments add your Google Pay merchant ID from the Google Pay & Wallet Console. The express button shows on the pages ticked in Show Google Pay button on.
Does it work with the Cart and Checkout blocks and HPOS?
Yes. It declares compatibility with High-Performance Order Storage and has block integrations for the card, eCheck, Google Pay and the Google Pay express button.
Does it work with page caching?
Never cache the cart, checkout or My Account pages; cache plugins exclude them by default. The card token is created in the shopper's browser at the moment they pay.
A customer was charged twice
Authorize.Net refuses an identical transaction within 120 seconds, which stops a double click. If a capture arrives by webhook for an order your store had already cancelled or failed, the plugin adds a note asking you to reconcile it rather than changing the order.
Saved cards disappeared
Deleting a customer profile or payment profile in Authorize.Net removes the matching saved card from your store through the webhook.
What happens when I uninstall?
By default, deleting the plugin keeps your settings and API keys, so deleting and reinstalling it does not lose the store's connection. It always clears the webhook-dedupe claims and every gatemi_authnet_ transient.
Tick Remove data on uninstall (Credit card tab) and deleting the plugin also removes the three gateway settings options (including the API keys), the stored Public Client Keys, the webhook ids and the review-notice options.
Either way, order meta, saved payment tokens and customer profile ids on user accounts are kept, and the webhook subscription and the CIM profiles at Authorize.Net are not removed. Deactivating removes nothing.
What does the plugin send outside my site?
Transactions go to api.authorize.net (apitest.authorize.net in sandbox), webhook registration to api.authorize.net/rest/v1/webhooks, and Accept.js loads from js.authorize.net. Google's pay.js loads only when Google Pay is switched on. Nothing is sent to Gatemi.
