Can this addendum be signed electronically?

Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and state electronic transaction laws (UETA where adopted), provided intent, consent, attribution, and reliable record retention are met.

When is notarization required?

Notarization is rarely required for a commercial addendum unless state recording or a specific contract clause mandates it; check local rules and the underlying merchant services agreement.

How do we correct an error after signing?

Use an agreed amendment or corrective addendum signed by authorized parties. Avoid handwritten changes on an executed document without a formal amendment to prevent enforceability disputes.

Who must sign for a corporate merchant?

An authorized corporate officer or agent with documented signing authority should sign. Include a printed name, title, and a statement of authority if not already present in corporate records.

How can a party revoke or cancel the addendum?

Revocation typically requires the process set out in the merchant services agreement or the addendum itself; unilateral revocation after execution may breach contract and expose the revoking party to liability.

What documentation supports chargeback disputes?

Provide transaction records, proof of delivery or service, customer communications, and any fraud-screening logs. Timely, complete evidence is essential to meet network dispute deadlines.

Electronic Signature
Templates
Legal
Legal Merchant Loss Addendum

Legal Merchant Loss Addendum

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

LEGAL MERCHANT LOSS ADDENDUM

This Legal Merchant Loss Addendum ("Addendum") is entered into as of Effective Date: by and between Merchant Name: with principal address: and Processor Name: with principal address: (each a Party and collectively the Parties).

RECITALS

WHEREAS, Merchant and Processor are parties to a Merchant Services Agreement under which Processor provides payment processing and related services (the "Agreement"); and

WHEREAS, the Parties desire to allocate responsibility for losses, chargebacks, reserves and related costs arising from transactions processed by Processor on behalf of Merchant, and to establish procedures for mitigation, notification, investigation and indemnification.

WHEREAS, this Addendum supersedes and supplements any conflicting provisions of the Agreement with respect to Merchant losses and Processor recovery rights.

NOW, THEREFORE, in consideration of the mutual covenants herein contained, the Parties agree as follows:

1. DEFINITIONS

For purposes of this Addendum, the following terms shall have the meanings set forth below:

