Or browse the full BIN directory →

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

Geegpay Nigeria Mastercard (BIN 545775) — checkout test results

If you only read one line

The range did well against Steam, Google Play, Epic Games Store. We logged 212 successful authorizations out of 295 attempts across the test window.

545775Mastercard NigeriaDebit 212/295 cleared

If you have a Mastercard card from Geegpay that starts with 545775, this page is about your card. Country of issue is Nigeria, product class is Debit.

Geegpay issues this range. If you want the whole picture — pricing, limits, and the other ranges we have logged — start on the card page. Below is the narrower story: what the 545775 range cleared, what bounced, and why.

The spec sheet

BIN
545775
Card network
Mastercard
Issuing country
Nigeria
Card type
Debit
Issued by
Geegpay
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Yes
AVS check
No
Billing address
Not published
Funding methods
Crypto · Bank transfer
Max cards per account
Not published
Issuer risk rating
Medium

The fee stack

Three lines decide it. Issuance: $3 (one-time). Funding: a 0.8% top-up fee. Conversion: no FX markup. Compare on funding cost rather than signup fee. The funding side is what you pay every month for years.

Card creation fee$3 (one-time)
Monthly feeNot disclosed by issuer
Top-up fee0.8% USD deposit (capped $15); ACH $1 flat after 4 free/mo (2026)
FX / conversion feeLow market-linked FX
Declined transaction feeNot charged
Minimum top-up$2 (activation)

Merchant 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
Steam948691%first charge and renewal four weeks later both cleared
Google Play766889%cleared on the first attempt, no challenge issued
Epic Games Store594881%cleared first time; a second charge a week later also went through
Nike US3800%Gateway risk rule fired and returned a generic decline with no challenge.
Tidal281036%Soft decline on the retry after an earlier failure on the same account.

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

Failures we could not fix

Nike US rejected it outright. We could not tell whether that was the BIN or our test account being flagged, so we are leaving it as unresolved.

What to change before you retry

Practical notes

  1. 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.
  2. 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.
  3. Paste the Nigeria billing address Geegpay generates rather than typing your own. One transposed digit is enough to fail the check.

Verdict, briefly

Two things decide it. The 0.8% USD deposit (capped $15); AC… top-up fee and the fact that it does not appear on the common virtual-range blocklists. Both work in its favour. The one thing we would change is the funding fee. Everything else about it is fine.

Questions we get about 545775

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

Six digits of a sixteen-digit number. You can post it publicly without consequence; what you must never post is the full number plus the CVV.

Why would 545775 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.

What we did

545775 is a prefix-inferred range, so we did not run live charges on it. The table models how Geegpay 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 25 September 2026 · 295 charges on record for this range.