BIN lookup · Visa · Netherlands · log through 13 Sep 2026 14:40 UTC

460552 VCC - Netherlands Visa Virtual Card Review

The gist

Tested across 11 weeks. Disney+, Udio AI, OpenAI held at or above 164 passes, and the failures clustered on two merchants only.

460552Visa NetherlandsDebit 164/226 cleared

We added 460552 to the directory after it cleared a checkout that had already rejected two better-known ranges. It is a Debit Visa prefix from COCA, issued in Netherlands.

What 460552 actually is

BIN
460552
Card network
Visa
Issuing country
Netherlands
Card type
Debit
Issued by
COCA
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Yes
AVS check
No
Billing address
Global
Funding methods
Crypto · Alipay / WeChat
Max cards per account
Multiple
Issuer risk rating
Medium

Costs, stacked up

This is a Debit product, so there is no interest and no annual fee to model. Just no issuance fee, no top-up fee and no FX markup. Compare on funding cost rather than signup fee. The funding side is what you pay every month for years.

Card creation feeFree
Monthly feeFree
Top-up fee
FX / conversion fee0%
Declined transaction fee
Minimum top-up

Merchant by merchant

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

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Disney+726692%went through on a fresh card with the issuer's default address
Udio AI585290%cleared, 3-D Secure completed in-app in under 20 seconds
OpenAI453884%no friction, and no AVS prompt
GOAT2900%Geo mismatch. The connection country did not match the card's country of issue.
StockX22836%3-D Secure challenge never completed. The order timed out waiting for the OTP.

Run from a Netherlands-region account between 17 Jun to 02 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

We only saw failures on GOAT when the account region did not match the card country. With both set to Netherlands it passed.

What to change before you retry

Three things worth doing

  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. Use the Netherlands address COCA gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
  3. 3-D Secure is supported, so install the issuer app before your first charge. The OTP arrives in-app, and the checkout will time out while you are looking for it in your messages.

What the numbers add up to

Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. We will keep it in the rotation and re-test it in a month.

FAQ

What does the 460552 BIN tell a merchant?

In practice the checkout reads COCA / Netherlands / Debit and decides. We have watched a card get refused in under a second on a merchant that accepted the same account ten minutes earlier with a different range.

Is 460552 a real card number?

It is the first six of sixteen digits. The remaining ten identify the account, and only COCA can map those. A BIN alone will never get anyone into your money.

Why would 460552 be declined if the range is fine?

Of the 226 attempts behind this page, the losses broke down as address mismatch first, incomplete 3-D Secure second, and merchant-side range blocks a distant third. Only the last one is about 460552.

Can thousands of people share the same BIN?

Shared by design. Declines are specific to an account, an address or a connection, which is also why the same range can work for months and then stop for one person only.

Method

We bought a COCA card, funded it, and pushed 226 charges through live merchant checkout pages between 17 Jun to 02 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 164 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 07 September 2026 · 226 charges on record for this range.