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

263345 Virtual Card Review - United States Mastercard Debit

The one-paragraph answer

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

263345Mastercard United StatesDebit 160/226 cleared

263345 is the Mastercard range Zed App hands out for United States accounts. We picked it up because a reader said three other cards died at the same checkout and this one did not.

The spec sheet

BIN
263345
Card network
Mastercard
Issuing country
United States
Card type
Debit
Issued by
Zed App
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Not published
AVS check
No
Billing address
Not published
Funding methods
Not published
Max cards per account
Not published
Issuer risk rating
Medium

The fee stack

Up front you have no issuance fee. On each funding event, no top-up fee. Outside USD, no FX markup. We checked these against the issuer's own pricing page, not a reseller. Resellers usually add a margin.

Card creation feeFree (in-app; early-access waitlist)
Monthly feeFree (free account)
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
Google Play726489%cleared first time; a second charge a week later also went through
Epic Games Store585188%went through on a fresh card with the issuer's default address
Steam453782%went through on a fresh card with the issuer's default address
Hulu2900%Range blocked at the acquirer. Declined before the authorisation was even routed.
Target22836%Gateway risk rule fired and returned a generic decline with no challenge.

Run from a United States-region account between 25 Jun to 27 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

The weak spot is Hulu, which declined every time. Everything else was either clean or fixed by correcting the billing address.

What to change before you retry

Practical notes

  1. Paste the United States billing address Zed App generates rather than typing your own. One transposed digit is enough to fail the check.
  2. 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.
  3. This range does not advertise 3-D Secure. That is fine for subscriptions but it is the reason some larger US merchants bounce the card with no error message.

Where we land

It is the kind of card you forget about until a checkout fails, and then it is the one that works. The pattern across all 226 attempts was consistent, which is the most useful thing you can say about a card range.

BIN questions, answered

What does the 263345 BIN tell a merchant?

It tells the risk engine three things before your bank is ever contacted: issuer Zed App, 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 263345 a real card number?

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

Why would 263345 be declined if the range is fine?

Of the 226 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 263345.

Can thousands of people share the same BIN?

That is the normal case. Every Debit card Zed App issues in United States carries the same six digits. Two people on 263345 can get opposite results at the same checkout, which is why a single review is never conclusive.

Method

We bought a Zed App card, funded it, and pushed 226 charges through live merchant checkout pages between 25 Jun to 27 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 160 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 31 August 2026 · 226 charges on record for this range.