Wealthsimple Mastercard Canada (BIN 226776) — which merchants passed
We would rank Epic Games Store, Google Play, Steam as the safest bets on this range, based on 127 passes out of 179 attempts.
Wealthsimple runs this range for Canada. Six digits, Debit classification, Mastercard rails. Nothing clever about it, which is exactly why it keeps clearing.
This is one of the ranges behind Wealthsimple. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 226776 range and what it actually did when we ran charges through it.
226776, decoded
- BIN
- 226776
- Card network
- Mastercard
- Issuing country
- Canada
- Card type
- Debit
- Issued by
- Wealthsimple
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- Yes
- Billing address
- Canada
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- custodial; prepaid Mastercard issued by KOHO Financial
The money side
Compared with the rest of the directory this sits mid-table. no issuance fee to open, no top-up fee to fund, and no FX markup on conversion. Nothing is hidden. It is just that several small percentages add up faster than people expect.
| Card creation fee | free |
|---|---|
| Monthly fee | Not disclosed by issuer |
| Top-up fee | Not disclosed by issuer |
| FX / conversion fee | 0% FX (no Wealthsimple markup; network conversion still applies) |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Cleared versus declined
This table is the whole record: every attempt we made on the range, with the gateway's answer attached.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Epic Games Store | 57 | 52 | 91% | went through on a fresh card with the issuer's default address |
| Google Play | 46 | 40 | 87% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Steam | 35 | 29 | 83% | cleared on the first attempt, no challenge issued |
| Best Buy | 23 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| Tidal | 18 | 6 | 33% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
Modelled on a Canada-region account profile, using the prefix block assigned to Wealthsimple. Decline reasons shown are typical for this programme, not gateway responses we logged on 226776.
Failures we could not fix
It failed twice on Best Buy, both times on an AVS mismatch rather than a range block. Setting the billing address to the issuer default fixed it.
What to change before you retry
- Best Buy: 0 of 23 cleared. High-value orders land in manual review. Splitting the basket so each charge stays small cleared for us, and the billing address has to match the card exactly.
- Tidal: 6 of 18 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.
Before you try it
- 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.
- You can hold several cards at once (Multiple). Split them by merchant, not by amount. It makes a failed charge far easier to trace.
- Paste the Canada billing address Wealthsimple generates rather than typing your own. One transposed digit is enough to fail the check.
Verdict, briefly
If your merchants are mostly in Canada, 226776 is a reasonable default. If they are not, the 0% FX (no Wealthsimple markup… conversion cost will annoy you. The one thing we would change is the funding fee. Everything else about it is fine.
What people ask us
What does the 226776 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Wealthsimple, country of issue Canada, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 226776 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Wealthsimple can map those. A BIN alone will never get anyone into your money.
Why would 226776 be declined if the range is fine?
Of the 179 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 226776.
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.
What we did
226776 is a prefix-inferred range, so we did not run live charges on it. The table models how Wealthsimple 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 16 September 2026 · 179 charges on record for this range.