Authorize.Net Transaction Audit
View a live copy of your Authorize.net transactions, print receipts, and export CSV reports without leaving CMS Max
Overview
If Authorize.net is your active credit card gateway, the Transactions page shows a live, always-up-to-date copy of your Authorize.net transaction history right inside CMS Max. Browse recent charges, refunds, and declines; jump straight to the matching order or form submission; print a receipt; or export a filtered list to CSV. This page reflects everything in your Authorize.net account for the selected date range — not only payments taken through this CMS.
Important: This page requires the Transaction Details API to be enabled on your Authorize.net account. If it isn't, you'll see a setup notice instead of the transaction list — see Enabling the Transaction Details API below.
Enabling the Transaction Details API
Authorize.net disables this API by default. Turn it on once per account:
- Sign in to your Authorize.Net merchant account.
- From the main menu, go to Account > Settings > Security Settings.
- Under General Security Settings, enable Transaction Details API.
- Click Submit to save. Authorize.net may ask you to confirm your identity by answering your security question before the change takes effect.
- Return to CMS Max and refresh the Transactions page — the transaction list now loads automatically.
Tip: This is a one-time setting on the Authorize.net side. It does not affect your ability to take payments — it only controls whether Authorize.net will report transaction history back to CMS Max.
Opening the Transactions Audit
- Navigate to Settings > Plugins > Payment Gateways.
- Click Transactions in the top-right corner of the page.
Note: The Transactions button only appears when Authorize.net is your selected and active credit card gateway. It's hidden for CardPointe, Stripe, or when the credit card gateway is disabled.
Using Filters and Search
| Filter | Description |
|---|---|
| Date range | From / Until date pickers. Defaults to the last 30 days. |
| Status | Filter by transaction status (e.g. Settled Successfully, Captured Pending Settlement, Declined, Voided, Refund Pending Settlement). Offers a curated list of common statuses — a transaction with a status outside that list still displays correctly, it's just not one of the filter options. |
| Search box | Matches against the Transaction ID or the last 4 digits of the card used. |
Adjust the date range and click outside the field to refresh the list — the wider the range, the longer the page may take to load since it queries Authorize.net live rather than a local copy.
Until must be on or after From; choosing the same day is allowed. If the dates are reversed, an error appears under Until and CSV export is disabled. Correct either date or click Reset to load transactions without refreshing the page.
If Authorize.net rejects the range or cannot load transactions, the filters remain available so you can choose more recent dates or use Reset. CSV export is unavailable until transactions load successfully.
Reading a Row
| Column | Description |
|---|---|
| Submitted At | When the transaction was submitted, in your site's time zone. |
| Transaction ID | Authorize.net's transaction ID. Click to copy it. |
| Type | A best-effort label (Sale, Refund, Void, Dispute). Dispute covers chargebacks, chargeback reversals, chargeback settlements, and eCheck/ACH returned items. The exact type is always shown on the receipt. |
| Status | Authorize.net's own transaction status, shown exactly as it appears on their dashboard (e.g. Settled Successfully, Captured Pending Settlement, Declined, Voided, Refund Pending Settlement). A charge that Authorize.net has captured but not yet run through its nightly settlement batch shows as Captured Pending Settlement, not Settled Successfully. |
| Amount | The transaction amount. |
| Card | Card brand and last 4 digits, when available. |
| Customer | The cardholder name on file with Authorize.net, when available. |
| Linked Record | A link to the matching CMS Max order or form submission, if one was found. |
Opening and Printing a Receipt
Click Receipt on any row to open a printable receipt in a new tab. It includes the transaction ID, exact transaction type, status, amounts, card and billing details, any line items, and a link back to the linked order or form submission.
Click Print / Save as PDF at the top of the receipt to print it or save it as a PDF using your browser's print dialog.
Exporting to CSV
Click Export CSV above the table to download the rows currently shown — respecting your date range, status filter, and search — as a CSV file you can open in Excel, Google Sheets, or Numbers.
Sandbox vs. Production
The Transactions page always reflects whichever environment is active for your Authorize.net gateway. If Sandbox Mode is turned on in your Payment Gateways settings, this page shows sandbox transactions; when Sandbox Mode is off, it shows live production transactions.
Frequently Asked Questions
Is this data live, or does it update on a schedule?
It's live. Every time you open the page, change a filter, or change the date range, CMS Max queries Authorize.net directly — there's no delay or nightly sync.
Why does a transaction's Type look approximate (Sale, Refund, Void, Dispute)?
Authorize.net's transaction list doesn't report an exact type for every row, so CMS Max shows a best-effort label based on the transaction's status. The Dispute label is a single bucket for chargebacks, chargeback reversals, chargeback settlements, and eCheck/ACH returned items — open the Receipt for that transaction to see its exact type.
Why don't all transactions have a Linked Record?
CMS Max only shows a linked order or form submission when it can match the transaction to one placed through this site. Transactions taken outside CMS Max (e.g. directly through Authorize.net's Virtual Terminal) won't have a match.
I enabled the Transaction Details API but still see the setup notice.
Refresh the page. If it persists, double check you enabled the API in the same environment (sandbox vs. production) that matches your current Sandbox Mode setting, and that your API Login ID and Transaction Key in Payment Gateways settings are correct and saved.