A Pluto user reported that they had been the victim of fraud, but their bank didn't find it immediately, they did... with the help of Pluto's features.
They weren't using any special fraud detection feature. Just using Pluto the way it's designed: planning transactions before they happen, then reviewing what actually posts.
This is when we realized: by building a budgeting system around planned transactions, we'd accidentally built one of the most effective fraud detection systems available.
I spend a few minutes every day in Pluto making sure I have a bead on any new transactions from the previous day. It provides quick and easy tools to ensure each transaction is accounted for. This daily habit helped me identify a fraudulent charge on my account before my bank. I was able to resolve the issue quickly and avoid the risk of any future fraud.
Mike K, Pluto user since 2022
Most budgeting apps work backward. They import your transactions after they've posted, then ask you to categorize them.
The workflow looks like this:
If a fraudulent charge appears, it looks like every other transaction. A $47 charge at 'Online Retailer XYZ'? Could be legitimate. Did you buy something and forget? Maybe. Better check your email receipts. Or your credit card statement. Or just assume it's fine.
By the time you realize it's fraud (if you realize at all), days or weeks have passed. The trail is cold. Disputing becomes harder.
Pluto flips this model. You don't categorize transactions after they happen—you plan them before they occur.
Your workflow:
Now here's what happens with fraud:
The fraudulent charge doesn't blend in. It stands out like a sore thumb because it's the only transaction that doesn't match your plans.
Here's how it can be detected:
Tuesday, 2:00 PM: Someone uses the user's card number for three charges totaling $287 at online retailers the user's never heard of.
Tuesday, 2:15 PM: Transactions post to the Pluto user's bank account as pending.
Tuesday, 3:45 PM: Pluto imports the transactions during its routine sync.
Tuesday, 3:46 PM: Transaction matching runs:
Searching for matches...
$127.84 - 'TechGadgets Online' - No matching planned transaction
$89.99 - 'Fashion Hub Store' - No matching planned transaction
$69.17 - 'Home Decor Plus' - No matching planned transaction
Result: 3 unmatched transactions requiring attentionTuesday, 4:20 PM: The user opens Pluto to check their Safe to Spend before buying groceries. The app shows a notification badge: '3 transactions need attention.'
They tap to review. Sees three transactions they doesn't recognize. Immediate red flag.
Tuesday, 4:25 PM: They call their bank, reports fraud, cancels card. Total elapsed time from fraud to discovery: 2 hours and 25 minutes.
Their bank's fraud detection? Never flagged anything. The charges were under typical fraud detection thresholds, made at legitimate retailers, spread across different merchants. Classic low-and-slow fraud designed to slip past automated systems.
Banks use sophisticated algorithms to detect fraud. They look for:
These systems are good at catching obvious fraud: someone buying a $5,000 TV in another state while you're at home.
They're terrible at catching subtle fraud:
Pluto doesn't care about patterns or thresholds. It asks one simple question: "Did you plan this transaction?"
If yes → Auto-match, confirm with one tap, move on.
If no → Flag immediately as unplanned, requires your attention.
No sophisticated algorithms needed. Just the simple logic of "planned vs. unplanned."
Here's how Pluto's matching works under the hood:
Every time Pluto syncs with your bank (typically every few hours for Premium users), it imports new transactions and runs the matching algorithm:
For each new bank transaction:
1. Search planned transactions within ±5 days
2. Compare amounts (exact or within tolerance)
3. Check merchant similarity
4. Verify account matches
5. Calculate confidence score (0-100%)High confidence matches (95%+): Auto-match, show in review queue
Medium confidence (70-94%): Suggest match, wait for confirmation
Low confidence (<70%): Show alternative matches or flag as unplanned
No matches found: Immediately flag as 'Needs Attention'
Pluto presents unmatched transactions in a dedicated review interface:
Unmatched Transaction Card:
If you select 'Find Match Manually,' Pluto shows:
If you select 'Mark as Unplanned,' Pluto:
Not every unmatched transaction is fraud. Sometimes you make purchases you didn't plan:
This is actually valuable information. Pluto shows you:
But here's the key: legitimate unplanned purchases feel different than fraud.
When you see '$8.47 - Coffee Shop' as unplanned, you think: 'Oh right, I grabbed coffee this morning and forgot to plan it.'
When you see '$127.84 - TechGadgets Online' as unplanned, and you've never heard of TechGadgets Online, your brain immediately flags: 'Wait, what is this?'
The system doesn't need to distinguish between intentional unplanned spending and fraud. You do that instantly because you know your own spending.
Most Pluto users check the app daily or near-daily. Not because we nag them to, but because they want to see their Safe to Spend before making decisions.
This creates a natural fraud detection habit:
As a frequent user, you'll have a good idea where that number should be.
Pluto brings it all together in the transactions tab, everything needing attention in one place.
If bank transactions come in that don't match anything you planned, you can see them right there.
Pluto isn't here to judge you, if you had a great time shopping, we're happy for you! The transactions you recognize that you didn't plan, mark them as unplanned and they fall right off the list. Anything left requires closer inspection. This is where you find fraud.
You can check this as many times a day as you want. Most banks only update once a day, but making a morning habit of quickly reviewing your transactions will ensure you know how your money is really flowing.
This is dramatically different from traditional budgeting apps where you might only check in weekly or monthly. By the time you notice fraud, significant time has passed.
It's also different from checking your bank app, where fraudulent charges blend in with dozens of legitimate transactions. The signal-to-noise ratio is terrible.
Pluto's review queue isolates only the transactions that need your attention. High signal, low noise.
While fraud detection is a compelling benefit, it's not why we built the system this way. Planning transactions has other advantages:
When you plan a purchase before making it, you're being intentional. You've thought about timing, checked your Safe to Spend, confirmed it fits your budget.
Unplanned purchases aren't bad, but seeing them as 'unplanned' creates awareness. You're not guilting yourself—you're just seeing the truth.
We all have subscriptions we forgot about. When they renew:
If planned → Expected charge, auto-matches, no surprise
If unplanned → 'Wait, am I still paying for that? Do I use it anymore?'
Many users discover subscriptions they want to cancel simply because the charge appears as unplanned.
Your electric bill is usually $85. You plan for $90 to be safe. It charges $142 this month.
Pluto flags it: 'Amount differs from planned by $52'
You investigate: meter reading error, get it corrected.
Without planning, that $142 might have looked normal. After all, utility bills vary, right?
In shared workspaces, both partners see planned transactions. If one person makes an unplanned purchase, the other sees it flagged.
This isn't about permission or surveillance—it's about shared awareness. 'Hey, I see an unplanned $200 charge. Did you buy something I should know about?' 'Oh right, car needed new tires. Emergency repair. Let me add that retroactively.'
Transparency prevents surprises and enables collaboration.
Some people worry: 'If I plan every transaction, isn't that data vulnerable?'
Fair concern. Here's how we handle it:
Planned transactions contain:
We don't store:
All data encrypted at rest and in transit. Bank connections use OAuth, not stored credentials. Even if our database were compromised, your financial data is encrypted.
Only you (and workspace members you invite) see your planned transactions. We don't sell data, don't share with advertisers, don't train AI models on your spending.
Your budget is yours. We're the tool, not the data broker.
To get the most fraud detection benefit from Pluto:
Start with your recurring bills and subscriptions. These are the easiest to plan and create the baseline of expected transactions.
Set these up once as schedules. Pluto generates planned transactions automatically.
When considering a purchase over $50-100, add it as a planned transaction before buying. This:
Make it a habit to open Pluto briefly each day. Not to stress about money—just to stay aware. Check Safe to Spend, review any flagged transactions, confirm matches.
This 30-second habit is your fraud detection shield.
Free tier users can enter transactions manually, but Premium users with bank connections get automatic imports every few hours. This speeds up fraud detection from 'next time you check your bank' to 'next time Pluto syncs.'
If a transaction appears as unplanned and you don't recognize it, investigate immediately. Don't dismiss it as 'probably something I forgot.'
Legitimate unplanned purchases are things you know you bought. If you don't remember buying it, that's a red flag.
We didn't set out to build fraud detection. We built a budgeting system around a simple idea: planning transactions before they happen gives you better control over your money.
The fraud detection benefit emerged organically from that design. When you plan your financial life at the transaction level, anything unplanned stands out.
This is the opposite of most feature development: usually you identify a problem (fraud), then build a solution (detection algorithm).
We built a solution to a different problem (forward-looking budgeting), and it happened to solve fraud detection better than purpose-built fraud tools.
Sometimes the best innovations are the ones you don't plan for.
Back when I was using spreadsheets to manage my money, I thought I was hacked because my bank balance kept shrinking quickly. As it turns out, I wasn't hacked, I was just really bad at keeping track of my spending. That's why I built Pluto!
Josh Randall - Founder of Pluto Budgeting