Why Your Sales Deposit Never Arrived
If you sold with a card and the deposit never hit your bank, there are three possible causes: it's not due yet, that charge never went through Stripe, or the deposit went out and the bank bounced it. The Deposits tab tells you which one.
Teresa runs a dry cleaner in Manzanillo with home pickup. She takes payments online through her site, had a good week, and Tuesday morning she opens her bank app expecting that week’s deposit. Nothing’s there.
She did what anyone would do: called the bank, who couldn’t tell her anything, and from there jumped to assuming her site was charging cards wrong. Neither one was the problem, and it took her two weeks and three deposits to figure that out.
If your sales deposit never showed up, the first move isn’t calling anyone — it’s figuring out which of three situations you’re in.
Why didn’t your sales deposit arrive?
When a sales deposit doesn’t show up, it’s almost always one of three reasons, and only one of them is an actual problem: it’s not due yet, that money never went through the pipeline that feeds your deposits, or the deposit did go out and the bank sent it back.
How do you know which one it is?
Open the Deposits tab in your site’s console. Each deposit is a row with its amount and status, and there are five possible statuses: pending, in transit, paid, failed, and canceled.
That’s enough to tell you which of the three you’re dealing with:
- There’s a row marked “in transit.” Nothing’s broken — that money just hasn’t landed in your bank yet. Deposits always arrive a few days after the sale, and never for the amount of a single order.
- There’s no row at all. Then that charge never went through this pipeline. Deposits is the history of your card payments via Stripe. If you got paid through your own Mercado Pago or PayPal account, that money went straight there and will never show up on this screen.
- There’s a row marked “failed.” A failed deposit is one that did go out toward your bank account and got sent back. That’s the case the rest of this post is about.
Quick tip for reading the list: a paid deposit shows its arrival date; a failed one shows none, because it never arrived.
And that’s exactly why this gets discovered late: charging a card and depositing the money are two separate stages, and your site only watches the first one. As long as you can accept cards, the cart works, the order comes through, and your customer is happy. When a charge breaks, a customer messages you the same day. When a deposit breaks, nobody messages you at all.
Is the money from a failed deposit lost?
No. Money that bounces goes back into your balance, which sits on that same screen, right above the deposit history. It’s still yours, and it’s still all there.
That row, though, won’t change. A failed deposit stays failed forever — it doesn’t flip to “paid” once the issue gets fixed. When the money finally does go out, it’ll be a brand-new deposit, with its own row and its own date. The old row just sits there as the receipt for what didn’t happen.
So there’s no point staring at that failed row waiting for it to change color. It’ll look exactly the same next month.
Why does a deposit bounce?
Because the bank on the other end couldn’t receive it. The reasons are boring and almost always about a typo: the account got closed, the business switched banks and nobody updated the info, the CLABE has a digit wrong, or the account just doesn’t accept that kind of deposit.
What took Teresa two weeks to understand is this: as long as the info stays wrong, the next attempt fails the same way. An unresolved failed deposit isn’t an isolated event — it’s the first in a line. She figured it was a one-off bank glitch and waited it out. Friday’s bounced too. So did the following week’s.
Where do you fix your bank account?
In the same console, under the Settings tab. From there you open your payments account panel, where you update your business details and the bank account you want the money sent to — all without leaving your site.
And here’s the part that sends a lot of people down a rabbit hole for an afternoon: you don’t have a separate Stripe dashboard. Your payments account gets created without its own login, so there’s no username or password to recover. Everything you need to touch lives in that one tab.
Once you fix the info, the money goes out on its own in the next payout cycle. You don’t need to request it — but it also doesn’t happen instantly: if this week’s cycle already ran, you’ll catch the next one.
Whenever something’s missing, a notice appears above that panel telling you exactly what. Read it even if it’s annoying — that notice is about as close as you get to someone actually flagging it for you.
A failed charge and a failed deposit aren’t the same thing
They sound alike and they’re opposite problems. Worth keeping them separate in your head:
- Failed charge: your customer’s card didn’t go through. No sale happened, and there’s no money. That gets resolved with your customer.
- Failed deposit: the sale did get charged, the money is yours, and it’s sitting safely. What failed was the last leg — from the processor to your bank. That gets resolved with your own details.
If you message a customer asking her to “pay again” for an order she already paid for, the second one was the actual problem.
How do you keep it from happening again?
Three habits, none of them take more than five minutes:
Treat your first deposit as a test, not a formality. The day you turn on card payments, the question isn’t “did I make a sale?” — it’s “did it land in my bank?” It’s the one moment you can catch a mistyped detail with zero pesos on the line.
The day you switch banks, update your info before the next payout cycle runs. Switching banks is one of those things everyone gets told except the place that actually matters.
Keep an eye on it right after a good week. That’s when the most money is in transit — and when missing a failed deposit costs you the most.
Describe it, and that screen comes built in
If you’re not taking payments through your own site yet, the console where you see your deposits isn’t something you have to set up separately — it comes with the site. You describe it in one line, the way Teresa would:
“I want a site for my dry cleaning business in Manzanillo, with home pickup and delivery, a price list by garment, and customers paying online when they book their pickup.”
Out comes your published site, with its own link, and with the console where you see your orders, your charges, and your deposits. It’s the same place where you edit your prices, so it’s not one more system to learn.
If you’re already taking card payments and have never opened the Deposits tab, open it today even if you’re not expecting anything. It takes a minute, and it’s the difference between catching the first bounce this week or catching it on the third.
You can describe your business and publish it at proyecta.dev.