> ## 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. # Afterpay on Vortex IQ > Monitor Afterpay payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow. Monitor Afterpay 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=afterpay) 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. Find storefront, speed, accessibility and journey problems. 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 | Share of 3DS-challenged Afterpay transactions abandoned at the challenge step - added friction / lost conversion. | | **Afterpay Refund Spike × Commerce Returns Spike** | Merchant rule | Afterpay refund volume rising in lockstep with commerce returns - a product / fulfilment / quality issue draining BNPL margin, not a payments glitch. | | **Afterpay-vs-Commerce Revenue Reconciliation Gap** | Alert band 0 / 2 | Captured Afterpay volume that doesn't reconcile to commerce-sibling Afterpay-paid order revenue = a sync / capture / settlement gap to chase. | | **Chargeback Rate** | Watch only | Chargebacks as a share of transactions. Above the 1% Visa/Mastercard programme threshold is monitoring-programme risk. | | **Decline Rate** | Alert band 5 / 8 | Share of Afterpay attempts declined by Afterpay's upfront risk model. Pair with Top Decline Reasons to see what's driving it. | | **Dispute Rate** | Watch only | Open disputes + inquiries as a share of transactions - early-warning band before formal chargebacks. | | **Refund Rate** | Alert band 3 / 8 | Refunded value as a share of captured Afterpay volume. A spike vs baseline flags returns / quality / fulfilment issues. | | **Refund Volume** | Merchant rule | Total value refunded through Afterpay in the period. Subtract from Total Volume for net BNPL revenue. | | **Top Decline Reasons** | Merchant rule | Decline-reason mix across declined Afterpay attempts - where recoverable BNPL revenue is leaking. | | **Total Volume** | Alert band 0 / -15 | Gross Afterpay Pay-in-4 volume captured in the period (status CAPTURED, summed by totalAmount). Gross of refunds + Afterpay's merchant fee; multi-curr | | Signal | Alert behaviour | What it tracks | | -------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | **Avg Settlement Time (days)** | Merchant rule | Mean days from capture to Afterpay payout landing. Afterpay typically settles 1-3 business days after capture. | | **Oldest Pending Payout (days)** | Watch only | Age in days of the oldest still-pending payout. Aging past the typical 1-3 day schedule is a cash-flow / settlement-health flag. | | **Pending Payouts** | Merchant rule | Gross value of Afterpay settlements still in PENDING / IN\_TRANSIT - cash captured but not yet in the bank. | | **Top Payment Methods** | Merchant rule | Mix of underlying payment instruments / Pay-in-4 channels (web, Cash App) backing Afterpay orders. | | **Total Transactions** | Merchant rule | Count of successful Afterpay Pay-in-4 orders (APPROVED + CAPTURED). Volume / this gives Afterpay AOV (typically \~25% above card AOV). | | **Volume Trend** | Merchant rule | Daily captured Afterpay volume over the window - the shape behind the headline Total Volume number. | | Signal | Alert behaviour | What it tracks | | ----------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------- | | **Average Transaction** | Merchant rule | Afterpay AOV - total captured volume / captured order count. The BNPL basket-size lift over card checkout. | | **Success Rate** | Alert band 95 / 90 | Share of Afterpay attempts that approved and captured. Below 90% signals checkout friction or underwriting tightening. | ### 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** 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` **Severity** medium · **Outcome** Protect revenue · **Fix status** Candidate remediation More than 3 in 10 shoppers who reach a 3D Secure identity challenge are abandoning it rather than completing it. These are customers who already committed to buying and entered payment details, so this is revenue lost at the very last step, to friction rather than to lack of interest. 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-3DS-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 **8 read** and **2 write** operations across disputes, payments, payment refunds, settlements, configurations, disputeresponds on Afterpay. 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=afterpay) #### Ready to build your first Afterpay 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 | | --------------- | --------------- | ---------------- | | disputes | 2 | 0 | | payments | 2 | 0 | | payment refunds | 1 | 1 | | settlements | 2 | 0 | | configurations | 1 | 0 | | disputeresponds | 0 | 1 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.