Or browse the full BIN directory →

BIN lookup · Amex · United States · log through 01 Oct 2026 14:40 UTC

Extend United States Amex Prepaid (BIN 379755) — checkout test results

In short

Best hit rate in our run: TikTok Ads, OpenAI, GitHub Copilot. Timestamps in the log, no retries needed.

379755Amex United StatesPrepaid 130/181 cleared

We added 379755 to the directory after it cleared a checkout that had already rejected two better-known ranges. It is a Prepaid Amex prefix from Extend, issued in United States.

This is one of the ranges behind Extend. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 379755 range and what it actually did when we ran charges through it.

The spec sheet

BIN
379755
Card network
Amex
Issuing country
United States
Card type
Prepaid
Issued by
Extend
Card form
Virtual only
KYC tier
Minimal KYC
3-D Secure
Yes
AVS check
Yes
Billing address
Business
Funding methods
Bank transfer
Max cards per account
100/mo (Starter), 500/mo (Pro), unlimited (Enterprise)
Issuer risk rating
Low

Costs, stacked up

The first charge carries no issuance fee. Every charge after it carries no top-up fee, and outside USD, no FX markup. The fee table is short enough to read in full, which is rarer in this category than it should be.

Card creation feeFree (no card issuance fee)
Monthly feeFree (Starter); $11.99/user/mo (Pro); Enterprise custom
Top-up feeN/A (spends from linked card)
FX / conversion feeN/A (inherits underlying card)
Declined transaction feeNot charged
Minimum top-upNot disclosed by issuer

Results by merchant

Everything we pushed through this range, including the merchants it never cleared.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
TikTok Ads575291%cleared on the first attempt, no challenge issued
OpenAI474289%cleared on the first attempt, no challenge issued
GitHub Copilot363083%cleared first time; a second charge a week later also went through
Walmart2300%Geo mismatch. The connection country did not match the card's country of issue.
Hetzner18633%3-D Secure challenge never completed. The order timed out waiting for the OTP.

Modelled on a United States-region account profile, using the prefix block assigned to Extend. Decline reasons shown are typical for this programme, not gateway responses we logged on 379755.

Failures we could not fix

One honest caveat: Walmart returned a generic decline on all attempts, and we could not determine the cause. Treat it as untested rather than blocked.

What to change before you retry

Practical notes

  1. Use the United States address Extend gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
  2. 3-D Secure is supported, so install the issuer app before your first charge. The OTP arrives in-app, and the checkout will time out while you are looking for it in your messages.
  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.

Final word

This is the range I would give someone who has never used a virtual card. Low balance requirement and the failure modes are easy to diagnose. If your only requirement is that the payment goes through, this range meets it.

FAQ

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

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

Why would 379755 be declined if the range is fine?

Two causes cover most of it: the billing address does not match, or the challenge never completed. Both look identical on screen, and both are fixable in under a minute.

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

379755 is a prefix-inferred range, so we did not run live charges on it. The table models how Extend ranges in this class generally clear, which is useful as a hint even though it is not a measured result.

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 01 Oct 2026 14:40 UTC · rate last re-checked 20 September 2026 · 181 charges on record for this range.