Authorize.net, Jul 27, 2026
What you'll learn
Authorize.net is your payment gateway. It connects your checkout to the card networks and processes your transactions. But Authorize.net has no role in the chargeback dispute process and provides no portal, notification system, or response mechanism for disputes.
When a cardholder disputes a transaction, the chargeback is handled entirely by your acquiring bank (also called your merchant bank or processor). This is the financial institution that holds your merchant account and settles funds into your business checking account. Depending on your setup, this may be Wells Fargo Merchant Services, Elavon, TSYS, Worldpay, or another processor.
Authorize.net sits in front of that relationship as the technology layer. When a dispute is filed, the card network (Visa or Mastercard) communicates directly with your acquiring bank, not with Authorize.net.
HOW TO IDENTIFY YOUR ACQUIRING BANK Look at the chargeback notification you received. The sender will be your acquiring bank, not Authorize.net. Your monthly processing statement also lists your acquirer name, Merchant ID (MID), and their dispute contact information.
This distinction matters because every response you submit goes to your acquiring bank. They then forward it on your behalf to Visa or Mastercard through their dispute systems. You never submit directly to the card networks, and any communication sent to Authorize.net will have no effect on your dispute.
Here is the chain of parties involved in every Visa and Mastercard dispute:
| Step | What happens |
|---|---|
| 1 | The cardholder disputes the charge with their issuing bank The cardholder contacts their bank (Chase, Bank of America, etc.) and claims the transaction was unauthorized, fraudulent, or that goods or services were not delivered as promised. |
| 2 | The issuer files a chargeback against your acquiring bank The cardholder's bank reverses the charge. The funds are debited from your merchant account and a chargeback fee (typically $20 to $100) is assessed. |
| 3 | Your acquiring bank notifies you You receive a chargeback notification by email or through your acquiring bank's portal. This notice contains your MID, the Acquirer Reference Number (ARN), the reason code, the transaction amount, and your response deadline. |
| 4 | You submit your response to your acquiring bank This is called representment. You submit a rebuttal letter plus supporting evidence to your acquiring bank, through their portal or dispute email address. They forward it to the card network on your behalf. |
| 5 | The issuer reviews and issues a final decision The cardholder's bank reviews your response. If it is compliant and compelling, they reverse the chargeback and the funds are returned. If not, the chargeback stands. |
Your chargeback notification letter will include a specific response deadline. This is the date your acquiring bank must receive your response in order to submit it to the card network on time.
Respond Before Your Stated Deadline: Not a Day Later Your acquiring bank has its own internal cutoff to compile and submit all responses to the card network. If you miss the deadline on your notification letter, they cannot forward your response regardless of how strong it is. The chargeback becomes final and the funds are lost. Check your notification letter immediately and mark the deadline. Do not assume you have more time than it states.
Every chargeback response requires two components: a rebuttal letter and supporting evidence documents. Submitting evidence alone, without a letter explaining it, is one of the most common reasons merchants lose winnable disputes.
Your rebuttal letter must include the following so the issuer can match it to the correct dispute file:
Letter header checklist
Missing any of these can cause your response to be rejected without review. All of them appear on your chargeback notification letter.
The right evidence depends on the reason code on your notification. Below are the most common dispute types Authorize.net merchants face, with evidence rated by effectiveness:
| Dispute type | Evidence and strength |
|---|---|
| Fraud / Unauthorized(Visa 10.4) | STRONG: 3D Secure / Verified by Visa authentication data: the most powerful defense STRONG: CE 3.0 enrollment confirmation if applicable (Compelling Evidence 3.0) MODERATE: AVS and CVV match confirmation (reduces liability but does not on its own overturn a fraud claim) MODERATE: IP address geolocation consistent with cardholder's billing address MODERATE: Device fingerprint or prior transaction history on same device/card |
| Cancelled Recurring(Visa 13.2) | STRONG: IP-timestamped record of cardholder agreeing to recurring billing terms at signup STRONG: History of prior undisputed recurring charges on the same card MODERATE: Pre-billing notification sent to cardholder before the disputed charge MODERATE: No cancellation request found in CRM or support logs HARMFUL: Any customer service record showing a cancellation was requested and not honored |
| Item Not Received(Visa 13.1) | STRONG: Carrier tracking confirmation showing delivery to cardholder's billing address STRONG: Digital delivery logs: download records, login timestamps, or usage data from cardholder's IP or device MODERATE: Customer communication acknowledging receipt of the goods or service MODERATE: Confirmed delivery date was within the expected window stated at checkout HARMFUL: Delivery to an address different from the cardholder's billing address without documented authorization |
| Not as Described(Visa 13.3) | STRONG: Screenshots of product listing, description, or service agreement that match what was delivered STRONG: Communications from the cardholder acknowledging they received the item MODERATE: Photos or inspection records documenting item condition at the time of shipment WEAK: Return or refund policy alone: this code supersedes your return policy by Visa rule |
| Mistake | |
|---|---|
| ✕ | Submitting to the wrong party Sending your response to Authorize.net, Visa, or Mastercard directly. The correct recipient is your acquiring bank, every time. |
| ✕ | Missing required identifiers Submitting a letter without the MID, ARN, or case number. Issuers use these to match your response to the correct dispute file. No match means no review. |
| ✕ | Generic evidence without narrative Attaching documents without explaining in the letter what each one shows and how it directly disproves the cardholder's claim. Evidence without context rarely wins. |
| ✕ | Missing your stated deadline Waiting until the last minute and discovering your acquirer's cutoff has already passed. Treat the deadline on your notification letter as a hard stop and respond well before it. |
The rebuttal letter is where most merchants lose ground. Issuers review a high volume of responses. A structured, code-specific letter that directly addresses the dispute will always outperform a general narrative.
Your letter needs to accomplish three things:
State your position clearly in the opening paragraph. Don't bury the lead. Open with a direct factual assertion: "The transaction on [date] for [amount] was authorized by the cardholder and the goods/services were delivered as agreed."
Reference each piece of evidence explicitly. Name every attachment and explain what it demonstrates. "Exhibit A is a screenshot of our checkout flow confirming the cardholder accepted recurring billing terms on [date] from IP address [X]."
Close with a clear request. Ask the issuer to reverse the chargeback and confirm you have submitted all required information within the response deadline.
TONE MATTERS Keep the letter factual and professional. Expressing frustration with the cardholder, using emotional language, or making accusations works against you. Issuers are evaluating evidence and procedural compliance, not your side of the story as a narrative.
Writing a compliant representment letter from scratch, one that includes all required identifiers, uses the correct structure for your specific reason code, avoids common rejection triggers, and references your evidence precisely, typically takes one to three hours for a merchant doing it for the first time.
FightMyChargeback builds that letter for you in under five minutes. You enter your transaction details, select your reason code, describe what happened, and upload your evidence. You receive a professionally drafted, issuer-ready response letter by email. You then submit it to your acquiring bank with your evidence attached.
No integration with Authorize.net or your acquiring bank required. No contract, no onboarding call, no monthly fee. Just the letter.
Generate your response letter at FightMyChargeback.com. $15 flat.
Start your response
Canyon Payments provides payment infrastructure advisory and products for Authorize.net and NMI merchants. FightMyChargeback is a document drafting tool and does not constitute legal advice.