Detailed Analysis
A recurring payment processing failure is preventing at least some Claude.ai users from upgrading from the Pro tier to the Max (20x) subscription plan, with affected users reporting that multiple credit cards from multiple financial institutions all produce the same error message: "Payment failed. Please try again later." The specificity of the failure pattern is notable — the user in question tested four cards across four separate banks, confirmed with each bank that no transaction block was applied on their end, and observed that the attempted charges appeared either as $0 amounts or as paired credit/debit entries that effectively canceled each other out. This strongly suggests the failure originates within Anthropic's payment stack rather than at the card-issuer level.
The technical hypothesis advanced by the affected user points to a race condition in Anthropic's Stripe integration, specifically a scenario in which a void_invoice call cancels the underlying Stripe PaymentIntent on the server side — reportedly around 42 seconds into the checkout process — before the client-side confirmation can complete. If accurate, this is a backend timing defect, not a client configuration issue. The user's methodical elimination of alternative causes — Stripe Link caching, browser or cache artifacts, and the mobile in-app purchase bypass path — lends credibility to this server-side diagnosis. The IAP workaround being unavailable due to an account email mismatch further narrows the remediation options available without direct support intervention.
The support experience described compounds the problem. Anthropic's Fin-powered support chatbot reportedly loops users through generic troubleshooting steps without escalating to human agents, leaving users with a billing defect and no clear resolution path. This is a meaningful friction point: the Max plan represents Anthropic's highest direct-to-consumer offering and the primary way individual users access greater compute capacity. Failures at this conversion step — particularly ones that survive multiple payment methods and explicit bank confirmation — represent both lost revenue and a degraded user experience at a critical juncture in the customer journey.
The incident reflects a broader operational challenge facing AI companies scaling their consumer subscription infrastructure rapidly. As Anthropic expands its tiered product lineup and processes increasing transaction volumes, the reliability of payment orchestration systems becomes a first-order concern. Stripe race conditions of the type described here — where server-side invoice lifecycle events outpace client-side checkout flows — are a known class of integration defect in high-volume SaaS billing, but they become more acute as transaction concurrency increases. The fact that multiple users appear to be encountering the same pattern, as implied by the poster's reference to "a growing list of users hitting this bug," suggests a systemic rather than isolated issue that likely requires a backend configuration or webhook timing fix rather than anything a user can resolve independently.
Read original article →