i got error U521 both times. There is no way I was beat both times
Noblesville 5.7.2010. Lexington 4.26.2016. Nashville 9.16.2022. St Louis 9.18.2022. Chicago 1 9.5.2023. Chicago 2 9.7.2023. *Noblesville 9.10.2023* (Gutted) Seattle 5.30.2024 Noblesville 8.26.2024 Chicago 8.29.2024 Chicago 8.31.2024
I've had SO many of these tickets in my cart. I really, really, really loathe the stupid credit card text code feature.
YES!! That CC text feature is BRUTAL. I've yet to come up with any workaroudn for it. I've tried every CC I have in the wallet and they all do it. I'm guessing its a feature turned on by TM but I could be wrong. Are the people scoring the tix getting prompted for a text code?!?!
Same - I've gotten that error AT LEAST 8 times this morning.
Right. I've gotten it before when I seemingly was right on it. So my question is, am I just wasting my time doing this? It seems like a fool's errand at this point.
Same - I've gotten that error AT LEAST 8 times this morning.
Right. I've gotten it before when I seemingly was right on it. So my question is, am I just wasting my time doing this? It seems like a fool's errand at this point.
starting to feel that way
Noblesville 5.7.2010. Lexington 4.26.2016. Nashville 9.16.2022. St Louis 9.18.2022. Chicago 1 9.5.2023. Chicago 2 9.7.2023. *Noblesville 9.10.2023* (Gutted) Seattle 5.30.2024 Noblesville 8.26.2024 Chicago 8.29.2024 Chicago 8.31.2024
I've had SO many of these tickets in my cart. I really, really, really loathe the stupid credit card text code feature.
YES!! That CC text feature is BRUTAL. I've yet to come up with any workaroudn for it. I've tried every CC I have in the wallet and they all do it. I'm guessing its a feature turned on by TM but I could be wrong. Are the people scoring the tix getting prompted for a text code?!?!
did you add a c/c to your TM profile? I just click which card I want to use, add the 3 digit code and it's done
Remember the Thomas Nine !! (10/02/2018)
1998: Noblesville; 2003: Noblesville; 2009: EV Nashville, Chicago, Chicago 2010: St Louis, Columbus, Noblesville; 2011: EV Chicago, East Troy, East Troy 2013: London ON, Wrigley; 2014: Cincy, St Louis, Moline (NO CODE) 2016: Lexington, Wrigley #1; 2018: Wrigley, Wrigley, Boston, Boston 2020: Oakland, Oakland:2021: EV Ohana, Ohana, Ohana, Ohana 2022: Oakland, Oakland, Nashville, Louisville; 2023: Chicago, Chicago, Noblesville 2024: Noblesville, Wrigley, Wrigley, Ohana, Ohana
I've had SO many of these tickets in my cart. I really, really, really loathe the stupid credit card text code feature.
YES!! That CC text feature is BRUTAL. I've yet to come up with any workaroudn for it. I've tried every CC I have in the wallet and they all do it. I'm guessing its a feature turned on by TM but I could be wrong. Are the people scoring the tix getting prompted for a text code?!?!
My understanding is that it’s an anti fraud device used by the card issuer. The cards in my TM account don’t ask for the code, which I suspect is true of most who are scoring
Same - I've gotten that error AT LEAST 8 times this morning.
Right. I've gotten it before when I seemingly was right on it. So my question is, am I just wasting my time doing this? It seems like a fool's errand at this point.
I've had SO many of these tickets in my cart. I really, really, really loathe the stupid credit card text code feature.
YES!! That CC text feature is BRUTAL. I've yet to come up with any workaroudn for it. I've tried every CC I have in the wallet and they all do it. I'm guessing its a feature turned on by TM but I could be wrong. Are the people scoring the tix getting prompted for a text code?!?!
Yeah, I was thinking yesterday that maybe it has something to do with F2F? I have never had to go through the text/enter code feature except for F2F. Someone said it's the CC driving it...but I've tried five separate ones (Citi MC/Chase Visa/Capital One Visa/AMEX) and I was prompted with all of them.
07/28/1992 - Cincinnati 07/11/1998 - Las Vegas 07/22/2006 - The Gorge 04/26/2016 - Lexington 08/08/2018 - Seattle 08/10/2018 - Seattle 08/20/2018 - Wrigley Field 04/02/2020 - Nashville 09/16/2022 - Nashville
I've had SO many of these tickets in my cart. I really, really, really loathe the stupid credit card text code feature.
YES!! That CC text feature is BRUTAL. I've yet to come up with any workaroudn for it. I've tried every CC I have in the wallet and they all do it. I'm guessing its a feature turned on by TM but I could be wrong. Are the people scoring the tix getting prompted for a text code?!?!
My understanding is that it’s an anti fraud device used by the card issuer. The cards in my TM account don’t ask for the code, which I suspect is true of most who are scoring
Yup - my card is loaded in TM and ready to go. I've tried an Amex and a Visa and each one is prompting me for the code. What is odd is that I was able to purchase a pair of Indy lawn on F2F about a week ago and wasnt prompted for a code. Since then I've been much more active on the TM page (refreshing, etc) in an attempt to find pavilion seats and when a pair does pop up it is now requiring the text code. Maybe TM is suspecting my increased activity as "bot" activity and it's a way to slow my activity- who knows.
is anyone familiar with code u521? thats what i get every time
Noblesville 5.7.2010. Lexington 4.26.2016. Nashville 9.16.2022. St Louis 9.18.2022. Chicago 1 9.5.2023. Chicago 2 9.7.2023. *Noblesville 9.10.2023* (Gutted) Seattle 5.30.2024 Noblesville 8.26.2024 Chicago 8.29.2024 Chicago 8.31.2024
I've had SO many of these tickets in my cart. I really, really, really loathe the stupid credit card text code feature.
YES!! That CC text feature is BRUTAL. I've yet to come up with any workaroudn for it. I've tried every CC I have in the wallet and they all do it. I'm guessing its a feature turned on by TM but I could be wrong. Are the people scoring the tix getting prompted for a text code?!?!
My understanding is that it’s an anti fraud device used by the card issuer. The cards in my TM account don’t ask for the code, which I suspect is true of most who are scoring
Yup - my card is loaded in TM and ready to go. I've tried an Amex and a Visa and each one is prompting me for the code. What is odd is that I was able to purchase a pair of Indy lawn on F2F about a week ago and wasnt prompted for a code. Since then I've been much more active on the TM page (refreshing, etc) in an attempt to find pavilion seats and when a pair does pop up it is now requiring the text code. Maybe TM is suspecting my increased activity as "bot" activity and it's a way to slow my activity- who knows.
I don't think it's driven by TM or your activity or else I would be getting coded and I never do It's a bank thing. Could be the lawn tickets were cheap enough not to trigger it but the higher price did
Has anyone successfully scored F2F drops via the TM app? Does the app also trigger a CC text verification?
Oh a few 😂 I've seen it on the app. It's about finding the right card or having a spending pattern that doesn't trigger the fraud alert
Can you refresh on the app? thats why I use browser
Noblesville 5.7.2010. Lexington 4.26.2016. Nashville 9.16.2022. St Louis 9.18.2022. Chicago 1 9.5.2023. Chicago 2 9.7.2023. *Noblesville 9.10.2023* (Gutted) Seattle 5.30.2024 Noblesville 8.26.2024 Chicago 8.29.2024 Chicago 8.31.2024
I've had SO many of these tickets in my cart. I really, really, really loathe the stupid credit card text code feature.
YES!! That CC text feature is BRUTAL. I've yet to come up with any workaroudn for it. I've tried every CC I have in the wallet and they all do it. I'm guessing its a feature turned on by TM but I could be wrong. Are the people scoring the tix getting prompted for a text code?!?!
My understanding is that it’s an anti fraud device used by the card issuer. The cards in my TM account don’t ask for the code, which I suspect is true of most who are scoring
Yup - my card is loaded in TM and ready to go. I've tried an Amex and a Visa and each one is prompting me for the code. What is odd is that I was able to purchase a pair of Indy lawn on F2F about a week ago and wasnt prompted for a code. Since then I've been much more active on the TM page (refreshing, etc) in an attempt to find pavilion seats and when a pair does pop up it is now requiring the text code. Maybe TM is suspecting my increased activity as "bot" activity and it's a way to slow my activity- who knows.
I don't think it's driven by TM or your activity or else I would be getting coded and I never do It's a bank thing. Could be the lawn tickets were cheap enough not to trigger it but the higher price did
If that were the case, I'm wondering if you couldn't just call your "bank" i.e...customer service number on the back of your card, and ask/tell them that temp charges coming from "Ticketmaster" or "Live Nation" are not fraudulent. But like @PJammin said, who knows. But it would really help to know.
07/28/1992 - Cincinnati 07/11/1998 - Las Vegas 07/22/2006 - The Gorge 04/26/2016 - Lexington 08/08/2018 - Seattle 08/10/2018 - Seattle 08/20/2018 - Wrigley Field 04/02/2020 - Nashville 09/16/2022 - Nashville
Comments
Sorry, Something Went Wrong.
What does that even mean? Happened on both sets. Tried again and it said another fan beat me to it, which was no surprise.
But if it brings you joy have at it
1998: Noblesville; 2003: Noblesville; 2009: EV Nashville, Chicago, Chicago
2010: St Louis, Columbus, Noblesville; 2011: EV Chicago, East Troy, East Troy
2013: London ON, Wrigley; 2014: Cincy, St Louis, Moline (NO CODE)
2016: Lexington, Wrigley #1; 2018: Wrigley, Wrigley, Boston, Boston
2020: Oakland, Oakland: 2021: EV Ohana, Ohana, Ohana, Ohana
2022: Oakland, Oakland, Nashville, Louisville; 2023: Chicago, Chicago, Noblesville
2024: Noblesville, Wrigley, Wrigley, Ohana, Ohana
Chicago 1 9.5.2023. Chicago 2 9.7.2023.
*Noblesville 9.10.2023* (Gutted)
Seattle 5.30.2024 Noblesville 8.26.2024 Chicago 8.29.2024 Chicago 8.31.2024
Chicago 1 9.5.2023. Chicago 2 9.7.2023.
*Noblesville 9.10.2023* (Gutted)
Seattle 5.30.2024 Noblesville 8.26.2024 Chicago 8.29.2024 Chicago 8.31.2024
1998: Noblesville; 2003: Noblesville; 2009: EV Nashville, Chicago, Chicago
2010: St Louis, Columbus, Noblesville; 2011: EV Chicago, East Troy, East Troy
2013: London ON, Wrigley; 2014: Cincy, St Louis, Moline (NO CODE)
2016: Lexington, Wrigley #1; 2018: Wrigley, Wrigley, Boston, Boston
2020: Oakland, Oakland: 2021: EV Ohana, Ohana, Ohana, Ohana
2022: Oakland, Oakland, Nashville, Louisville; 2023: Chicago, Chicago, Noblesville
2024: Noblesville, Wrigley, Wrigley, Ohana, Ohana
1998: Noblesville; 2003: Noblesville; 2009: EV Nashville, Chicago, Chicago
2010: St Louis, Columbus, Noblesville; 2011: EV Chicago, East Troy, East Troy
2013: London ON, Wrigley; 2014: Cincy, St Louis, Moline (NO CODE)
2016: Lexington, Wrigley #1; 2018: Wrigley, Wrigley, Boston, Boston
2020: Oakland, Oakland: 2021: EV Ohana, Ohana, Ohana, Ohana
2022: Oakland, Oakland, Nashville, Louisville; 2023: Chicago, Chicago, Noblesville
2024: Noblesville, Wrigley, Wrigley, Ohana, Ohana
07/11/1998 - Las Vegas
07/22/2006 - The Gorge
04/26/2016 - Lexington
08/08/2018 - Seattle
08/10/2018 - Seattle
08/20/2018 - Wrigley Field
04/02/2020 - Nashville
09/16/2022 - Nashville
Chicago 1 9.5.2023. Chicago 2 9.7.2023.
*Noblesville 9.10.2023* (Gutted)
Seattle 5.30.2024 Noblesville 8.26.2024 Chicago 8.29.2024 Chicago 8.31.2024
Chicago 1 9.5.2023. Chicago 2 9.7.2023.
*Noblesville 9.10.2023* (Gutted)
Seattle 5.30.2024 Noblesville 8.26.2024 Chicago 8.29.2024 Chicago 8.31.2024
07/11/1998 - Las Vegas
07/22/2006 - The Gorge
04/26/2016 - Lexington
08/08/2018 - Seattle
08/10/2018 - Seattle
08/20/2018 - Wrigley Field
04/02/2020 - Nashville
09/16/2022 - Nashville