Ok, so people have been posting they are having problems with using game time cards as the codes on them are invalid. So I wanted to make a post of my issue telling you exactly what happened and how ZOS resolved the issue.
First I do like the game. I would like to see some changes and fixes come down the pipe but all in all, I get my enjoyment out of it. That being said I am not always a subscriber. I buy 1-2 game time cards and throw them on the shelf for those rainy days when I want to sub but don't have the money available. I purchased 2 cards from Gamestop back on July 25, 205. I threw the cards on the shelf, let my current sub lapse, used the crowns I had stored and purchased IC. Now I went to use one of the cards this past Saturday and it did not work, invalid. OK, lets try the other card... also invalid. Tried calling ZOS customer support... on hold for an hour. So, I sent an email and explained the issue.
Later that same day, much later to be honest, I received an e-mail telling me they needed pictures of the front and back of the game time cards and a proof of purchase. Proof of purchase would be the receipt or invoice I received when purchasing the cards. I no longer had the receipt as they were purchased 6 weeks ago or so. No problem, went back o Gamestop, had them search for the receipt and print it out. Have to say they were very helpful at Gamestop but without proof I was out my $60 bucks for the cards. Came home and snapped a bunch of pictures that I emailed to ZOS customer support. They replied saying they were escalating the issue.
Woke up this morning, it is Thursday now ,to an email with new codes in it to apply to my account. So, a big hearty thank you to the guy at Gamestop for helping me out and to ZOS customer support for solving the dilemma. So for those having this issue, hope you have your receipt, if not just back to the place of purchase and see if they can get it reprinted and simply e-mail ZOS customer support the pictures. Problem solved. Though I would like to not have the problem in the first place, but still solved.
Thanks again ZOS, but please work on not having this issue in the future.