Mercury · Mercury Terms of Service · View original document ↗

Wire Transfer Identifying Information Liability

High severity High confidence Explicitdocumentlanguage Unique · 0 of 352 platforms
Get alerted the next time Mercury changes these terms. Get same-day alerts →
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity Mercury recorded 3 documented changes in the last 30 days.
Get same-day alerts →
Monitor governance changes for Mercury Monitor emails you the same day this changes. The archive stays free.
Get same-day alerts →

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.

Document Record

What it is

Where a wire instruction contains inconsistent identifying information, Mercury and its wire services providers may execute the payment order using only the account or identifying number, and the user bears sole responsibility for all claims, losses, and expenses arising from any such inconsistency. Mercury and its providers have no obligation to review wire instructions for accuracy.

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision establishes that users assume sole liability for financial losses arising from wire instruction errors or inconsistencies, including cases where Mercury or its providers choose to execute a payment order based on incomplete or conflicting information. The clause also states that neither Mercury nor the International Wire Services Providers have any obligation to notify users of rejected or delayed wire instructions.

Recent Activity

This document changed recently

Medium Jun 26, 2026

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 →
Medium May 29, 2026

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 →

Consumer impact (what this means for users)

Under this clause, users who submit wire instructions with inconsistent identifying information bear sole responsibility for any resulting financial losses, even where Mercury or its provider elects to execute the payment based on the account number alone. The agreement states that Mercury and its providers have no obligation to review wire instructions for accuracy or to notify users of rejections or delays.

Cross-platform context

See how other platforms handle Wire Transfer Identifying Information Liability 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 25 platforms.

Get Monitor Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
In the event of any inconsistency in the identifying information provided to us in a Wire Instruction (e.g., between name and account or identifying number), we in our discretion may communicate the corresponding Payment Order to the International Wire Services Provider, and the International Wire Services Provider in its discretion may execute the Payment Order, based solely on the account or identifying number provided in the Wire Instruction, and you will be solely responsible for any claims, losses, liabilities, damages, costs or expenses arising from the inconsistency.

Excerpt from Mercury's Terms of Service

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

1) REGULATORY LANDSCAPE: For wire instructions used for consumer purposes, Regulation E (12 CFR Part 1005) governs international wire transfers and includes error resolution rights that the agreement acknowledges supersede inconsistent contractual terms for consumer accounts. Article 4A of the California Uniform Commercial Code governs commercial wire transfers and addresses payment order liability allocation, including provisions related to erroneous payment orders. The agreement's liability allocation for commercial users may be assessed against Article 4A default rules and whether contractual variation is permitted. 2) GOVERNANCE EXPOSURE: High. The provision assigns sole user liability for wire transfer losses arising from identifying information inconsistencies and states that neither Mercury nor its providers have any obligation to notify users of rejected or delayed payment orders. For organizations processing high-value international transfers, this creates material exposure to unrecoverable financial losses in cases of input error or fraud involving wire instruction manipulation. 3) JURISDICTION FLAGS: Consumer account holders are afforded error resolution protections under Regulation E that may supersede this liability allocation. California-based commercial users should evaluate this provision against Article 4A of the California Uniform Commercial Code. Organizations operating in jurisdictions with additional payment services regulations (such as the EU Payment Services Directive for EU-side beneficiaries) should assess whether additional protections apply to the receiving end of transfers. 4) CONTRACT AND VENDOR IMPLICATIONS: This provision represents a significant liability shift to the user for wire instruction errors. Organizations with high-volume international wire activity should assess whether their internal wire instruction review and approval workflows provide sufficient controls to mitigate the risk created by this liability allocation. The provision also indemnifies Mercury and its providers for costs incurred in attempting to cancel or amend accepted wire instructions, which should be factored into operational risk assessments. 5) COMPLIANCE CONSIDERATIONS: Legal teams should assess whether the commercial wire transfer liability allocation is consistent with Article 4A default rules and whether any negotiated modifications are available for high-volume customers. Treasury and operations teams should implement dual-approval workflows for wire instructions and verify all identifying information prior to submission, given the contractual bar on post-acceptance cancellation or amendment.

Full institutional analysis

Regulatory citations, enforcement risk, and due diligence action items.

Get same-day alerts when this changes → Get Analyst

Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.

Applicable agencies

  • CFPB
    The CFPB has supervisory authority over Regulation E compliance for consumer international wire transfers and error resolution rights.
    File a complaint →

Provision details

Document information
Document
Mercury Terms of Service
Entity
Mercury
Document last updated
May 5, 2026
Tracking information
First tracked
July 9, 2026
Last verified
July 9, 2026
Record ID
CA-P-014136
Document ID
CA-D-00529
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
3ac7ab54812d292da7660282e68a275955e77d625774ffe806d425e9b70bcc72
Analysis generated
July 9, 2026 04:51 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Mercury
Document: Mercury Terms of Service
Record ID: CA-P-014136
Captured: 2026-07-09 04:51:50 UTC
SHA-256: 3ac7ab54812d292d…
URL: https://conductatlas.com/platform/mercury/mercury-terms-of-service/provision/CA-P-014136/wire-transfer-identifying-information-liability/
Accessed: July 23, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
Categories

Other risks in this policy

Compliance Governance Intelligence

Need to monitor specific governance provisions?

Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Get Compliance

Or start with Monitor →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does Mercury's Wire Transfer Identifying Information Liability clause do?

This provision establishes that users assume sole liability for financial losses arising from wire instruction errors or inconsistencies, including cases where Mercury or its providers choose to execute a payment order based on incomplete or conflicting information. The clause also states that neither Mercury nor the International Wire Services Providers have any obligation to notify users of rejected or delayed …

How does this clause affect you?

Under this clause, users who submit wire instructions with inconsistent identifying information bear sole responsibility for any resulting financial losses, even where Mercury or its provider elects to execute the payment based on the account number alone. The agreement states that Mercury and its providers have no obligation to review wire instructions for accuracy or to notify users of rejections …

Is ConductAtlas affiliated with Mercury?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Mercury.