ePlaya

hello everyone!

I registered my burner profile for the ticket sale tomorrow, but my boyfriend was not able to. I have a ticketfly account of my own and had planned on using his credit card to purchase our tickets. I'm wondering if this is going to be an issue. I tried to research myself, and I'm seeing that "technically" one is allowed to purchase tickets under a different name than the burner profile, but it just makes everything more difficult.

Basically, registration and ticketfly is in my name, but billing and shipping would be to my boyfriend's name. How much of a problem will this cause? Is there anything I can do before tickets go on sale to make our lives easier?

Having a CC in the same name as the billing and shipping may be sufficient, but who really knows if the "name on the order" in "The name on the credit card used to purchase is the name on the ticket order" means the shipping/billing name or the profile/ticketfly account name. You could try emailing them to see what they say, but there is not much time.

In the end, if you don't have a payment method under your name, what choice do you have? Go for it and see how it turns out. Maybe email after the sale if you're fortunate enough to be able to buy something.

In this years pre-sale we weren't asked for a credit card name just the number, expiry and security code.

A camp buddy used my credit card on their Ticketfly account to purchase tickets in their name no problem.

I expect the new system is to make allowance for the use of prepaid over the counter credit cards.

This was a Will Call pickup order I don't know if that makes any difference.

You got this ginger! You should be fine.

If you're successful in the sale, you should send an email to [email protected] with your order # and pertinent details to explain the situation.

Burning Man does a few rounds of 'de-duping' to look for known and new scalpers, as well as flag suspicious purchases for human review (that's not an automatic canceling of the order, but more of a yellow alert that requires more behind-the-scenes work). The credit card (and yes they know from the numbers) should match the name on the TFly order as well as the Burner Profile, or it will likely be flagged for human review. If you do get through and send them an email, they should be able to add notes on the order on their end that not only ensure everything goes smoothly for you, but is easier for them on the back end.

Good luck!

Thanks for the insight everyone! Crossing my fingers for this sale!

trilobyte wrote:If The credit card (and yes they know from the numbers) should match the name on the TFly order as well as the Burner Profile, ............!

That's an interesting comment, it appears to contradict  PCI Data Security Standards.

If the only data stored is the last 4 numbers of a credit card number how is it possible to recall client information at a later date?

Actually, it is. A card name would be verified at the point of sale (and not stored), and immediately trigger a name does not match flag and it's the flag that would stay on the file. Later, the review team could see burner profile details, ticketfly account details, and whether the name matched the account at the time of transaction.

trilobyte wrote:.......... Later, the review team could see burner profile details, ticketfly account details, and whether the name matched the account at the time of transaction.

If the name on the credit card is not stored how is it possible to conduct such an audit?

A retrospective review requires conformation data. as in: Do the names match the accounts at the time of transaction.

I'd suggest taking your questions up with the ticket support team.

LukyPhil wrote:If the only data stored is the last 4 numbers of a credit card number how is it possible to recall client information at a later date?

They wouldn't actually have to store all of the numbers. A one-way hash of the card number would enable them to check whether the same card was being used for multiple transactions, but wouldn't be reversible to the original number.

Papa Bear wrote:

LukyPhil wrote:If the only data stored is the last 4 numbers of a credit card number how is it possible to recall client information at a later date?

They wouldn't actually have to store all of the numbers. A one-way hash of the card number would enable them to check whether the same card was being used for multiple transactions, but wouldn't be reversible to the original number.

Not sure about now, but I know for sure a couple of years ago this was being checked post... like very post... it might have been hashed but if the system wasn't smart enough to check for the same CC at POS, then I'm gonna assume it wasn't fancy enough to hash the credit card numbers.