> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Authorize.net on Vortex IQ > Monitor Authorize.net payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow. Monitor Authorize.net payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=authorize-net) performance signals automated checks prepared fixes proven workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Find failures, leaks and risks before they cost sales. Monitor orders, fulfilment, delivery and settlement. Improve discovery, conversion, campaigns and repeat purchase. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. ### Monitor performance 18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | ----------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- | | **3DS Abandonment Rate** | Watch only | Customers who saw the Cardinal 3DS challenge and bailed (expired session). UX friction, not issuer rejection. | | **Captured vs Commerce Revenue** | Merchant rule | Reconciliation gap between gateway-captured dollars and commerce order revenue. >2% drift = double-count, refund-timing or routing leak. | | **Chargeback Rate** | Watch only | Buyer-initiated reversals / settled. >0.9% triggers Visa AMP / Mastercard ECM monitoring; >1% risks account termination. | | **Decline Rate** | Alert band 5 / 8 | Declined + voided + FDS-rejected over all attempts. 3DS-failed counts here; 3DS-abandoned does not. | | **Decline Spike vs Checkout Funnel Drop** | Merchant rule | When Authorize.Net declines spike, does commerce checkout completion drop? If yes, declines are causing real revenue loss. | | **Dispute Rate** | Watch only | Transactions in active dispute (pending + recently resolved). The leading indicator that pairs with chargeback rate. | | **Refund Rate** | Alert band 3 / 8 | Refund value / settled revenue. Merchant-initiated returns view, separate from chargebacks. | | **Refund Volume** | Merchant rule | Absolute dollars refunded (full + partial). Subtract from gross volume for a net-of-refunds figure. | | **Top Decline Reasons** | Watch only | responseReasonCode breakdown (2 DO\_NOT\_HONOR, 65 exceeds limit, 27 AVS mismatch, 200 3DS failed…). First card to open on a spike. | | **Total Transactions** | Alert band 0 / -15 | Count of settled authCapture / captureOnly transactions. Refunds, voids, declines and FDS-held excluded. | | **Total Volume** | Alert band 0 / -15 | Gross settled dollars through the gateway (pre-refund, pre-fees, pre-chargeback). Gateway-level, not bank-funded. | | Signal | Alert behaviour | What it tracks | | -------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------- | | **Avg Settlement Time (days)** | Watch only | Average days from capture to acquirer-funded bank deposit. Acquirer-driven (T+1/T+2 cards, T+3/T+5 ACH), not gateway-driven. | | **Oldest Pending Payout (days)** | Alert band 2 / 5 | Days since the oldest unfunded capture. Anything past the 5-day acquirer window is stuck money - investigate. | | **Pending Payouts** | Watch only | Captured-but-not-yet-acquirer-funded balance. The in-flight money: customer paid, acquirer hasn't disbursed yet. | | **Success Rate** | Alert band 95 / 90 | Settled / all-attempts. The best single gauge of auth quality, BIN routing and FDS-rule sanity. | | **Volume Trend** | Alert band 0 / -15 | Daily settled volume by settlement date. Shows batch-cut-off rhythm, B2B weekday pulse and EOM surges. | | Signal | Alert behaviour | What it tracks | | ----------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------- | | **Average Transaction** | Merchant rule | SUM(settleAmount) / COUNT(settled). Mostly mix-shift, not basket growth - open the channel split first. | | **Top Payment Methods** | Watch only | Visa / MC / Amex / Discover / Diners / JCB / eCheck split by count and volume. Where interchange-optimisation gains hide. | ### Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail. **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation 1% is the threshold Visa and Mastercard use to flag a merchant as excessive, and crossing it puts the account at risk of monitoring programs, extra fees, and in sustained cases, the ability to accept those card networks at all, on top of losing the disputed sales themselves. A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided. Reference: `PAYMENT-DISPUTE-001` **Severity** high · **Outcome** Protect revenue · **Fix status** Report only More than 8% of payment attempts are being declined. Every decline is a customer who was ready to pay and did not complete the sale, so this is lost revenue at the very last step of the funnel, after every earlier marketing and conversion cost has already been paid. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `PAYMENT-DECLINE-001` **Severity** high · **Outcome** Protect revenue · **Fix status** Report only Refunds jumped more than 50% above the recent weekly average. A spike this fast and this size usually has one specific, recent cause worth finding quickly, before it settles into an ongoing pattern that is harder to trace back to its origin. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `PAYMENT-REFUND-001` **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation A payout is running more than 5 days behind this gateway's usual schedule. That is revenue already earned that has not reached the store's bank account, which affects cash flow directly regardless of how sales themselves are performing. A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided. Reference: `PAYMENT-PAYOUT-001` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change. ### Automate approved work Vortex IQ is integrated with **0 read** and **6 write** operations across report :authenticatetestrequests, report :getsettledbatchlistrequests, report :gettransactiondetailsrequests, report :gettransactionlistforbatchs, report :getunsettledtransactionlistrequests, xmlrequestapis on Authorize.net. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=authorize-net) #### Ready to build your first Authorize.net workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. | Resource | Read operations | Write operations | | ------------------------------------------- | --------------- | ---------------- | | report :authenticatetestrequests | 0 | 1 | | report :getsettledbatchlistrequests | 0 | 1 | | report :gettransactiondetailsrequests | 0 | 1 | | report :gettransactionlistforbatchs | 0 | 1 | | report :getunsettledtransactionlistrequests | 0 | 1 | | xmlrequestapis | 0 | 1 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.