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

[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=mollie)

<CardGroup cols={5}>
  <Card title="18">
    performance signals
  </Card>

  <Card title="5">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Protect revenue (8 signals)">
        | Signal                                    | Alert behaviour      | What it tracks                                                                                                      |
        | ----------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------- |
        | **3DS Abandonment Rate**                  | Alert band 15 / 30   | Customers who saw the 3DS / SCA challenge and bailed. High abandon = checkout friction.                             |
        | **Chargeback Rate**                       | Alert band 0.5 / 0.9 | Chargebacks / total payments. Above \~0.9% risks network monitoring programmes.                                     |
        | **Decline Rate**                          | Alert band 5 / 8     | Description pending editorial review; the signal is live.                                                           |
        | **Decline Spike vs Checkout Funnel Drop** | Merchant rule        | When Mollie declines spike, does commerce checkout completion drop? If yes, declines are causing real revenue loss. |
        | **Dispute Rate**                          | Alert band 0.5 / 1   | Description pending editorial review; the signal is live.                                                           |
        | **Refund Rate**                           | Alert band 3 / 8     | Description pending editorial review; the signal is live.                                                           |
        | **Refund Volume**                         | Merchant rule        | Description pending editorial review; the signal is live.                                                           |
        | **Top Decline Reasons**                   | Merchant rule        | Mollie failureReason coded (insufficient\_funds, card\_declined, invalid\_card\_number) - each has a different fix. |
      </Accordion>

      <Accordion title="Run operations (8 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                          |
        | -------------------------------- | ------------------ | --------------------------------------------------------------------------------------- |
        | **Average Transaction**          | Merchant rule      | Description pending editorial review; the signal is live.                               |
        | **Avg Settlement Time (days)**   | Alert band 2 / 5   | Capture-to-payout lag in days.                                                          |
        | **Oldest Pending Payout (days)** | Alert band 2 / 5   | Description pending editorial review; the signal is live.                               |
        | **Pending Payouts**              | Merchant rule      | Captured value not yet paid out to the merchant bank.                                   |
        | **Success Rate**                 | Alert band 95 / 90 | Paid / total attempts. The headline payments-health number.                             |
        | **Top Payment Methods**          | Merchant rule      | iDEAL vs card vs Bancontact vs PayPal vs Klarna mix - watch for rail-specific breakage. |
        | **Total Transactions**           | Merchant rule      | Description pending editorial review; the signal is live.                               |
        | **Total Volume**                 | Merchant rule      | Gross payment value captured over the window.                                           |
      </Accordion>

      <Accordion title="Grow revenue (2 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                   |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------ |
        | **Captured vs Commerce Revenue** | Merchant rule      | Reconciliation gap between what Mollie captured and what the commerce sibling booked as revenue. |
        | **Volume Trend**                 | Alert band 0 / -15 | Captured volume over time - spot weekly cadence and dips.                                        |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (5)">
    ### 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.

    <AccordionGroup>
      <Accordion title="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`
      </Accordion>

      <Accordion title="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`
      </Accordion>

      <Accordion title="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`
      </Accordion>

      <Accordion title="3DS challenge friction , > 30% of qualifying transactions abandoned">
        **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`
      </Accordion>

      <Accordion title="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`
      </Accordion>
    </AccordionGroup>

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

  <Tab title="Automate">
    ### 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 **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=mollie)

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

    <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>
  </Tab>
</Tabs>
