BLACKHATMAPAffiliate & infrastructure forum

usdtcryptocard — anyone getting geographic blocks on card attempts?

Started 28 Sep 2026 · 14:12 · 8 replies · 634 views

Page 1 of 19 posts

paulofrz

Member

28 Sep 2026 · 14:12#1

I have been testing USDTCryptoCard from Brazil this week. The card loads fine, the balance shows, but every card transaction attempt declines with a generic 'not authorised' error.

I tried with three different merchants — one local, one US-based, and one EU-based. All the same decline. Support has not responded in two days.

The terms mention availability in 'most countries' but do not list exclusions. Wondering if LATAM is blocked and they just do not say it, or if this is a technical issue on their end.

Anyone in this region actually got a transaction through?

5 thanks

grindstone

Senior Member

28 Sep 2026 · 14:28↑ replying to #1#2

check the decline code

—

paulofrz

Member

28 Sep 2026 · 14:35↑ replying to #2#3

It is not showing a code in the app, just the error message. I will try to get it from the merchant side.

—

hana_v

Member

28 Sep 2026 · 15:02↑ replying to #1#4

I am in Singapore and the card works here without issues. Did a $45 transaction yesterday and a $120 one today, both cleared immediately.

This sounds like a regional block rather than a technical failure. A lot of these cards have different BIN ranges that are approved or blocked by the card network depending on the issuing region. The issuer might not even know it is happening — the network is filtering at the routing level.

If you can get the decline code, look up the first two digits. That will tell you if it is a network-level block (usually 05 or 51) or an issuer-level decision (usually 07 or 57).

8 thanks

vlad_ptk

Member

28 Sep 2026 · 15:41↑ replying to #1#5

Have same problem from Moldova. Card load, balance show, but transaction decline. I try with VPN to different countries — same result.

Is not merchant blocking. Is card itself blocked for my region. Support finally reply and say 'we are reviewing availability in your jurisdiction'. This is not helpful answer.

3 thanks

Ravenstack

Senior Member

28 Sep 2026 · 16:12↑ replying to #5#6

'Reviewing availability' is code for 'we do not accept your jurisdiction and will not say why'. If they were actually reviewing, they would give you a timeframe.

2 thanks

paulofrz

Member

28 Sep 2026 · 16:38↑ replying to #5#7

Thanks for confirming my friend. At least I know it is not just me. I will move on to another option for now.

—

nullroute

Senior Member

28 Sep 2026 · 17:05↑ replying to #1#8

The broader lesson here: test with a small amount before loading a card that you cannot easily withdraw from.

You loaded funds that are now stuck on a card that will not spend in your region. If the issuer will not reverse the load, that money is gone unless the region unblocks or you find a way to spend it elsewhere.

For no-KYC cards, the exit strategy matters as much as the entry. If you cannot withdraw to self-custody, you are at the mercy of the card network's geographic filters.

4 thanksopsec is a process, not a purchase

paulofrz

Member

13 Oct 2026 · 14:22↑ replying to #8#9

Update my friend: they finally reversed the load after I threatened to dispute the transaction. Took 10 days but got the money back.

—

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