A flower shop in Phoenix. October, which the owner described as the busiest month the shop has ever had. Money left the business's payment account over a few days, more than $126,000 of it. When it was gone, he took out a loan to cover payroll and bills.
That last sentence is the story. Not the account, not the platform, not the technical details nobody outside the business will ever fully reconstruct. A business owner borrowed money so his people could get paid on time while he tried to get answers about where the money went.
The instinct when you read something like that is to look for the mistake. Somebody reused a password. Somebody skipped the two-factor step. Somebody clicked something.
We do not know that, and neither does the reporting. What we know is worth more, because it applies to almost every small business reading this: the payment account is the least-defended system in the business, and it is the one where the money already sits.
Short answer
Many small businesses protect their email and computers but leave the payment platform to whoever handles the books. Yet that platform is where the money already is. Useful safeguards include giving people separate access based on what they need to do, enabling multi-factor authentication (MFA) for every user, requiring a second approval for payout or bank-detail changes, and sending payout alerts to someone who will read them.
Most of these controls do not require a special IT budget. Many are available in the platformâs own settings. They may not explain or prevent every incident, but they can reduce exposure and help a business notice changes sooner.
What we know, and what we donât
According to FOX 10 Phoenix, a Phoenix flower shop owner reported that more than $126,000 was removed from the companyâs Stripe account. The unauthorized activity began in October, and the funds were taken over a few days. It happened during what the owner described as the shopâs busiest month on record.
The owner said he took out a loan to cover payroll and bills while trying to resolve the situation with Stripe. He also described difficulty getting progress on escalated support tickets. He contacted local law enforcement and the FBI.
The reporting does not establish how access was obtained. It does not establish that the owner or anyone on the team lacked MFA, reused a password, or acted carelessly. It does not establish that Stripe was breached. Stripe had not responded to the station at publication.
That distinction matters. When the cause of an incident is unknown, guessing can lead to fixing the wrong thing. The useful response is to review the controls a business can check, not to claim certainty about what happened.
And the most important detail is the loan. This is not only a data-security story. It is a payroll story: money needed for the business and its people was suddenly unavailable.
Why payment platforms can be a soft spot
Payment platforms are built to move money efficiently. They connect to bank accounts, process payments, and may support refunds and payouts. Those capabilities are useful, but they also make account access important.
Businesses often treat these platforms as ordinary software rather than as a system that can affect cash flow. Access may be shared among whoever needs to reconcile transactions, handle refunds, or manage payouts. Over time, a bookkeeper, family member, former employee, or the person who set up the account years ago may still have access.
A bank account is usually treated with obvious caution. A payment-platform login can feel more like a routine software account. That difference in perception can leave an important financial system without the same careful review.

Five controls that can reduce the risk
1. Find out who can get in
Review every user on the payment platform. Record their role and, where the platform provides it, when they last logged in. Remove access for anyone who no longer needs it.
This is a practical first step because it answers a basic question: who can reach the account today? Set aside about 20 to 30 minutes to do the review, then repeat it when someone changes roles or leaves the business.
2. Turn on MFA for every user
Enable MFA on the payment account itself, and check that it is active for each user, not only the owner. MFA adds a verification step beyond a password.
It is important to be honest about what this does and does not mean: because the cause of the Phoenix incident is unknown, we cannot say that MFA would have prevented it. MFA is still a baseline safeguard for accounts that can access business funds.
3. Separate viewing from moving money
The person reconciling transactions may need to see payments without being able to send payouts or change account details. Where the platform offers roles and permissions, use the most limited role that still lets each person do their job.
This wonât make an account impossible to misuse. It can, however, reduce what one user can do if their login is compromised or used in error.
4. Require a second approval for payout changes
A change to bank or payout details can redirect where money goes. Where possible, require a second person to review and approve such a change. Keep the approval process clear enough that people will follow it during a busy day.
5. Turn on useful alerts
Enable notifications for payouts, refunds, and logins from new devices, if those alerts are available. Send them to an inbox or phone that a responsible person actually checks.
A silent dashboard is not monitoring. An alert only helps when someone sees it and knows what to do next.
The one rule for banking changes
No bank or payout detail changes because of an inbound call, email, chat, or message. Verify the request using a number you looked up yourself, confirm it with a person you can identify, and have a second human approve the change.
That rule applies whether the message appears to come from a vendor, a colleague, a payment platform, or someone claiming to be technical support. A familiar name or urgent request is not verification.
| Control | Time to set up | What it helps prevent | Illustrative value |
|---|---|---|---|
| Enumerate payment-platform users | About 20â30 minutes | Forgotten or unnecessary access | Makes account access visible so outdated users can be removed |
| Enable MFA for every user | About 10 minutes per user | Password-only access | Adds a verification step beyond a password |
| Split view and move permissions | About 20 minutes | A single login having more access than its user needs | Limits what one account can do, where roles support it |
| Require second approval for payout changes | About 10 minutes, plus a policy | Unreviewed payout redirection | Adds a human check before a high-impact change |
| Enable payout and new-device alerts | About 5 minutes | Changes going unnoticed | Can help prompt a quicker review; hours rather than weeks is an illustrative goal, not a measured result |
These times and values are planning examples, not measured results. The exact options depend on the payment platform and the businessâs setup.
If it happens to you: the first 48 hours
If you spot unauthorized activity, move quickly while preserving a clear record of what happened:
- Contact the payment platform and your bank immediately. Make contact in writing as well as through available urgent support channels. Keep copies of messages, case numbers, and responses.
- Preserve records. Save account alerts, transaction details, emails, and screenshots. Do not clean up or delete evidence before it has been documented.
- Report the incident. Contact local law enforcement and submit a report to the FBIâs Internet Crime Complaint Center. IC3 says its reports help the FBI collect information about cyber-enabled crime, though it cannot guarantee a response to every complaint.
- Tell your insurer early. Many cyber policies require prompt notice. Some policies also require payment verification using a previously known phone number. Check your own policy and follow its reporting requirements.
- Secure the account and its recovery path. Change the payment-platform credentials and rotate the password for the email account attached to it. That email may be used to reset access or receive security notices.

What this has to do with us
We are not in the payment-platform business, and we do not manage Stripe. But we can help with the surrounding work that is easy to overlook: finding business logins, documenting who has access, reviewing whether people still need it, and making sure written procedures are available when a request comes in.
That is part of the practical value of managed IT services in Phoenix: before we can protect an account, somebody has to know it exists and who can reach it. That inventory work is unglamorous and it is usually where the real surprises live, because most owners have never seen a complete list of the logins attached to their business.
If you would like to talk through how account access and approval rules fit into your business, you can schedule an introductory call. No scare tactics, just a chance to identify practical next steps.
Takeaways
- List everyone who can access the payment platform, and remove anyone who no longer needs it.
- Enable MFA for every user, not just the account owner.
- Separate the ability to view transactions from the ability to move money.
- Require a second approval for bank or payout detail changes.
- Send payout alerts to a person who will see and act on them.





