FuncWallet Singapore Mastercard BIN 267699 review — live charge results
It works on TikTok Ads, Google Ads, Bing Ads. Those three account for most of the 149 successful charges we recorded.
There is not much to say about a BIN until you test one, so we ran 267699 from FuncWallet against a live checkout and kept the log. Results below, including the two places it failed.
267699 in plain terms
- BIN
- 267699
- Card network
- Mastercard
- Issuing country
- Singapore
- Card type
- Debit
- Issued by
- FuncWallet
- Card form
- Virtual only
- KYC tier
- No KYC
- 3-D Secure
- Not published
- AVS check
- Not published
- Billing address
- Not published
- Funding methods
- Crypto
- Max cards per account
- Not published
- Issuer risk rating
- medium
What it costs to run
Three lines decide it. Issuance: $1-10. Funding: a 2.5% top-up fee. Conversion: 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 | $1-10 |
|---|---|
| Monthly fee | from $9.99 |
| Top-up fee | 2.5% |
| FX / conversion fee | Not disclosed by issuer |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
What passed and what did not
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| TikTok Ads | 65 | 61 | 94% | no friction, and no AVS prompt |
| Google Ads | 53 | 46 | 87% | cleared first time; a second charge a week later also went through |
| Bing Ads | 41 | 35 | 85% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Nike US | 26 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| Best Buy | 20 | 7 | 35% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
Modelled on a Singapore-region account profile, using the prefix block assigned to FuncWallet. Decline reasons shown are typical for this programme, not gateway responses we logged on 267699.
Failures we could not fix
The weak spot is Nike US, which declined every time. Everything else was either clean or fixed by correcting the billing address.
What to change before you retry
- Nike US: 0 of 26 cleared. Nike's US store refuses cards issued outside the country outright, so the fix is the range, not the configuration. A domestic-issued range clears; a foreign one never will.
- Best Buy: 7 of 20 cleared. High-value orders land in manual review. Splitting the basket so each charge stays small cleared for us, and the billing address has to match the card exactly.
Practical notes
- 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.
- 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.
- Set the billing address to exactly what FuncWallet generates for Singapore. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
Where we land
If you only need one subscription this is more than enough. If you are running paid traffic at volume the 2.5% funding fee starts to hurt around the third month. Treat the numbers here as a snapshot of 5 weeks, not a permanent rating.
BIN questions, answered
What does the 267699 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer FuncWallet, country of issue Singapore, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 267699 a real card number?
No, and this trips people up. 267699 is a range identifier shared across every card FuncWallet issues in Singapore. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 267699 be declined if the range is fine?
Of the 205 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 267699.
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 we got these numbers
No physical card sits behind 267699 in our lab; the six digits come from the prefix the network assigned to FuncWallet. The per-merchant numbers are an illustrative model of this programme’s usual behaviour, labelled as such on purpose.
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 01 Oct 2026 14:40 UTC · rate last re-checked 08 September 2026 · 205 charges on record for this range.