[BUG] Gift code silently consumed when redeemed over active subscription. Never applied after first gift expires

Resolved 💬 2 comments Opened Jun 3, 2026 by choidavid4 Closed Jun 6, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

A gift subscription code ($60 / 3 months) was redeemed while the recipient already had an active gift subscription on their account. The system accepted the redemption without any warning or error. Once the first gift expired, the 3-month subscription was never applied. The code now shows as "no longer available" and the $60 is effectively lost.

What Should Happen?

The second gift code should queue and activate automatically once the first subscription expires. At minimum, the system should warn the user at redemption time that redeeming while a subscription is active may cause the new gift to not apply correctly.

Error Messages/Logs

Gift code status after first subscription expired: "no longer available"

No error was shown at redemption time — the UI confirmed the redemption as successful.

Steps to Reproduce

  1. Recipient has an active gift subscription on their Claude account
  2. Purchaser buys a 3-month gift code ($60) and sends it to the recipient
  3. Recipient redeems the gift code while the first subscription is still active
  4. System shows redemption as successful — no warning shown
  5. First gift subscription expires
  6. Second gift is never applied — code shows as expired/unavailable

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.161 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This is a billing system bug — the gift redemption flow silently consumes codes without queuing or warning when another subscription is already active.

Support was contacted via Fin AI. Case was fully documented but not resolved.
Fin AI conversation ID: 215474508749714

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