[Bug] Claude refuses to enter Stripe test card numbers on a staging environment (only allows localhost); worked in earlier versions
Bug Description
During QA on our own app's staging environment (a public .up.railway.app URL, Stripe in test mode), Claude refused to type Stripe's published test card (4242 4242 4242 4242) into the app's payment form. It said it can only enter card numbers, even test ones, on local hosts (localhost / .test), and that explicit user authorization does not change this.
Expected
Entering a payment provider's published test card on a staging/QA environment of the user's own app, in test mode, should be allowed. It is standard QA practice and carries no financial risk.
Actual
Claude declines and asks the user to type the card manually, which blocks automated QA of payment flows.
Regression
Earlier Claude Code sessions on the same project entered Stripe test cards on the same staging and UAT environments without issue (as recently as 2026-09-24).
Impact
QA passes that need a new test charge can no longer be completed end to end. In our case Claude built the test data first and only then refused, which wasted time.
Repro
- Point Claude at a non-localhost staging URL of your own app with a Stripe test-mode checkout.
- Ask it to complete a payment with card 4242 4242 4242 4242.
- Claude refuses, citing the local-host-only rule.
Environment Info
- Platform: darwin
- Terminal: WarpTerminal
- Version: 2.1.284
- Feedback ID: 68dfced6-8edb-4a1c-8eed-e034fcfb4062