Banking · Power BI template
Card Fraud Monitoring Power BI template
Dark Power BI fraud detection dashboard template: fraud loss and rate in basis points, alerts by hour, false-positive rate and an open alert queue.
By Nawaf Sharaf · Founder & Reliability Engineer · Updated
Free for commercial useLight version: same layout, colours re-solved and checked for WCAG AA contrast.
BetaOpens in Power BI Desktop with 6 tables of sample data and every visual bound. See what’s inside
Free, no sign-up. The PBIP with sample data includes the background, theme and a README. 1920×1080 fits a new page in a Fluent 2 report; 1280×720 and 2× fit Classic pages. Downloads carry a small “Made with VizForge” mark (sign in to the studio to remove it).
- Layout
- 2×2 KPI block beside a weekly loss trend, hour-of-day columns + merchant bars + open-alert queue
- Page size
- 1280×720 px (16:9, Power BI default)
- Theme
- Carbon Neon
Open the sample-data PBIP in Power BI Desktop
Checked against Microsoft Learn's Power BI Desktop projects documentation (as of Nov 2026).
- 1
Unzip to a short path and open the .pbip
Extract the zip to a short local folder such as C:\PBI (Windows limits project paths to 260 characters, and Desktop can't save a project straight to OneDrive or SharePoint), then double-click the .pbip file or use File → Open in Power BI Desktop. Microsoft still lists projects and TMDL as preview features (as of Nov 2026): if Desktop won't open the project, go to File → Options and settings → Options → Preview features, tick “Power BI Project (.pbip) save option” and “Store semantic model using TMDL format”, then restart Desktop.
- 2
Select Refresh once
The project ships without the local data cache (.pbi/cache.abf), so Desktop opens the full model definition without data. Select Home → Refresh: every table is built from values written into its Power Query step, so there is no data source to sign in to.
- 3
Save as .pbix or connect your data
Use File → Save as to keep a single .pbix file, or open Transform data and replace each table's Source step with your own query, keeping the column names so the measures and visuals keep working.
What’s inside the Fraud Detection sample model
Rendered from the same definition the download writes as TMDL, so this list always matches the file.
Six months of weekly card volumes for a fictional issuer across four channels, with fraud losses and fraud prevented, plus 300 fraud alerts from the last eight weeks with the hour of day, merchant category, model score and review outcome. Units: Euros; fraud rate in basis points (1 bp = 0.01% of transaction value).
Tables and columns
Calendar
Date table · 2026, one row per dayDate table generated in Power Query (List.Dates), marked as the model's date table.
- Date (date)
- Year (whole number)
- Quarter (text)
- Month (text)
- Month Name (text)
- Week Start (date)
- Weekday (text)
- Fiscal Year (text)
Channel
Dimension · 4 rowsHow the card was used.
- Channel (text)
Merchant Category
Dimension · 6 rowsMerchant category of the alerted transaction.
- Merchant Category (text)
Hour
Dimension · 24 rowsHour of day (00–23) the alerted transaction happened.
- Hour Label (text)
Card Volume
Fact · 104 rowsWeekly transactions, value, fraud losses and fraud prevented per channel.
- Week (date)
- Channel (text)
- Transactions (whole number)
- Transaction Value (decimal)
- Fraud Loss (decimal)
- Fraud Prevented (decimal)
Alerts
Fact · 300 rowsOne row per fraud alert raised by the scoring model.
- Alert ID (text)
- Date (date)
- Hour (whole number)
- Channel (text)
- Merchant Category (text)
- Amount (decimal)
- Score (whole number)
- Outcome (text)
Relationships
Many-to-one, single direction. Inactive relationships are switched on inside a measure with USERELATIONSHIP.
- 'Card Volume'[Week] → 'Calendar'[Date]
- 'Card Volume'[Channel] → Channel[Channel]
- Alerts[Date] → 'Calendar'[Date]
- Alerts[Channel] → Channel[Channel]
- Alerts[Merchant Category] → 'Merchant Category'[Merchant Category]
- Alerts[Hour] → Hour[Hour]
DAX measures
All measures live in a dedicated Key Measures table. Copy any of them into your own model; rename the table and column references to match.
Fraud LossFraud that got through.
Fraud Loss =
SUM ( 'Card Volume'[Fraud Loss] )Format string: €#,0
Fraud PreventedFraud stopped by rules, model or review.
Fraud Prevented =
SUM ( 'Card Volume'[Fraud Prevented] )Format string: €#,0
Fraud Rate (bps)Fraud loss per 10,000 of card spend.
Fraud Rate (bps) =
DIVIDE ( [Fraud Loss], SUM ( 'Card Volume'[Transaction Value] ) ) * 10000Format string: 0.0
Alerts RaisedAlerts raised.
Alerts Raised =
COUNTROWS ( Alerts )Format string: #,0
False Positive RateReviewed alerts that turned out to be genuine customer spend.
False Positive Rate =
DIVIDE (
CALCULATE ( COUNTROWS ( Alerts ), Alerts[Outcome] = "False positive" ),
CALCULATE ( COUNTROWS ( Alerts ), Alerts[Outcome] <> "Open" )
)Format string: 0%
Confirmed Fraud AmountValue of alerts confirmed as fraud.
Confirmed Fraud Amount =
CALCULATE ( SUM ( Alerts[Amount] ), Alerts[Outcome] = "Confirmed fraud" )Format string: €#,0
Open Alert ValueValue of alerts still waiting for review.
Open Alert Value =
CALCULATE ( SUM ( Alerts[Amount] ), Alerts[Outcome] = "Open" )Format string: €#,0
What each visual is bound to
The PBIP opens with these fields already on each visual.
| Visual | Type | Fields |
|---|---|---|
| ChannelSlicer | Slicer | Channel[Channel] |
| Merchant categorySlicer | Slicer | 'Merchant Category'[Merchant Category] |
| Fraud lossCard | Card | [Fraud Loss] |
| Fraud rate (bps)Card | Card | [Fraud Rate (bps)] |
| Fraud loss vs prevented by weekLine chart | Line chart | Calendar[Week Start], [Fraud Loss], [Fraud Prevented] |
| Alerts raisedCard | Card | [Alerts Raised] |
| False positive rateCard | Card | [False Positive Rate] |
| Alerts by hour of dayColumn chart | Column chart | Hour[Hour Label], [Alerts Raised] |
| Confirmed fraud by merchant categoryBar chart | Bar chart | 'Merchant Category'[Merchant Category], [Confirmed Fraud Amount] |
| Open alert queueTable | Table | Alerts[Alert ID], Alerts[Date], 'Merchant Category'[Merchant Category], Alerts[Score], [Open Alert Value] |
Questions this dashboard answers
Each one is answered by a visual on the page, from the sample model's own tables and measures.
- Is fraud loss as a share of card spend (basis points) rising, and in which channel?
- How much fraud did the rules and model stop compared with what got through?
- What share of reviewed alerts were false positives?
- At what hours do alerts cluster, and which open alerts carry the most value?
About this dashboard layout
Fraud teams watch two numbers that pull against each other: how much fraud gets through and how many genuine customers get blocked. The 2×2 block at the top left holds both sides, fraud loss and fraud rate in basis points of card spend next to alerts raised and the false-positive rate of reviewed alerts, with the weekly trend of fraud lost against fraud prevented beside it.
Alerts by hour of day is a column chart over a 24-row hour table (00:00 to 23:00, sorted by a hidden hour number), because fraud does not keep office hours and the overnight cluster is what staffing decisions hang on. Confirmed fraud by merchant category shows where the losses land.
The open alert queue on the right is the analysts' to-do list: open alerts only, through a measure that is blank for anything already reviewed, sorted by value with the model score alongside. Keep it on the main page; a queue hidden on page three is a queue nobody works.
The sample has 26 weeks of card volume for a fictional issuer across online, contactless, chip & PIN and ATM channels, and 300 alerts from the last eight weeks. Note that the Merchant category slicer only filters the alert visuals, because the weekly volume table is held by channel.
Visuals on the page
Positions are Power BI page pixels. Enter them in Format → General → Properties → Size and position, or use the PBIP download where they are already set.
| Visual | Type | X | Y | Width | Height |
|---|---|---|---|---|---|
| Channel | Slicer | 888 | 24 | 176 | 40 |
| Merchant category | Slicer | 1080 | 24 | 176 | 40 |
| Fraud loss | Card | 40 | 120 | 216 | 72 |
| Fraud rate (bps) | Card | 304 | 120 | 216 | 72 |
| Fraud loss vs prevented by week | Line chart | 568 | 120 | 672 | 192 |
| Alerts raised | Card | 40 | 240 | 216 | 72 |
| False positive rate | Card | 304 | 240 | 216 | 72 |
| Alerts by hour of day | Column chart | 40 | 360 | 328 | 320 |
| Confirmed fraud by merchant category | Bar chart | 416 | 360 | 328 | 320 |
| Open alert queue | Table | 792 | 360 | 448 | 320 |
Custom visuals for this layout
Built-in Power BI visuals cover most slots above. These slots also suit a custom visual; each page covers the data shape, DAX and a prompt to generate it as a .pbiviz.
Slot: Fraud loss
KPI CardExecutive dashboard KPI row (revenue, customers, NPS, churn)
Slot: Alerts by hour of day
HeatmapHour-of-day × day-of-week traffic or activity patterns
Already have a report?
Brand Makeover tries Card Fraud Monitoring first on every page of your Power BI project (.pbip zip) where it fits: the page's visuals have to go into its 8 data slots without overlaps. Pages it can't seat get another catalog layout or a brand grid. Queries, filters and bookmarks are left as they are. Free, in your browser.
Opens with the Analyst / Dense preset, because the Executive preset doesn't use this layout (8 data slots; this preset uses templates with at most 7).
Restyle my report into thisSwap a slot for a custom visual
Pick any slot and VizForge AI writes a custom visual (.pbiviz, with TypeScript source) sized to it, in this template's colours and shaped for the fields it is bound to.
Generate one that fits this layout.
Card · 216×72 px · bound to [Fraud Loss]
1, 2 or 5 credits depending on the brief · 5 free on signup. Sign in or create a free account on the next screen; the brief is saved for 30 minutes.
A Power BI card visual titled "Fraud loss". It sits in a 216×72 px slot on a designed report page. Match the report's brand: data colours #C6FF3D, #FF3DAD, #3DD6FF, #A26BFF, #FF9A3D, #3DFFB0; background #15151C; text #F4F4F8; font Segoe UI. Transparent visual background so the page design shows through; no visual border. In the sample model it is bound to [Fraud Loss]; keep the same data roles so the fields drop straight in.
Not sure what to build? Browse the visual catalog or open the template in the design studio and hand off any slot from there. Or start in the AI generator with a blank brief.
Colours and theme
Neon-on-carbon dark Power BI theme: electric lime, magenta, cyan and violet data colours on near-black for gaming, esports, tech-startup and launch dashboards.
Use the background in an existing report
Prefer to keep your own report? Apply the design to it instead of opening the PBIP.
- 1
Download the background
Take the 1920×1080 PNG for a new page in a Fluent 2 report (the default size for new pages), or the 2× PNG (2560×1440) for sharp text on a 1280×720 Classic page. Power BI scales the image to the canvas.
- 2
Set the canvas background
Format page → Canvas background → Browse. Set Image fit to Fill and transparency to 0%.
- 3
Import the theme
Design ribbon → Import theme (in the Power BI service: View → Theme pane), then pick the downloaded JSON. Data colours and fonts now match the design. Older Desktop builds: View → Themes → Browse for themes.
- 4
Place your visuals
Size each visual to the positions above with background and border off, or open the PBIP project where they are already placed.
Questions about this template
Does the Card Fraud Monitoring template come with sample data?
Yes. The “PBIP with sample data” download contains a semantic model with 6 tables and 7 DAX measures, and every visual on the page is already bound to it. The sample: Six months of weekly card volumes for a fictional issuer across four channels, with fraud losses and fraud prevented, plus 300 fraud alerts from the last eight weeks with the hour of day, merchant category, model score and review outcome. The data is written into each table's Power Query step, so there is no data source or sign-in.
Is it a .pbix file?
It is a Power BI project (PBIP): a folder of text files that Power BI Desktop opens like a .pbix. Open the .pbip file, select Refresh once to load the sample rows, then use File → Save as if you want a single .pbix.
What visuals are in the Card Fraud Monitoring template?
The page has 10 visual areas: 2 slicers, 4 cards, 1 line chart, 1 column chart, 1 bar chart, 1 table. Their exact positions are listed on this page so you can match them in Power BI's Format → General → Properties panel, or skip that step by downloading the PBIP project.
Which theme does the Card Fraud Monitoring template use?
It ships with the Carbon Neon theme (dark tone). Download the theme JSON here, or open the template in the design studio and switch to any other theme or your own brand colours.
Is there a light version of the Card Fraud Monitoring template?
Yes. Switch the preview to Light and every download (background, theme JSON and PBIP) comes in that version. The layout is identical; the page, card and text colours are re-solved for a light page, and the accent, status and data colours keep their hues but are adjusted until text meets WCAG AA (4.5:1) and chart colours reach 3:1 against the cards.
How do I use the background image in Power BI Desktop?
Select the page, open Format page → Canvas background, choose Browse and pick the PNG, then set Image fit to Fill and transparency to 0%. Give your visuals a transparent background and no border so the designed panels show through.
Can I open the PBIP project in Power BI Desktop?
Yes. PBIR is the default report format in Power BI Desktop since September 2026, and the download is a PBIP project: unzip it and open the .pbip file, select Refresh once and the sample data loads into visuals that are already bound (the empty PBIP leaves the containers unbound for your own data). Microsoft still lists projects and TMDL as preview features (as of Nov 2026), so if Desktop won't open it, enable them under File → Options and settings → Options → Preview features.
Dashboard guides that use these visuals
Guides to the same dashboard job: which custom visuals it needs, the DAX behind them and prompts to generate them.
Dashboard job
Best Power BI Visuals for an Executive ScorecardThe best Power BI visuals for an executive scorecard — KPI cards, bullet grids, sparkline rows, SPC quality…
Dashboard job
Best Power BI Visuals for a Sales DashboardThe best Power BI visuals for a sales dashboard: pipeline funnel, KPI cards, bullet charts, territory…
Dashboard job
Best Power BI Visuals for Retail AnalyticsThe best Power BI visuals for retail analytics — store heatmaps, category Pareto, basket Sankeys, promotional…
Team
Power BI for financeVariance bridges, balance-sheet smalls, scenario sliders — the finance visuals Power BI's native waterfall and cards don't cover.
KPI cards for this layout
Headline numbers drawn by one DAX SVG measure each, for the Card visual or a table row.
Want the headline numbers to look like cards rather than plain values? Browse the KPI card gallery or build your own in the SVG measure builder.
Related templates
Keep exploring
61 hand-designed Power BI page layouts by department.
80 contrast-checked theme JSON files, light and dark.
Page backgrounds at 1280×720 and 1920×1080 with visual positions.
3,034 icons in 40 categories as SVG, PNG, DAX or theme icon JSON.
Make the Card Fraud Monitoring template yours
Swap in your brand colours and logo, move panels, add icons and generate missing visuals with AI, then export the background, theme JSON and PBIP project.
The design studio for Power BI. Free, in your browser, no sign-up.