Establishing secure connection…Loading editor…Preparing document…

Payment Acceptance Agreement

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

PAYMENT ACCEPTANCE AGREEMENT

Parties and Effective Date

This Payment Acceptance Agreement (the Agreement) is entered into between Merchant Name: with primary address: and Payment Service Provider: .

Effective Date:

Recitals

WHEREAS, Merchant seeks to accept electronic and other forms of payment from its customers; and WHEREAS, Provider offers payment processing, settlement and related services and agrees to provide such services subject to the terms of this Agreement.

Definitions

"Accepted Payment Methods" means the payment types listed in the Payment Methods section below. "Settlement" means transfer of cleared funds to Merchant's designated account. "Chargeback" means a reversal or dispute of a payment initiated by a cardholder or card issuer.

Payment Methods Accepted

Select Accepted Payment Methods (check all that apply):

Authorization and Processing

Merchant authorizes Provider to accept and process payments on Merchant's behalf in accordance with this Agreement. Merchant shall provide accurate transaction data and authorizations necessary to permit Provider to process payments. Merchant Account Identifier:

Settlement Bank Account for ACH/direct deposit:

Fees and Pricing

Provider will charge Merchant the following fees for services rendered. Flat percentage fee per card transaction: % and Per-transaction fixed fee:

Monthly account fee: | Chargeback fee:

Merchant acknowledges that fees may include interchange, network and processing fees passed through by Provider. Merchant elects to have fees:

Settlement and Reporting

Settlement Cycle (choose standard or describe):

Reporting Frequency:

Refunds, Chargebacks and Disputes

Merchant is responsible for refund policies and handling customer disputes. Merchant will cooperate with Provider in responding to chargebacks and will reimburse Provider for any final chargeback, losses, fees, fines, or assessments attributable to Merchant's transactions. Dispute resolution contact:

Representations and Warranties

Each party represents and warrants that it has full power and authority to enter into this Agreement, that its execution and performance will not violate any applicable law, and that all information provided to the other party is true and complete. Merchant further represents that it will comply with applicable card brand rules and applicable law in connection with payment acceptance.

Compliance and Data Security

Merchant shall maintain compliance with applicable data-security requirements, including but not limited to payment card industry standards. Merchant confirms it will not store cardholder data in violation of such requirements. PCI compliance status:

Data security contact:

Taxes and Withholding

Merchant is responsible for all taxes associated with transactions except taxes based on Provider's net income. If Provider is required by law to withhold taxes from amounts payable to Merchant, Provider may do so and will provide documentation of such withholding. Tax identification number:

Indemnification

