Skip to main content
[email protected] 24/7 Support
Menu

Support review of PremiumFakes

posted by idguyidk 20 hours ago 98 views 0 comments

I opened a support ticket with PremiumFakes about ten days ago to address a discrepancy between the proof I approved and the card I received. Writing up the experience because the PremiumFakes support thread in the forum is mostly people asking questions rather than sharing actual documented outcomes.

The issue: the expiration date on my card printed as one year later than what I'd entered in the order form and approved on the proof. Not my error — I double-checked my proof approval screenshot and the date was correct in the proof. Something changed between proof approval and production.

I submitted the ticket with: order number, photo of the received card showing the expiration date, screenshot of the proof showing the correct date, and a short description of the discrepancy. I kept the message factual and didn't editorialize about what caused the error.

First response came on day four. The support message acknowledged the discrepancy, confirmed that the proof and the card didn't match, and offered a replacement at no charge. No argument, no request for additional documentation, no asking me to prove it was their error. That part was handled well.

I replied accepting the replacement and confirming my shipping address on day four. As of today — day ten — I'm still waiting for confirmation that the replacement is in production. The acceptance reply hasn't been followed up with a status update. This is the frustrating part of PremiumFakes support: the initial response was reasonable, but the follow-through has been slower than expected.

I'll update this when the replacement arrives. Based on the initial handling, I have confidence they'll make it right — the question is just timeline. My overall read is that PremiumFakes will resolve legitimate warranty claims, but plan for the process to take longer than you'd want.

20

No comments yet. Be the first to comment!

Please login to comment on this thread.