> ## 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.

# Mollie on Vortex IQ

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

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

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.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue)

| **18**              | **5**            | **Build your own** | **Ready to build yours** | **10**         |
| ------------------- | ---------------- | ------------------ | ------------------------ | -------------- |
| performance signals | automated checks | automated fixes    | workflows                | API operations |

## Monitor performance

18 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher.

| Signal                                    | Outcome         | Alert behaviour      | What it tracks                                                                                                      |
| ----------------------------------------- | --------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Captured vs Commerce Revenue**          | Grow revenue    | Merchant rule        | Reconciliation gap between what Mollie captured and what the commerce sibling booked as revenue.                    |
| **Decline Spike vs Checkout Funnel Drop** | Protect revenue | Merchant rule        | When Mollie declines spike, does commerce checkout completion drop? If yes, declines are causing real revenue loss. |
| **3DS Abandonment Rate**                  | Protect revenue | Alert band 15 / 30   | Customers who saw the 3DS / SCA challenge and bailed. High abandon = checkout friction.                             |
| **Avg Settlement Time (days)**            | Run operations  | Alert band 2 / 5     | Capture-to-payout lag in days.                                                                                      |
| **Chargeback Rate**                       | Protect revenue | Alert band 0.5 / 0.9 | Chargebacks / total payments. Above \~0.9% risks network monitoring programmes.                                     |
| **Pending Payouts**                       | Run operations  | Merchant rule        | Captured value not yet paid out to the merchant bank.                                                               |
| **Success Rate**                          | Run operations  | Alert band 95 / 90   | Paid / total attempts. The headline payments-health number.                                                         |
| **Top Decline Reasons**                   | Protect revenue | Merchant rule        | Mollie failureReason coded (insufficient\_funds, card\_declined, invalid\_card\_number) - each has a different fix. |
| **Top Payment Methods**                   | Run operations  | Merchant rule        | iDEAL vs card vs Bancontact vs PayPal vs Klarna mix - watch for rail-specific breakage.                             |
| **Total Volume**                          | Run operations  | Merchant rule        | Gross payment value captured over the window.                                                                       |
| **Volume Trend**                          | Grow revenue    | Alert band 0 / -15   | Captured volume over time - spot weekly cadence and dips.                                                           |
| **Average Transaction**                   | Run operations  | Merchant rule        | Description pending editorial review; the signal is live.                                                           |
| **Decline Rate**                          | Protect revenue | Alert band 5 / 8     | Description pending editorial review; the signal is live.                                                           |
| **Dispute Rate**                          | Protect revenue | Alert band 0.5 / 1   | Description pending editorial review; the signal is live.                                                           |
| **Oldest Pending Payout (days)**          | Run operations  | Alert band 2 / 5     | Description pending editorial review; the signal is live.                                                           |
| **Refund Rate**                           | Protect revenue | Alert band 3 / 8     | Description pending editorial review; the signal is live.                                                           |
| **Refund Volume**                         | Protect revenue | Merchant rule        | Description pending editorial review; the signal is live.                                                           |
| **Total Transactions**                    | Run operations  | Merchant rule        | Description pending editorial review; the signal is live.                                                           |

## 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.

| Check                                                                    | Severity | Outcome         | Why it matters                                                                                                                                                                                 | Fix status            |
| ------------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| **Dispute rate above 1% (Visa/Mastercard threshold)**                    | critical | Protect revenue | 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  | Candidate remediation |
| **Decline rate above 8%**                                                | high     | Protect revenue | 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 funn | Report only           |
| **Refund rate spiked > 50% vs 7-day average**                            | high     | Protect revenue | 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  | Candidate remediation |
| **3DS challenge friction ,  > 30% of qualifying transactions abandoned** | medium   | Protect revenue | 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 detai | Candidate remediation |
| **Payout overdue > 5 days vs typical schedule**                          | medium   | Grow revenue    | 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 rega | Candidate remediation |

### Build your own automated fixes

5 checks report findings on Mollie today. Turn any finding into an automated fix with a Vortex IQ workflow: **13,885 read and write operations across 229 connectors** are available as building blocks, with approval, verification and rollback on every change.

## Automate approved work

Vortex IQ is integrated with **9 read** and **1 write** operations across payments, payment refunds, chargebacks, methods, organizationmes, refunds on Mollie. Combine them with anything from the **13,885 operations across 229 connectors** to automate the work in your own words.

Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. Read-only operations do not modify the connected system.

[Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=mollie)

<Accordion title="Browse the operations you can build with">
  | Resource           | Read operations | Write operations |
  | ------------------ | --------------- | ---------------- |
  | payments           | 2               | 0                |
  | payment refunds    | 1               | 1                |
  | chargebacks        | 1               | 0                |
  | methods            | 1               | 0                |
  | organizationmes    | 1               | 0                |
  | refunds            | 1               | 0                |
  | settlements        | 1               | 0                |
  | settlementpayments | 1               | 0                |

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

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

***

*Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*
