Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
Mercury reserves the right to debit a merchant's deposit account for the amount of any returned or reversed ACH invoice payment. Mercury expressly disclaims any warranty that invoice payments will be completed or will not be returned after initial credit.
This analysis describes what Mercury's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes that merchants who have received initial credit for an invoice payment may have their accounts debited if the payment is subsequently returned or reversed, with Mercury disclaiming responsibility for the return. This creates a financial exposure for merchants who may have already disbursed or relied upon funds that are subsequently clawed back.
Mercury's updated terms establish detailed rules for how recurring autopay works on invoices. Under the revised language, payers authorize recurring ACH debits through a separate addendum, Mercury will not retry failed payments (except once if caused by a Mercury system issue), and autopay authorization will automatically cancel after two consecutive failures in a series. You can prevent autopay cancellation by ensuring payers have sufficient funds, re-enrolling the payer, or requesting manual payment if the series fails twice.
View change record →The updated terms establish that when customers pay invoices you issue through Mercury Invoicing via ACH debit, Mercury will apply a hold period before crediting the funds to your account. The hold period is determined by Mercury in its sole discretion based on risk factors related to the transaction, payer, and payment history, and may range from 1 to 4 business days from the date the ACH debit is initiated. Mercury will display an estimated funds availability date for each incoming invoice payment in your Invoicing dashboard.
View change record →Under this clause, merchants accept that Mercury may debit their account for any returned or reversed ACH invoice payment, including after initial credit has been applied. Mercury does not warrant that invoice payments will be completed or that credited funds will not be subject to reversal.
Cross-platform context
See how other platforms handle ACH Return Debit Authorization Against Merchant Accounts and similar clauses.
Compare across platforms →Monitoring
Mercury has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"Mercury does not warrant or guarantee that any payer will complete an Invoice Payment or that any Invoice Payment will not be returned, reversed, or disputed after initial credit to your Account. Mercury is not responsible for returned or reversed ACH entries and reserves the right to debit your Account for the amount of any returned or reversed Invoice Payment, consistent with the terms of your Deposit Account agreement with your Banking Provider.Excerpt from Mercury's Terms of Service
1) REGULATORY LANDSCAPE: ACH return rights and obligations are governed by Nacha Operating Rules, which specify return reason codes, timeframes, and participant responsibilities. Mercury's right to debit merchant accounts for returns is stated to be consistent with the terms of the Deposit Account agreement with the Banking Provider, making that agreement a critical companion document for assessing the full scope of this provision. FTC Act standards may be relevant if return debit practices are applied in a manner that constitutes unfair or deceptive conduct. 2) GOVERNANCE EXPOSURE: Medium. Merchants who rely on Mercury Invoicing for receivables must account for the possibility that credited funds may be clawed back via account debit following ACH returns. The provision does not specify a notice requirement prior to executing a return debit, and Mercury's disclaimer of responsibility for returned entries places the collection burden on the merchant. 3) JURISDICTION FLAGS: The provision references the Deposit Account agreement with the Banking Provider as governing the return debit mechanism, creating a multi-document dependency. The specific terms of that agreement, which may vary by banking provider, are not fully disclosed within the Terms of Use. 4) CONTRACT AND VENDOR IMPLICATIONS: Procurement and treasury teams should review the Deposit Account agreement with Mercury's Banking Provider to understand the full scope of return debit rights and any notice or dispute procedures available to merchants. Organizations with high-volume ACH invoicing activity should assess return rate exposure and whether reserve or buffer mechanisms are available. 5) COMPLIANCE CONSIDERATIONS: Merchants should maintain sufficient account balances to cover potential return debits and establish internal monitoring for ACH return notifications. Legal teams should review whether Mercury's return debit practices comply with Nacha Operating Rules regarding notice and return timeframes.
This provision establishes that merchants who have received initial credit for an invoice payment may have their accounts debited if the payment is subsequently returned or reversed, with Mercury disclaiming responsibility for the return. This creates a financial exposure for merchants who may have already disbursed or relied upon funds that are subsequently clawed back.
Under this clause, merchants accept that Mercury may debit their account for any returned or reversed ACH invoice payment, including after initial credit has been applied. Mercury does not warrant that invoice payments will be completed or that credited funds will not be subject to reversal.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Mercury.