Order Changed from Pending Payment to Failed—Was the Customer Charged?

14 hours ago

6 min read

A customer says money left their account. Your store shows Pending Payment, then changes the order to Failed. Asking them to try again immediately can turn one uncertain payment into two real charges.

An order status is not a bank statement, and a bank’s pending line is not proof that your business captured funds. Before you fulfill, refund, cancel, or retry anything, reconcile three records: the store order, the payment provider transaction, and the customer’s bank entry.

This evidence-first workflow establishes whether money was authorized, captured, declined, reversed, or never reached the provider. Only then should you choose the next action.

First: Do Not Ask the Customer to Pay Again

Pause the retry until the payment provider confirms the first attempt’s outcome. A failed store order can coexist with a card authorization hold, a delayed payment, or a successful provider transaction whose update never reached the website.

Do not fulfill because a screenshot says “pending.” Pending usually means the bank reserved funds while waiting for the merchant’s final message. It may disappear without becoming a posted charge.

If the provider shows captured funds, follow Webcurry’s double-charge diagnostic before initiating another payment.

What the Payment Statuses Mean

Pending payment

The order exists, but the platform has not confirmed completed payment. The provider may still be processing, waiting for authentication, reviewing the transaction, or completing an off-site method. Wix pending orders can later become Paid or Declined. WooCommerce uses Pending payment when an order exists without confirmed payment.

Failed or declined

The platform did not receive confirmation of success. Causes include a bank decline, failed 3-D Secure authentication, unsupported currency, provider-account restriction, expired checkout session, or gateway error. The label does not prove that no temporary authorization exists.

Authorized or requires capture

The issuer approved the amount and reserved funds, but the merchant has not captured them. This is neither a completed sale nor a failure. Capture only if the order is valid; otherwise void the authorization.

Processing

The provider is waiting for a final result. Delayed methods can remain here longer than card payments. Do not force the store status or create another payment merely because the update is not immediate.

Successful or captured

The provider confirms payment completed. If the store still says Failed, inspect the handoff: a missed webhook, callback error, plugin conflict, timeout, or mismatched transaction reference.

Voided, canceled, or reversed

The authorization was released or payment was canceled before settlement. The customer may still see a pending line until their bank removes it. Do not refund an authorization that was never captured.

Reconcile Three Records

Store record: order number, current status, created time, amount, currency, customer email, payment method, order notes, and transaction or payment ID.
Provider record: exact transaction, PaymentIntent, charge, or payment ID; amount and currency; status chronology; decline reason; authorization and capture timestamps; and webhook delivery history.
Bank evidence: whether the line is pending or posted, its date, amount, merchant descriptor, and whether it later disappeared or settled.

Convert timestamps to one time zone before comparing them. Match currency as well as amount. If no provider transaction matches, the failure likely occurred before a charge was created. If the provider shows success, treat that financial record as the source of truth and repair the order connection.

A Safe Diagnosis Sequence

1. Check whether the bank line is pending or posted

Ask for the status—not a full statement or card number. A pending line usually indicates an authorization hold. A posted line needs immediate reconciliation with the provider. Keep sensitive payment data out of email.

2. Open the order’s payment details and notes

Find the payment ID, provider response, failure reason, and timestamps. In Wix, use Payment info. In WooCommerce, read order notes. In Shopify, inspect the order timeline and abandoned checkout if no order completed.

3. Search the provider with the exact reference

Search by transaction ID first; use amount, email, and time only as fallback clues. Confirm whether the status is failed, processing, authorized, captured, canceled, or refunded.

4. Reconstruct the chronology

A common sequence is: authorization succeeds, the customer closes the tab or the return request times out, the store marks the attempt failed, and the provider later sends a success webhook. Check whether that event was delivered, rejected, duplicated, or received before the order was ready.

5. Choose the action supported by the provider

Failed with no capture can be retried after fixing the cause. Authorization only should be captured or voided. Processing should be allowed to finish. Captured funds require restoring or recreating the order and preventing another retry.

