{"version":"2.1.284","anchor":"extra-usage-inline-dialog-buy-select-is-handled-before-the","canonical_anchor":"extra-usage-inline-dialog-buy-select-is-handled-before-the","heading":"Buying extra usage checks for a saved card before checking the usage lookup","tier":"notice","area":"Usage & Limits","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/extra-usage-inline-dialog-buy-select-is-handled-before-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Buying extra usage checks for a saved card before checking the usage lookup\n\nIn the extra-usage buy flow, Claude Code now checks for a saved card before looking at whether fetching your usage worked\n\n**Unclear.** The exact difference you would see is not settled.\n\n**What**\n\nWhen you choose to buy extra usage from the in-app dialog, Claude Code now checks for a saved payment card first, before looking at whether your usage details loaded:\n\n- With no card on file, it sends you to the browser, even if loading your usage failed.\n\n- With a card on file, it goes straight to the buy step.\n\nBefore, this step ran only after the usage lookup and its error handling.\n\n**Why**\n\nThe buy flow may now open in cases where it used to show an error.\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}