Bitbucket LFS storage not auto-expanding on Standard plan despite active billing and payment method

[Michał Rafacz]

Hello,

I'm having an issue with Git LFS storage in Bitbucket and would like to clarify how the automatic storage expansion is supposed to work.

Our workspace is on the Standard plan and we have a valid payment method attached to the account. According to the documentation, my understanding is that when the included 5 GB of Git LFS storage is exceeded, additional storage should be billed automatically (e.g. $10 for an extra storage 100GB pack).

However, when I try to push a large Git LFS commit that exceeds the available storage, the push is rejected instead of triggering any automatic storage purchase. No additional charge appears, and the repository remains unable to accept the new LFS objects.

What I would like to know:

1. Is there any additional step required to enable automatic Git LFS storage expansion?

2. Does billing need to be manually activated somewhere beyond simply having a payment method attached?

3. Is there a delay between adding a payment method and Bitbucket being able to purchase additional LFS storage?

4. Are there any workspace-level or organization-level settings that can prevent automatic storage expansion?

5. How can I verify whether my workspace is actually eligible for automatic LFS storage purchases?

Thank you.