What NoChargeback reads from Authorize.net
Through the Transaction Details API, NoChargeback reads the data issuers ask for in most disputes.
-
AVS and CVV response codes from the authorization.
-
The customer IP address, customer ID and email recorded with the transaction.
-
Billing and shipping address, invoice number and line items.
-
Settlement data, batch and status, plus refunds or voids already processed on the same card.
-
Earlier transactions from the same customer, useful for Compelling Evidence 3.0 style arguments on fraud disputes.
Permissions and credentials we ask for
You connect Authorize.net with an API login ID and transaction key used only for read calls to transaction details. NoChargeback never runs charges, refunds, captures, voids or payouts, and it does not create or change subscriptions in your account. If you prefer, generate a new transaction key for NoChargeback and rotate it whenever you want. Credentials are encrypted at rest, as described on the security page.
Which dispute data we ingest and which evidence we fill
The dispute itself arrives from your processor, so you add it to NoChargeback in one of two ways. Upload the dispute notice PDF and we read the case number, reason code, amount and due date from it, or enter those fields by hand. NoChargeback then matches the case to the Authorize.net transaction and fills the pack.
-
An evidence PDF with the transaction summary, AVS and CVV results, IP and location match and delivery or usage proof you attach.
-
A drafted rebuttal letter written for the reason code, for example Visa reason code 13.1 or Mastercard reason code 4837.
-
Copy ready fields for the processor's dispute portal, such as the reason summary, transaction facts and list of attached documents.
-
Your terms and refund policy and customer communication, attached in the order issuers expect.
-
1
Step 1 Get your API login ID and transaction key
In the Authorize.net Merchant Interface, open the API credentials and keys page and copy the API login ID. Create a transaction key for NoChargeback.
-
2
Step 2 Connect Authorize.net in NoChargeback
Open Integrations in your workspace, choose Authorize.net and paste both values. We run a read call against transaction details to confirm access.
-
3
Step 3 Add your first dispute notice
Upload the dispute notice from your processor or type its fields. NoChargeback finds the matching transaction and starts the countdown.
-
4
Step 4 Upload the pack in your processor's portal
Download the evidence PDF and copy the ready fields into the dispute portal of your acquiring processor, then mark the case as submitted.
Deadline countdown and submission
The due date comes from the dispute notice, and every case shows a countdown to it with reminders by email or Slack. Because evidence for Authorize.net transactions goes through your processor, the final upload happens in the processor's portal. NoChargeback has the pack complete well before the deadline, by default 48 hours ahead of the due date on Scale and Enterprise, and flags any case still not marked as submitted. Read more about chargeback alerts.