Establishing secure connection…Loading editor…Preparing document…

Payment Processing Cardconnect Document

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

PAYMENT PROCESSING AGREEMENT — CARDCONNECT

RECITALS

Merchant Name:

Processor Name:

WHEREAS, Merchant operates a business that accepts payment card transactions and seeks payment processing and related services; and

WHEREAS, Processor provides payment card processing, settlement and related services (collectively, the Services) and is willing to provide such Services to Merchant subject to the terms and conditions set forth in this Agreement.

PARTY INFORMATION

SCOPE OF WORK

Processor shall provide the following services to Merchant: card transaction authorization, settlement, fund disbursement, dispute and chargeback handling support, payment gateway services, and related reporting and reconciliation (collectively, the Services). Merchant and Processor acknowledge that specific configuration and optional features are set forth below.

PAYMENT TERMS

Merchant shall pay Processor fees for Services as set forth below. Fees are payable in USD and are exclusive of taxes which shall be Merchant's responsibility unless otherwise required by law.

Chargebacks, fines, and other issuer, card network or acquirer assessments arising from Merchant transactions that are the result of Merchant's acts or omissions shall be the responsibility of Merchant. Processor may debit Merchant account(s) for such amounts in accordance with settlement procedures and may withhold funds or establish reserves to cover liabilities.

TERM AND TERMINATION

This Agreement commences on Start Date and continues through End Date unless earlier terminated as provided herein.

Start Date:     End Date:

Either party may terminate for material breach if such breach is not cured within thirty (30) days after written notice, or immediately for insolvency, bankruptcy filing, or violation of card brand operating rules that materially jeopardizes Processor or acquirer relationships.

CONFIDENTIALITY

Each party will hold confidential and will not disclose to any third party, except as provided below, any non-public information received from the other party that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information. Confidential information excludes information that: (a) is or becomes public other than through breach of this Agreement; (b) is known to the receiving party without restriction prior to disclosure; or (c) is independently developed by the receiving party without use of the disclosing party's confidential information. Each party may disclose confidential information to its employees, agents, affiliates, acquirers or service providers who have a need to know provided such parties are bound by confidentiality obligations at least as protective as those herein.

DATA SECURITY & PCI COMPLIANCE

Merchant acknowledges that it is responsible for maintaining applicable PCI DSS standards for Merchant-controlled systems and for any cardholder data it stores, transmits, or processes. Processor will maintain administrative, physical and technical safeguards appropriate to protect cardholder data processed by Processor. Merchant shall cooperate with Processor and acquirers in any compliance audits and shall promptly remediate any security deficiencies affecting transactions.

I acknowledge Merchant responsibility for PCI compliance

INDEMNIFICATION; LIMITATION OF LIABILITY

