No payments possible.

[rajeshkanakarajan]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Body

My organization has been billing-locked because of an outstanding GitHub Actions payment. However, I am unable to update the payment method or complete the payment. I tried with multiple credit cards. The weird thing is "Pay Now -> Save Payment Information" does not save anything, it simply stays Green and on clicking nothing happens, no errors no feedback.

Steps to reproduce

1. Open Billing and licensing → Payment information.
2. Enter a valid credit or debit card.
3. Click Save payment information.

Actual result

Nothing happens after clicking the button:

• No error message is displayed.
• No loading indicator or redirect appears.
• No payment request is generated in the Network tab.
• No OTP, 3-D Secure verification, or bank authorization is initiated.

I have tested multiple eligible cards using Chrome and Firefox, including Incognito/Private mode and a different network. The result is always the same.

Firefox shows that the Zuora payment page’s reCAPTCHA Enterprise script is blocked by the page’s Content Security Policy:

https://www.recaptcha.net/recaptcha/enterprise.js

The blocked script uses reCAPOnloadZuoraCallback. This may be preventing the payment form from completing its validation and submitting the payment information.

Expected result

The payment information should be saved successfully, or the page should display a clear validation or payment-processing error.

Is anyone else experiencing this issue? Could the GitHub Billing team investigate the Zuora/reCAPTCHA integration or provide an alternative way to pay the outstanding invoice?

I have already opened a GitHub Support ticket, but the issue remains unresolved.

A similiar discussion exists, but it is closed without resolution, need urgent help, help me please
https://github.com/orgs/community/discussions/205266

[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. ⭐

[techscribr]

Facing exact same issue since last 2 weeks on my personal github account. Raised support ticket with all the details (similar to yours - logs from firefox dev console) - but no response so far. Funny thing is, people are willing to pay and they are not even bothering to fix it. This should be taught as a case study in schools on how to lose (paying) customers.

[developercommit]

I'm facing exact same issue