Merchant shall indemnify, defend and hold harmless Provider and its affiliates from and against any claim, loss, liability, damage, cost or expense (including reasonable attorneys' fees) arising out of Merchant's breach of this Agreement, Merchant's fraudulent or negligent acts, or Merchant's failure to comply with applicable laws or card brand rules.

Limitation of Liability

Except for breaches of confidentiality, willful misconduct, or liabilities arising from indemnification obligations, neither party will be liable to the other for consequential, incidental, special or punitive damages. Provider's aggregate liability under this Agreement will not exceed the total fees paid by Merchant to Provider in the three (3) months preceding the claim.

Term, Termination and Suspension

The term of this Agreement begins on the Effective Date and continues until terminated by either party. Initial term (months):

Termination upon notice requires: days' prior written notice.

Notices

All notices required or permitted under this Agreement shall be in writing and delivered to the addresses below. Merchant notice recipient:

Miscellaneous

Governing Law: The validity, interpretation and performance of this Agreement shall be governed by the laws of:

This Agreement constitutes the entire agreement between the parties with respect to payment acceptance and supersedes prior agreements on the same subject. Any amendment must be in writing and signed by both parties.

Additional Terms and Notes

Merchant Printed Name:

By:

Date:

Payment Service Provider Printed Name:

By:

Date:

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What a Payment Acceptance Agreement Is and when it applies

A Payment Acceptance Agreement is a written contract that sets the terms under which one party accepts payment from another, defining payment methods, timing, fees, disputes, and liabilities. It clarifies responsibilities for processors, merchants, and customers and can be standalone or part of a larger sales, services, or vendor contract. For many organizations it helps document collection rules, refund policies, chargeback handling, and any third-party payment processor obligations.

Why documenting payment terms matters legally and operationally

A clear Payment Acceptance Agreement reduces billing disputes, sets expectations for payment timing and responsibility, and provides evidence for collections or regulatory compliance. It makes fee allocation, refund policy, and processor liability explicit, which lowers operational friction and legal risk.

Why documenting payment terms matters legally and operationally

Who typically completes a Payment Acceptance Agreement

Organizations that collect or process payments use this agreement to set payment rules and to allocate risk between payer, payee, and payment processor.

  • Small businesses and merchants managing credit card or ACH collections and requiring clear refund and chargeback procedures.
  • Service providers and vendors defining invoicing terms, late fees, and accepted payment channels for clients.
  • Finance, accounts receivable, and legal teams at mid-market and enterprise firms integrating payment terms into procurement or vendor contracts.

Use by the appropriate business owner (finance, legal, or payments lead) helps ensure enforceability and alignment with processor terms and applicable law.

Core elements to include in a professional Payment Acceptance Agreement

A robust agreement combines operational detail with legal protections. Include clear definitions, payment methods, timing, responsibilities, dispute processes, and signature blocks to reduce ambiguity and support enforcement.

Definitions

Define payer, payee, processor, settlement, chargeback, effective date and scope to avoid later interpretation disputes.

Payment Methods

Specify accepted methods (ACH, credit card, check, wire), processor names, and any fees charged to the payer or deducted by the processor.

Payment Terms

State due dates, grace periods, late fees, discount terms, and conditions for recurring payments or automatic renewals.

Chargebacks & Refunds

Describe chargeback responsibility, time limits to dispute claims, refund eligibility, and the documentation required to resolve disputes.

Compliance & Data

Allocate responsibility for PCI, HIPAA (if PHI involved), data breach notifications, and any required Business Associate Agreement (BAA).

Indemnity & Limits

State indemnification, liability caps, and consequences for nonpayment or fraudulent activity, plus governing law and dispute resolution.

Essential data fields the agreement should capture

Payer Identity: Full legal name and taxpayer ID (EIN/SSN) of the payer.
Payee Identity: Registered business name and EIN or tax ID for the receiving party.
Payment Method: Selected method: ACH, credit card, wire, or check.
Amount Terms: Payment amount, frequency, and currency.
Processor Details: Name of payment processor and merchant account ID.
Effective Date: Start date for obligations and recurring payments.

Step-by-step process to complete and execute the agreement

Follow a clear sequence to reduce errors: prepare, verify, sign, and distribute. Confirm identity and payment details before finalizing signatures.

  • 01
    Prepare Document: Populate payer/payee details and payment terms; attach processor addendum if required.
  • 02
    Verify Identity: Confirm signer authority and payment account details with supporting ID or bank verification.
  • 03
    Authorize Payments: Obtain explicit agreement to recurring payments or ACH debit mandates where applicable.
  • 04
    Execute and Archive: Sign, date, and save final copy; distribute to accounting and the payer.

Configuring a digital workflow for Payment Acceptance Agreements

Set up a repeatable template that enforces required fields, signer authentication, and routing to accounting and legal for approval.

Field Configuration
Authentication Method Email link, SMS code, or KBA depending on risk and compliance.
Signature Fields Require full name, title, date, and optional initial fields for key clauses.
Payment Capture Enable secure payment collection or tokenization through the processor integration.
Reminder Schedule Set automatic reminders and escalation rules for unsigned agreements.

Technical considerations for eSigning and eSubmission

Choose a platform that supports secure signatures, audit trails, and the file formats used by your systems.

  • File Formats: PDF, DOCX and HTML are commonly supported and preserve form fields.
  • Integrations: Must connect to accounting/CRM: Salesforce, NetSuite, Microsoft 365, Google Workspace.
  • Security Controls: TLS in transit and AES-256 at rest are required for PCI/HIPAA contexts.

Ensure the chosen solution produces an audit trail, supports required authentication strength, and can export signed records for long-term retention.

Where signed Payment Acceptance Agreements are routed

Document routing defines who receives and stores the agreement after execution. Standard recipients include accounting, legal, the payment processor, and both contracting parties.

  • Accounting: Stores agreement for invoice matching and reconciliation.
  • Payment Processor: Receives contract terms or addenda when required by the processor.
  • Legal: Retains final signed copy for dispute defense and audits.
  • Payer Copy: Provide recipient with a signed copy and proof of consent.

Time-sensitive requirements and common deadlines to track

Track statutory and operational deadlines: tax reporting, payer notification, and timelines for responding to disputes or chargebacks.

Provide W-9 on request:

Payers should supply a completed W-9 when requested to avoid backup withholding.

1099-NEC filing deadline:

Issue 1099-NEC to recipients by January 31 for nonemployee compensation.

Chargeback response times:

Processor deadlines vary; respond promptly to preserve dispute rights.

ACH authorization retention:

Retain ACH authorizations per bank rules and auditor requirements, commonly three years.

Contract renewals:

Note automatic renewal notice periods specified in the agreement to manage changes.

Key processing milestones from offer through settlement

View the lifecycle as sequential milestones to ensure compliance and timely settlement of funds.

01

Draft & Review

Prepare terms and obtain internal approvals before sending to the payer.

02

Obtain Authorization

Secure payer signature and payment method authorization.

03

Processor Setup

Register merchant account and configure payment flows.

04

Settlement & Reconciliation

Confirm funds are settled and reconcile with accounting records.

Common mistakes to avoid when preparing payment agreements

  • Vague payment terms: failing to define due dates and late fees clearly.
  • Mismatched names: signer name differs from bank or tax records causing verification failures.
  • Missing processor clauses: no allocation of chargeback or refund responsibility.
  • Insufficient authentication: weak signer verification increases fraud and disputes.

Principal legal and financial risks of an incorrect or missing agreement

IRS Reporting Penalties: IRC §6721 penalties for incorrect/missing information returns.
Backup Withholding: 24% backup withholding may apply if TIN is incorrect.
Processor Fines: Violation of processor terms can lead to fines or account termination.
Chargeback Losses: Untimely documentation may forfeit dispute rights and financial recovery.
HIPAA Violations: Improper handling of PHI can trigger 45 CFR §164 penalties.
Contract Liability: Ambiguous terms increase litigation and collection costs.

Typical eSignature provider pricing and feature snapshot for payment agreements

Compare entry-level pricing and core capabilities that affect Payment Acceptance Agreement workflows, such as HIPAA support and any envelope/document caps.

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 by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes Varies by plan
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year No cap No cap No cap

Frequently asked questions about Payment Acceptance Agreements

Answers to common questions about validity, electronic execution, notarization, and how to correct or revoke payment authorizations.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.