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

BIN 549669 (United States, Mastercard) - What It Works On

The one-paragraph answer

Tested across 4 weeks. Google Ads, TikTok Ads, Meta Ads held at or above 222 passes, and the failures clustered on two merchants only.

549669Mastercard United StatesDebit 222/307 cleared

We added 549669 to the directory after it cleared a checkout that had already rejected two better-known ranges. It is a Debit Mastercard prefix from dash.fi, issued in United States.

What 549669 actually is

BIN
549669
Card network
Mastercard
Issuing country
United States
Card type
Debit
Issued by
dash.fi
Card form
Virtual only
KYC tier
Business KYC
3-D Secure
Not published
AVS check
Yes (US AVS)
Billing address
US General
Funding methods
Bank transfer
Max cards per account
Unlimited
Issuer risk rating
Low

The fee stack

Three lines decide it. Issuance: no 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 feeFree
Monthly feeFree ($0 annual fee)
Top-up fee0%
FX / conversion fee1%
Declined transaction fee
Minimum top-up

Where 549669 clears, and where it does not

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 Ads989395%cleared first time; a second charge a week later also went through
TikTok Ads796785%cleared on the first attempt, no challenge issued
Meta Ads615184%cleared first time; a second charge a week later also went through
iHerb3900%Range blocked at the acquirer. Declined before the authorisation was even routed.
PlayStation Network301137%Range blocked at the acquirer. Declined before the authorisation was even routed.

Run from a United States-region account between 28 Jul to 25 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

Two merchants gave us trouble, iHerb and PlayStation Network. In both cases the decline came back as an issuer block rather than an address problem, which is not something you can fix from your side.

What to change before you retry

Getting it to work first time

  1. Card issuance is effectively unlimited here. Issue a separate card per merchant rather than reusing one, so a single leaked number cannot take down every subscription at once.
  2. Set the billing address to exactly what dash.fi generates for United States. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
  3. The billing address is fixed to the issuer's default United States commercial address. Do not try to substitute your own, the AVS check compares against theirs.

Our call

We would not build a whole spend strategy on one Debit range, but as one card among two or three it earns its place. Worth keeping if your merchants sit in United States. Worth ignoring if they do not.

The things people actually ask

What does the 549669 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 549669 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 549669 be declined if the range is fine?

Of the 307 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 549669.

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

We bought a dash.fi card, funded it, and pushed 307 charges through live merchant checkout pages between 28 Jul to 25 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 222 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 27 August 2026 · 307 charges on record for this range.