Look what Taylor made her do.
A 25-year-old woman claimed that she waited in the now-infamous virtual queue for tickets to Taylor Swift’s “Eras” tour and was charged 14 times for tickets that she never received.
Sydney Wallace told Insider that she entered her credit card information before the onslaught of fans and managed to score a couple of tickets to the “Love Story” singer’s concert. However, when she went to check out, she claimed SeatGeek would not let her complete the purchase.
The site “would not let me checkout,” Wallace said.
Then, she claimed she was rerouted to get new tickets several times and each time, ticket prices increased.
The chaos left a blank space in her bank account and cause it to be flagged for potential fraud.
“Waited in line for @taylorswift13 tickets for 8 hours today. And @SeatGeek charged me 14+ times for tickets I was never able to purchase,” tweeted Wallace alongside bank statements.
“So now my bank accounts (happened on multiple cards) are frozen, I’m broke, it overdrafted my accounts, and I did NOT get tickets.”
In total, Wallace said that the tickets left her $9,000 in overdraft fees.
Wallace reportedly reached out to SeatGeek in an attempt to get her money back.
“After talking with their live chat, they said that none of the charges resulted in a ticket purchase and that I had to wait 3-5 business days to receive a refund,” claimed Wallace.
According to SeatGeek, the charges should shake off after 24 hours, and she would still be able to secure tickets during the public sale on Friday — which was postponed by SeatGeek.
The Post reached out to Swift, SeatGeek and Wallace for comment.
Wallace said that her bank “has been really nice about it” and since removed the overdraft fees.
“Well. It goes without saying that I’m extremely protective of my fans,” Swift shared on Instagram.
“It’s really difficult to trust an outside entity with these relationships and loyalties and excruciating for me to just watch mistakes happen with no recourse.”
The Tennessee Attorney General pledged to investigate what caused the site to crash.