GitHub Team Subscription Stuck – Manual Repayment Not Being Triggered

[ill-admin]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Hello everyone,

I'm experiencing an ongoing billing issue with our organisation's GitHub Team subscription and would appreciate some guidance from anyone who has encountered something similar.

My team's subscription has hit the limit, and this is affecting our ability to use GitHub Actions and execute deployments.

We have made several attempts to resolve the issue, but the payment process does not appear to be progressing.

What we have tried so far:

1. Updated our payment method using three different credit cards.

2. Each card was successfully saved to our GitHub billing account.

3. We received card verification notifications from our bank, including a transaction notification for a GitHub card verification.

However, GitHub has not initiated the actual subscription repayment.

Despite these attempts, the subscription remains stuck, and our GitHub Actions workflows and deployments continue to encounter errors.

We have also submitted a support ticket to GitHub, which has remained open for several days without a response.

Has anyone experienced a similar issue, particularly with a GitHub Team organisation subscription?

We have already tried multiple payment methods, so we would appreciate suggestions that address the underlying billing issue rather than simply recommending another card.

This is becoming increasingly urgent because it is affecting our development and deployment activities.

Any guidance or assistance would be greatly appreciated.

[ilhamwahyuj]

GitHub’s billing system does not always automatically re-trigger a failed charge immediately when a new card is added. Because your GitHub Actions minutes and seats are locked due to past-due status, here is what typically resolves the lock and how to unblock your pipeline:

---

1. Manually Trigger the Past-Due Invoice Payment

Simply saving a new card often only runs a card authorization probe ($0 or $1 verification), leaving the pending balance unsettled.

• Navigate to your Organization Settings > Billing and plans > Payment history (or Invoices).
• Locate the unpaid / past-due invoice.
• Click Pay now (or Retry payment) directly next to the outstanding charge to force GitHub's payment processor (Stripe) to charge the new default card on demand.

---

2. Check Actions Spending Limits

If the subscription fee is current but your Actions runs are blocked, you likely reached the monthly included minutes limit:

• Go to Billing and plans > Spending limits.
• If your Actions spending limit is set to $0 (the default stop-gap), workflows halt as soon as free/included minutes run out, regardless of saved payment methods.
• Increase the spending limit above $0 to allow metered overage billing.

---

3. Immediate Workaround to Unblock Deployments

• Use Self-Hosted Runners / ARC: Since the topic references ARC (Actions Runner Controller), note that self-hosted runners consume zero GitHub Actions billing minutes. You can temporarily switch urgent deployment jobs from runs-on: ubuntu-latest to self-hosted labels (runs-on: [self-hosted, arc-runner]) to bypass GitHub-hosted runner quota locks while the billing state reconciles.

---

4. Escalate the Existing Ticket

• Community members cannot manually trigger charges or clear billing flags.
• In your open ticket, reply with the explicit subject/flag "Past Due - Production Down / Deployment Blocked" and include the last 4 digits of the verified card, the outstanding invoice number, and authorization timestamps. Billing tickets affecting production access receive elevated priority when marked as service-impacting.

[AnuragVerma777]

Since you've already tried multiple verified payment methods, I would focus on identifying whether the issue is with the outstanding invoice, the organisation's billing status, or the payment processing system.

A few things worth checking:

1. Check the invoice status: Under Organization Settings → Billing and licensing, review the outstanding invoice and confirm whether it is marked as unpaid, past due, or payment failed.

2. Verify the default payment method: Make sure the newly added card is actually selected as the default payment method, not simply saved to the billing account.

3. Check for payment failure details: Look for any billing notifications or error messages associated with the invoice. A successful card verification does not necessarily mean the actual invoice charge was approved.

4. Ask Support for a billing-side review: Since multiple cards have already been tested, ask GitHub Support to investigate the failed payment attempts and confirm whether a manual payment retry or billing-status correction is required.

I would avoid repeatedly adding more cards until GitHub confirms the reason the payment is not being initiated.

One important detail that could help narrow this down: does the invoice show as Past Due, or does it show as Unpaid without any failed payment attempt?

That distinction may help identify the next troubleshooting step.

[christoferpedrosanchezzuzunaga-eng]

Hi @ill-admin,

When a payment fails and the automated retry doesn't clear the suspension, the payment gateway usually places a cooldown lock on that specific card.

The quickest way to unblock the organization without waiting days for billing tickets:

1. Go to Organization Settings > Billing and plans > Payment information.
2. Add a different credit card or link a business PayPal account as the primary payment method.
3. Linking a new payment method triggers an immediate authorization charge for the outstanding balance, clearing the account lock automatically within minutes.

[christoferpedrosanchezzuzunaga-eng]

Hi @ill-admin,

When a payment fails and the automated retry doesn't clear the suspension, the payment gateway usually places a cooldown lock on that specific card.

The quickest way to unblock the organization without waiting days for billing tickets:

1. Go to Organization Settings > Billing and plans > Payment information.
2. Add a different credit card or link a business PayPal account as the primary payment method.
3. Linking a new payment method triggers an immediate authorization charge for the outstanding balance, clearing the account lock automatically within minutes.