Can I submit the form electronically?

Yes. Electronic submission is valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states if intent, consent, attribution, and retention requirements are met.

Is a notarized signature required?

Usually no for debit blocks, but some institutions or states may request notarization for corporate accounts or high-risk transactions; verify with the receiving bank.

How do I revoke a block?

Submit a signed revocation to the same recipient and note the desired effective date; banks require time to process cancellations and to update clearing instructions.

What if the bank ignores the block?

Escalate to your bank's compliance or dispute unit, retain proof of submission, and consider filing an ACH dispute under your bank's procedures.

Can I use a consumer eSign option like an email link?

Yes when consumer-facing disclosures are provided per ESIGN (15 U.S.C. §7001(c)); verify the recipient can access records and that consent to electronic delivery is recorded.

What records should I keep?

Keep the signed form, confirmation receipt, audit trail, and supporting bank statements; follow retention guidance (IRS 3 years, HIPAA 6 years) as applicable.

Electronic Signature
Templates
Miscellaneous
Payment Debit Block Form

Payment Debit Block Form

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

Payment Debit Block Form

This Payment Debit Block Agreement (the Agreement) is entered into as of Effective Date: by and between Client Name: and Service Provider Name: .

WHEREAS

WHEREAS, Client maintains one or more accounts from which automated debits and electronic withdrawals (Debits) are authorized by merchants and third parties; and

WHEREAS, Service Provider specializes in implementing payment debit block services and filtering to prevent unauthorized or undesired Debits from being processed against Client accounts; and

WHEREAS, Client desires to engage Service Provider to implement and manage a debit block in accordance with the terms and conditions set forth in this Agreement.

PARTIES' CONTACT INFORMATION

Client Address Service Provider Address Primary Contact (Client) Primary Contact (Service Provider)

SCOPE OF WORK

Service Provider will undertake reasonable commercial efforts to configure, implement and maintain a payment debit block service as described below. The scope includes rule creation, merchant exclusion lists, monitoring, reporting, and escalation procedures as agreed between the parties.

Detailed Scope (describe services, limits, and exclusions)

PAYMENT TERMS

Client shall pay Service Provider the fees set forth below in exchange for the Services. All amounts are in United States dollars unless otherwise agreed in writing.

Total Fee Payment Schedule Late Fee

Late payments shall accrue interest at the lesser of: (i) % per month, or (ii) the maximum rate permitted by applicable law. Additionally, a fixed administrative fee of may be applied to each delinquent invoice.

TERM AND TERMINATION

This Agreement commences on Start Date: and continues until End Date: unless earlier terminated in accordance with this section.

Either party may terminate this Agreement for convenience upon written notice to the other party delivered at least days prior to the effective termination date. Either party may terminate immediately for cause upon material breach by the other party if the breach remains uncured 15 days after written notice.

CONFIDENTIALITY

Each party shall treat as confidential and shall not disclose to any third party any non-public information of the other party provided in connection with this Agreement, including account numbers, payment histories, and rule configurations (Confidential Information). Confidential Information shall be used solely for the performance of this Agreement. The obligations of confidentiality shall survive termination of this Agreement for a period of three (3) years, or as otherwise required by applicable law.

LIMITATIONS, INDEMNITY AND WARRANTIES

Service Provider warrants that it will perform the Services in a professional and workmanlike manner. EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, SERVICE PROVIDER MAKES NO OTHER WARRANTIES, EXPRESS OR IMPLIED. Client acknowledges that debit blocking may not prevent all unauthorized charges and that certain financial institutions or third parties may process Debits notwithstanding a block request. Client shall indemnify and hold Service Provider harmless from any claim, loss or liability arising from Client's failure to provide accurate account information, timely instructions, or from Client's instruction to permit a Debit previously blocked.

GOVERNING LAW; DISPUTE RESOLUTION

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to conflict of law principles. Any dispute arising out of or relating to this Agreement shall be resolved by binding arbitration in accordance with the commercial arbitration rules mutually agreed by the parties, unless otherwise prohibited by applicable law.

ENTIRE AGREEMENT

This Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals and communications, whether oral or written. Any amendment to this Agreement must be in writing and signed by authorized representatives of both parties.

NOTICES

All notices under this Agreement shall be in writing and delivered to the addresses set forth above or to such other address as either party may designate in writing. Notices are effective upon receipt.

ACKNOWLEDGMENT

By signing below, each party represents and warrants that it has the authority to enter into this Agreement and that the information provided herein is true and correct. Client acknowledges that implementation of debit block rules may require coordination with Client's financial institution and that Service Provider's obligations are subject to the actions and cooperation of third parties.

Client:

By:

Date:

Service Provider:

By:

Date:

What the Payment Debit Block Form Is and when it matters

A Payment Debit Block Form is a written authorization that instructs a bank, payment processor, or payee to prevent specified debit entries from being applied to an account. Commonly used to stop recurring ACH withdrawals, merchant-initiated debits, or specific third-party debits, the form documents the account holder's intent, the scope of the block, and the effective period. It can be used by consumers and businesses to limit exposure to unauthorized or disputed debits and to provide a clear paper or electronic record for routing and compliance with banking and payments rules.

Why a Payment Debit Block Form is useful

A properly completed block form establishes authorization, narrows which debits are prevented, and creates a record for banks or processors to act on. It reduces transaction risk and supports timely dispute resolution while documenting the account holder's intent under electronic signature laws such as ESIGN and UETA.

Who typically completes a Payment Debit Block Form

Individuals and organizations complete this form when they want to stop specific debit activity while preserving other payment permissions.

Consumers protecting personal bank accounts from unwanted recurring debits or suspected fraud.
Small businesses preventing vendor or subscription ACH debits during billing disputes or contract termination.
Banks and corporate treasury teams enforcing customer-directed debit blocks and maintaining compliance records.

The form is also used by financial operations teams and compliance officers to document controls and to support audit trails for payment disputes or reconciliations.

Step-by-step: completing a Payment Debit Block Form

Follow these steps in order to create a complete, actionable block that a bank or processor can implement without follow-up.

01

Verify account: Confirm routing and account numbers against a bank statement.
02

Define scope: List merchant names, company IDs, or transaction types to block.
03

Set dates: Enter effective date and a clear end date or 'indefinite'.
04

Sign and submit: Sign using required authentication method and send to the listed recipient.

Core components every professional Payment Debit Block Form should include

A professional form clarifies authority, scope, timing, and contact details so the receiving bank or processor can act promptly and with audit evidence.

Authorization

Clear statement that the account holder directs the bank to block specific debit entries and the legal basis or account authorization being changed.

Account Identification

Unambiguous routing and account numbers plus account type so the instruction targets the intended ledger entries.

Debit Specification

Detailed merchant identifiers, company names, or ACH company IDs and transaction descriptions to prevent overbroad restrictions.

Timing

Effective date, duration, and any required advance notice so banks can align with clearing cycles and NACHA rules.

Signatory Authority

Name, title (if business), and contact information for the person authorized to request the block.

Processing Instructions

Where to return the form, required supporting documents, and preferred communication channel for confirmation.

Essential data fields at a glance

Account name: Full legal name

Account number: Numeric account identifier

Routing number: Nine-digit ABA routing

Block scope: Specific merchant/company IDs

Effective date: MM/DD/YYYY format

Authorized signer: Name and title

How to configure an online block workflow

If you use an electronic form, configure fields and authentication so the receiving party can validate identity and retain an audit trail.

Field	Configuration
Signature Authentication	Email link with optional SMS code or 2FA per policy
Conditional Fields	Show merchant ID field when 'merchant' is selected
Auto-routing	Send completed form to bank compliance and payer
Export Format	PDF/A with embedded audit trail

Digital submission and platform requirements

Choose a platform that supports secure file formats, strong signer authentication, and an auditable completion record.

Formats supported: PDF, DOCX, and PDF/A
Integrations: CRM and document storage such as Salesforce, NetSuite, Box, Google Workspace
Security: TLS 1.2/1.3 in transit, AES-256 at rest

Where to send the completed form

Deliver the form according to the recipient's preferred channel to ensure timely processing and a clear receipt record.

