Can a summary be signed electronically?

Yes. In the United States electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws adopted by most states. Ensure the signature method documents intent, consent, attribution, and that the record is retained and reproducible.

When is notarization required?

Notarization is required only when a recipient or state law demands a notarized attestation. Verify with the acquirer or legal counsel; some jurisdictions and specific documents (deeds, POAs) impose notarization or witness rules.

What authentication strength should I use?

Use authentication aligned to transaction risk: basic email OTP for routine internal attestations, SMS or KBA for external attestation, and multifactor or PKI for high-assurance legal or regulatory submissions.

How long must I retain signed summaries?

Retention depends on the legal basis: IRS records three years (IRC §6501(a)), HIPAA six years (45 CFR §164.530(j)), and industry rules may require longer. Keep a defensible retention schedule.

What supporting documents are essential?

Include processor statements, bank deposit records, merchant agreement, reserve calculations, and dispute correspondence. These items reduce follow-up requests and substantiate figures during audits or underwriting.

What if a recipient rejects an electronic summary?

Determine the reason—format, missing notarization, or authentication level—and correct. If required, provide a notarized paper copy or use a remote online notarization process where accepted by the recipient.

Electronic Signature
Templates
Finance
Financial Merchant Summary

Financial Merchant Summary

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

FINANCIAL MERCHANT SUMMARY

Summary Date: Prepared By:

Merchant Information

Merchant Legal Name Doing Business As (DBA)

Merchant ID: Tax ID / EIN:

Primary Contact

Title: Phone: Email:

Business Address

Processor / Acquirer Details

Acquirer / Processor Name:

Processor Contact: Processor Phone:

Merchant Account Number: MCC:

Business Type (select all that apply)

Retail Restaurant E‑Commerce MOTO / Phone Order Other:

PCI Compliance Status

Validated PCI Compliance Self-Assessment Questionnaire (SAQ) Not Compliant

Transaction & Volume Summary

Average Ticket: Monthly Gross Volume: Monthly Transaction Count:

Peak Day Volume: Card Present %: Card Not Present %:

Chargeback Rate (last 12 months): % Refund Rate: %

Open Disputes Outstanding:

Settlement & Funding Details

Funding Bank

Routing Number: Account Number:

Funding Frequency

Daily Twice Monthly Weekly Monthly

Standard Funding Delay (days):

Fees & Pricing Summary

Enter the applicable fee components below. Amounts should reflect monthly totals where applicable.

Description	Quantity	Unit Rate	Amount
Interchange (pass-through)
Discount / Markup
Processor / Network Fees
Monthly Minimum Fee
Chargeback / Retrieval Fee
PCI / Compliance Fee
Other Fees (describe)
Subtotal
Tax
Total Monthly Fees

Notes / Terms & Conditions

Risk, Compliance & Underwriting Notes

Certifications & Authorization

By signing below, Merchant certifies that the information contained in this Financial Merchant Summary is true, complete, and accurate to the best of Merchant's knowledge. Merchant authorizes the processor and its agents to verify bank accounts, credit history, processing history, and to obtain necessary records to underwrite and service the merchant account. Merchant agrees to comply with applicable card network rules and to maintain required data security measures.

Merchant acknowledges and agrees that settlement may be initiated to the designated funding account and that fees, chargebacks, adjustments, and returns may be debited from the funding account in accordance with the merchant processing agreement. Merchant agrees to indemnify and hold harmless the processor for losses resulting from inaccurate information, breach of representations, or failure to comply with network rules.

Authorization (select all that apply)

Permit account verification and micro-deposits Authorize ACH debits for fees and chargebacks Certify tax identification information is correct

Required Attachments Checklist

Voided check or bank letter Processing statements (last 3 months) Government-issued ID for principal(s)

Signature

Merchant Authorized Signatory

Print Name:

Title:

Signature:

Date:

What a Financial Merchant Summary Is and when it’s used

A Financial Merchant Summary is a concise account-level report that aggregates a merchant’s payment processing activity, balances, fees, reserves, chargebacks, returns, and settlement history for a defined reporting period. Acquirers, processors, underwriters, and merchants use the summary for underwriting, reconciliation, dispute handling, and regulatory review. Summaries often accompany applications for acquiring relationships, working capital, or audits, and can be delivered as signed electronic records. When executed electronically, summaries should meet ESIGN/UETA validity criteria to serve as enforceable documentation across U.S. jurisdictions.

Why standardizing the summary matters

A standardized Financial Merchant Summary reduces review time, improves comparability across accounts, and surfaces risk indicators like chargeback ratios or reserve shortfalls while preserving original transaction records and auditability.

Typical users and reviewers

Primary users include merchant finance teams, payment processors, acquiring banks, and underwriters who evaluate account health and risk.

Merchant owners and controllers review volumes, fees, reserves, and settlement timing to manage cash flow.
Payment processors and acquiring banks use it for underwriting, fraud monitoring, and settlement reconciliation.
Underwriting and compliance teams check chargeback rates, reserve levels, and lawful disclosures during periodic reviews.

Tailor the summary to the recipient: a processor may require technical reconciliation data, while an underwriter focuses on chargebacks and reserves.

Key elements every professional summary should include

Present a verifiable snapshot of processing volumes, fees, settlements, chargebacks, reserves, and counterparty details so reviewers can assess performance and risk quickly.

Account Overview

Merchant legal name, merchant ID, processing bank, merchant category code, account opening date, and reporting period for clear identity and context during underwriting or audits.

Volume & Settlements

Daily and monthly gross processing volumes, net settlement totals, payout schedules, and settlement lead times reconciled to bank deposits to highlight cashflow patterns.

Fees & Reserving

