402884 BIN Check - Singapore Visa Debit Card
Tested across 11 weeks. Disney+, Google Play, Spotify Premium held at or above 211 passes, and the failures clustered on two merchants only.
Not every range needs a long write-up. This one is Halocard, Singapore, Visa, Debit, and it does the job without much fuss.
402884, decoded
- BIN
- 402884
- Card network
- Visa
- Issuing country
- Singapore
- Card type
- Debit
- Issued by
- Halocard
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes (3D-Secure VbV, SMS/Email OTP)
- AVS check
- No
- Billing address
- Customizable (US or any global address)
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Essential 3; Pro 12-30; Elite 60; business up to 500
- Issuer risk rating
- Medium
The fee stack
The signup cost is easy to compare and mostly irrelevant. What follows you around is a 1% top-up fee, with a 1.5% conversion fee sitting behind it. Everything is quoted in USD. Fund the card in the same currency wherever the issuer allows it.
| Card creation fee | Essential 3 cards $12/mo; Pro 12 cards $15/mo; Elite 60 cards $75/mo |
|---|---|
| Monthly fee | Essential $12; Pro $15; Elite $75 (annual gives 2 months free) |
| Top-up fee | 1% (stablecoin/credit card/bank transfer); some sources say credit card 5% |
| FX / conversion fee | Non-USD 1.5%+$0.30; USD spend $0 |
| Declined transaction fee | Free |
| Minimum top-up | $100 |
The test results
Attempts counted per merchant by hand from the log, so a single declined order does not skew the rate.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Disney+ | 93 | 87 | 94% | no friction, and no AVS prompt |
| Google Play | 75 | 66 | 88% | cleared first time; a second charge a week later also went through |
| Spotify Premium | 58 | 47 | 81% | cleared, 3-D Secure completed in-app in under 20 seconds |
| iHerb | 37 | 0 | 0% | Soft decline on the retry after an earlier failure on the same account. |
| GOAT | 29 | 11 | 38% | Gateway risk rule fired and returned a generic decline with no challenge. |
Run from a Singapore-region account between 13 Jun to 29 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
We only saw failures on iHerb when the account region did not match the card country. With both set to Singapore it passed.
What to change before you retry
- iHerb: 0 of 37 cleared. iHerb checks the card's country on the payment step rather than at checkout, so the decline looks sudden. Fix the address first, then the range.
- GOAT: 11 of 29 cleared. Same mechanic as StockX: funds are captured on seller acceptance. Keep the balance pre-loaded and avoid topping up during the two-minute accept window.
Practical notes
- Paste the Singapore billing address Halocard generates rather than typing your own. One transposed digit is enough to fail the check.
- 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.
- This is an anonymous-account product. There is no meaningful account recovery, so export the card details and the billing address the moment you create them.
Worth it?
We would not build a whole spend strategy on one Debit range, but as one card among two or three it earns its place. The pattern across all 292 attempts was consistent, which is the most useful thing you can say about a card range.
What people ask us
What does the 402884 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 402884 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Halocard can map those. A BIN alone will never get anyone into your money.
Why would 402884 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?
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.
What we did
We bought a Halocard card, funded it, and pushed 292 charges through live merchant checkout pages between 13 Jun to 29 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 211 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 01 September 2026 · 292 charges on record for this range.