Failed with no captured funds: fix the decline or configuration issue, then let the customer retry once.
Authorization only: capture it for a valid order or void it; do not refund an uncaptured hold.
Processing: wait for the documented final event and keep fulfillment paused.
Captured but order failed: restore or recreate the order, link the transaction, notify the customer, and stop another retry.
Captured twice: identify the duplicate and refund only that duplicate transaction.
Posted bank charge with no provider match: escalate with date, amount, descriptor, and safe reference details.

Wix: Check Payment Info and the Provider

Copy the Payment ID from the Wix order’s Payment info and open the provider transaction. Wix describes Pending as approved but not yet available and Successful as captured; Failed means the transaction failed. Two-step payments can remain Authorized until captured.

If Wix says Failed while the provider shows successful capture, do not manually mark the order paid until the transaction, amount, currency, and customer match. Investigate provider setup, 3-D Secure, delayed processing, and the event handoff. For the opposite incident, use Webcurry’s payment-successful-but-no-order guide.

Shopify: Separate the Order from a Card Hold

Shopify notes that a failed attempt can still produce a temporary pending charge that later reverses. Confirm the attempt in the gateway and Shopify timeline. A pending bank item is not a completed Shopify payment.

If the charge posts and Shopify has no successful transaction, contact the gateway before another checkout attempt. Verify checkout still offers the intended option with the missing payment methods diagnostic.

WooCommerce: Read Order Notes Before Retrying

WooCommerce defines Pending payment as an order received without confirmed payment and Failed as declined or unsuccessful. Order notes often contain the gateway response, transaction ID, or webhook update that explains the change.

Check the gateway dashboard and logs. Exclude cart, checkout, and account pages from cache; verify webhook endpoints; and use the gateway’s test mode. Never flip the order to Processing solely to make it look correct—the financial record must support it.

Why Pending Payment Changes to Failed

The customer did not complete 3-D Secure or another authentication step.
The bank declined after an initial authorization request.
The provider account is restricted, incomplete, or not enabled for the currency.
The checkout session expired while the provider was still processing.
A redirect, popup, cookie, browser extension, or network interruption broke the return path.
The payment succeeded, but a webhook or callback failed to update the order.
A plugin, app, custom checkout script, or aggressive cache changed the expected flow.
A delayed payment method was treated like an instant card payment and timed out too early.

Customer-facing wording should reflect uncertainty. “Payment not confirmed” is safer than “You were not charged” until reconciliation is complete.

Prevent Repeat Incidents

Block fulfillment until a trusted captured or paid event is recorded.
Store the provider transaction ID on the order and make it searchable.
Handle webhooks idempotently so retries cannot create duplicate charges or fulfillment.
Log status changes with event IDs, timestamps, amounts, and currencies.
Test success, decline, authentication failure, delay, abandonment, and duplicate callbacks.
Show a visible processing state instead of letting customers click Pay repeatedly.
Alert staff when a captured provider transaction has no paid order.

After correcting the payment record, confirm the operational follow-through. If no message arrived, use the order-confirmation email diagnostic. If a refund is needed, keep the provider reference linked and follow the refund tracing guide.

What to Tell the Customer

A clear message is: “We can see that the order was not confirmed, and we are checking the payment provider before asking you to try again. Please do not repeat the payment yet. If the bank entry is still pending, it may be an authorization hold rather than a completed charge. We will update you after matching the transaction reference.”

Do not guarantee when a bank will release a hold; the issuer controls that timing. If payment posted, provide a case reference and explain whether you are restoring the order or tracing a refund.

The Decision Rule

Do not let the store label make the financial decision. Match the order, provider, and bank evidence. A failed transaction can be retried; an authorization should be captured or voided; a processing payment should finish; and a captured payment must be linked to an order before the customer pays again.

If the records still disagree, contact Webcurry for a checkout and payment-flow review. Bring the order number, payment reference, timestamps, amount, currency, and redacted provider events—not card details.

Authoritative References

Wix Help Center: Troubleshooting Pending or Missing Orders; Wix Payments transaction statuses.
Shopify Help Center: checkout payment troubleshooting and pending charges after failed attempts.
WooCommerce documentation: order statuses and failed-order troubleshooting.
Stripe documentation: PaymentIntent status lifecycle and event handling.