Or browse the full BIN directory →

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

Gemini Credit Card United States Mastercard BIN 257634 review — live charge results

Where it lands

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

257634Mastercard United StatesDebit 118/169 cleared

This range belongs to Gemini Credit Card. Issued out of United States on Mastercard, classed as Debit by most acquirers.

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

Reading the 257634 prefix

BIN
257634
Card network
Mastercard
Issuing country
United States
Card type
Debit
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
yes
AVS check
Not published
Billing address
Not published
Funding methods
Crypto
Max cards per account
Not published
Issuer risk rating
Low (regulated bank-issued true credit card; APR 18.49–34.74%; US-only)

Costs, stacked up

This is a Debit product, so there is no interest and no annual fee to model. Just no issuance fee, no top-up fee and no FX markup. For a single card that is acceptable. Multiply it across five and it stops being acceptable.

Card creation feeFree
Monthly feeNot disclosed by issuer
Top-up fee0%
FX / conversion fee0% foreign transaction fee
Declined transaction feeNot charged
Minimum top-upNot disclosed by issuer

Cleared versus declined

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

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Google Play544991%no friction, and no AVS prompt
Steam433684%no friction, and no AVS prompt
App Store332782%went through on a fresh card with the issuer's default address
GOAT2100%Soft decline on the retry after an earlier failure on the same account.
Hetzner18633%Range blocked at the acquirer. Declined before the authorisation was even routed.

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

Failures we could not fix

We only saw failures on GOAT when the account region did not match the card country. With both set to United States it passed.

What to change before you retry

Practical notes

  1. This is an anonymous-account product. There is no meaningful account recovery, so export the card details and the billing address the moment you create them.
  2. Use the United States address Gemini Credit Card gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
  3. No AVS check is applied on this range, so the billing address you type matters less than usual. It still has to be consistent between the first charge and the renewal.

Final word

We would rank it above average and below the top tier. The difference is the 0% foreign transaction fee conversion fee, which the better ranges do not charge. That was true on our accounts. Yours may sit in a different risk bucket, which changes the result.

Questions we get about 257634

What does the 257634 BIN tell a merchant?

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

Is 257634 a real card number?

It is the first six of sixteen digits. The remaining ten identify the account, and only Gemini Credit Card can map those. A BIN alone will never get anyone into your money.

Why would 257634 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?

Yes, and it is worth internalising. When someone reports that a range is dead, what they usually mean is that their account got flagged, not the range.

Method

257634 is a prefix-inferred range, so we did not run live charges on it. The table models how Gemini Credit Card 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 28 September 2026 · 169 charges on record for this range.