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
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 →How other platforms handle this
Use our Services in relation to any political campaign financing or for the purpose of influencing any election, other than sharing your own personal political opinions;
You agree that use of any Beta Services will at all times be subject to your compliance with the Beta Services Terms.
index, frame, embed or link to the Services in a manner not authorized by us, or to collect information about users for the purpose of sending, facilitating, or encouraging unsolicited bulk or other communications
"You should not use Beta Services for any critical or important functions without taking appropriate precautions to prevent loss or damage resulting from such use.Excerpt from Mercury's Terms of Service
Get the 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.
The clause states: “You should not use Beta Services for any critical or important functions without taking appropriate precautions to prevent loss or damage resulting from such use.”
ConductAtlas has identified this type of provision across 282 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Mercury.