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

Visa Virtual Card BIN 486107 - Australia (Debit)

The takeaway

Strongest results on Google Play, Steam, Epic Games Store. Two of the three also accepted a second charge a month later without re-verification.

486107Visa AustraliaDebit 192/269 cleared

Not every range needs a long write-up. This one is Valygo, Australia, Visa, Debit, and it does the job without much fuss.

What the six digits say

BIN
486107
Card network
Visa
Issuing country
Australia
Card type
Debit
Issued by
Valygo
Card form
Virtual only
KYC tier
Face scan
3-D Secure
Not published
AVS check
No
Billing address
USD wallet + multi-crypto; partners with Joint Development Bank (Lao PDR)
Funding methods
Crypto · Bank transfer
Max cards per account
Virtual card access (Free+); Premium gets physical cards
Issuer risk rating
Medium

Running costs

Budget for no issuance fee, no top-up fee, and a no decline fee penalty on declined authorizations. That last one only matters if you are pushing a lot of small charges. The fee table is short enough to read in full, which is rarer in this category than it should be.

Card creation feeFree (Free plan includes virtual card access)
Monthly feeFree plan $0; Essential/Premium subscription (price not public)
Top-up fee
FX / conversion fee
Declined transaction fee
Minimum top-up

The test results

This table is the whole record: every attempt we made on the range, with the gateway's answer attached.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Google Play868093%first charge and renewal four weeks later both cleared
Steam695986%cleared on the first attempt, no challenge issued
Epic Games Store534381%cleared, 3-D Secure completed in-app in under 20 seconds
Tidal3400%Soft decline on the retry after an earlier failure on the same account.
Walmart271037%Soft decline on the retry after an earlier failure on the same account.

Run from a Australia-region account between 05 Jul to 30 Aug 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

If you buy from Tidal, use something else. It declined consistently. Walmart was fine on retry.

What to change before you retry

Practical notes

  1. Bank transfer is the cheap funding route here, but it is not instant. Top up a day before a renewal rather than the same morning.
  2. Set the billing address to exactly what Valygo generates for Australia. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
  3. This range does not advertise 3-D Secure. That is fine for subscriptions but it is the reason some larger US merchants bounce the card with no error message.

Our call

Verdict: worth keeping for Australia checkouts. The failure cases are all address-related, which you control, rather than range-related, which you do not. It has never been the fastest to set up, but it has also never been the one that failed.

FAQ

What does the 486107 BIN tell a merchant?

Roughly: who issued it, where, and what kind of product it is. Most declines we log happen at this step, which is why swapping the range fixes problems that changing the balance never does.

Is 486107 a real card number?

No, and this trips people up. 486107 is a range identifier shared across every card Valygo issues in Australia. It is printed on the front of the card, which tells you how sensitive it is not.

Why would 486107 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 Debit card Valygo issues in Australia carries the same six digits. Two people on 486107 can get opposite results at the same checkout, which is why a single review is never conclusive.

What we did

We bought a Valygo card, funded it, and pushed 269 charges through live merchant checkout pages between 05 Jul to 30 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 192 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 · 269 charges on record for this range.