Subs that rebill monthly keep dying at month two — what's holding for you?

Pattern I've now seen on four different cards and I'd like to know if it's universal or if I'm doing something wrong.

First charge on a new subscription: fine, always. Second charge, thirty days later: fine, usually. Third charge: dead, roughly half the time.

It is not the balance. It is not the amount, which is identical every month by definition. What I think is happening is that the first charge is a fresh authorisation and the later ones come through as a merchant-initiated transaction against a stored credential, and something in that flow stops matching. IME the response looks like this:

auth_type: MIT / recurring
result: declined
reason: 14 - invalid card number

Reason 14 on a card number that worked twice already is nonsense on its face, which is what makes me think it's the stored-credential handshake rather than the card.

Anyone actually running monthly rebills past six months on one card? Which one, and did you do anything specific to keep it alive?

14 means the merchant's stored token expired and they re-sent a stale PAN. nothing to do with your card

That would explain it happening on all four. Is there anything I can do about that from my side or is it purely the merchant's problem?

re entering the card every month here. tedious but it works

re-enter the card every few months before it happens. tedious, works

Your diagnosis is close but there's a second thing going on that only affects this category.

Several of these providers rotate or reissue the underlying number more often than a bank would — sometimes silently, sometimes as part of a BIN migration on their side. When that happens the merchant's stored credential is genuinely stale and you get exactly the response you posted. Bleap is the one I've seen this on most: one-off purchases fine, renewals dying, and there's a whole thread on the board about that specific behaviour.

The cards that hold longest for me are the ones where the number is stable for the life of the card and the provider says so. PrivCards and Vyrion have both carried monthly subs for me past the six-month mark without a re-entry.

Grindstone's advice is still the right operational answer though. Re-enter the card at month four whether or not you think you need to.

I have this logged because it annoyed me too. Eighteen subscription lines across three cards, tracked from first charge to first failure:

Charges survived before first decline	Lines
1-2	3
3-5	7
6-11	4
12+ (still alive)	4

Median is four. Your "third charge, half the time" is a bit pessimistic against my data but it's the same shape, and the cluster at 3-5 is real rather than noise.

What I cannot separate from this is which failures were the merchant and which were the issuer, because the decline reason is written by whoever declined and neither of them is honest about it.

median of four charges. so a monthly sub on these cards has a working life of a third of a year. that's the actual headline and everyone's discussing decline codes

Past six months on which card, and how many lines? "Both have carried subs for me" could be two subscriptions and it reads like a fleet.

Four lines across the two, oldest is fourteen months. Small sample and you're right to ask.

Eleven weeks of doing the re-enter-at-month-four thing across nine subscription lines. Two failures in that window, both on lines I forgot to re-enter.

So the workaround holds and the underlying problem is untouched, which is roughly where I expected to land. I've automated the reminder rather than the fix:

0 9 1 */3 * /home/ops/bin/notify "re-enter cards on billing pages"

Not marking this solved. A calendar entry is not a solution, it's an admission.

A cron job to re-type card numbers. 2025 in one line!