Critical Bug: "Session Bleed" during Enrollment - Payment renewed wrong account despite correct UI

I experienced a severe backend session handling error where the payment gateway used a wrong billing token, despite the frontend UI explicitly displaying the current user's details. This resulted in an accidental renewal of a different developer account.

  1. The Setup You opened the Developer App and logged in as ____. You filled in your details correctly (Name: AB, Last Name: CD). The screen confirmed this: "You are paying for ____."

  2. The Action You pressed the Enroll/Pay button. You approved the payment with your card/UPI.

  3. The Invisible Switch (The Bug) At the exact moment you clicked "Pay," the Apple App didn't look at the screen you were seeing. Instead, it looked deep into your phone’s history and said: "Wait, I know this phone! This phone belongs to an old account that already has a membership. I'll just renew that one."

  4. The Result The system took your money and sent it to the Old Account it remembered from history, completely ignoring the New Account (____) that was right there on the screen.

  5. The Outcome

New Account (____): Still says "Pending" because it never got the money.

Old Account: Got renewed instantly because the system prioritized the "device history" over the "logged-in user."

It was a bait-and-switch by the app. You clicked "Pay" for AB, but the wire connected to Old Friend.

Thanks for the very detailed post.

We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to Developer Account I would recommend you to contact the developer account support at https://developer.apple.com/contact to make sure they are aware of the issue.

Albert Pascual
  Worldwide Developer Relations.

Critical Bug: "Session Bleed" during Enrollment - Payment renewed wrong account despite correct UI
 
 
Q