Unknown Email in Stripe Checkout for X Premium

radhouanex

Newbie
Joined
May 30, 2024
Messages
7
Reaction score
1
Hi

I’m trying to subscribe to X (Twitter) Premium through the website, but when I reach the Stripe checkout page, an unknown email appears in the "Contact Information" field.

I haven’t used this email, and I’m worried if I proceed, that email might get my payment info or receipt.

Has anyone faced this issue? How can I fix it or change the email? Will paying through the X mobile app (Google Play) avoid this problem?

Thanks for any help!
 
Paying through the app is fine and should work just as well (I think, needs checking out if that still holds up) but I'm more concerned about the unknown email you're describing. It's difficult to visualise what you're saying exactly, but I'd be concerned about whether or not you're hit by some sort of malware that auto-fills certain fields and such. Think you'd be able to provide some imagery of where or what the unknown email is exactly?
 
Paying through the app is fine and should work just as well (I think, needs checking out if that still holds up) but I'm more concerned about the unknown email you're describing. It's difficult to visualise what you're saying exactly, but I'd be concerned about whether or not you're hit by some sort of malware that auto-fills certain fields and such. Think you'd be able to provide some imagery of where or what the unknown email is exactly?
The unknown email shows up pre-filled in the Stripe checkout contact info. A while ago, I shared my checkout link with someone who offered to pay for me, but they didn’t. Could that be the reason?

I’ve subscribed via the app instead, but I’d like to understand this issue better. Do you think it’s related to that, or could it be something else?
 
The unknown email shows up pre-filled in the Stripe checkout contact info. A while ago, I shared my checkout link with someone who offered to pay for me, but they didn’t. Could that be the reason?
Yeah, I'd say that's probably what caused it. Barring cashing issues, browser auto-fill, or something related to using a shared device, I can't imagine how else that could have happened.
 
Back
Top