Merchant shall defend, indemnify, and hold Processor harmless from and against any third-party claims, losses, liabilities, costs and expenses (including reasonable attorneys' fees) arising out of Merchant's breach of this Agreement, fraudulent transactions, breaches of law or card brand rules, negligence, or willful misconduct. Processor shall indemnify Merchant for Processor's gross negligence or willful misconduct.

EXCEPT FOR EACH PARTY'S INDEMNIFICATION OBLIGATIONS AND LIABILITY FOR WILLFUL MISCONDUCT, NEITHER PARTY SHALL BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES. THE AGGREGATE LIABILITY OF EITHER PARTY ARISING OUT OF OR RELATED TO THIS AGREEMENT SHALL NOT EXCEED THE TOTAL FEES PAID BY MERCHANT TO PROCESSOR DURING THE TWELVE (12) MONTH PERIOD PRECEDING THE EVENT GIVING RISE TO LIABILITY.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to conflict of laws principles. Venue for any dispute shall be the state or federal courts located in the jurisdiction selected above.

NOTICES

Notices under this Agreement shall be in writing and delivered to the addresses set forth above or to any updated address provided in writing. Notices may be delivered by hand, certified mail (return receipt requested), or overnight courier and shall be effective upon receipt.

ENTIRE AGREEMENT; AMENDMENT

This Agreement, together with any schedules, addenda, and exhibits expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, proposals, or communications. No amendment or modification shall be effective unless in a writing signed by authorized representatives of both parties.

MISCELLANEOUS

If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. Neither party may assign this Agreement without the prior written consent of the other, except that Processor may assign to an acquirer, affiliate or successor in connection with a merger or sale of Processor's assets.

Merchant:

By:

Date:

Processor:

By:

Date:

Enter text✕

What the Payment Processing Cardconnect Document Is

The Payment Processing Cardconnect Document is a merchant onboarding and authorization form used to establish CardConnect payment services for a U.S. business. It collects merchant-identifying information (legal name, DBA, EIN), bank routing and account numbers for deposit settlement, card-processing preferences and fee schedules, PCI/PCI-DSS attestations, and signatures authorizing payment routing and chargeback handling. The form can include optional addenda for ACH authorization or submerchant arrangements and is commonly executed digitally under U.S. e-signature law when permitted.

Why this document matters for merchant accounts

A complete, accurate Cardconnect onboarding document speeds underwriting, enables timely settlement, and documents merchant consent for processing and chargeback rules while helping maintain PCI compliance and audit readiness.

Why this document matters for merchant accounts

Who prepares and signs this document

Typical preparers and signers for Cardconnect onboarding include merchant finance, operations, and authorized officers.

  • Merchant Operations Manager — completes processing preferences and settlement schedule; ensures account details are correct.
  • Chief Financial Officer or Treasurer — signs for corporate authorization, grants chargeback and settlement permissions.
  • Third‑party Billing Provider — completes submerchant sections when using facilitators or payment service providers.

Different roles require different fields and attestations; ensure the authorized signer has legal authority to bind the business.

Step-by-step: completing and submitting the document

Follow these steps to prepare, verify, and submit a Cardconnect onboarding document for fast processing.

  • 01
    Gather documents: Collect EIN confirmation, voided check, and government ID.
  • 02
    Complete fields: Enter merchant, banking, and fee schedule information accurately.
  • 03
    Authenticate signer: Confirm authorized officer or attach board resolution when needed.
  • 04
    Submit to underwriter: Send with supporting documents and retain a signed copy.

Required data elements and security attestations

Merchant Legal Name: Exact as IRS
EIN / TIN: Nine-digit tax ID
Bank Routing: Nine-digit ABA
Bank Account: Full account number
PCI Attestation: Level and SAQ type
Authorized Signer: Name, title, date

Consequences and common compliance risks

Backup Withholding: 24% withholding risk
Chargeback Liability: Financial exposure to merchant
PCI Fines: Noncompliance penalties possible
Account Freeze: Underwriter may suspend processing
Delayed Settlement: Settlement hold or delayed funds
Fraud Risk: Elevated monitoring or reserves

Frequent errors that delay onboarding

  • Mismatch between EIN and legal business name causes IRS verification failures and may require corrected forms.
  • Incorrect routing or account numbers lead to failed micro-deposit verification and delayed first settlement.
  • Incomplete signature blocks or missing corporate authorization force resubmission and slow underwriting.
  • Missing PCI attestation or incomplete SAQ information can trigger additional security review and remediation.

Key sections to include in a professional Cardconnect document

A clear, complete document groups identity, banking, processing, compliance, fee, and signature sections to streamline review and support auditability.

Merchant Identity

Full legal name, DBA, business address, and EIN for tax and underwriting verification; attach formation or tax exemption documents when applicable.

Bank Details

Routing and account numbers plus voided check or bank letter for settlement verification; optional micro-deposit process described.

Processing Options

Card types accepted, recurring billing preferences, ACH authorization, chargeback handling, and settlement timing for clear expectations.

Fees and Holdbacks

Specify transaction fees, monthly charges, and any reserve or rolling reserve terms to avoid later disputes.

Compliance Attestations

PCI-DSS level, SAQ type, AML/KYC confirmation, and data security responsibilities required by processor and acquirer.

Authorized Signatures

Signature, printed name, title, date, and any corporate resolution or power-of-attorney documentation proving authority to bind the business.

How electronic submission and approval typically flows

Digital workflows reduce friction and capture essential audit data during onboarding.

  • Upload: Sender uploads document and attachments.
  • Field placement: Place signature, date, and bank fields.
  • Signer authentication: Signers authenticate via email, SMS, or stronger methods.
  • Underwriting review: Processor reviews and verifies supporting documents.

Recommended digital workflow settings

Configure your e-submission workflow to collect the right evidence and reduce rework during underwriting.

Field Configuration
Signature Field Required for all authorized signers
Bank Verification Attach voided check or enable micro-deposits
ID Verification Require government ID upload for high-risk merchants
Audit Trail Capture timestamps, IP, and authentication events

Technical formats and integration notes

Choose a platform that preserves audit trails and supports your CRM or accounting systems to automate underwriting handoffs and settlement notifications.

  • File types: PDF, DOCX accepted
  • Integrations: NetSuite, Salesforce, Google Workspace
  • Export formats: Signed PDF with audit trail

Typical timelines and processing expectations

Timing varies by processor and risk profile; these are common benchmarks to set expectations.

Document Submission:

Same day if complete

Underwriting Review:

24–72 hours typical

Bank Verification:

Micro-deposits 1–3 business days

Account Activation:

Often 3–7 business days after clearance

Settlement Schedule:

Next-day to T+3 depending on processor

eSignature pricing and capability comparison (signNow first)

Compare starting price and common capability lines that affect Cardconnect document workflows; do not rely on this table for procurement decisions without vendor confirmation.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
Envelope Cap No cap 100 env/user/yr Varies Varies Varies

Frequently asked questions about execution and e-submission

Answers to common technical, legal, and processing questions when completing a Cardconnect onboarding form.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users