Shopify Failed Payment Customer Email Template: What to Send in Each Case

A failed payment attempt does not always call for an email asking the customer to try again. You might have an existing Shopify order that is still unpaid, a checkout that never became an order, or a customer who sees a charge you cannot yet reconcile. Check which case you have before choosing a message. In particular, do not send a payment link while a reported charge is unresolved.

Check the payment state before you email

Search your Shopify records using the customer details and any order reference they supplied. If you find an order, check its current payment information and any later attempts—not just the first declined attempt. If you find a checkout but no corresponding order, do not describe it as an unpaid order. If you cannot establish either, ask for enough information to locate the purchase before making a payment claim.

These templates cover payment uncertainty. For other situations, see the broader collection of customer service templates for EU online stores.

If a customer contacts you after an email has already gone out, reassess the case. A message that was accurate before their next payment attempt may no longer be the right reply.

Use this template when a card payment was declined

Use this email for an existing order when the payment attempt is recorded as declined and you have verified that the order is still unpaid. A decline tells you the outcome of that attempt, not whether the bank, card details or available funds caused it. Check that the route you offer is appropriate for this order before sending.

Replace the status placeholder with wording your records support, such as “unpaid”; do not copy an internal label a customer may not understand. Open the destination before sending and verify that it is an approved shop route for this order. If you cannot verify a suitable link, remove it and tell the customer how to reach their account or your storefront instead. Do not reuse a payment link from an old conversation without checking it.

If the customer replies that they can see a charge, stop using this template. A currently unpaid order does not, by itself, resolve what the customer sees in their banking app. Investigate before suggesting another attempt.

Use this template when payment was not completed

A checkout that never became an order needs different wording. Do not assign it an order number, say that the order was cancelled, or imply that stock and prices from the earlier checkout have been held.

Use this wording only when you can identify the checkout in question. If you cannot, ask the customer to clarify which purchase they mean rather than claiming you found it. Check the route in the placeholder: if the earlier checkout is unavailable, point to the shop account or storefront instead of promising that the old cart can be resumed.

If you find an order while preparing the email, stop and inspect its payment state; this is no longer an incomplete-checkout message. Add a payment deadline only if you can verify both the deadline and what happens when it passes. Otherwise, leave it out.

Reply differently when the customer fears a duplicate charge

A banking-app entry can appear while the payment outcome is still unresolved. What the customer sees is important, but it is not proof that duplicate charges have settled. Your immediate goal is to prevent another attempt while you check.

Check the order and the payment attempts you can locate, including any later changes in status. In the case notes, separate “customer reports two entries” from “shop records show [verified state].” If the entries do not reconcile, contact your payment provider through your merchant support route. Do not diagnose the banking-app entries from an order status alone, promise when an entry will disappear, or give a refund date you cannot substantiate.

Follow up with a concrete update even if the investigation is ongoing: state what your records show, what remains unconfirmed and whether you are waiting for the payment provider. Keep the case open if the customer’s report and your records still differ.

Choose wording that matches the evidence

Use the sentence that describes the information you actually have. A customer-reported pending entry is not the same as a payment marked pending in your shop’s records; say whose information you are describing.

What you can verify	Customer-facing wording	Next action
Payment is not confirmed and the outcome is unclear	“We can’t confirm the payment outcome yet. We’re checking it before advising you to try again.”	Investigate; omit the payment request.
Your available payment information shows pending	“The payment currently appears as pending in the information available to us. Please wait for our update before making another attempt.”	Check the appropriate payment records and follow up.
The customer reports a pending bank entry, but you cannot reconcile it	“You’ve told us the entry appears as pending in your banking app. We’re checking it against our records before advising you to pay again.”	Record the report and investigate the discrepancy.
An existing order is verified as unpaid, with no unresolved charge report	“We haven’t received payment for [order reference]. You can review the order at [approved shop route].”	Share the route only after checking that it fits this order.

Do not write “your bank rejected your card” to explain a decline you cannot diagnose. Do not write “your order is cancelled” unless you have verified that status. And do not write “pay again now” while a reported charge or pending attempt is unresolved. When in doubt, acknowledge the report and investigate rather than sending a reminder.

Put the templates into your support workflow

Save the messages separately, with a note above each one stating its send condition. Keep placeholders for the verified payment state, an order reference only where one exists, and an approved shop route. Before sending, have the agent check those fields against the current record and the latest customer message. Delete any sentence whose factual claim has not been verified.

In the case notes, record the last payment state checked, the customer’s description of any charge, the link shared, and whether a payment-provider enquiry is open. This gives the next agent a way to avoid repeating a payment request after the customer has raised a concern.

If you use askVela’s Shopify integration, order lookup can show payment information in chat to the extent the shop supplies it. Agents can use the team inbox for payment enquiries to keep internal notes with the conversation. That order context does not establish whether a disputed card charge has settled; investigate discrepancies through the appropriate payment records and provider.

Finally, review any reusable AI guidance. With askVela’s bot rules and test console, you can write guidelines and preview a response without a real chat. Test a prompt such as “I see a charge, but you say my order is unpaid.” Your guideline should tell the bot not to request payment credentials or recommend another attempt, and to direct the unresolved question to a person for review.