Does Authorize.net Handle Chargebacks? Credit Card vs. eCheck

Authorize.net records payment activity but its merchant service provider handles card chargebacks, while eCheck returns follow a separate, final ACH process.

I've had a client ask why Authorize.net wouldn't just refund an eCheck dispute the way a card issuer handles a chargeback. For card-side Authorize.net chargebacks, your processor handles the dispute.

Your merchant service provider handles credit card chargebacks. Authorize.net is only the gateway. eCheck (ACH) disputes work differently. Authorize.net records those, and they're final once the bank pulls the funds.

Read this once and you'll know if a dispute on your account is one you can fight.

Key takeaways

  1. 01Dispute a card chargeback through your merchant service provider, the party that decides it.
  2. 02Check the Returns Report in the Merchant Interface for eCheck activity.
  3. 03An eCheck chargeback is final once the customer's bank pulls the funds.
  4. 04Customers get 60 days under NACHA rules to dispute an ACH payment.
  5. 05Resolve a dispute within the 72-hour CDRN window and skip the $74 cost.

Want the dispute stopped before it lands? Our chargeback alerts reach you while a refund still fixes it.

Does Authorize.net handle chargebacks?

Authorize.net is a payment gateway, not a bank or processor, so it does not handle credit card chargebacks directly. Those go through your payment processor or acquiring bank instead.

eCheck (ACH) chargebacks are different. Authorize.net records them in the Returns Report, but there's no dispute-evidence process for them. Once the customer's bank pulls the funds back, the return is final.

A gateway passes transaction data between you, your processor, and the card networks.

Your processor gets the dispute, holds the money, and decides who wins.

That's why Authorize.net's support docs send merchants to their provider for chargeback records. Call gateway support about a card chargeback and you get a polite redirect.

eCheck payments are the one exception Authorize.net tracks itself. They follow NACHA's rules instead.

Credit card vs. eCheck chargebacks on Authorize.net

You can dispute a card chargeback through your processor, because card networks run an evidence stage. An eCheck chargeback is final once the bank pulls the funds.

Each payment type runs on different rules. Card networks give you a dispute process with an evidence stage, and your processor runs it for you.

NACHA governs the ACH network, and its rules end the matter when the bank returns the funds. Authorize.net's support docs put it plainly. There is "no formal process to challenge an eCheck chargeback or provide evidence to reverse it."

Your one option is calling the customer and asking them to pay again.

Here's how the two payment types compare:

DimensionCredit card chargebackeCheck (ACH) chargeback
Who handles itYour processor or acquiring bankThe customer's bank, then Authorize.net records it
Dispute process availableYes, through your processorNo
Evidence acceptedYes, matched to the reason codeNone
Final outcomeWon or lost on the evidenceFinal when the funds are pulled
Typical timeframe120 days to file, weeks to decide60 days for the customer, longer for the bank

The filing window catches most merchants off guard. Under NACHA rules, a customer gets 60 days to dispute an ACH payment. The bank can send one back for even longer.

A payment you settled two months ago can still come back.

Summary: Your processor can fight a card chargeback. The eCheck kind arrives already settled.

How do you view eCheck chargebacks in Authorize.net?

Authorize.net shows eCheck returns and chargebacks in the Returns Report inside the Merchant Interface. You can filter it by settlement date, batch date, or transaction ID.

The report mixes two things you should read differently. A standard return is a routine banking failure, like insufficient funds in the account.

An eCheck chargeback is a return the customer started, which means someone read their statement and objected.

Chargebacks are the entries to watch. That money is gone, and no dispute process exists to get it back.

Notices of Change show up in the same place and look similar at a glance. A Notice of Change is the bank fixing old account details, so there's nothing to fight. Update those details in your customer profile before the next debit.

What is Verifi's CDRN, and does it help with Authorize.net?

It helps, but CDRN runs outside Authorize.net, through your processor or an alert provider. Verifi's Cardholder Dispute Resolution Network gives you 72 hours to fix a card dispute first.

CDRN tells you about the complaint sooner. Your customer calls their bank, and the bank routes it to Verifi's CDRN network rather than the chargeback cycle.

What reaches you is a pre-dispute alert. You refund, the customer gets their money, and the bank files nothing.

Resolving one filed chargeback costs a merchant $74 on average, counting the fee and the staff time. Catch it in the window and you avoid both.

If a dispute does reach the chargeback stage, our reason code lookup shows the exact evidence the assigned code needs.

Visa owns Verifi, and CDRN covers Visa disputes with limited reach elsewhere. Merchants taking Mastercard need Ethoca, Mastercard's alert network too.

How alert-based tools catch disputes before Authorize.net

An alert service can refund a disputed charge before it becomes a chargeback on your Authorize.net account. The refund closes the case while the bank is still taking the complaint.

The card network sends the alert the moment your customer calls their bank. That's days before the bank finalizes anything.

Chargeback alerts work the same on any gateway, because the alert never passes through it.

In our dataset, Authorize.net accounts for 0.5% of alerts among merchants with a recorded processor. That's well behind Stripe and Shopify, and it tracks how many have enrolled so far.

 
Share of alerts by payment processor
 
Stripe
80.9%
 
Shopify
16.6%
 
Braintree
1.4%
 
Authorize.net
0.5%
 
Chargeback.io platform data, alerts with a recorded processor. Bars scaled to the largest share.

Ethoca and Verifi see card transactions only, so an eCheck chargeback never sets off an alert. To prevent those, fix what the customer sees before they pay:

  • Set your statement descriptor to the storefront name customers bought from, plus a support number.
  • State the charge amount and billing date at checkout, then repeat both in the confirmation email.

You can add alerts to an Authorize.net account and leave your gateway setup alone.

Our Chargeback.io Authorize.net integration matches each alert to your transaction and refunds it inside the window.

How we sourced our data

Chargeback.io's own platform data is the source of the 0.5% Authorize.net alert share. We counted dispute alerts by processor across the merchants on our platform. Each count is reported as a share of the total, anonymized and aggregated.

Those shares reflect our own merchant base, so they say nothing about Authorize.net's industry-wide volume.

FAQ

Can a merchant dispute an Authorize.net chargeback?

You can dispute a card chargeback, but you file it with your processor, not Authorize.net. Nobody can dispute the eCheck kind.

Is an Authorize.net chargeback reversible?

A card chargeback reverses if you win the dispute with your processor, and the funds come back. On the eCheck side, the debit stands.

What happens if I ignore an eCheck return notice?

The funds stay debited and the return closes on its own timeline whatever you do. Repeated returns can also put your eCheck privileges at risk.

Does Authorize.net charge a chargeback or return fee?

Authorize.net's fee schedule includes a per-item charge for eCheck returns and chargebacks. Confirm your exact rate in your merchant agreement, since it varies by reseller.

Disminuya su tasa de disputas hoy

Únase a más de 800 empresas que utilizan Chargeback para evitar las devoluciones de cargo automáticamente; la configuración lleva menos de 2 minutos.