Itemized interchange, processor fees, chargeback costs, and current reserve balances with clear reserve release schedules and calculation formulas.

Chargebacks & Disputes

Chargeback counts by reason code, representment outcomes, dispute timelines, and chargeback-to-transaction ratios; flag recurring reason codes for remediation.

Liquidity Metrics

Available account balances, pending settlements, projected settlement dates, and net projected cashflow for the upcoming settlement cycle.

Supporting Documents

Attach merchant agreement, processing statements, bank statements, and any correspondence related to disputes, underwriting, or regulatory inquiries for verification.

Step-by-step: prepare and deliver the summary

Follow a consistent sequence: collect records, verify figures, complete the summary fields, obtain signatures, and archive the final package with supporting documentation.

01

Collect documents: Bank statements, processor reports, merchant agreement, chargeback logs.
02

Verify figures: Reconcile totals, fees, reserves, and dispute outcomes to source documents.
03

Complete fields: Enter standardized identifiers, reporting period, and itemized fee lines.
04

Sign and archive: Obtain signatures, attach exhibits, and store with retention metadata.

Configuring an online completion workflow

Configure the document workflow so fields, authentication, and notifications align with internal controls and recipient expectations.

Field \| Configuration	Setting
Upload Source	PDF upload, CSV import, or API ingestion from processor statements.
Signature Method	ESIGN-compliant electronic signature or PKI-based digital signature if required.
Authentication	Email OTP, SMS code, or knowledge-based authentication for higher assurance.
Notification	Email notifications to merchant, underwriter, and processor with archived copies.

Typical routing and submission flow

A clear routing flow reduces processing delays: prepare, route to reviewers, obtain attestations, and archive with the audit trail.

Prepare summary: Assemble figures and supporting documents into the standardized template.
Route to reviewers: Send to internal finance, external acquirer, or underwriting teams in order.
Attest and sign: Authorized signers attest to accuracy and sign electronically, capturing identity and timestamp.
Archive with audit: Store signed record with audit metadata and attachments for future inspection.

Technical requirements for digital completion

Ensure file format, integration touchpoints, and authentication options match recipient expectations before sending.

File Formats: PDF, DOCX, and CSV accepted for statements and attachments.
Integrations: CRM and ERP integrations such as Salesforce or NetSuite simplify imports.
Authentication: Email OTP, SMS, or stronger KBA as required by recipient policies.

Security and compliance basics to include

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

Audit Trail: Timestamp, IP address, and action log

HIPAA (if applicable): BAA required for protected health information

SOC 2: Controls for availability and confidentiality

PCI Considerations: Avoid storing raw PAN data

Access Controls: Role-based permissions and SSO

eSignature vendor pricing and feature snapshot

Comparison of common eSignature plans and capabilities to consider when choosing a platform for Financial Merchant Summary execution; signNow appears first per platform comparison conventions.

	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	No	No	No	No
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Typical time expectations and processing windows

Understanding common timing expectations helps prevent missed deadlines and preserve disputable rights; confirm specific windows with the processor or acquirer.

Monthly statement issuance:

Most processors issue monthly statements within 5–10 business days of month close.

Settlement posting:

Net settlement timing typically occurs on scheduled payout days per the merchant agreement.

Chargeback response window:

Respond within the processor or card network windows—often measured in days from receipt.

Reserve review periods:

Processors typically review reserve levels monthly or upon material changes in activity.

Document retention checkpoints:

Retain signed summaries and exhibits according to internal and regulatory retention policies.

Common mistakes to avoid when preparing the summary

Submitting incomplete merchant identifiers or mismatched legal names, which causes delays or rejects from acquirers and banks.
Failing to reconcile gross volumes to processor statements, creating discrepancies reviewers treat as potential fraud or accounting errors.
Omitting reserve formulas or release schedules, leading to confusion about held funds and disputes over release timing.
Using improper signature methods that lack clear attribution, timestamp, or retention metadata and therefore may be questioned in disputes.

Consequences of inaccurate or late summaries

Chargeback Liability: Loss of funds and additional fees

Reporting Penalties: Fines or regulatory action possible

Tax Exposure: Incorrect reporting can trigger audits

Suspended Account: Processor may freeze or terminate account

Fraud Risk: Higher chargeback ratios and scrutiny

Compliance Breach: HIPAA or PCI fines may apply

Frequently asked questions and common issues

Below are answers to frequent practical and legal questions encountered when preparing, signing, and submitting Financial Merchant Summaries.

Need help? Contact support

Can a summary be signed electronically?
Yes. In the United States electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws adopted by most states. Ensure the signature method documents intent, consent, attribution, and that the record is retained and reproducible.
When is notarization required?
Notarization is required only when a recipient or state law demands a notarized attestation. Verify with the acquirer or legal counsel; some jurisdictions and specific documents (deeds, POAs) impose notarization or witness rules.
What authentication strength should I use?
Use authentication aligned to transaction risk: basic email OTP for routine internal attestations, SMS or KBA for external attestation, and multifactor or PKI for high-assurance legal or regulatory submissions.
How long must I retain signed summaries?
Retention depends on the legal basis: IRS records three years (IRC §6501(a)), HIPAA six years (45 CFR §164.530(j)), and industry rules may require longer. Keep a defensible retention schedule.
What supporting documents are essential?
Include processor statements, bank deposit records, merchant agreement, reserve calculations, and dispute correspondence. These items reduce follow-up requests and substantiate figures during audits or underwriting.
What if a recipient rejects an electronic summary?
Determine the reason—format, missing notarization, or authentication level—and correct. If required, provide a notarized paper copy or use a remote online notarization process where accepted by the recipient.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now