BIN 491423: India Visa Virtual Card (Debit)
87 of 122 attempts cleared, and most of those came from three merchants: Google Play, Steam, App Store.
Not every range needs a long write-up. This one is DhaniPay, India, Visa, Debit, and it does the job without much fuss.
491423, decoded
- BIN
- 491423
- Card network
- Visa
- Issuing country
- India
- Card type
- Debit
- Issued by
- DhaniPay
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- India
- Funding methods
- Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- Medium
Running costs
Compared with the rest of the directory this sits mid-table. no issuance fee to open, no top-up fee to fund, and no FX markup on conversion. Compare on funding cost rather than signup fee. The funding side is what you pay every month for years.
| Card creation fee | Free |
|---|---|
| Monthly fee | Free |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
Results by merchant
Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Google Play | 39 | 35 | 90% | no friction, and no AVS prompt |
| Steam | 31 | 28 | 90% | cleared on the first attempt, no challenge issued |
| App Store | 24 | 20 | 83% | no friction, and no AVS prompt |
| Walmart | 15 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| Tidal | 13 | 4 | 31% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Run from a India-region account between 21 Jul to 01 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
The pattern in our failures is geographic. Walmart accepted it once the account region matched India, and refused it every time it did not.
What to change before you retry
- Walmart: 0 of 15 cleared. Walmart re-authorises on partial shipments and its fraud rules treat non-domestic ranges as high risk. A US-issued range with a billing ZIP that matches the account city is what cleared for us; topping up the balance changed nothing.
- Tidal: 4 of 13 cleared. Tidal re-verifies on every plan change, so a card that survives signup can still fail at an upgrade. Keep the address static between changes.
Before you try it
- 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.
- 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.
- Use the India address DhaniPay gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
Our call
Overall a solid Debit range for India-region accounts. Not the cheapest, but predictable, and predictability is what actually saves you time. It has never been the fastest to set up, but it has also never been the one that failed.
Questions we get about 491423
What does the 491423 BIN tell a merchant?
In practice the checkout reads DhaniPay / India / 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 491423 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 491423 be declined if the range is fine?
Of the 122 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 491423.
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.
How this test was run
We bought a DhaniPay card, funded it, and pushed 122 charges through live merchant checkout pages between 21 Jul to 01 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 87 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 08 September 2026 · 122 charges on record for this range.