Mercury added a new section governing automatic recurring payments (autopay) on invoices. The updated terms establish that payers authorize recurring ACH debits through separate addenda, that Mercury does not guarantee recurring payments will process, that two consecutive failed payments automatically cancel the payer's autopay authorization, and that Mercury limits its liability for failures or unauthorized debits except as required by law. Previously, the terms addressed returned or reversed ACH entries but did not detail autopay-specific procedures or liability limitations.
Merchants: If a customer's autopay fails twice in a row, Mercury stops trying to collect automatically, and the merchant must contact the customer to collect payment manually.
Consumers: If your autopay fails twice, it stops working automatically and you must set it up again or pay manually.
Merchants: Mercury is not responsible for losses you suffer if a customer's autopay fails or is cancelled, except where law requires it.
The updated terms establish new procedures for automatic recurring invoice payments. Under the revised language, when a payer enables autopay, Mercury does not guarantee that recurring payments will process, and if two consecutive payments fail, the payer's autopay authorization is automatically cancelled without advance notice. The terms also state that Mercury will not re-attempt failed recurring payments except when a Mercury system issue caused the failure (in which case Mercury will attempt once on the next banking day). Mercury limits its liability for losses arising from payment failures, authorization issues, or unauthorized debits except as required by applicable law. Merchants and payers should review their autopay settings and payment methods to ensure continuity of recurring billing.
→ Review your autopay settings and payment methods to ensure they remain active and current.
→ If your autopay fails, contact the merchant to re-enroll or arrange manual payment before a second failure triggers automatic cancellation.
Recurring payment authorization automatically cancels after 2 consecutive payment failures; payer must re-enroll or pay manually to continue.
Mercury is not liable for losses, penalties, or damages from payment failures, authorization issues, or unauthorized debits except as required by law.
Mercury will not re-attempt failed recurring payments except when a Mercury system issue caused the failure, in which case Mercury will attempt once on the next banking day.
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
Wording edits to this record that do not change what it claims. Changes to a claim are published as corrections.
Mercury added detailed autopay governance establishing that recurring payment authorization automatically terminates after 2 consecutive failures, that Mercury does not guarantee payment processing, and that Mercury's liability for payment failures is limited except as required …
Regulatory exposure, obligation change, escalation trigger, board-ready language, and recommended action for legal and compliance teams.
Unlock the full institutional analysis — InsightConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-X-003292.
Mercury updated its Terms of Service to October 5, 2026 and added a new section on third-party AI connections. The …
Mercury revised its promotional offers section to clarify that third-party partners may change or discontinue perks at any time, even …
Mercury expanded its privacy policy to clarify how it collects and processes personal information for business customers and their connected …
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
Get alerted when this policy changes again, including what changed and why it matters.