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

251469 BIN Check - United States Mastercard Credit Card

In short

Tested across 6 weeks. Steam, App Store, Google Play held at or above 184 passes, and the failures clustered on two merchants only.

251469Mastercard United StatesCredit 184/258 cleared

BILL Divvy runs this range for United States. Six digits, Credit classification, Mastercard rails. Nothing clever about it, which is exactly why it keeps clearing.

251469 in plain terms

BIN
251469
Card network
Mastercard
Issuing country
United States
Card type
Credit
Issued by
BILL Divvy
Card form
Virtual only
KYC tier
Business KYC
3-D Secure
No
AVS check
Yes (US AVS)
Billing address
US General
Funding methods
Bank transfer
Max cards per account
Unlimited (department/vendor)
Issuer risk rating
Low

Costs, stacked up

Budget for no issuance fee, no top-up fee, and a no decline fee penalty on declined authorizations. That last one only matters if you are pushing a lot of small charges. Compare on funding cost rather than signup fee. The funding side is what you pay every month for years.

Card creation feeFree (no subscription)
Monthly feeFree (no annual/per-user fees)
Top-up fee
FX / conversion fee
Declined transaction fee
Minimum top-up

The test results

This table is the whole record: every attempt we made on the range, with the gateway's answer attached.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Steam827389%cleared first time; a second charge a week later also went through
App Store676090%no friction, and no AVS prompt
Google Play514282%no friction, and no AVS prompt
Nike US3300%Gateway risk rule fired and returned a generic decline with no challenge.
GOAT25936%3-D Secure challenge never completed. The order timed out waiting for the OTP.

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

If you buy from Nike US, use something else. It declined consistently. GOAT was fine on retry.

What to change before you retry

Three things worth doing

  1. Set the billing address to exactly what BILL Divvy generates for United States. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
  2. 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.
  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.

Our call

We would rank it above average and below the top tier. The difference is the no FX markup conversion fee, which the better ranges do not charge. Treat the numbers here as a snapshot of 6 weeks, not a permanent rating.

The things people actually ask

What does the 251469 BIN tell a merchant?

It tells the risk engine three things before your bank is ever contacted: issuer BILL Divvy, country of issue United States, product class Credit. That is enough for a gateway to decline on the spot without a human ever seeing it.

Is 251469 a real card number?

No, and this trips people up. 251469 is a range identifier shared across every card BILL Divvy issues in United States. It is printed on the front of the card, which tells you how sensitive it is not.

Why would 251469 be declined if the range is fine?

Of the 258 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 251469.

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 BILL Divvy card, funded it, and pushed 258 charges through live merchant checkout pages between 16 Jul to 27 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 184 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 03 September 2026 · 258 charges on record for this range.