MY HUSBAND HAD BEEN TAKING MONEY FROM OUR RETIREMENT — BUT IT WASN’T GOING TO HIS ACCOUNT

The brokerage confirmed the withdrawals were authorized online. But the receiving account belonged to the wedding venue in Toledo, and the payer’s name was Bailey’s. I asked the representative to read me the dates. January 15th. February 15th. March 15th. Six identical transfers. I hadn’t paid for anything related to that wedding, and Bailey had told everyone she didn’t want me there. Then I remembered something my husband had said weeks earlier: “Don’t worry about the wedding. I’ve got it handled.” I had assumed he meant with his own money.

I confronted him that night. He didn’t deny the withdrawals. He said Bailey had called him crying because the wedding was over budget, and he couldn’t stand watching his daughter struggle. I asked why he’d used the account holding the money from my mother’s house. He said it was our retirement, so it was his money too. Then I asked why the payments were going directly to the venue instead of Bailey. He stared at the floor and finally admitted Bailey had told him the venue would cancel everything if the remaining balance wasn’t paid. She’d also told him I would never agree to give her another dollar.

I called the brokerage the next morning and froze every withdrawal. Then I asked for the complete transaction history. There was one more transfer scheduled for Friday — and it was nearly twice the amount of the others. I canceled it before it went through. That afternoon Bailey called me for the first time in months. She didn’t apologize. She asked whether the “final payment” had cleared. I said no. She went silent and then said, “Dad promised me you wouldn’t find out until after the wedding.” I looked at my husband sitting across from me and realized the wedding wasn’t the only thing he’d been paying for. There was something else on the statement, dated three days before the first wedding payment, and the description simply said: “Deposit — new account.”

Leave a Reply

Your email address will not be published. Required fields are marked *