anomalyco / anomalyco/opencode

Payment Declined After 3 Months Despite No Issue With Card or Bank

Open
#45,278 21 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

What happened

My existing payment method is suddenly being declined when I try to renew my OpenCode subscription.

The same card has successfully been used for OpenCode payments for approximately three months. The problem started suddenly, and I have not changed the card.

My bank has confirmed that there are no blocks or problems with the card and that they do not see a declined transaction from their side.

Steps to reproduce
  1. Log in to my OpenCode account.
  2. Open the subscription/billing page.
  3. Start the payment/renewal process for the existing subscription.
  4. Select the previously used payment card.
  5. Submit the payment.
  6. The payment is declined and the subscription cannot be renewed.
Expected behavior

The payment should be processed successfully, as the same payment method has previously worked for approximately three months.

Actual behavior

The payment is declined and the subscription cannot be renewed.

The bank does not report a declined transaction, block, or other problem on their side.

Error message

The checkout reports that the payment/card was declined.

Additional context

I have already:

  • Verified that the card details are correct.
  • Tried adding the same card again.
  • Contacted my bank, which found no issue.
  • Contacted OpenCode support, but the responses I received did not resolve the problem.

This may be related to the existing payment issues reported in #43400, #43153, #35630, or #28408.

I would appreciate it if this could be investigated as a reproducible payment/checkout issue rather than simply being referred back to my bank, since the bank has already confirmed that there is no problem on their side.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing the checkout and renewal behavior alongside issues #43400, #43153, #35630, and #28408; the work is done when the cause of this declined renewal is identified and an affected existing subscription can renew successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
payments
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.