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.
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
you agree that before taking any formal action, you will contact us at dispute-notice@asana.com and provide a brief, written description of the dispute and your contact information...
Before filing any legal action, you agree to work together with us to resolve all potential disputes respectfully and amicably.
The party initiating a Dispute must give notice to the other party in writing of his or her intent to initiate an Informal Dispute Resolution Conference, which shall occur within 45 days after the other party receives such notice...
Monitoring
Mercury has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"For any claim, dispute, or controversy with Mercury...you agree to first contact us...and attempt to resolve the dispute with us informally. In the unlikely event that Mercury has not been able to resolve a dispute...after sixty (60) days...Excerpt from Mercury's Terms of Service
Coinbase's User Agreement includes a mandatory arbitration clause that most users may not have reviewed. Here is what the clause states and how the opt-out process works.
561 arbitration provisions across 197 platforms. ConductAtlas tracks how dispute resolution is being restructured across the internet.
Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.
The clause states: “For any claim, dispute, or controversy with Mercury...you agree to first contact us...and attempt to resolve the dispute with us informally. In the unlikely event that Mercury has not been able to resolve a dispute...after sixty (60) days...”
ConductAtlas has identified this type of provision across 210 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Mercury.