"Losses" means all losses, liabilities, damages, fines, penalties, assessments, settlements, chargebacks, fees, costs and expenses (including reasonable attorneys' fees and costs of investigation and remediation) arising out of or related to Transactions, Merchant conduct, fraud, negligence, breach, data compromise, or claims by cardholders, issuers, networks or other third parties.

"Chargeback" means a reversal of a transaction initiated by an issuer, cardholder or network, including any dispute, retrieval, representment, arbitration or related processing event that results in a debit to Processor or Merchant.

2. ALLOCATION OF LOSSES

Merchant shall be solely responsible for and shall indemnify and hold harmless Processor from all Losses arising from: (a) Merchant's breach of the Agreement or this Addendum; (b) Merchant's fraud, intentional misconduct, or gross negligence; (c) failure to comply with card brand rules, applicable law, or applicable data security standards; and (d) defective goods or services provided by Merchant.

Processor shall be responsible for Losses only to the extent such Losses result directly from Processor's willful misconduct or gross negligence in performing services under the Agreement, and subject to the limitations and procedures set forth in this Addendum.

3. CHARGEBACKS, RESERVE AND RECOVERY

Merchant agrees to promptly reimburse Processor for Chargebacks and related Losses. Processor may, at its election, establish and maintain a reserve to secure potential Losses. The initial reserve amount shall be: or a rolling reserve equal to of merchant processing volume, as determined by Processor in its commercially reasonable discretion.

Processor may replenish the reserve from amounts otherwise payable to Merchant or by presenting an invoice to Merchant for immediate payment. Merchant shall pay any such invoice within days of receipt.

4. REPORTING, NOTICE AND INVESTIGATION

Merchant shall notify Processor in writing within days of discovering any suspected fraud, data compromise, unauthorized access, or any event that could reasonably give rise to Losses. Processor shall have the right to investigate Losses and chargebacks and Merchant shall fully cooperate with such investigation.

Merchant shall preserve all relevant transaction records, logs, communications, and supporting documentation for a period of no less than months and deliver such records promptly upon Processor's request.

5. INSURANCE

Merchant shall maintain and, upon request, provide evidence of commercial general liability insurance and cyber liability insurance covering data breaches and network security incidents with minimum limits of per occurrence. Merchant shall name Processor as an additional insured and shall provide certificates of insurance within days of Processor's request.

6. COOPERATION AND MITIGATION

Merchant shall take commercially reasonable steps to mitigate Losses, including but not limited to (a) promptly suspending or cancelling transactions that pose unreasonable risk, (b) cooperating with Processor and law enforcement, and (c) implementing remedial measures to prevent recurrence. Failure to cooperate shall relieve Processor of obligations to indemnify Merchant for resulting Losses.

7. AUDIT RIGHTS

Processor shall have the right, upon providing no less than days' prior notice (except in cases of suspected fraud or compromise, where no notice is required), to inspect Merchant's books, records, systems and facilities related to Transactions. Merchant shall make such records available during normal business hours and shall cooperate with Processor's auditors.

8. INDEMNIFICATION AND DEFENSE

Merchant shall indemnify, defend and hold harmless Processor and its affiliates, officers, directors, employees and agents from and against any third party claim arising from or relating to Merchant's breach, negligence, fraud, failure to perform, or violation of applicable law. Merchant's indemnity obligation includes payment of judgments, settlements, costs, fees and expenses, including reasonable attorneys' fees.

Processor shall provide prompt written notice of a claim subject to indemnification. Failure to provide timely notice shall not relieve Merchant of its indemnity obligations except to the extent Merchant is materially prejudiced by such delay. Merchant shall have the right to assume control of the defense of any claim at its expense, provided Merchant conducts the defense diligently and does not admit liability or settle claims without Processor's prior written consent, which shall not be unreasonably withheld.

9. LIMITATION OF LIABILITY

EXCEPT FOR LIABILITY ARISING FROM A PARTY'S FRAUD, WILLFUL MISCONDUCT, OR GROSS NEGLIGENCE, OR A PARTY'S PAYMENT OBLIGATIONS UNDER THIS ADDENDUM, IN NO EVENT SHALL EITHER PARTY BE LIABLE TO THE OTHER FOR SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES, LOST PROFITS OR LOST BUSINESS OPPORTUNITY, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

10. TERM AND TERMINATION

This Addendum shall commence on the Effective Date and continue in full force and effect for the term of the Agreement, unless earlier terminated in accordance with the Agreement. Termination shall not relieve Merchant of obligations to pay for Losses or to cooperate with investigations that relate to events occurring prior to termination.

11. NOTICES

Merchant Notice Address Processor Notice Address

12. AMENDMENTS; WAIVER

No amendment, modification or waiver of any provision of this Addendum shall be effective unless made in writing and signed by authorized representatives of both Parties. No failure or delay by a Party in exercising any right or remedy will constitute a waiver of that right or remedy.

13. COUNTERPARTS; ELECTRONIC SIGNATURES

This Addendum may be executed in counterparts, each of which shall be deemed an original and all of which together shall constitute one instrument. Facsimile or electronically transmitted signatures shall be treated as original signatures for all purposes.

14. GOVERNING LAW

This Addendum shall be governed by and construed in accordance with the laws of the State of without regard to conflicts of law principles.

15. ENTIRE AGREEMENT

This Addendum, together with the Agreement, constitutes the entire agreement between the Parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings and communications relating thereto.

16. SEVERABILITY

If any provision of this Addendum is held invalid or unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable, and the remaining provisions shall continue in full force and effect.

ADDITIONAL PROVISIONS

Remedies provided in this Addendum are cumulative and in addition to any other remedies available at law or in equity. The prevailing party in any dispute arising under this Addendum shall be entitled to recover reasonable attorneys' fees and costs.

Description of Known Loss Events or Ongoing Disputes (if any) Entity Type — Merchant (check all that apply)

Corporation LLC Partnership Individual/Sole Proprietor

Merchant Representative Contact Processor Representative Contact

Merchant Printed Name:

By:

Date:

Processor Printed Name:

By:

Date:

What the Legal Merchant Loss Addendum Covers

The Legal Merchant Loss Addendum is a contract supplement that defines how merchant-related losses — including chargebacks, fraud, reimbursement obligations, and related remediation costs — are allocated between a merchant and its acquirer, processor, or payment service provider. It clarifies definitions, reporting procedures, dispute handling, reserve or holdback arrangements, indemnification, and insurance requirements. The addendum is intended to sit alongside a merchant services agreement and provide an auditable record of responsibilities, timing, and remedies. Electronic execution is generally accepted under U.S. law when the parties satisfy ESIGN and applicable state electronic transaction rules.

Why a Clear Loss Addendum Matters

A focused Legal Merchant Loss Addendum reduces uncertainty by allocating financial responsibility for chargebacks and fraud, documenting notification and dispute procedures, and establishing reserve mechanics and evidence standards that support reimbursement and audit processes.

Who Typically Prepares and Signs This Addendum

The addendum is used by parties in the payments ecosystem who need precise loss allocation and operational procedures.

Merchant finance and operations teams who accept card or alternative payments and need contractual clarity on liability and reserves.
Payment processors and acquiring banks that manage chargebacks, refunds, and fraud investigations across portfolios.
Legal, compliance, and risk departments that require contractual language to support audits, card network investigations, or regulatory inquiries.

It is commonly integrated into onboarding, contract renewals, or when a merchant changes processing risk profiles.

Core Provisions to Include in a Professional Addendum

A professional Legal Merchant Loss Addendum contains standard clauses that remove ambiguity and set measurable procedures for notification, investigation, and recovery of merchant-related losses.

Loss Definitions

Precisely list covered loss types (chargebacks, refunds, reversals, fines, PCI failure costs, fraud losses) and exclude items not intended to be covered to avoid later disputes.

Notification Procedures

Specify how losses are reported, required timing for merchant response, the information and documentation merchants must supply, and escalation steps for unresolved disputes.

Reserve and Holdback

Define reserve triggers, calculation method, release schedule, and maximum holdback amounts to ensure predictable liquidity impacts for the merchant.

Dispute and Chargeback Handling

Assign responsibility for representment, evidence collection, deadlines for submitting evidence, and acceptance criteria for merchant-supplied documentation.

Indemnity and Limitations

Allocate indemnification obligations, carve out caps or exclusions where appropriate, and describe reimbursement mechanics and timing for settled liabilities.

Insurance and Remedies

Require minimum insurance coverage where relevant, set notice obligations for claims, and list remedies available to the acquirer or processor for unpaid losses.

Stepwise Completion Process

Follow a concise sequence to prepare, execute, and store the executed addendum to ensure enforceability and operational readiness.

01

Prepare: Assemble merchant profile, MID, and prior agreement details.
02

Populate: Complete all fields, use MM/DD/YYYY, and attach supporting schedules.
03

Execute: Obtain signatures from authorized representatives in the agreed order.
04

Archive: Store executed copies with audit trail and make accessible to reconciliation teams.

How to Configure an Online Signing Workflow

Set up a digital workflow that enforces signing order, required fields, and authentication to reduce processing errors and produce an auditable record.

Field	Configuration
Signature Method	eSignature with audit trail
Authentication	Email plus SMS one-time code
Routing Order	Merchant then Acquirer
Storage	Encrypted cloud storage

Where to Send and How the Process Flows

A clear routing flow ensures the addendum reaches all signers, triggers internal workflows, and creates an immutable execution record.

Upload: Add the executed template to the contract repository.
Tag Fields: Place signature, date, and required data fields.
Send: Deliver to signers in configured order with authentication.
Archive: Capture final PDF and audit trail for retention.

Digital Signing and Format Requirements

Use platforms that preserve an audit trail, support required authentication, and export tamper-evident signed PDFs.

Integrations: Salesforce, NetSuite, or accounting system links
File Formats: PDF and DOCX supported for templates
Authentication: Email, SMS OTP, or stronger methods

Typical Timing and Response Deadlines

The addendum should specify clear timeframes for notification, merchant response, and dispute submission to align with card network and internal processing windows.

Onboarding Effective Date:

Addendum becomes effective on the stated MM/DD/YYYY date.

Loss Notification:

Report suspected loss within 5 business days of detection.

Chargeback Response:

Provide evidence and dispute within 30 days of notification.

Reserve Review:

Review holdback calculations every 90 days or on trigger.

Record Availability:

Make requested records available within 10 business days.

Consequences of Failing to Follow the Addendum

Chargeback Liability: Merchant bears reimbursable chargebacks

Network Fines: Card brand penalties may apply

Regulatory Penalties: Compliance failures expose fines

Contract Termination: Provider may suspend services

Reserve Forfeiture: Held funds may be used for losses

Reputational Harm: Customer trust and relationships affected

Common Preparation Errors to Avoid

Vague liability language that fails to define loss categories, leading to disputes over coverage and reimbursement responsibility.
Omitting the correct Merchant ID or corporate legal name, causing chargebacks or reserves to be misapplied or rejected during reconciliation.
Late or incomplete evidence submission that misses network deadlines and results in automatic adverse chargeback outcomes.
Failing to align the addendum with existing merchant services agreements, producing conflicting obligations between documents.

Real-World Examples of Addendum Use

These condensed case examples show how organizations incorporate a loss addendum into payments workflows to reduce disputes and improve recoveries.

Optica Ventures (COO)

Optica standardized its merchant loss language across portfolios to reduce chargeback disputes.

The team required consistent Merchant IDs and evidence packets.
As a result, reconciliations become auditable and internal teams resolved disputes faster while preserving merchant relationships.

Martin Properties (Founder)

A real estate operator added precise reserve and notification rules for short-term rental bookings.

This clarified holdback timing and documentation.
The change reduced settlement surprises and ensured timely reimbursement for fraudulent bookings and related fees.

Frequently Asked Questions

Answers to common questions about enforceability, execution requirements, corrections, and revocation for the Legal Merchant Loss Addendum.

Need help? Contact support

Can this addendum be signed electronically?
Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and state electronic transaction laws (UETA where adopted), provided intent, consent, attribution, and reliable record retention are met.
When is notarization required?
Notarization is rarely required for a commercial addendum unless state recording or a specific contract clause mandates it; check local rules and the underlying merchant services agreement.
How do we correct an error after signing?
Use an agreed amendment or corrective addendum signed by authorized parties. Avoid handwritten changes on an executed document without a formal amendment to prevent enforceability disputes.
Who must sign for a corporate merchant?
An authorized corporate officer or agent with documented signing authority should sign. Include a printed name, title, and a statement of authority if not already present in corporate records.
How can a party revoke or cancel the addendum?
Revocation typically requires the process set out in the merchant services agreement or the addendum itself; unilateral revocation after execution may breach contract and expose the revoking party to liability.
What documentation supports chargeback disputes?
Provide transaction records, proof of delivery or service, customer communications, and any fraud-screening logs. Timely, complete evidence is essential to meet network dispute deadlines.

eSignature Pricing and Feature Snapshot for Addendum Execution

Comparison of common eSignature vendors and key criteria relevant to executing a Legal Merchant Loss Addendum; signNow appears first per vendor ordering rules.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Practical Tips for Accurate and Efficient Completion

Adopt standard practices to reduce errors, speed execution, and improve operational handling of merchant losses.

Use canonical identifiers

Always include the legal entity name, DBA, and Merchant ID to ensure events are attributed correctly during reconciliation and dispute handling.

Standardize evidence packages

Create a checklist of required documents for chargeback representment to speed responses and reduce missed deadlines.

Configure automation

Use templates and conditional fields to ensure every addendum includes required clauses and that optional clauses appear only when applicable.

Maintain an audit trail

Capture signer authentication, timestamps, IP addresses, and signed PDF exports to support legal and network disputes.

Typical Authorized Signatories

Chief Financial Officer

The CFO or delegated finance leader usually signs for financial commitments, reserves, and indemnity clauses. This signer should be listed in corporate records and have authority to bind the entity for payment obligations.

Head of Payments

An operations or payments executive often signs operational provisions related to chargebacks, dispute coordination, and evidence submission processes; their role should be documented in internal delegation policies.

Security and Compliance Considerations

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest

Certifications: SOC 2 Type II; ISO 27001

HIPAA: BAA required for PHI handling

21 CFR Part 11: Supported with appropriate controls

ESIGN/UETA: Meets electronic signature legal tests

Accessibility: WCAG 2.0 Level AA compatibility

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now