The strange thing about money that keeps arriving
Here is a detail almost no founder plans for: when you die, your business does not stop earning. The subscriptions renew on schedule. Stripe or Paddle or PayPal keeps charging cards, keeps netting out fees, keeps queuing payouts. For days or weeks, the machine you built runs exactly as you designed it. Money keeps coming.
It just stops being reachable.
This is the part that surprises families most. They imagine the problem will be a dead business — a silence, an empty account. Instead they find a live one: revenue flowing into a system nobody can open, settling toward a bank account nobody can drain, governed by a contract that quietly voided itself the moment you stopped being alive to honor it.
Understanding why is worth a few minutes, whether or not you ever do anything about it. Because the failure isn't technical. It's a collision between three institutions that each, individually, are behaving correctly.
The payout has nowhere safe to land
Start with the bank account. Your processor doesn't hold your money indefinitely; it sweeps it, on a rolling schedule, into the business checking account you linked at signup. That cadence is the whole point — it's why your balance doesn't just pile up at Stripe.
Now the account holder dies. Banks have a firm, old rule for this: when they receive notice of a depositor's death, they freeze the account. Not out of cruelty — to protect the estate from anyone draining it before a court decides who's entitled. Standing authorizations stop. Debit cards stop. And here's the cruel symmetry: incoming deposits often stop too, or land in an account that no living person can withdraw from until probate appoints someone.
So the processor faithfully pushes a payout. The bank faithfully refuses to release it. Both are right. The money is real, it's earmarked, and it's locked between two institutions that aren't allowed to talk to your family yet.
The contract was with a person, and the person is gone
The deeper trap lives in the processor's terms of service. When you opened that Stripe or PayPal account, you didn't open a neutral utility. You signed a contract, as an individual or an officer, and that contract is built on a requirement you can no longer satisfy: that you are who you say you are.
Payment processors live under KYC and AML rules — Know Your Customer and Anti-Money Laundering. These aren't optional politeness; they're legal obligations baked into the global financial system to stop fraud and laundering. The processor must, on an ongoing basis, be able to verify that the human behind the account is real, identifiable, and authorized.
A dead account holder cannot be re-verified. There is no document a grieving spouse can upload that makes the processor's compliance system see you again. The identity at the center of the account has simply gone dark. And because most processor agreements are personal and explicitly non-transferable, your executor doesn't inherit the account — they inherit a contract that has lost the party it was written for.
The usual outcome is not a smooth handover. It's account suspension pending review, a support queue that was designed for fraud disputes rather than death, and a request for documents — a death certificate, letters testamentary, proof of estate authority — that take weeks or months to obtain. All while the meter keeps running.
Reserves, chargebacks, and the long tail of liability
There's one more layer, and it's the one that turns a freeze into a genuine financial loss.
Processors hold a rolling reserve — a slice of your revenue kept in escrow against future chargebacks and refunds. For a subscription business, that liability doesn't die when you do. Every customer you charged still has months in which their bank can claw back a payment. If your product quietly stops working because no one is maintaining it — a server lapses, support goes unanswered — those customers will, reasonably, dispute the charges.
Now picture the sequence. The account is frozen. Payouts are stuck. But chargebacks keep landing, drawn against a balance no one is feeding. The reserve drains. In some cases the estate ends up owing the processor — a negative balance built from refunds on a service the deceased can no longer provide. Money that looked like an asset becomes a debt, accruing in silence, addressed to someone who may not even know the account exists.
This is the quiet horror of unmanaged recurring revenue: left alone, it doesn't just stop paying. It can invert.
Why "my spouse knows my password" doesn't solve it
The instinct is to fix this with access. Share the login, leave the 2FA codes, make sure someone can get in.
Access helps, but it isn't the lock. Even a family member logged into your dashboard cannot make the processor's compliance system believe a dead person is still verifying their identity. They cannot change the destination bank account to a living one without triggering exactly the re-verification that's impossible. They cannot transfer the contract, because the contract says they can't. Logging in lets them see the trapped money. It doesn't unfreeze it.
What actually moves money out of this trap is legal standing — an appointed executor, a death certificate, court documentation — paired with knowing the account exists in the first place. And that second half is where most families lose the most time. They can't unfreeze what they never knew to look for. A processor doesn't send the estate a letter; it just suspends, reserves, and waits. The revenue you were proud of becomes a needle in a haystack of forgotten logins.
What's actually worth doing
The useful response isn't to obsess over any one processor's policy — those change. It's to make three things findable by the person who'll have to act for you.
First, an inventory. A plain list of every place money enters or rests: the processors, the connected bank accounts, the merchant-of-record services. Not credentials — existence. The single hardest problem your family faces is not access; it's awareness.
Second, the legal path written down. A note that says, in human language, this account is governed by a contract that requires legal proof of death to release funds; here is the documentation you'll need, and here is who to call. You're writing instructions for someone in shock, not a fellow engineer.
Third, a decision about the live revenue. Should the service be wound down gracefully to stop the chargeback bleed? Refunded? Sold? Your family can't make that call under deadline pressure with no context. You can make it now, calmly, in a sentence.
None of this requires a lawyer's afternoon. It requires admitting that the most automated, hands-off part of your business — the recurring revenue you stopped thinking about — is also the part most likely to strand the people you love.
Where this fits
This is exactly the gap Heirloom was built to close. It's a death-binder for solo founders: one vault where your payment processors, linked bank accounts, and the legal steps to release them live together, handed to a named beneficiary the moment it's needed — so the people you leave behind inherit money they can actually reach, not a frozen account they never knew to find.
You built something that earns while you sleep. It's worth ten quiet minutes to make sure it doesn't keep earning while it's locked away from everyone who needs it. You can start your binder at https://heirloom.lumenlabs.works.