Last Friday, I nearly wrote off a final payment
I was delivering a website for a freelance client in Shenzhen when they said the payment page kept spinning. A regular customer might simply retry. But when we run small businesses, the worst outcome is when they think the money never left and we think it never arrived—then both sides start chasing each other. Banking systems do fail sometimes. The article mentions outages involving Bank of America, Chase, U.S. Bank, Wells Fargo, and Zelle. I panicked too: if receiving payments stayed unstable, would the client move to someone else?
Instead of waiting for the system to recover, I did this
I set up a “backup receiving channel”: the main channel handles normal payments, while a second platform or bank account is used to verify transactions when the main channel fails. In my order sheet, I record the payment reference, amount, and arrival status. My friend Chen Min, who does design outsourcing in Hangzhou, said her team normally keeps only one receiving account. During system maintenance, a client’s payment record becomes unclear, and they can spend at least half an hour messaging each other. My process is simple: I stop sending new payment codes, then check the status through the bank or platform’s notice. When the payment genuinely cannot be credited automatically, I switch to a manual transfer method both sides have agreed on and keep the receipt. It isn’t a new tool. It’s more like keeping an umbrella beside the cash register.
Today’s setup is cheap to replicate
Replication cost: roughly RMB 0–50 for an additional account or platform, depending on the provider; about 60 minutes to organize the process. The technical barrier is low: copy a payment link and check arrival records. First step: open the “backup payment method” or “add account” page in my current payment platform and see whether I can add an independent channel. If not, I ask the bank’s relationship manager how manual transfers, arrival checks, and proof of payment work. A free spreadsheet can track the client, order, amount due, payment time, and status. There’s no need to start with a complicated system.
I’d Prepare According to My Current Client Volume
If I’m just starting and have only a handful of clients each month, I’d keep a manual-transfer backup plan before buying another service. Once I have one or two stable clients, I’d add a second receiving platform and put “how soon payment is confirmed after transfer” into the quote or contract. If my team is scaling, I’d also set up daily reconciliation, alerts for unusual orders, and a handover checklist so the next person knows which payment is stuck. Not everyone needs this setup. Pure cash transactions or teams with reliable finance support may never use it. If I’m not ready to organize everything today, I can simply note which step took the longest during my last payment outage.