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

BIN 441357: Singapore Visa Virtual Card (Debit)

If you only read one line

199 of 280 attempts cleared, and most of those came from three merchants: Google Play, Steam, Epic Games Store.

441357Visa SingaporeDebit 199/280 cleared

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

441357 in plain terms

BIN
441357
Card network
Visa
Issuing country
Singapore
Card type
Debit
Issued by
Dotva
Card form
Virtual only
KYC tier
Business KYC
3-D Secure
No
AVS check
No
Billing address
Not published
Funding methods
Bank transfer
Max cards per account
Multiple (API-driven)
Issuer risk rating
Medium

The fee stack

Up front you have $3/card. On each funding event, no top-up fee. Outside USD, no FX markup. Compare on funding cost rather than signup fee. The funding side is what you pay every month for years.

Card creation fee$3/card
Monthly fee
Top-up fee
FX / conversion fee
Declined transaction fee
Minimum top-up

Cleared versus declined

Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Google Play898090%cleared on the first attempt, no challenge issued
Steam726286%cleared first time; a second charge a week later also went through
Epic Games Store564784%first charge and renewal four weeks later both cleared
iHerb3600%Gateway risk rule fired and returned a generic decline with no challenge.
Sephora US271037%Geo mismatch. The connection country did not match the card's country of issue.

Run from a Singapore-region account between 12 Aug 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

iHerb rejected it outright. We could not tell whether that was the BIN or our test account being flagged, so we are leaving it as unresolved.

What to change before you retry

Do these first

  1. Set the billing address to exactly what Dotva generates for Singapore. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
  2. 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.
  3. No AVS check is applied on this range, so the billing address you type matters less than usual. It still has to be consistent between the first charge and the renewal.

Where we land

Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. The pattern across all 280 attempts was consistent, which is the most useful thing you can say about a card range.

What people ask us

What does the 441357 BIN tell a merchant?

In practice the checkout reads Dotva / Singapore / 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 441357 a real card number?

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

Why would 441357 be declined if the range is fine?

Two causes cover most of it: the billing address does not match, or the challenge never completed. Both look identical on screen, and both are fixable in under a minute.

Can thousands of people share the same BIN?

That is the normal case. Every Debit card Dotva issues in Singapore carries the same six digits. Two people on 441357 can get opposite results at the same checkout, which is why a single review is never conclusive.

How this test was run

We bought a Dotva card, funded it, and pushed 280 charges through live merchant checkout pages between 12 Aug 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. 199 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. The BIN itself is taken from the issuer's own published card list. Country and product class are derived from the network prefix block, not from the issuer's documentation. 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 05 September 2026 · 280 charges on record for this range.