A restaurant chain's chargebacks just jumped. What happened, what do the rules say, and who do we call?

Moneris sees one in three Canadian transactions. Today, answering that question means pulling disputes from Snowflake, terminal telemetry from Databricks, network rules and contracts from SharePoint, news from the web and the last conversation from someone's inbox. Four Microsoft IQ layers do it together in minutes, and a person approves before anything goes out.

"Stripe sells merchants its network's intelligence. Microsoft IQ lets Moneris build and own its own — on Canadian in‑person and bank‑channel data Stripe doesn't have."

🟢 Fabric IQ (lead)

Live view of merchants, terminals, transactions and chargebacks. Flags approval-rate drops, terminal outages and merchants likely to leave.

⚔️ vs Stripe: one governed view over Snowflake + Databricks + CRM — Moneris owns the intelligence.

🔵 Foundry IQ

Agents that know card-network rules, PCI and AML requirements, and merchant contracts. Help with chargebacks, merchant support and developers using the Unified API.

⚔️ vs Stripe: faster, rule-correct dispute and support answers.

🟣 Work IQ

Merchant account briefs, faster onboarding and dispute handling, smoother RBC/BMO branch referrals.

⚔️ vs Stripe: the human, bank-channel relationship Stripe can't replicate.

🟠 Web IQ

Merchant due diligence: website checks, adverse-media screening. Tracks competitors and regulation.

⚔️ vs Stripe: see competitor and rule changes the day they land — with citations.

Merchants monitored (sample portfolio)

4,812

Tier‑1 & Tier‑2 · ON, QC, BC, AB, SK, MB, NS

Chargeback alerts this week

—

▲ 3.1× vs. 4‑week average

Open disputes on flagged merchants

—

Across Visa, Mastercard, Interac

Time to a dispute response pack

2 days → 8 min

Illustrative target · agent-assembled

🟢 One governed view of merchant, terminal, transaction and chargeback — without moving off Snowflake or Databricks Powered by Fabric IQ

❄️ SnowflakeAuthorizations, settlement, disputes & chargebacks · Mirrored into OneLake (near real-time, no ETL)

🧱 Azure DatabricksTerminal telemetry, firmware, anomaly & churn models · Unity Catalog shortcut/mirror into OneLake (no copy)

📇 Dynamics 365 + Field ServiceAccounts, contracts, firmware rollouts, work orders · native in OneLake

➜

OneLakeOne copy · Delta/Iceberg · Purview lineage & sensitivity labels follow the data

➜

Fabric IQ ontologyMerchant → Location → Terminal (firmware) → Transaction → Dispute → Contract → Referral Bank · defined once, used by every agent

One example, four layers →

🟢 Fabric IQ flags the chargeback jump and links it to a terminal firmware issue

🔵 Foundry IQ pulls the card-network rules and the merchant's contract

🟠 Web IQ checks news, the merchant's website, rule changes and competitors

🟣 Work IQ finds the relationship manager and the last email thread

🎯 An agent drafts the outreach and the chargeback response · ⏸️ you approve

🚨 Merchant alerts — this week

Fabric IQ data agent

Merchant	Segment · Region	Locations	Annual volume	Chargebacks (30d)	Approval rate	Terminal firmware	Churn risk	Referral	Leading signal

IQ legend: 🟢 Fabric IQ — the What (data) 🔵 Foundry IQ — the Why (knowledge) 🟣 Work IQ — the Who (people) 🟠 Web IQ — the World (live public web) · Governed by Microsoft Agent 365