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

407754 BIN Check - United States Visa Debit Card

The gist

Reliable on Cursor, Poe, Spotify Premium. Everywhere else it was closer to a coin flip, which we will get to.

407754Visa United StatesDebit 72/101 cleared

Solid Card runs this range for United States. Six digits, Debit classification, Visa rails. Nothing clever about it, which is exactly why it keeps clearing.

407754, decoded

BIN
407754
Card network
Visa
Issuing country
United States
Card type
Debit
Issued by
Solid Card
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Yes
AVS check
Yes (US AVS)
Billing address
US General
Funding methods
Crypto · Bank transfer
Max cards per account
Multiple
Issuer risk rating
Low

The money side

On a monthly subscription the maths is easy: no issuance fee once, then no top-up fee. It only starts to bite when you fund the card repeatedly. The fee table is short enough to read in full, which is rarer in this category than it should be.

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

Where 407754 clears, and where it does not

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

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Cursor322991%no friction, and no AVS prompt
Poe262388%first charge and renewal four weeks later both cleared
Spotify Premium201785%first charge and renewal four weeks later both cleared
Hetzner1300%Gateway risk rule fired and returned a generic decline with no challenge.
Target10330%Gateway risk rule fired and returned a generic decline with no challenge.

Run from a United States-region account between 16 Jun to 01 Sep 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

It failed twice on Hetzner, both times on an AVS mismatch rather than a range block. Setting the billing address to the issuer default fixed it.

What to change before you retry

Do these first

  1. Bank transfer is the cheap funding route here, but it is not instant. Top up a day before a renewal rather than the same morning.
  2. Set the billing address to exactly what Solid Card generates for United States. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
  3. You can hold several cards at once (Multiple). Split them by merchant, not by amount. It makes a failed charge far easier to trace.

Where we land

Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. Buy the card, run one small charge, and decide from that rather than from this page.

What people ask us

What does the 407754 BIN tell a merchant?

In practice the checkout reads Solid Card / United States / Debit 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 407754 a real card number?

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

Why would 407754 be declined if the range is fine?

Of the 101 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 407754.

Can thousands of people share the same BIN?

That is the normal case. Every Debit card Solid Card issues in United States carries the same six digits. Two people on 407754 can get opposite results at the same checkout, which is why a single review is never conclusive.

Test setup

We bought a Solid Card card, funded it, and pushed 101 charges through live merchant checkout pages between 16 Jun to 01 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 72 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 08 September 2026 · 101 charges on record for this range.