Of course, YMMV, this is just what my bank does.
Yes. Anyplace that bills you regularly on the old number will automatically get the new number.
> You can't continue to use the old number for new transactions.
It depends on how you define new. A new biller, then correct. But if it's a biller that you have an existing relationship with, i.e. they bill you every month, then they do send them the new numbers (and/or allow them to use the old number).
I can't say if this is a global policy of all issuers, but I can say that I've experienced it. I've also seen it in the fine print when I signed up for repeated billing.
Here's an older Braintree blog post about it: https://www.braintreepayments.com/blog/automatic-update-of-c...
It doesn't look like they can. Uploading apps to the app store is done via iTunes Connect. That's always been a separate login from the developer center, and it has not been down during the current dev center outage.
So? Who cares about credit card data - it so easy to just send a list of compromised numbers to the banks and get new numbers. I've been sent new cards at least twice without being told why they are changing the number, except for some nebulous "security measure", so they clearly do do this.
Of all things to worry about credit card numbers hardly rank.
I don't know how it works - but can the breach allow attackers to upload modified apps in the name of the developer?