A verification step that is not completed is not a problem with your store, and it never leaves money in a strange place. In every case below, no payment was taken and there is nothing to refund. What changes between the cases is what gets recorded, and whether the bank ever said anything about the card.
The first case is the one that turns into support tickets. To the customer a failed verification looks like a declined card, and the order note opens with the word "failed", so it is easy to read as the gateway being broken. It is neither. The card's own bank was asked to confirm the cardholder and did not, so the payment was stopped before anyone was asked to approve it.
Case 1. The verification failed
The customer completed the step, or the bank tried to confirm them in the background, and the bank did not confirm the cardholder. The payment is stopped there, before it is ever submitted to the card issuer for approval, so no money moves.
What the customer sees: the same message on your WooCommerce checkout, on the customer payment page for a pending order, and on a WeeConnectPay payment link: "Your card could not be verified with your bank. Please try again, or use a different card." After several failed attempts in a row, the wording falls back to a short general message that does not name the reason. On a WooCommerce store that message is "The payment could not be processed. Please try again." The fallback is a deliberate protection against people testing stolen cards on your checkout.
What your order shows: the order moves to Failed and gets a note. The note opens with "Clover payment failed.", and the line right under it is the one to read: "The card could not be verified with the customer's bank, so the payment was stopped before it reached the issuer for approval. Nothing is wrong with your store. The customer can try again or use a different card." The lines below that are for support: the charge ID, and the raw code and message Clover returned. When the bank had asked the customer for the verification step, the note ends with "3-D Secure:" "Authentication failed during challenge." When the bank refused in the background instead, the 3-D Secure line shows the result, for example "Authentication failed".
What your dashboard shows: the attempt appears in Transactions as a payment that did not go through. Opening it shows the Why this payment did not go through panel, which carries the same explanation as the order note: "The card could not be verified with the customer's bank, so the payment was stopped before it reached the issuer for approval. Nothing is wrong with your store. The customer can try again or use a different card."
Case 2. The customer walked away mid-verification
The bank's verification window opened and the customer closed it, switched away, or simply gave up. Nothing was verified and nothing was submitted for approval, so no money moved and there is nothing to refund or cancel.
What your order shows: the order stays in Pending payment, with a note saying a 3-D Secure flow was initiated and is waiting for the browser to complete verification. Nothing else is written until the customer comes back. They can pay in the usual way, from the checkout or from the Pay for this order link in the order email, and the new attempt starts fresh.
Case 3. Verified, then declined
This one looks similar to your customer but is a different thing. Verification succeeded, the payment went to the card issuer for approval as normal, and the issuer refused it. That is an ordinary decline, and it has nothing to do with 3-D Secure.
Your order note and your dashboard both tell the two apart, and they do so no matter how many attempts came before. This is the quick reference.
| Failed verification | Declined card | |
|---|---|---|
| Who said no | The customer's bank, when asked to confirm the cardholder | The card issuer, when asked to approve the amount |
| What the customer saw | "Your card could not be verified with your bank. Please try again, or use a different card." | "Your card was declined. Please try a different card or contact your bank." |
| What the order note says | "The card could not be verified with the customer's bank, so the payment was stopped before it reached the issuer for approval. Nothing is wrong with your store. The customer can try again or use a different card." | "The customer's card issuer refused the payment. Nothing is wrong with your store. The customer can retry with another card or contact their bank." |
| Was money taken | No | No |
| What fixes it | Another attempt, another card, or a word with the customer's bank | Another card, or a word with the customer's bank |
The checkout message is the weaker signal of the two. After several failed attempts in a row, both cases show the same short general message to the customer, while the order note and the dashboard keep the full explanation every time.
What to tell the customer
The verification step is run by the customer's own bank, so the useful advice is about the card and the bank rather than about your store.
- It was not a decline, and no money was taken. The bank was asked to confirm who was using the card and did not. Nothing was charged, and nothing about the card's balance or standing was checked.
- Try again. A fresh attempt is often verified, especially if the first one timed out while they were looking for the code.
- Try a different card. Another card means another issuer and another verification.
- Ask their bank about the verification. The bank chooses how the code is sent, to which phone number or email, and whether the banking app is involved. If the customer never receives the code, their bank is the only place that can fix it.
- Never ask for the code. The one-time code is entered in the bank's own window and no one at your store ever needs it. Nobody legitimate will ever ask a customer to share it.
If it keeps happening
A run of failed verifications from different customers and different cards is worth a look. Email support@weeconnectpay.com with the order numbers, the times of the attempts, and what the customers saw on screen, and we will trace exactly what was sent and returned for those payments. If you want to pause verification while we look, Turning on 3-D Secure for your store covers turning the store setting back off.