How to File a Complaint with Authorize.net

Authorize.net complaints need a clear role first. A merchant complaint about gateway access, transaction errors, refunds, chargebacks, eCheck funding, or risk holds belongs in the Merchant Interface and Authorize.net Support Center. A consumer who bought from a merchant that uses Authorize.net usually needs the merchant and the card issuer, because Authorize.net is generally the payment gateway behind the transaction rather than the seller.

Authorize.net's current support pages list 24x7 merchant support by phone, chat, and support case, closed on major holidays. The public technical support page lists merchant support at 877-447-3938 in the U.S., +44 (0) 203 564 4844 for the UK/Europe, and +61 1800 019 932 for Australia. Partner support is separate and uses 888-437-0481 in the U.S.

Best Authorize.net Complaint Paths

For business-critical payment issues, call and open a support case. Phone support can triage urgency; the case creates a written record for follow-up.

Step-by-Step: How to File an Authorize.net Complaint

What to Have Ready Before Contacting Support

If the complaint involves a live outage or checkout failure, capture timestamps, endpoint, response code, request ID if available, and whether the issue affects all transactions or only one card type/payment method.

Refunds, Voids, and Customer Disputes

Authorize.net's transaction help says merchants can refund from the Transaction Detail page. The refund button is available until the original transaction is fully refunded or the transaction is more than 180 days old. Authorize.net also describes Expanded Credit Capabilities for refunds beyond the standard 180-day window, subject to approval.

Use the right term:

Authorize.net's own chargeback guidance explains the difference between a refund and a chargeback: a refund is initiated by the customer with the merchant, while a chargeback is started by the customer with the card issuer. If you are a consumer cardholder, the merchant and your issuer are usually the right path; Authorize.net may not be able to change a merchant's return or delivery decision for you.

eCheck, Funding, Holds, and Reserves

eCheck complaints need special handling because they involve ACH timing, returns, chargebacks, and funding reports. Authorize.net support articles describe eCheck reports, returns, and chargebacks in the Merchant Interface, and note that eCheck chargeback timing can vary by bank and transaction type. A support article also says customers generally have up to 60 days to dispute an ACH transaction.

For eCheck or funding complaints, ask:

• Which batch or settlement sub-account is affected?
• Is the item a return, chargeback, refund, billing charge, or risk reserve?
• Which bank, processor, MSP, or reseller controls the funding decision?
• What is the expected release date or review date?
• What transaction-level evidence is needed?
• Is any chargeback/refund window still open?

Authorize.net support content describes settlement and reserve sub-accounts, including risk withholdings and transfers after the appropriate hold period. If funds are held, ask for the contract section, hold reason, affected transaction list, expected review date, and whether the issue is controlled by Authorize.net or by your merchant service provider/acquiring bank.

Merchant, Reseller, and Consumer Boundaries

Authorize.net may provide the gateway while another party provides the merchant account, underwriting, acquiring bank relationship, or reseller support. This matters for complaints.

Do not assume Authorize.net can release funds or reverse a charge if a processor, acquirer, merchant, or card issuer owns that decision.

When to Escalate Beyond Authorize.net

For merchant-account disputes, the contract, reseller, and acquiring bank matter. For consumer purchase disputes, the merchant and card issuer matter. Escalating to the wrong party can delay the resolution.

What to Say in an Authorize.net Complaint

Use this script:

"I need Authorize.net to review a complaint for Merchant ID [ID] / account [business name]. The issue is [gateway access, transaction error, refund, eCheck funding, chargeback, risk hold, reserve, billing fee, reseller issue, or consumer purchase issue]. The relevant record is [transaction ID, batch ID, settlement date, invoice, amount, customer email, response code, or support case]. I have attached [logs, screenshots, transaction details, chargeback notice, billing statement, customer communication, and prior support messages]. I am requesting [refund status, transaction diagnosis, settlement explanation, reserve/hold basis, billing correction, responsible-party confirmation, or written next step]. Please confirm the case number and decision in writing."

Useful follow-up questions:

• "Does Authorize.net or my merchant service provider control this decision?"
• "Is this a gateway issue, merchant account issue, eCheck issue, or card-network dispute?"
• "What transaction IDs or batch IDs are affected?"
• "Is the refund blocked by the 180-day limit?"
• "Is this item a return, chargeback, risk reserve, billing fee, or settlement hold?"
• "What deadline applies to my chargeback response?"
• "Can you identify the reseller, MSP, or acquiring bank I should contact?"
• "Can you confirm the support case number in writing?"

Let Pine AI Help File the Complaint

Frequently Asked Questions

Sources Checked

• Authorize.net Support Center
• Authorize.net technical support
• Authorize.net contact support article
• Authorize.net plans and pricing
• Authorize.net refund a transaction
• Authorize.net refund transaction through CIM
• Authorize.net eCheck reports and statements
• Authorize.net eCheck chargebacks article
• Authorize.net glossary
• Authorize.net chargeback vs refund guidance
• CFPB Submit a complaint