Square on Vortex IQ

Monitor Square payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Square payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Connect or manage this source · How connecting works · Create a workflow

17

performance signals

4

automated checks

0

prepared fixes

0

proven workflows

8

API operations

Overview

What you can achieve

Capabilities are grouped around merchant outcomes, not API terminology.

Protect revenue

Find failures, leaks and risks before they cost sales.

Run operations

Monitor orders, fulfilment, delivery and settlement.

Grow revenue

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.

1. Connect

   Authorise the source. Scopes are shown before access is granted.

2. Monitor

   Watch the signals against your own baselines, not universal defaults.

3. Detect

   Run checks and gather evidence specific to your store.

4. Recommend

   Explain what happened, why it matters and the proposed action.

5. Approve

   You review scope, risk and reversibility before anything changes.

6. Execute

   Apply through governed connector operations.

7. Verify

   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 (17)

Monitor performance

17 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

Protect revenue (10 signals)

Signal	Alert behaviour	What it tracks
3DS Abandonment Rate	Watch only	Square Online checkouts that hit a 3DS-2 challenge and the customer abandoned (CANCELED with 3DS error). Online-only; POS uses chip + PIN, no 3DS. Dif
Chargeback Rate	Merchant rule	Disputes in state = LOST / payments succeeded * 100. A trailing metric (disputes resolve 30-60d after opening). Above 0.9% Square may impose a rolling
Decline Rate	Alert band 3 / 8	FAILED / (COMPLETED + FAILED + CANCELED) * 100. CANCELED (3DS abandon) excluded and tracked separately. POS <1%; Online 4-8%.
Dispute Rate	Alert band 0.5 / 0.9	Disputes opened / payments succeeded * 100, on /v2/disputes. POS card-present <0.05% (chip + PIN liability shift); CNP 0.3-1.5%. The leading indica
Online Decline Spike vs Checkout Funnel Drop	Merchant rule	When Square Online declines spike, does commerce checkout completion drop in the same window? If yes, declines are causing real revenue loss - and the
Refund Rate	Alert band 2 / 5	SUM(refunds.amount) / SUM(payments.amount) * 100. Spikes signal product/fulfilment issues; gentle creep signals subscription churn. Bookshops 1-3%, ap
Refund Volume	Merchant rule	SUM(amount) over /v2/refunds where status = COMPLETED, per currency. Partial refunds counted at the partial amount. Retail 2-5%; ecom 5-12%.
Success Rate	Alert band 97 / 92	COMPLETED / (COMPLETED + FAILED + CANCELED) * 100. APPROVED (auth-only) excluded. POS card-present ~99%; Square Online ~92-96%.
Top Decline Reasons	Merchant rule	COUNT GROUP BY failure_code over FAILED /v2/payments. CARD_DECLINED, INSUFFICIENT_FUNDS, CVV_FAILURE, EXPIRED_CARD, CHIP_INSERTION_REQUIRED - each has
Total Volume	Alert band 0 / -15	Every /v2/payments row where status = COMPLETED, summed by amount_money.amount, across POS, Square Online, Invoices, Virtual Terminal, Tap to Pay and

Run operations (7 signals)

Signal	Alert behaviour	What it tracks
Average Transaction	Merchant rule	SUM(amount) / COUNT(*) over COMPLETED payments, per currency. Channel mix-shift moves this more than any single-channel pricing change.
Avg Settlement Time (days)	Alert band 2 / 5	AVG(payout.created_at - payment.created_at) in days, amount-weighted. Square default is T+1 (~1.0-1.5 days); Instant Deposit usage drags it down; rese
Oldest Pending Payout (days)	Alert band 2 / 5	Calendar days since the last successful payout to the linked bank. Healthy 1-2d (T+1); >3d suggests weekend/holiday closure or schedule change; &gt
Pending Payouts	Merchant rule	Captured COMPLETED payments not yet rolled into a settled payout. Snapshot, not trended. Reserves count as pending; Instant Deposit reduces it.
Top Payment Methods	Merchant rule	COUNT GROUP BY entry_method + source_type over COMPLETED payments: chip, contactless, magstripe, manual, cash, Cash App Pay, Apple/Google Pay, gift ca
Total Transactions	Alert band 0 / -15	COUNT of COMPLETED /v2/payments rows - one per payment, all source_type values. The denominator behind average transaction.
Volume Trend	Watch only	Daily COMPLETED payment volume plotted over the period. The cleanest card for spotting weekday/weekend seasonality and sudden cliff-drops (terminal ou

Audit (4)

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.

Dispute rate above 1% (Visa/Mastercard threshold)

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

Decline rate above 8%

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

Refund rate spiked > 50% vs 7-day average

Severity high · Outcome Protect revenue · Fix status Candidate remediation

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.

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-REFUND-001

Payout overdue > 5 days vs typical schedule

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

Automate approved work

Vortex IQ is integrated with 7 read and 1 write operations across payments, disputes, disputeaccepts, merchants, orders, payouts on Square. 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

Ready to build your first Square 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.

Browse the operations you can build with

Resource	Read operations	Write operations
payments	2	0
disputes	1	0
disputeaccepts	0	1
merchants	1	0
orders	1	0
payouts	1	0
refunds	1	0

Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.