TL;DR: enter card details manually, not using Link, if you need to change your payment method and it’s stuck.

Three days ago my Claude Pro subscription was up for renewal but I’d forgotten to top-up the prepaid credit card I use for this. It was (logically) declined and my subscription was suspended. 

I was using Link as the payment method.

No sweat, I thought, I’ll top up the credit card and “try again”. No luck, still declined. 

Cool cucumber, I’ll just use another card this month. Clicked through to select an other payment method, but… once I was back on the Anthropic payment screen, the active payment method displayed was still the first card that had been declined.

What I did:

What I got:

Then I went a bit wild. I tried to change the payment method again. I went into Link and removed the card, leaving only the second one, but the payment was still attempted by Anthropic (Link?) with the card I had removed  

I logged out of Link and back in. I even tried Apple Pay. My card transaction statement shows a string of $0 card checks, and my inbox is full of e-mails telling me my payment was unsuccessful, but that is all that there is to show for these efforts. Whatever card I chose, Anthropic insisted on trying the same one again and again.

At some point, inspiration hit and I tried settling the open subscription invoice from inside Link directly, with my other card, instead of through the Anthropic billing screen. That worked! 

But I wasn’t out of the woods. I wanted to buy some extra usage (I know, I know). The same frustrating dance started again, to no avail. 

I decided to let it rest 24 hours and try again.

I tried again today. Same same.

In desperation (of course I’d already had a frustrating chat with Fin the Anthropic “support bot” and sent an e-mail to support) I tried chatting up the Link support chatbot. It confirmed that there was indeed a trace of the failed purchase on their side. At least something! I requested a human, and started chatting up my credit card’s support too, as I now had a clear indication that the purchase request had left Anthropic’s walls.

I’ll spare you the hour of slow, mind-numbing, half-chatbot-half-human support chats. You’ve been there I’m sure. There would be a lot to say.

In the end, after going around in many more circles, here is what worked:

• I clicked to change the payment method on checkout on the Anthropic site
• I disconnected Link in there
• I entered my card details manually

What I did (notice how I’m not signing into Link here):

What I got (notice how this time I actually did manage to get it to switch to the Mastercard and drop the Visa!):

Lo and behold, the payment went through! 

(This is the second card, mind you, I’m not that crazy. Next step, before my next subscription invoice comes around, will be to try and make a purchase with the initial – preferred – card. Maybe by then the e-mail the service cyborg promised with details of why the transaction failed will have reached me.)

Sharing this in hope it can spare at least one other person some headaches.

See on Reddit.

End 2024 is when I really started to get going with “AI” (or LLMs – I know saying “AI” is kinda wrong, but there seems to be no good way to escape it right now). I’d been dabbling a bit before that: as a search engine, to help me with my excel formulas at work, or translating an e-mail here or there. But over that Christmas break, I realised it went further than that: helping me manage my tasks; keep lists updated; make sense of my investment portfolio; troubleshooting technical stuff that’s above my pay-grade; and build actual systems to do stuff. I didn’t really know what I was doing, but I saw enough to find it really exciting. I was quite busy with work and life during that period, and not finding time to blog much.

And then I had a skiing accident. Everything stopped, but in time, as I started becoming more functional, I turned back to playing with AI some more, doing a little more vibe-coding too. Excitement grew. But I was also hitting limitations, fed up with the sycophancy, context bloat, hallucinations and endless rabbit-holes. Oh, and really sick of AI slop. (Really: nobody wants to read your AI slop, people.) But the exciting was still there, I was just biding my time. Integrations, agents and AI-powered browsers showed up, with the security risks that are bundled in. I was tempted but stopped myself. And a few loved ones.

Three articles amongst many that tell cautionary tales. I have more to say, particularly about the brain fry one, but not today.

Recently, like many others, I jumped ship from ChatGPT to Claude. I’d been thinking about it for a while, because I have been working hard on migrating my diabetic cat community from Facebook to Discourse, and had come to the conclusion I would have to code a plugin or component or two, and it seemed obvious that Claude was the better AI assistant for that. Around that time, I read this article:

In it, the author describes one key aspect of working with AI that I had understood to be important, but that I didn’t know how to put into practice: using different conversations for different “roles” or aspects of the project. And here I had a real example.

I put that in practice (a bit as an exercise) in applying these instructions to migrate my personal context from ChatGPT to Claude. It was extremely satisfying and a great learning experience. I was itching to get going with Claude Cowork and Claude Code, but still a bit anxious. As I see it, Cowork is like being handed a powerboat when all you’re used to are the free permitless motorboats you can rent by the hour on a sunny Sunday afternoon like this one. You can really get in trouble if you’re not careful. And probably, even if you are.

I asked around a bit and Claire pointed me to this wonderful guide to Cowork. What she also explained to me is that Cowork is sandboxed, so it only has access to the folders you give it access to. That’s reassuring. And just a few days ago, Matt shipped Taxonomist, an AI-app (? what do we call these things?) that he used to cleanly recategorise all his blog posts. Unsurprisingly, categories here on CTTS have been a mess since time immemorial, and one of the things that has been clear for some time for me is that AI can help me clean things up a bit around here – in general, not just the categories. But that felt like a great way to get started seeing what the powerboat can do, with a trusted friend on board to keep me from crashing on the rocks.

So earlier today I installed Claude Desktop, downloaded the guide, and started it in Cowork. And wow. Honestly. It’s wild. My 3TB of archived files going back nearly three decades are now hopeful they will one day be deduplicated and cleaned up. Of course, I hit my usage limit (which is why I’m writing this instead of playing with my new AI friend), so I went to have a look at what something like Taxonomist really looks like under the hood. You know, open the files and read them. And it’s starting to come together in my mind. The powerboat is starting to feel like something I will be able to manage in time.

Of course, I’m not going to point Cowork at my external hard drive right now. There are still a lot of steps until I feel comfortable enough with the powerboat to attempt that. But doors are opening. My diabetic cat community migration feels more manageable. I’m hopeful I can tidy my files and clean up my blog. Come up with a system to make sharing links to the open web as easy as on Facebook. Reboot the blogosphere. And I’m sure other ideas will come along the way. I am also trying to be very, very careful about AI brain fry, as I already have my own concussion brain fry to deal with.

If you haven’t yet started learning how to use AI beyond as a proxy for Google or Wikipedia, really, it’s time to get cracking. I’m going back to Lesson 5 (honestly, just read through that page for starters if you don’t know what to do first), making a note to check out Cursor (I’m using Visual Studio Code for now) and read this article on Teaching AI to Design.

First, however: a nap.