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

Amex Virtual Card BIN 377695 - United States (Prepaid)

Where it lands

Best hit rate in our run: Steam, Epic Games Store, Google Play. Timestamps in the log, no retries needed.

377695Amex United StatesPrepaid 102/144 cleared

This range belongs to Navan. Issued out of United States on Amex, classed as Prepaid by most acquirers.

Reading the 377695 prefix

BIN
377695
Card network
Amex
Issuing country
United States
Card type
Prepaid
Issued by
Navan
Card form
Virtual only
KYC tier
Business KYC
3-D Secure
Yes
AVS check
Yes (US AVS)
Billing address
US/UK/EU
Funding methods
Bank transfer
Max cards per account
Unlimited
Issuer risk rating
Low

The money side

Three lines decide it. Issuance: no issuance fee. Funding: no top-up fee. Conversion: no FX markup. Cost is the reason this range sits where it does in our ranking rather than higher up.

Card creation feeFree (no annual card fee)
Monthly feeFree (Expense: free first 15 users, then $15/user/mo)
Top-up fee
FX / conversion fee
Declined transaction fee
Minimum top-up

Results by merchant

Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Steam464291%first charge and renewal four weeks later both cleared
Epic Games Store373286%went through on a fresh card with the issuer's default address
Google Play282382%cleared on the first attempt, no challenge issued
Crunchyroll1800%Soft decline on the retry after an earlier failure on the same account.
StockX15533%3-D Secure challenge never completed. The order timed out waiting for the OTP.

Run from a United States-region account between 29 Jul to 26 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, Crunchyroll and StockX. 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

Setup notes for Navan

  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 Navan generates for United States. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
  3. 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.

Our call

Nothing here is a dealbreaker, but nothing is a standout either. It does the job on United States-region checkouts. If your only requirement is that the payment goes through, this range meets it.

The things people actually ask

What does the 377695 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 377695 a real card number?

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

Why would 377695 be declined if the range is fine?

Changing one variable at a time is the only way to diagnose this. Address first, then card, then the connection country. We have seen people change all three and learn nothing.

Can thousands of people share the same BIN?

That is the normal case. Every Prepaid card Navan issues in United States carries the same six digits. Two people on 377695 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 Navan card, funded it, and pushed 144 charges through live merchant checkout pages between 29 Jul to 26 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 102 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 28 August 2026 · 144 charges on record for this range.