A returned mobile ACH payment means the bank that received your transfer rejected it and sent the money back to your account

When you send money via ACH (Automated Clearing House), the receiving bank has a window to review the transaction. If something doesn't match—a closed account, insufficient funds on the receiving end, a mismatched account number, or a fraud flag—the bank can reject it. The funds return to your account, usually within one to three business days, though the exact timeline depends on your bank and the reason for the return.

A returned mobile ACH payment CONA specifically means the receiving bank rejected it because the account number or routing information didn't match their records. CONA stands for "Correct On Next Attempt"—the bank is telling you the account details need to be verified and corrected before you try again. This is different from other return codes like insufficient funds or a closed account, because it points directly to an error in how you entered the destination information.

The money comes back to you automatically. You don't need to do anything to retrieve it. But you do need to fix the account information before attempting the transfer again, or it will be rejected a second time.

Key Takeaways

  • A CONA return means the account number or routing number you entered doesn't match what the receiving bank has on file.
  • Your money returns to your account within one to three business days without any action required on your part.
  • You must verify the correct account and routing numbers with the recipient before sending the payment again.
  • Repeated rejections for the same reason can trigger fraud holds or temporary blocks on your account, so confirm details in writing before retrying.
  • Some banks allow you to see the return code in your transaction history, which helps you understand exactly why the payment was rejected.

Why the receiving bank rejected your payment

The most common reason for a CONA return is a typo or transposition in the account number. A single digit wrong—or a routing number that doesn't belong to the bank the recipient named—causes the receiving bank's system to flag it as a mismatch. The bank doesn't process the payment; it bounces it back when ready.

Less often, a CONA return happens because the account number format doesn't match what that bank uses. Some banks use 10-digit account numbers, others use 12 or 14. If you entered the right number but in the wrong format for that institution, the receiving bank's system rejects it as invalid.

The key point: a CONA return is not about your account or your bank's decision. It's the receiving bank saying "this destination doesn't exist in my system as you've described it." Your bank straightforward honors that rejection and sends the money back.

How to verify the correct account information

Before you retry the payment, contact the recipient directly and ask them to confirm their account number and routing number in writing. Don't rely on a verbal confirmation or a text message. Ask them to provide a voided check, a bank statement, or a direct message from their bank's official app or website showing those numbers.

Verify the routing number separately using your bank's routing number lookup tool or the Federal Reserve's routing number database. Type the routing number into the search box and confirm it matches the bank name the recipient gave you. A wrong routing number is one of the easiest mistakes to make and one of the most common causes of CONA returns.

Once you have the numbers confirmed, enter them slowly into your mobile banking app. Read them back to yourself before you hit send. Some banks let you preview the destination account holder's name before the payment processes—if your bank offers this, use it. If the name doesn't match who you're trying to pay, stop and ask the recipient again.

What happens if you keep getting CONA returns

If the same payment is rejected twice or more for the same CONA reason, your bank may place a temporary hold on your account or flag it for manual review. This is a fraud prevention step—the system is noticing a pattern of rejected transfers to an account that doesn't seem to exist, which can indicate either user error or an attempt to move money to a fraudulent account.

A hold typically lasts 24 to 48 hours. During that time, you can still receive deposits and make other payments, but your bank may require you to call and confirm the details of the transfer before it goes through. This is not a penalty; it's a safety measure.

To avoid a hold, verify the account information one more time before retrying. If the recipient insists the number is correct but your bank keeps rejecting it, contact your bank's customer service line and ask them to review the receiving bank's details. Sometimes a bank's routing number or account format has changed, and your bank's system may have outdated information.

The timeline for your money to return

Most banks return rejected ACH payments within one to three business days. Some return them the same day the rejection is processed. Check your account transaction history to see when the return posted—this tells you when the money is available again.

If more than three business days have passed and you don't see the return, contact your bank. Provide them with the original transaction date and the amount. They can trace the return and confirm whether it's still in process or whether something else went wrong.

Once the money is back in your account, it's available to use when ready. You can retry the transfer to the corrected account number, send it somewhere else, or leave it where it is. There's no important date to retry.

How to prevent CONA returns in the future

The simplest prevention is to ask the recipient for their account details in writing before you send anything. A screenshot of their bank statement, a photo of a voided check, or a message directly from their bank's app all work. Verbal confirmations are straightforward to mishear.

When you enter the information into your mobile banking app, use copy-and-paste rather than typing it manually. This eliminates transposition errors. If your app doesn't allow pasting, type slowly and read the numbers back aloud before confirming.

If you send money to the same person regularly, most mobile banking apps let you save the account as a payee. Once it's saved and confirmed, you can reuse it without re-entering the details each time. This reduces the chance of a typo on subsequent transfers.

When a CONA return might signal something else

In rare cases, a CONA return can mean the recipient gave you a fake or closed account number intentionally. If someone you don't know well asked you to send money and the payment was rejected, do not retry it. Contact the person through a phone number or email address you know is legitimate and ask them to confirm the account details again. If they become evasive or the story changes, stop the transfer entirely.

If you're sending money as part of a job offer, a prize claim, or a refund from an unexpected source, a CONA return is a red flag. Legitimate employers, government agencies, and established businesses don't ask you to send money first and then return it via ACH. A rejected payment in that context may mean you've encountered a scam.

Frequently Asked Questions

Does a CONA return hurt my credit score?

No. A returned ACH payment does not appear on your credit report and does not affect your credit score. It's a transaction issue between banks, not a missed payment or default. Your credit is not involved.

Can I dispute a CONA return?

You can ask your bank to review it, but there's usually nothing to dispute. The receiving bank rejected it because the account information didn't match their records. Your bank will confirm this and explain the reason. The solution is to correct the information and retry, not to dispute the return.

Will I be charged a fee for a returned ACH payment?

Most banks do not charge a fee for an inbound ACH return. Some banks charge a small fee (typically $5 to $15) if you initiated the outbound transfer and it was rejected, though many waive this for the first occurrence. Check your bank's fee schedule or call to ask.

How many times can I retry a payment to the same account?

You can retry as many times as you want, but if the account information is wrong, it will keep being rejected. Each rejection takes one to three days to process. Verify the account details are correct before each retry, or you'll just repeat the cycle.

What if the recipient says the account is correct but the bank keeps rejecting it?

Ask the recipient to contact their own bank and confirm the account number and routing number are correct in their bank's system. Sometimes a recent account change or a bank merger causes mismatches. Have the recipient provide written confirmation from their bank, then contact your bank's customer service to see if there's a known issue with that receiving bank.