Payment failed customer email templates
Opening
A payment failed message should be short, calm, and secure. The buyer needs to know that the order is not complete yet, what they can safely check, and where to retry without sending private payment details through email.
Before writing, separate the support message from the payment operation: support can explain the visible order status, but it should not collect card details, change the checkout total, promise a bank outcome, or manually process payment inside the reply.
This guide is for support wording only. It does not change checkout behavior, pricing, discounts, refunds, payment-provider settings, tax settings, payout settings, or customer account permissions.
Payment status triage table
| What the record shows | Safer first message | What not to do |
|---|---|---|
| Checkout attempt failed before an order was confirmed. | Say the order is not confirmed yet and ask the buyer to retry through secure checkout. | Do not promise fulfillment, reserve inventory, or ask for card details by email. |
| Provider says card, wallet, or payment method was declined. | Use neutral wording: the payment provider did not confirm the payment. Suggest checking billing details, available balance, card status, or another secure method. | Do not guess the decline reason or blame the buyer's bank unless the provider record explicitly says so. |
| Payment link, invoice, cart, or checkout session expired. | Ask the buyer to start a new checkout session and note that current totals and availability are shown at checkout. | Do not quote an old total as guaranteed if checkout can recalculate shipping, tax, discounts, or stock. |
| Payment is pending, authorized, or not yet captured. | Explain that fulfillment waits for a confirmed paid order and ask the buyer to check the provider or marketplace status. | Do not call it a completed charge or a refund unless the store record confirms that stage. |
| Buyer says they were charged but store shows unpaid. | Ask for a non-sensitive order reference and payment provider name only, then compare the store record with the buyer-facing status. | Do not request full screenshots, card numbers, bank login details, security codes, or passwords. |
Example 1: payment failed before order confirmation
Hi [customer name],
We could not complete order [order number / attempted order reference] because the payment did not go through.
Please return to checkout and try again with your preferred payment method. For your security, please do not send card numbers, security codes, passwords, or banking details by email.
Thank you,
[store name]Use this when the customer attempted checkout but the store has not confirmed a paid order.
Example 2: card declined or payment method rejected
Hi [customer name],
The payment method used for order [order number / cart reference] was declined by the payment provider. We are not able to see or update your full payment details from support.
Please check the billing details, available balance, card status, or try another payment method through the secure checkout page.
Thank you,
[store name]Use this when the provider or marketplace shows a declined payment status. Avoid guessing the reason for the decline.
Example 3: saved cart or invoice payment expired
Hi [customer name],
The payment link or checkout session for [order/cart reference] has expired before payment was completed.
Please start a new checkout session from the product page if you still want to place the order. Current product availability and checkout totals may be shown again during checkout.
Thank you,
[store name]Use this for expired payment links, abandoned checkouts, or invoice links when the order has not been paid.
Example 4: payment pending but not confirmed
Hi [customer name],
We can see that payment for [order number] has not been confirmed yet. Because the payment is not complete, the order is not ready for fulfillment.
Please check your payment provider or marketplace account for the latest status. If the payment completes, you should receive the normal order confirmation. If it does not complete, you may need to retry checkout.
Thank you,
[store name]Use this when the payment is pending or incomplete. Do not promise shipment until the paid order is confirmed.
Example 5: retry request after failed subscription or repeat purchase payment
Hi [customer name],
Your recent payment for [product / repeat order] did not complete. Please update or retry the payment method through the secure checkout or account area provided by [payment provider / marketplace].
We cannot collect payment details by email, but we can help confirm whether the order shows as paid after the retry is complete.
Thank you,
[store name]Use this when a repeat payment fails, while keeping credential and payment-data handling outside email.
Example 6: buyer says they were charged but store shows unpaid
Hi [customer name],
Thanks for letting us know. Our order record currently does not show a confirmed payment for [order number / attempted order reference].
Please check whether the charge is pending, authorized, reversed, or completed in your payment provider or bank app. If it shows as completed, reply with the order reference and the payment provider name only. Please do not send card numbers, screenshots with full payment details, passwords, or security codes.
Thank you,
[store name]Use this when the buyer reports a charge but the store record is unpaid. Ask only for non-sensitive references.
Payment failed email checklist
- Verify whether there is a paid order, unpaid attempt, pending authorization, expired payment link, abandoned checkout, or buyer-facing charge claim.
- State that the order is not confirmed or not ready for fulfillment unless payment has completed.
- Send the buyer back to the secure checkout, payment provider, or marketplace flow instead of collecting payment details by email.
- Never request card numbers, security codes, passwords, bank login details, full unredacted screenshots, or payment-account access.
- Avoid saying the bank declined the charge for a specific reason unless the provider record explicitly states that reason.
- Clarify whether product availability, shipping timing, and totals are confirmed only after checkout completes.
- When a buyer says they were charged, separate an authorization hold, pending charge, completed payment, reversal, and duplicate attempt before choosing wording.
Safe detail request checklist
If support needs context, keep the request narrow and non-sensitive. Ask for the order reference, attempted checkout email, date of the attempt, payment provider or marketplace name, and the last safe status message the buyer saw. Do not ask for full card numbers, CVV/security codes, passwords, bank screenshots, wallet login pages, one-time codes, or identity documents.
Payment retry wording examples
- Simple retry: “Please return to the secure checkout page and try again with your preferred payment method. We cannot take payment details by email.”
- Provider-declined retry: “The payment provider did not confirm the payment. You may want to check the billing address, card status, wallet balance, or use another secure method at checkout.”
- Expired link retry: “That checkout link has expired, so please start a new checkout session. The current total and availability will be shown before you pay.”
- Buyer-says-charged follow-up: “Our order record does not show a confirmed paid order yet. Please check whether your provider shows the amount as pending, authorized, reversed, or completed, and send only the order reference and provider name if you need us to compare records.”
Common payment email mistakes
| Mistake | Safer alternative |
|---|---|
| Asking the buyer to email card details or screenshots with full payment information. | Direct them to the secure checkout or payment-provider flow, and ask only for a non-sensitive order reference if needed. |
| Promising shipment while payment is still pending. | Say fulfillment starts only after the order is confirmed as paid in the system. |
| Blaming the buyer's bank or card without proof. | Use neutral wording: the payment did not complete or the provider did not confirm it. |
| Changing prices, discounts, or checkout instructions inside a support reply. | Keep the reply about communication and point to the current checkout page for any live totals. |
When to use a different guide
If the order is already paid but has not shipped yet, use the order not shipped yet templates. If the buyer is asking to cancel after payment, use the cancellation request response templates or order cancellation confirmation templates after status is verified. If the issue is about refund timing after a confirmed refund process, use the refund process email templates, refund approved but not received templates, or partial refund templates depending on the refund stage. If the buyer only needs an invoice or receipt for a successful payment, use the invoice or receipt request templates.
FAQ
Can I ask the customer to send payment details by email?
No. Keep payment credentials out of support email. Ask the buyer to use the secure checkout, payment provider, or marketplace flow.
What if the buyer says they were charged?
Check the store record first. If your record is unpaid, ask for a non-sensitive order reference and provider name only, then direct the buyer to verify whether the amount is pending, authorized, reversed, or completed with their payment provider.
What if a payment failed more than once?
Use neutral wording and suggest trying a different secure payment method or contacting the payment provider. Do not diagnose the bank, card, wallet, fraud filter, or marketplace account unless the provider record gives a specific support-safe reason.
Can this template change checkout, pricing, or refunds?
No. The wording only explains a verified failed-payment status and safe next steps. It does not change checkout behavior, price, discounts, tax, refund policy, payout settings, payment-provider configuration, or customer-account permissions.
Need a larger set of support wording? View sample replies or browse the SellerTone guide hub before adapting any template to your own store policy.