B2B agreements
How to use CCD entries and signed consent for B2B payments—and why it dramatically reduces your dispute exposure.
When you process ACH payments from business customers, how you obtain authorization matters. Using signed consent instead of internet consent provides a major advantage: the unauthorized return window drops from 60 days to just 2 business days.
With signed consent, business customers can only dispute unauthorized transactions within 2 business days of settlement—compared to 60 calendar days when using internet consent. This dramatically reduces your chargeback exposure for B2B payments.
Internet vs. Signed Consent for B2B
Even when your customer is a business, using internet consent gives them the same 60-day dispute window as consumers. To take advantage of the shorter 2-day window, you must:
- Use
consent_type: "signed"in your API request - Have a signed agreement on file before initiating the payment
- Ensure the agreement binds the business to Nacha Operating Rules
Using Signed Consent
When you create a charge with consent_type: "signed" for a business customer, Straddle applies the appropriate entry class that qualifies for the 2-day dispute window.
B2B Invoice Payment
Your customer signed an ACH authorization as part of their vendor agreement. You're now initiating payment based on that signed contract.
{
"consent_type": "signed",
"device": {
"ip_address": "0.0.0.0"
}
}
Use 0.0.0.0 for the IP address when the signed agreement was obtained offline (paper contract, DocuSign, etc.).
Authorization Requirements
Unlike internet-initiated transactions, Nacha doesn't prescribe a specific authorization format for signed B2B agreements. Instead, Nacha requires that you and your business customer have a trading partner agreement that:
- Binds both parties to Nacha Operating Rules
- Contains authorization requirements and procedures
- Is negotiated between the parties
This flexibility exists because B2B relationships vary widely—from simple vendor payments to complex supply chain arrangements.
Follow the same best practices as consumer authorizations (clear consent language, revocation instructions, record retention), but also include specific language binding both parties to Nacha Operating Rules.
Required Agreement Language
Your B2B agreement should include language similar to the following:
This language can be included in:
- A standalone ACH authorization form
- Your master services agreement
- A payment terms addendum
- An invoice payment agreement
Sample Authorization Template
ACH DEBIT AUTHORIZATION - BUSINESS ACCOUNT
Company Name: _______________________________
Authorized Signer: ___________________________
Title: ______________________________________
Bank Account Information:
Bank Name: __________________________________
Routing Number: _____________________________
Account Number: _____________________________
I authorize [YOUR COMPANY NAME] to initiate ACH debit entries
to the business bank account listed above. This authorization
will remain in effect until I provide written notice of
termination.
Both parties agree to be bound by Nacha Operating Rules as
they pertain to all ACH transactions initiated by
[YOUR COMPANY NAME] that credit or debit the above-listed
bank account and acknowledge that the origination of ACH
transactions to the listed account must comply with
provisions of U.S. law.
To revoke this authorization, contact [YOUR COMPANY] at:
Email: ______________________________________
Phone: ______________________________________
Notice must be received at least 3 business days before the
scheduled debit date.
Signature: __________________________________
Date: _______________________________________
Record Retention
Retain your signed CCD authorization for 2 years after the final transaction or 2 years after termination of the agreement, whichever is later.
| Record | Retention period |
|---|---|
| Signed authorization agreement | 2 years after final transaction |
| Proof of each transaction | 2 years after transaction date |
| Revocation requests | 2 years after revocation |