Copilot Pro+ annual paid → account blocked due to billing mismatch (403)

[Dieg0bl]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot in GitHub

Body

’m experiencing a billing issue with GitHub Copilot that has resulted in my account being blocked despite having an active annual subscription.

Subscription
Copilot Pro+ yearly plan
Payment completed successfully (January 2026)
Subscription period: Jan 2026 → Jan 2027
Issue

After the annual payment, additional billing attempts appeared that do not correspond to a new subscription.

Some of these charges were:

Successfully charged (unexpected)
Later attempts were blocked intentionally via PayPal

After blocking those charges, my account entered a billing error state.

Current status
Error message: “We are having a problem billing your account”
Copilot access blocked (403)
Account flagged as past due
Verification

I checked usage and:

No additional consumption (Actions, Packages, Codespaces, etc.)

So the issue seems isolated to Copilot billing.

Problem summary

It appears the system is:

Attempting additional charges despite an active annual subscription
Marking the account as unpaid after those charges are blocked
Restricting access incorrectly
Question

Has anyone experienced a similar issue with Copilot Pro+ billing?

Is this related to:

duplicated subscription cycles
metered billing errors
or PayPal synchronization issues
Expected resolution
Correct billing state
Removal of invalid charges
Restoration of access

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