Jeeves Multi-region Mastercard (BIN 248959) — tested at checkout
149 of 209 attempts cleared, and most of those came from three merchants: Spotify Premium, Google Ads, v0.dev.
There is not much to say about a BIN until you test one, so we ran 248959 from Jeeves against a live checkout and kept the log. Results below, including the two places it failed.
This range sits inside the Jeeves. The card page covers what it costs to open and reload, what the sign-up asks for, and every other range we have logged under this issuer — this page goes one level deeper, into what the 248959 range itself did at checkout.
Reading the 248959 prefix
- BIN
- 248959
- Card network
- Mastercard
- Issuing country
- Multi-region
- Card type
- Prepaid
- Issued by
- Jeeves
- Card form
- Virtual only
- KYC tier
- Business KYC
- 3-D Secure
- Yes
- AVS check
- Yes
- Billing address
- Business
- Funding methods
- Bank transfer
- Max cards per account
- Unlimited virtual & physical
- Issuer risk rating
- Low-Medium
What you pay, line by line
This is a Prepaid product, so there is no interest and no annual fee to model. Just no issuance fee, no top-up fee and no FX markup. Nobody advertises the decline fee, so we list it. That is the number that surprises people.
| Card creation fee | Free (no card fees) |
|---|---|
| Monthly fee | Free (no monthly fee; paid tiers $5-15/user/mo) |
| Top-up fee | N/A (corporate charge card / credit) |
| FX / conversion fee | Applies on cross-border (rate not published transparently) |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
The test results
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Spotify Premium | 66 | 62 | 94% | no friction, and no AVS prompt |
| Google Ads | 54 | 46 | 85% | first charge and renewal four weeks later both cleared |
| v0.dev | 41 | 34 | 83% | first charge and renewal four weeks later both cleared |
| Tidal | 27 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| Nike US | 21 | 7 | 33% | Soft decline on the retry after an earlier failure on the same account. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to Jeeves. Decline reasons shown are typical for this programme, not gateway responses we logged on 248959.
Failures we could not fix
The weak spot is Tidal, which declined every time. Everything else was either clean or fixed by correcting the billing address.
What to change before you retry
- Tidal: 0 of 27 cleared. Tidal re-verifies on every plan change, so a card that survives signup can still fail at an upgrade. Keep the address static between changes.
- Nike US: 7 of 21 cleared. Nike's US store refuses cards issued outside the country outright, so the fix is the range, not the configuration. A domestic-issued range clears; a foreign one never will.
Getting it to work first time
- 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.
- 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.
- Set the billing address to exactly what Jeeves generates for Multi-region. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
What the numbers add up to
Nothing here is a dealbreaker, but nothing is a standout either. It does the job on Multi-region-region checkouts. The pattern across all 209 attempts was consistent, which is the most useful thing you can say about a card range.
The things people actually ask
What does the 248959 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 248959 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 248959 be declined if the range is fine?
Of the 209 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 248959.
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
No physical card sits behind 248959 in our lab; the six digits come from the prefix the network assigned to Jeeves. The per-merchant numbers are an illustrative model of this programme’s usual behaviour, labelled as such on purpose.
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 08 September 2026 · 209 charges on record for this range.