Bank ACH Department: Submit via bank secure portal or compliance email address
Payee / Merchant: Send to merchant billing or collections contact
Internal Records: Store copy with treasury or accounts payable
Third-party Processor: Upload to processor portal if processor manages debits

Typical timelines and expected processing windows

Processing times vary by bank and processor; provide clear dates and allow time for clearing cycles and internal review.

Submission to action:

Banks typically process within 3–10 business days

Effective date notice:

Specify effective date at least one banking cycle ahead

Confirmation receipt:

Expect written confirmation within 5–10 business days

Dispute window:

Preserve transaction records for at least 60 days for investigations

Revocation period:

Allow bank processing time when cancelling an active block

Common preparation mistakes to avoid

Entering an incorrect routing or account number leads to failed processing and additional bank follow-up that can delay mitigation.
Using vague merchant descriptions results in overbroad blocks that interrupt authorized payments and require manual exception handling.
Omitting signer authority details or failing to include business title causes the receiving institution to request further proof of authorization.
Relying on a single informal notice to the merchant without submitting the formal block form increases the chance of continued debits.

Risks and potential consequences of errors

Continued debits: Bank cannot act without correct authorization

Account fees: Overdrafts or returned item charges

Liability disputes: Merchant may claim contract breach

Delay costs: Operational disruption for payables

Regulatory risk: Noncompliance with payments rules

Data exposure: Poor handling may raise privacy concerns

Saving, exporting, and supporting documents to include

Save completed forms with supporting evidence and export them in tamper-evident formats to preserve authenticity and create a reliable audit trail.

File formats

Export signed files as PDF or PDF/A for long-term preservation and compatibility.

Audit trail

Include an audit log showing signer email, IP, timestamps, and actions for evidentiary value.

Supporting documents

Attach bank statement excerpts, authorization letters, or merchant correspondence to substantiate the request.

Storage

Store in encrypted cloud or secure records system with access controls and retention policies.

Real-world examples of Payment Debit Block Form use

Practical examples show how organizations reduce payment risk and speed dispute resolution using standardized forms and e-signature workflows.

Martin Properties / Tim Martin

Tim Martin used an online debit block to halt unauthorized tenant ACH withdrawals during a lease dispute.

The block targeted a single merchant ID tied to the vendor.
The company processed the request electronically, retained an audit trail, and resolved the dispute without in-person signatures, improving turnaround and compliance.

Optica Ventures / Brian Fitzgibbons

Optica Ventures implemented a standardized block form to manage vendor billing errors across portfolios.

The form required merchant identifiers and an attached bank statement.
Standardization reduced follow-up, created consistent documentation for banks, and simplified reconciliation across multiple properties.

Comparing eSignature options for completing and storing the form

Platform choices affect cost, compliance, and bulk processing; comparison below lists starting prices and key capabilities with signNow first.

	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 vendor	Varies by vendor	Varies by vendor	Varies by vendor
Bulk Send	Yes (Business Premium)	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes (BAA)	Yes	Yes	No	No

Frequently asked questions about Payment Debit Block Forms

Answers to common questions about validity, electronic signatures, revocation, and what to expect after submission.

Need help? Contact support

Can I submit the form electronically?
Yes. Electronic submission is valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states if intent, consent, attribution, and retention requirements are met.
Is a notarized signature required?
Usually no for debit blocks, but some institutions or states may request notarization for corporate accounts or high-risk transactions; verify with the receiving bank.
How do I revoke a block?
Submit a signed revocation to the same recipient and note the desired effective date; banks require time to process cancellations and to update clearing instructions.
What if the bank ignores the block?
Escalate to your bank's compliance or dispute unit, retain proof of submission, and consider filing an ACH dispute under your bank's procedures.
Can I use a consumer eSign option like an email link?
Yes when consumer-facing disclosures are provided per ESIGN (15 U.S.C. §7001(c)); verify the recipient can access records and that consent to electronic delivery is recorded.
What records should I keep?
Keep the signed form, confirmation receipt, audit trail, and supporting bank statements; follow retention guidance (IRS 3 years, HIPAA 6 years) as applicable.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now