Parties
Identify the cardholder and merchant by full legal name, DBA if used, and contact details to avoid ambiguity during processing and dispute resolution.
A Cardholder Payment Agreement reduces ambiguity about billing, documents consent for card charges, and sets cancellation and refund rules. It helps manage disputes, supports compliance with payment and privacy rules, and provides an auditable record for reconciliation and regulatory review.
Organizations with recurring billing or regulated payments should document consent and retention practices to reduce disputes and meet network and legal requirements.
Identify the cardholder and merchant by full legal name, DBA if used, and contact details to avoid ambiguity during processing and dispute resolution.
Specify whether payments are one-time or recurring, exact amounts or a formula, billing frequency, and any trial or introductory pricing that affects charges.
Record card brand and last four digits; avoid retaining full PAN unless using a PCI-compliant tokenization method with secure processors.
State effective date, expiration or open-ended status, renewal terms, and the precise conditions under which charges may continue or stop.
Detail how a cardholder may cancel, required notice period and acceptable notice methods, and how final or prorated charges will be handled.
Explain chargeback procedures, refund eligibility and timing, required documentation, and the contact point for submitting dispute information.
| Field | Configuration |
|---|---|
| Required field enforcement and alerts | Flag missing data and prevent submission when required fields are empty. |
| Conditional visibility for card fields | Show tokenization field only if recurring payment option is selected. |
| Signature authentication and verification methods | Offer email, SMS code, or stronger KBA based on risk level. |
| Automatic receipts, logs, and audit trail | Send signed copy and capture IP, timestamp, and signer identity. |
Electronic completion requires a platform that provides secure signatures, tamper-evident audit trails, and signer authentication options matched to transaction risk.
Enter MM/DD/YYYY; determines when charges may commence.
Commonly 30 days; check specific agreement terms.
Charges typically appear within one to two billing cycles.
Retention usually counted from creation or last effective date.
Keep transactional records to support IRS inquiries for at least 3 years.
| Criteria | Card Agreement | ACH Authorization | Invoice |
|---|---|---|---|
| Involves Card | sometimes | ||
| Authorization Type | card token or imprint | bank debit authorization | billing request |
| Typical Use | recurring card billing | direct debit of bank account | one-time or billed amounts |
| Regulatory Note | pci required | nacha rules | standard accounting records |
| 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 | Varies | Trial available | Trial available |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |