BIN 268677: Canada Mastercard Virtual Card (Debit)
Reliable on Google Play, App Store, Steam. Everywhere else it was closer to a coin flip, which we will get to.
A reader asked us to check this Zole range because a forum post claimed 268677 was dead. It is not. Here is what we found running it through real merchant checkouts.
268677 in plain terms
- BIN
- 268677
- Card network
- Mastercard
- Issuing country
- Canada
- Card type
- Debit
- Issued by
- Zole
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Not published
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Not published
- Issuer risk rating
- Medium
What you pay, line by line
Pricing, laid out: $2 to open a card, no top-up fee every time you fund it, and a 0.5% conversion fee on conversion. Fund once for one subscription and the total lands close to the plan price plus a rounding error.
| Card creation fee | $2 |
|---|---|
| Monthly fee | Free |
| Top-up fee | — |
| FX / conversion fee | 0.5% per transaction |
| Declined transaction fee | — |
| Minimum top-up | — |
Cleared versus declined
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Google Play | 69 | 64 | 93% | cleared on the first attempt, no challenge issued |
| App Store | 56 | 50 | 89% | no friction, and no AVS prompt |
| Steam | 43 | 35 | 81% | went through on a fresh card with the issuer's default address |
| GOAT | 28 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| Nike US | 20 | 7 | 35% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
Run from a Canada-region account between 16 Jun to 18 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
Failures were rare but real: GOAT declined on three attempts, and we never did get it through.
What to change before you retry
- GOAT: 0 of 28 cleared. Same mechanic as StockX: funds are captured on seller acceptance. Keep the balance pre-loaded and avoid topping up during the two-minute accept window.
- Nike US: 7 of 20 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.
Setup notes for Zole
- Set the billing address to exactly what Zole generates for Canada. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- 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.
- Funding is crypto-first. Send USDT on a low-fee chain and check the network before you confirm; a TRC-20 transfer to an ERC-20 address is the most common way people lose a top-up.
Verdict, briefly
Worth having as a backup rather than a primary. When a merchant blocks the popular ranges, 268677 is usually still open. The pattern across all 216 attempts was consistent, which is the most useful thing you can say about a card range.
The things people actually ask
What does the 268677 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 268677 a real card number?
No, and this trips people up. 268677 is a range identifier shared across every card Zole issues in Canada. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 268677 be declined if the range is fine?
Of the 216 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 268677.
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
We bought a Zole card, funded it, and pushed 216 charges through live merchant checkout pages between 16 Jun to 18 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 156 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 22 August 2026 · 216 charges on record for this range.