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

BIN 229716 (Singapore, Mastercard) - What It Works On

The gist

Our log shows clean passes on Leonardo.ai, Claude.ai, Poe, first charge and renewal both going through.

229716Mastercard SingaporePrepaid 150/209 cleared

The first thing to know about 229716 is that it is not an anonymous range. Bpay issues it in Singapore and the Mastercard prefix is registered, which is why fewer merchants treat it as high risk.

Reading the 229716 prefix

BIN
229716
Card network
Mastercard
Issuing country
Singapore
Card type
Prepaid
Issued by
Bpay
Card form
Virtual only
KYC tier
ID only
3-D Secure
Not published
AVS check
No
Billing address
Not published
Funding methods
Crypto
Max cards per account
Not published
Issuer risk rating
High

What it costs to run

Three lines decide it. Issuance: an undisclosed issuance fee. Funding: no top-up fee. Conversion: no FX markup. Nobody advertises the decline fee, so we list it. That is the number that surprises people.

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

Cleared versus declined

Attempts counted per merchant by hand from the log, so a single declined order does not skew the rate.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Leonardo.ai666091%first charge and renewal four weeks later both cleared
Claude.ai544889%went through on a fresh card with the issuer's default address
Poe413585%went through on a fresh card with the issuer's default address
Nintendo eShop2700%Geo mismatch. The connection country did not match the card's country of issue.
Hetzner21733%Geo mismatch. The connection country did not match the card's country of issue.

Run from a Singapore-region account between 14 Jun to 16 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

Failures were rare but real: Nintendo eShop declined on three attempts, and we never did get it through.

What to change before you retry

Practical notes

  1. 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.
  2. Use the Singapore address Bpay gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
  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.

Final word

Nothing here is a dealbreaker, but nothing is a standout either. It does the job on Singapore-region checkouts. The pattern across all 209 attempts was consistent, which is the most useful thing you can say about a card range.

Questions we get about 229716

What does the 229716 BIN tell a merchant?

In practice the checkout reads Bpay / Singapore / Prepaid 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 229716 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 229716 be declined if the range is fine?

Of the 209 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 229716.

Can thousands of people share the same BIN?

That is the normal case. Every Prepaid card Bpay issues in Singapore carries the same six digits. Two people on 229716 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 Bpay card, funded it, and pushed 209 charges through live merchant checkout pages between 14 Jun to 16 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 150 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 20 August 2026 · 209 charges on record for this range.