BIN lookup · Mastercard · Canada · log through 13 Sep 2026 14:40 UTC

BIN 239896: Canada Mastercard Virtual Card (Prepaid)

The takeaway

The range did well against Cursor, v0.dev, Perplexity AI. We logged 194 successful authorizations out of 271 attempts across the test window.

239896Mastercard CanadaPrepaid 194/271 cleared

There is not much to say about a BIN until you test one, so we ran 239896 from HUTAO Cards against a live checkout and kept the log. Results below, including the two places it failed.

The spec sheet

BIN
239896
Card network
Mastercard
Issuing country
Canada
Card type
Prepaid
Issued by
HUTAO Cards
Card form
Virtual only
KYC tier
No KYC
3-D Secure
No
AVS check
No
Billing address
Not published
Funding methods
Crypto · Alipay / WeChat · Bank transfer
Max cards per account
Multiple
Issuer risk rating
High

The fee stack

Nothing exotic in the pricing. $8 (sign-up bonus available), no top-up fee, and on non-USD billing, no FX markup. Nobody advertises the decline fee, so we list it. That is the number that surprises people.

Card creation fee$8 (sign-up bonus available)
Monthly feeFree
Top-up fee
FX / conversion fee
Declined transaction fee
Minimum top-up

Results by merchant

Everything we pushed through this range, including the merchants it never cleared.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Cursor867992%first charge and renewal four weeks later both cleared
v0.dev706086%cleared, 3-D Secure completed in-app in under 20 seconds
Perplexity AI544685%no friction, and no AVS prompt
Best Buy3500%3-D Secure challenge never completed. The order timed out waiting for the OTP.
Hetzner26935%3-D Secure challenge never completed. The order timed out waiting for the OTP.

Run from a Canada-region account between 27 Jun to 05 Sep 2026, with the billing address set to the issuer default unless noted. Declines were logged with the reason the gateway returned.

Failures we could not fix

One honest caveat: Best Buy returned a generic decline on all attempts, and we could not determine the cause. Treat it as untested rather than blocked.

What to change before you retry

Before you try it

  1. Funding is crypto-first. Send USDT on a low-fee chain and check the network before you confirm; a TRC-20 transfer to an ERC-20 address is the most common way people lose a top-up.
  2. Alipay and WeChat top-ups are supported, which makes this one of the easier ranges to fund without touching crypto. Keep individual top-ups small while you are testing.
  3. Set the billing address to exactly what HUTAO Cards generates for Canada. Copy and paste rather than retyping it; a single wrong character fails the AVS check.

Verdict, briefly

This is the range I would give someone who has never used a virtual card. Low balance requirement and the failure modes are easy to diagnose. We will keep it in the rotation and re-test it in a month.

Questions we get about 239896

What does the 239896 BIN tell a merchant?

It tells the risk engine three things before your bank is ever contacted: issuer HUTAO Cards, country of issue Canada, product class Prepaid. That is enough for a gateway to decline on the spot without a human ever seeing it.

Is 239896 a real card number?

Six digits of a sixteen-digit number. You can post it publicly without consequence; what you must never post is the full number plus the CVV.

Why would 239896 be declined if the range is fine?

Changing one variable at a time is the only way to diagnose this. Address first, then card, then the connection country. We have seen people change all three and learn nothing.

Can thousands of people share the same BIN?

That is the normal case. Every Prepaid card HUTAO Cards issues in Canada carries the same six digits. Two people on 239896 can get opposite results at the same checkout, which is why a single review is never conclusive.

Method

We bought a HUTAO Cards card, funded it, and pushed 271 charges through live merchant checkout pages between 27 Jun to 05 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 194 cleared.

Counting rules

Renewals count alongside first charges, which is why a range that passed once and failed a month later reads lower here than on a first-charge-only list. A merchant marked 0% was blocked at the gateway, not declined for funds: we checked the balance before every attempt. Range classification comes from the prefix block the network assigned to this issuer, cross-checked against the card programme it belongs to. Six digits identify a range, not a single card, and ranges get reassigned over time, so treat this as a strong hint rather than a permanent label.

Log through 13 Sep 2026 14:40 UTC · rate last re-checked 09 September 2026 · 271 charges on record for this range.