What Does Return Mobile ACH Payment Mean?

E-invoicing as purchase invoice document digital transfer outlin

    TABLE OF CONTENTS

      ACH payments keep money flowing for subscription businesses, utility companies, and anyone collecting recurring payments.

      But when you see something like “Return Mobile ACH Payment CONA” errors pop up, it means payments aren’t going through – and that hits your revenue directly.

      These return codes aren’t just random error messages. They tell you exactly why a payment failed, so you can fix the problem fast and prevent repeat failures.

      This guide covers mobile ACH scenarios, card-based transactions, and the specific issues that cause payments to bounce back.

      Key Takeaways

      • ACH Transaction Problems: Whenever an issue arises with a direct debit or credit card transaction processed through the Automated Clearing House (ACH) method, the involved parties send a code to identify the problem.
      • Common ACH Return Codes: These are usually due to incorrectly entered information or insufficient funds. However, they can also reflect issues with authorization and more.
      • Understanding ACH Returns: An ACH return occurs when the ACH fails to charge money from a customer’s account. The ACH return code reveals more about the problem’s source.
      • ACH Payment Processing: Five parties are involved – Originator, Originating Depository Financial Institution (ODFI), ACH Operator, Receiving Depository Financial Institution (RDFI), and Receiver. If an issue occurs, usually the RDFI sends an ACH return message.

      What Is an ACH Return?

      An ACH return indicates that the Automated Clearing House (ACH) failed to complete a transaction from a customer’s account. When this happens, you’ll always receive an ACH return code that explains what caused the failure.

      ACH returns apply to both mobile ACH payments and desktop recurring debits. The process works the same whether someone initiates a payment through their bank’s mobile app or sets up autopay through a website.

      To understand why ACH returns appear, you need to know how they work in the first place. There are five parties involved in making the payment processing go through:

      1. Originator

      This is a person who submits an ACH transfer to the ODFI.

      1. Originating Depository Financial Institution (ODFI)

      The ODFI receives the request from the Originator and passes it to the ACH Operator.

      1. ACH Operator

      The ACH Operator links the two accounts by processing transactions (e.g., clearing, delivery, settlement).

      1. Receiving Depository Financial Institution (RDFI)

      The RDFI is the bank that is being charged or refunded. It receives the ACH entry and submits it to the Receiver.

      1. Receiver

      The receiver is the individual or company that allows the Originator to initiate an ACH entry.

      ACH or automated clearing house as electronic money transfer out

      If there is a problem with the payment processing, it is usually the RDFI that sends an ACH return message. In rare cases, you may need to have the ACH Operator or ODFI perform this action. It is always one of the parties involved that sends the error code, which is, in turn, provided by the National Automated Clearing House.

      Understanding Mobile ACH Payments

      A mobile ACH payment refers to bank-to-bank transfers initiated through smartphone apps, online banking platforms, or autopay systems. These transactions facilitate recurring mobile billing, bill pay setups, and popular apps like Zelle, Venmo, and Capital One’s mobile banking services.

      Businesses use them every day for:

      • Subscription billing
      • Utility and energy autopay
      • E-commerce orders
      • Healthcare or education payment plans

      The mobile aspect doesn’t change how ACH returns work, but it does affect timing and notification methods. Mobile banking apps often provide faster alerts about returned payments compared to traditional banking statements.

      ℹ️ CONA Errors

      Mobile ACH payment CONA errors specifically relate to Capital One’s system messaging. Some users encounter messages like “Return Mobile ACH Payment CONA Capital One.” CONA is Capital One’s internal system code for certain types of returned transactions.

      Why Was My ACH or Mobile Payment Returned?

      Several common scenarios trigger ACH returns:

      Account Issues: The most frequent cause involves problems with the funding account, such as an insufficient balance, closed accounts, or frozen accounts due to suspicious activity.

      Authorization Problems: Payments can bounce when proper authorization wasn’t obtained, or when customers revoke previously granted permission.

      Data Entry Errors: Incorrect account numbers, routing numbers, or mismatched account holder names will cause immediate returns.

      Timing Issues: Some returns occur when payments hit accounts during processing cutoffs or when banks place temporary holds.

      Why was my Capital One payment returned?

      Capital One users might see specific messaging about returned payments due to the bank’s mobile app integration and real-time processing systems.

      Most Common ACH Return Codes & What They Mean

      To understand the code, you need to have its definition. There are over 80 ACH return codes; we will look at the most common ones.

      Go ahead and search for the one you need, or bookmark this page in case you see an ACH return code for the first time.

      There are ten most common ACH return codes that you are likely to see.

      Reason for return ACH return code Description Time Frame
      Insufficient funds R01 The bank account you requested money from does not have sufficient funds 2 banking days
      Account closed R02 The account you requested money from has been closed 2 banking days
      No Account/Unable to locate account R03 The account number does not match the customer’s name/ The account does not exist 2 banking days
      Invalid account number R04 There is an error in the account number (e.g., incorrect digits) 2 banking days
      Unauthorized debit to consumer account using the Corporate SEC code R05 The account number of a customer is a personal bank account, not a corporate one (in cases of B2B payments) 60 calendar days
      Returned due to ODFI’s request R06 Authorization failed (e.g., in cases of fraudulent payments) Undefined
      Authorization revoked by the customer R07 A customer who authorized the ACH payment has withdrawn it 60 calendar days
      Payment stopped R08 A customer has issued a stop payment, which cancels a transaction 2 banking days
      Unable to collect funds R09 A payment wasn’t completed because of a lack of funds 2 banking days
      Originator not known or not authorized to Debit Receiver’s Account R10 A transaction was incomplete or incorrectly submitted 60 calendar days

      How Long Does an ACH Return Take?

      That depends on the specific reason why the return was initiated. However, in most cases, it will take 2 business days.

      The customer has the right to request that an unauthorized transaction be returned within 60 days – especially important for those businesses that are subscription-based or that take direct debit payments.

      Returns related to mobile apps like Capital One or PayPal usually post within 1-2 business days due to faster processing systems.

      Can Returned Mobile ACH Payments Be Disputed?

      Yes. If your business receives a return you believe is incorrect, you can dispute it. Valid dispute reasons include:

      • Duplicate transactions: Same payment processed multiple times
      • Misrouted payments: Sent to the wrong account due to a bank error
      • Unauthorized debits: Payments made without proper permission
      • Incorrect information: Wrong amounts or account details
      • Reversal errors: Accidental credits that resulted from improper reversals

      While consumer banks often make the dispute process slow, using a business ACH processor like Payment Savvy gives you faster access to support and better tools for resolving these issues.

      ACH Return Fees and Compliance Limits

      Every return has a cost. Most financial institutions charge $2 to $5 per returned transaction. That may not sound like much, but high volumes quickly add up.

      More importantly, Nacha requires businesses to keep administrative returns under 3%. This rule applies to returned ACH card payments and all mobile ACH transactions. Exceeding these ACH limits can trigger warnings, additional scrutiny, or even suspension from ACH processing.

      For businesses handling recurring billing, staying compliant is crucial. Working with a processor that monitors returned ACH card payments can protect your ability to keep collecting payments.

      Best Practices to Avoid ACH Returns

      Businesses can reduce ACH return risk by tightening processes:

      • Verify account information: Use micro-deposit verification to confirm account details before processing larger transactions
      • Obtain proper authorization: Require clear, documented consent for all ACH debits
      • Communicate payment schedules: Notify customers before billing to ensure sufficient funds
      • Monitor failed payments: Track patterns to identify recurring issues
      • Update account information: Regularly confirm customer banking details remain current

      Common ACH Return Scenarios (Examples)

      Scenario 1: Customer sets up autopay through Capital One’s mobile app for a monthly subscription. Three months later, they close that checking account but forget to update the payment method. The next billing attempt triggers an R02 return for “account closed.”

      Scenario 2: A business client authorizes ACH payments through PayPal’s recurring billing system. Later, they dispute the charges as unauthorized, resulting in an R07 return. The business must provide documentation proving proper authorization was obtained.

      Scenario 3: A customer sees “Returned ACH Card Payment CONA” in their Capital One account. This system message indicates a failed automatic payment pull from their mobile banking app, often due to insufficient funds or temporary account restrictions.

      Scenario 4: A Small business owner enters the wrong digit in a customer’s account number when setting up recurring billing. The payment immediately returns with R04 code for “invalid account number,” alerting them to the data entry error.

      FAQs

      Can ACH payments be returned?

      Yes, ACH payments can be returned for various reasons, including insufficient funds, incorrect account information, or authorization issues.

      What is a returned mobile ACH payment?

      It’s any ACH transaction initiated through mobile apps or online banking that gets rejected and sent back to the originator.

      Why does it say ‘Return Mobile ACH Payment CONA Capital One’?

      That’s Capital One’s way of showing a failed mobile ACH pull. Common reasons include insufficient funds, closed accounts, or missing authorization.

      How much is an ACH return fee?

      ACH return fees may vary between $2-$5 per return.

      Are there ACH limits on how many ACH returns you can have?

      Yes, your administrative returns need to stay within 3%.

      Final Thoughts on Returned Mobile ACH Payments

      ACH returns are part of doing business, but the goal is to keep them as rare as possible. Every return represents delayed revenue, added fees, and compliance risk.

      If your business struggles with returned ACH payments, consider switching to a processor that offers comprehensive risk management and reliable human support.

      Reduce return rates and improve your payment processing reliability.

      Chad Deatherage

      Chad Deatherage

      Chad is a serial entrepreneur and founded Payment Savvy in 2011 armed with the goal of providing high-risk establishments with a pioneering and tailored payment processing solution that allows them to flourish. Having decades of knowledge in the financial services and debt recovery industries, he ensures every client receives the same level of expertise, resourcefulness, and strategic vision no matter the size of the organization. Always willing to push the envelope, Chad’s forward-thinking and leadership skills are responsible for Payment Savvy being on the map as an industry-leading payment processor.