Can I withdraw consent electronically?

Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and state e-signature laws, electronic withdrawals are generally enforceable if intent and attribution are clear and the record is retained.

Do I need a notary for the rejection?

Usually not for standard merchant disputes. Notarization may be useful for corporate delegations or when a third party requests a notarized affidavit; check state notary rules if adding an acknowledgement.

Will the issuer require proof?

Issuers often request supporting documents such as receipts, cancellation emails, or screenshots. Providing clear evidence with your rejection increases the chance of a favorable, faster outcome.

How do I protect card data when submitting evidence?

Redact full card numbers and include only the last four digits. Use secure attachments and platforms that use TLS and AES-256 storage to reduce PCI and privacy risk.

What if the merchant ignores the rejection?

File a dispute with the issuing bank and preserve all communications. Banks follow card network rules and may initiate a chargeback if the evidence supports your claim.

Can an electronic signature satisfy legal requirements?

Yes. eSignatures meet ESIGN and UETA criteria when the signature shows intent, consent, attribution, and record retention. For consumer-facing records, ensure any required ESIGN consumer disclosures are provided.

Electronic Signature
Templates
Legal
Legal Rejection of Credit Card Authorization

Legal Rejection of Credit Card Authorization

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

LEGAL REJECTION OF CREDIT CARD AUTHORIZATION

This Legal Rejection of Credit Card Authorization (the "Rejection") is made effective as of by and between Merchant Name: and Requesting Party Name: .

RECITALS

WHEREAS, Requesting Party submitted a request for credit card authorization identified by Authorization Reference Number: relating to a proposed Transaction in the amount of $ on Cardholder: (Card Last Four: ) dated .

WHEREAS, Merchant has reviewed the requested authorization and determined that the request, or the circumstances surrounding it, do not meet Merchant's payment acceptance policies or applicable network rules; and

WHEREAS, the parties desire to document the formal rejection of the requested credit card authorization and to allocate responsibilities and liabilities arising from such rejection.

NOW, THEREFORE, in consideration of the mutual covenants and promises contained herein, the parties agree as follows:

1. DEFINITIONS

For purposes of this Rejection, the following capitalized terms shall have the meanings set forth below:

"Authorization" means any approval, hold, or reservation of funds requested from a card issuer or payment network to effect a proposed Transaction.

"Rejection Notice" means this written statement by Merchant expressly refusing to honor or proceed with the requested Authorization described above.

2. REJECTION OF AUTHORIZATION

Merchant hereby issues the Rejection Notice with respect to the Authorization described in the Recitals. Effective upon Merchant's delivery of this Rejection Notice to Requesting Party in accordance with Section 9 (Notices), Merchant shall not capture, settle, or submit any charge to the cardholder's account related to the referenced Authorization, and no funds shall be deemed accepted by Merchant on account of the referenced Transaction.

3. REASONS FOR REJECTION

Merchant has rejected the Authorization for one or more of the following reasons (check all that apply):

Insufficient or expired authorization from issuer Suspected fraud, theft, or unauthorized use Mismatch between cardholder data and transaction information Transaction involves prohibited goods or services Cardholder dispute or earlier chargeback pending Other (specify below)

If Other, explain:

4. EFFECT ON FUNDS, HOLDS, AND OBLIGATIONS

Upon issuance of this Rejection Notice, Merchant will not initiate settlement of the referenced Transaction. If a pre-authorization hold exists on the cardholder's account as a result of the attempted Authorization, Merchant will, where practicable, release the hold in accordance with card network rules and applicable law. Neither party shall attempt to re-submit the same Authorization unless a new written authorization is obtained and delivered to Merchant.

5. REPRESENTATIONS AND WARRANTIES

Each party represents and warrants to the other that: (a) it has full corporate or organizational power and authority to enter into and perform its obligations under this Rejection; (b) execution and delivery of this Rejection has been duly authorized by all necessary action; and (c) this Rejection constitutes a valid and binding obligation enforceable in accordance with its terms.

6. INDEMNIFICATION

