BLACKHATMAPAffiliate & infrastructure forum

Card was fine for three weeks, now declines everywhere, balance still shows

Started 19 Feb 2026 · 09:14 · 8 replies · 617 views

Page 1 of 19 posts

d_marchetti

Jr. Member

19 Feb 2026 · 09:14#1

Sorry if this is the wrong section, I nearly put it in newbie corner but it's a card question so I figured here is better. Mods move it if not.

Background in case it matters. I set the card up at the end of January after reading about half this board. PayPaw, through the bot, took maybe fifteen minutes exactly like people said it would. First three weeks were completely fine — eleven or twelve charges, mostly small recurring things and two hosting invoices, nothing above $90.

Since Tuesday every single transaction declines. Not one has gone through, including the two subscriptions that had already billed successfully twice before. The balance is still sitting there in the dashboard, $340 and change, and there's no notice, no email, nothing saying the card is frozen or restricted or anything at all.

Merchant end just says the payment was unsuccessful, contact your card issuer. The card issuer is a Telegram bot that hasn't answered in two days.

Has anyone had this and actually got it back? Or is that balance just gone.

—

grindstone

Senior Member

19 Feb 2026 · 09:41↑ replying to #1#2

what does the decline actually say. "unsuccessful" is not an error code, there's a number behind it and the number is the only thing here that tells you whether it's your card or their checkout

—

d_marchetti

Jr. Member

19 Feb 2026 · 10:26↑ replying to #2#3

I don't get a number anywhere. It's a checkout page that turns red and says the payment could not be processed, that's the whole message. Is there somewhere else I should be looking for it? Genuinely don't know what I'm supposed to be reading here, sorry.

—

PipelineRat

Member

19 Feb 2026 · 12:03↑ replying to #1#4

IME you will never see the real code out of a hosted checkout, they swallow it deliberately so people don't card-test against the message. So stop chasing it.

What's worth separating before anyone starts guessing:

  1. declined by the issuer — your card, your balance, their risk engine
  2. declined by the acquirer or the merchant's own rules before it ever reached the issuer

One merchant breaks and then it spreads, that's usually 2 leaking into a shared processor. Every merchant at once from a specific day, all categories, is 1.

Cheapest test in the world: find something that charges a dollar and run it. Not a subscription, not a retry of one that already failed — a fresh single charge at a merchant you've never used. If a $1 auth at a new merchant also dies, you've ruled out limits, ruled out the merchant, and you know the problem is upstream of everything you control.

Do that before you top up another cent, because the failure mode where people lose money here is topping up to "fix" a card that was never going to authorise again.

11 thanks

crypt97

Jr. Member

19 Feb 2026 · 12:19↑ replying to #3#5

and a bot is not an issuer, mate

—

hana_v

Member

19 Feb 2026 · 23:47↑ replying to #1#6

This shape — works for weeks, then nothing anywhere, dashboard balance untouched — is usually the BIN rather than your account.

These programs don't issue anything themselves; they sit on a range from a sponsor bank. When the sponsor pulls the program, every card on that range stops authorising the same afternoon, while the balance keeps displaying perfectly, because the balance is a number in their own ledger and the authorisation isn't.

Run PipelineRat's dollar test. If it dies, issue a second card on the same account and compare the first six digits against the old one. Different range and it authorises, you've confirmed it and you spend the balance down through the new card. Same range, don't put another cent anywhere near it.

23 thanks

nullroute

Senior Member

20 Feb 2026 · 08:12↑ replying to #6#7

Disagree, and the disagreement is not academic because it changes what he does next.

BIN pulls are loud. A range dies and there are four threads about it here by the next morning, not one confused Jr member. This is one confused Jr member.

Twelve charges in three weeks, small recurring amounts, digital goods and hosting, almost certainly from one device on one address. That is a profile, and the profile got scored. Programs with no identity on file compensate with behavioural risk scoring, and "small repeating charges at digital merchants" is close to the centre of what they're watching for, because it is also what card testers look like. They don't freeze you and they don't tell you, they just quietly stop approving, because telling you is how people learn to route around it.

Which means issuing a second card on the same account confirms nothing. The account is what's flagged, and the new card inherits it.

19 thanksopsec is a process, not a purchase

hana_v

Member

20 Feb 2026 · 09:05↑ replying to #7#8

Fair on the noise point in general, but I've watched a range go quiet with nothing posted about it anywhere. Most people holding these cards aren't on a forum, they just shrug and move on.

Either way the first test is the same one, and the first six digits tell us which of us is right.

—

d_marchetti

Jr. Member

22 Feb 2026 · 18:31#9

Reporting back. Dollar charge at a merchant I'd never used, declined. Issued a second card, the number starts with the same four digits as the old one — I don't know if that means the same range or not — and the dollar charge on the new card declined too. Didn't top up anything.

Bot still hasn't replied, six days now.

So I don't really know which of you is right and I'm not sure it matters much from where I'm sitting. Going to leave it over the weekend and see. Thank you both, and PipelineRat especially, I'd have had no idea what to even test otherwise.

—

You must be logged in to reply. Request an account — new registrations are reviewed by a moderator before approval.