ACH return codes are technical, but the customer conversation does not have to be. Most people do not know what R01 or R10 means, and a cold message can feel like an accusation. A clear, calm, helpful note solves the problem faster and keeps the relationship.
This guide explains how to write customer messages for common returns. Rules about fees and notices vary, so confirm details with your bank, your processor, and a legal advisor where needed.
Customers often feel embarrassed or confused about a failed payment. A respectful message invites a fast reply. A harsh one invites a dispute or a cancellation.
Keep messages short, specific, and free of jargon.
The amount and date of the payment
A plain explanation of what happened
What the customer can do
A secure way to pay or update details
A deadline and a contact point
Avoid putting full account numbers in any message.
Say the payment could not be completed because the account did not have enough available funds. Offer a secure link to retry or pay another way, and mention any late fee only if your agreement allows it.
Say the bank could not match the account details. Ask the customer to update their information through a secure portal. Never ask them to send bank details by email or text.
Plain language helps both you and your customers. Resources such as Secure Merchant Solution publish plain-language guides on payment topics, which can help you prepare before you write your templates.
Use any guide as background, and confirm details with your processor.
Be careful and neutral. Say the bank reported an issue with authorization, and that you would like to understand what happened. Do not accuse the customer, and do not retry the debit. Offer a call or a reply path.
Acknowledge the stop, ask whether the customer meant to cancel, and offer help. If they cancelled, confirm it and stop future debits.
Polite and direct
Specific about amounts and dates
Free of legal threats unless required
Easy to answer with a single reply
Consistent across customers
Write templates for each common code, review them for tone and accuracy, and train staff to personalize lightly. Keep a log of messages sent.
Using code numbers without explanation
Asking for bank details by email
Threatening or blaming customers
Promising retries you cannot make
Forgetting to follow up
Good customer messages turn ACH return codes into simple, solvable problems. Explain in plain language, offer a secure fix, and stay consistent. Confirm current rules with your bank, your processor, and a legal advisor where needed, and customers will respond faster.
1. Should I mention the return code?
Usually no. Explain the reason in plain words.
2. Can I ask for bank details by email?
No. Use a secure portal or payment link.
3. Should I mention fees?
Only if your agreement allows them and rules permit.
4. How quickly should I contact customers?
As soon as you confirm the return.