Skip to main content
← Back

Billing and payments

Understand your billing cycle, renewals, payment methods, and invoices.

How does my billing cycle work?

Your cycle starts on the date you subscribe. It renews monthly or yearly based on your plan.

  • Individual plans renew on your signup date
  • Teams plans renew on the team signup date
  • Renewal dates stay the same when members are added or removed

When does included usage reset?

Included usage resets with your billing cycle.

  • Individual plans reset monthly
  • Teams plans include usage per paid seat each cycle, based on seat type (Standard or Premium)
  • Usage beyond included amounts appears as on-demand usage

What can create charges before renewal?

You can see charges between renewal dates when one of these events happens:

  • On-demand usage is billed after included usage is consumed
  • Team seats are added mid-cycle and charged pro-rata
  • Team seat removals can create billing adjustments or credits

How do seats work on a Teams plan?

Cursor bills teams per active paid seat, not pre-allocated seats. Seat price depends on the seat type (Standard or Premium).

  • Adding a member mid-cycle creates a pro-rated charge
  • Removing a member who used credits keeps the seat occupied until the cycle ends
  • Billing adjustments appear on a future invoice as credit when applicable

How do I update my payment method?

  1. Go to cursor.com/dashboard/billing
  2. Click Manage Subscription to open the Stripe billing portal
  3. Update your card in the Stripe billing portal

How do I update billing details for invoices?

Update your company name, address, and tax details in the Stripe billing portal. Changes apply to future invoices.

Where do I find invoices and receipts?

Go to cursor.com/dashboard/billing and click Manage Subscription. In the Stripe portal, open any invoice to view or download the PDF. See Invoices for details.

What if I still need billing help?

Contact support while signed in to your Cursor account and include invoice IDs, dates, and a short issue description.

Was this article helpful?