Requesting Party shall indemnify, defend and hold harmless Merchant and its affiliates, officers, employees, agents and service providers from and against any and all losses, liabilities, damages, fines, penalties, costs and expenses (including reasonable attorneys' fees) arising out of or relating to Requesting Party's submission of the Authorization, any attempted capture in violation of this Rejection, or any misrepresentation in the information provided in connection with the Authorization.

7. LIMITATION OF LIABILITY

EXCEPT FOR LIABILITY ARISING FROM A PARTY'S WILLFUL MISCONDUCT OR BREACH OF THE CONFIDENTIALITY OR INDEMNITY PROVISIONS HEREOF, NEITHER PARTY SHALL BE LIABLE TO THE OTHER FOR INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR SPECIAL DAMAGES, INCLUDING LOSS OF PROFITS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

8. CONFIDENTIALITY

Each party shall treat the terms of this Rejection and any non-public information obtained in connection with the Authorization as confidential and shall not disclose such information except as required by law, regulation, or a binding order of a court or regulatory authority.

9. NOTICES

All notices required or permitted under this Rejection shall be in writing and delivered to the addresses set forth below by certified mail, overnight courier, or hand delivery. Notices shall be effective upon receipt.

Merchant Notice Address Requesting Party Notice Address

10. AMENDMENT; WAIVER; COUNTERPARTS

This Rejection may be amended only by a written instrument executed by both parties. No waiver of any provision shall be effective unless in writing and signed by the party waiving compliance. This Rejection may be executed in counterparts, each of which shall be an original and all of which together shall constitute one instrument.

11. GOVERNING LAW; SEVERABILITY; ENTIRE AGREEMENT

This Rejection shall be governed by and construed in accordance with the laws of the jurisdiction specified below without regard to its conflicts of law principles.

Governing Law Jurisdiction

If any provision of this Rejection is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect. This Rejection constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements and understandings.

12. MISCELLANEOUS

The parties agree to cooperate in good faith to effectuate the terms of this Rejection, including providing reasonable documentation or communications to card issuers or payment processors as may be necessary to confirm release of any authorization hold or to prevent improper captures or settlements.

Merchant Name:

By:

Date:

Requesting Party Name:

By:

Date:

What a Legal Rejection of Credit Card Authorization Is

A Legal Rejection of Credit Card Authorization is a written notice by which a payer or cardholder formally refuses or withdraws consent for a previously granted card-payment authorization. The document records the reason for rejection, identifies the original authorization, and instructs the merchant, processor, or financial institution to stop processing charges and to return or refund funds as applicable. It can be used in consumer disputes, merchant billing errors, or internal billing corrections and is often retained as evidence in chargeback or regulatory proceedings.

Why this document matters and how it holds up legally

Providing a clear, dated rejection creates an audit trail and helps establish intent, attribution, and retention—the four ESIGN test elements for enforceable electronic records. A documented rejection clarifies obligations for card issuers and merchants, reduces dispute timing, and supports remedies such as refunds, chargeback defenses, or account corrections under card network rules and consumer-protection laws.

Who commonly prepares and receives this rejection

Organizations and individuals use a rejection notice to stop unauthorized or disputed credit-card charges and to document a formal refusal of prior consent.

Consumers disputing unauthorized or erroneous charges with merchant and issuer
Billing or accounts payable teams reversing company card charges or stopping recurring payments
Legal or compliance teams preserving evidence for regulatory reviews or litigation

The recipient list typically includes the merchant, payment processor, issuing bank, and any internal accounts receivable or billing contacts to ensure coordinated handling.

Who can sign and act on the rejection

Billing Manager

A billing manager or accounts payable officer signs when a company cardholder revokes approval for a vendor charge. Their signature should include title and corporate authority; attach a company letterhead and internal authorization to validate corporate signatory power.

Cardholder

An individual cardholder signs to reject charges on a personal card. The notice should include the cardholder's full name, last four digits of the card, contact information, and a clear statement withdrawing consent to the listed authorization.

Essential elements to include in a professional rejection letter

A complete rejection closely links the refusal to the original authorization, provides precise dates and amounts, and supplies contact details and preferred remedies. Include supporting evidence and signature blocks to reduce processing friction.

Document header

Clear title, date, and recipient details so the notice is immediately identifiable in an issuer or merchant workflow and searchable in records.

Authorization reference

Reference the original authorization ID, invoice number, date, and charge amount so processors can match the rejection to the specific transaction.

Reason for rejection

Concise explanation: unauthorized charge, billing error, duplicate billing, canceled order, or revoked recurring authorization with factual support.

Requested remedy

Specify refund, reversal, stop future charges, or confirmation of cancellation; be explicit about full or partial refund expectations.

Supporting attachments

Attach receipts, order confirmations, cancellation emails, or screenshots that substantiate the claim and speed dispute resolution.

Signature block

Full printed name, signature, title (if corporate), contact info, and date; note whether signature is electronic and include audit-trail reference if available.

Required identifying details

Cardholder name: Full legal name

Card details: Last four digits

Authorization ID: Transaction or auth code

Charge amount: Exact dollar amount

Transaction date: MM/DD/YYYY

Contact info: Phone and email

Step-by-step process to prepare and send a rejection

Follow these sequential actions to ensure the rejection is complete, routed correctly, and retained for potential disputes.

01

Identify transaction: Locate invoice and authorization details.
02

Draft notice: State facts, date, and remedy requested.
03

Attach evidence: Include receipts or cancellation emails.
04

Send and confirm: Email or submit to merchant and issuer with delivery record.

How to set up an online rejection workflow

Configure fields, recipients, and authentication to minimize friction and ensure compliance with card network and regulatory requirements.

Field	Configuration
Authorization ID field	Required, one-line text
Attachment field	Optional, allow PDF/JPG
Recipient routing	Merchant + issuer + AR
Authentication	Email link or SMS code

Where to send or file the rejection

Choose delivery channels that produce an auditable record and meet card network expectations; include both the merchant and card issuer where appropriate.

Merchant: Primary recipient for refund requests.
Payment processor: For routing reversals or network credits.
Issuing bank: File for chargeback initiation if unresolved.
Internal records: Store in billing and legal folders.

Digital signing and eSubmission essentials

Use platforms that provide an audit trail, secure transmission, and the ability to attach evidence when submitting a rejection.

Audit trail: Timestamp, IP, and signer identity
Encryption: TLS in transit; AES-256 at rest
Authentication: Email link or SMS code

Time-sensitive dates and processing expectations

Several deadlines affect dispute rights and chargeback windows; act promptly and document all communications to preserve remedies.

Immediate action recommended:

Send rejection as soon as error is discovered to meet network timeframes.

Chargeback windows:

Typically 60–120 days depending on network rules.

Issuer response time:

Expect 7–45 business days for initial acknowledgment.

Refund processing:

Merchant refunds can take 3–10 business days to post.

Record retention:

Keep supporting records for relevant statutory periods.

Common mistakes that delay rejection handling

Missing authorization identifiers that prevent processors from matching the rejection to the correct transaction.
Including full card numbers in email or attachment, which increases PCI exposure and may be redacted by recipients.
Vague reason descriptions like 'I changed my mind' that trigger merchant follow-up instead of immediate reversal.
Failing to send the rejection to both merchant and issuer, which can create duplicate workflows and longer resolution times.

Risks and potential consequences of incorrect or late rejections

Chargeback denial: Late or insufficient evidence

Backup withholding: Tax consequences if TIN issues exist

Regulatory fines: PCI or consumer protection risk

Contract breach: Vendor dispute over terms

Reputational harm: Customer or partner dissatisfaction

Legal costs: Attorney fees for contested disputes

eSignature vendor pricing and compliance comparison

Comparing common vendor plans and compliance features can help decide which eSignature provider meets authentication, audit trail, and HIPAA needs for submitting rejections.

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

Real-world examples of how organizations use a rejection notice

Two concise client stories show how documented rejections solve billing disputes and speed refunds in practice.

Optica Ventures LLC

A billing error triggered duplicate charges after a subscription renewal

The accounts payable team sent a signed rejection with screenshots
The merchant reversed the duplicate charge and provided a written confirmation, shortening resolution from weeks to days and preserving vendor relationship.

Fertility Centers of Illinois

A patient revoked recurring authorization after treatment changes

The patient sent a dated rejection with appointment proof
The provider processed a refund and updated billing records; the center noted the rejection in the patient account for future audits.

Frequently asked questions about rejections and disputes

Answers to typical legal and operational questions about preparing and submitting a credit card authorization rejection.

Need help? Contact support

Can I withdraw consent electronically?
Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and state e-signature laws, electronic withdrawals are generally enforceable if intent and attribution are clear and the record is retained.
Do I need a notary for the rejection?
Usually not for standard merchant disputes. Notarization may be useful for corporate delegations or when a third party requests a notarized affidavit; check state notary rules if adding an acknowledgement.
Will the issuer require proof?
Issuers often request supporting documents such as receipts, cancellation emails, or screenshots. Providing clear evidence with your rejection increases the chance of a favorable, faster outcome.
How do I protect card data when submitting evidence?
Redact full card numbers and include only the last four digits. Use secure attachments and platforms that use TLS and AES-256 storage to reduce PCI and privacy risk.
What if the merchant ignores the rejection?
File a dispute with the issuing bank and preserve all communications. Banks follow card network rules and may initiate a chargeback if the evidence supports your claim.
Can an electronic signature satisfy legal requirements?
Yes. eSignatures meet ESIGN and UETA criteria when the signature shows intent, consent, attribution, and record retention. For consumer-facing records, ensure any required ESIGN consumer disclosures are provided.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now