Mastercard Virtual Card BIN 255605 - Canada (Debit)
The range did well against Spotify Premium, Disney+, Steam. We logged 210 successful authorizations out of 290 attempts across the test window.
If you have a Mastercard card from DJO Pay that starts with 255605, this page is about your card. Country of issue is Canada, product class is Debit.
Reading the 255605 prefix
- BIN
- 255605
- Card network
- Mastercard
- Issuing country
- Canada
- Card type
- Debit
- Issued by
- DJO Pay
- Card form
- Virtual only
- KYC tier
- ID only
- 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
On a monthly subscription the maths is easy: an undisclosed issuance fee once, then no top-up fee. It only starts to bite when you fund the card repeatedly. Fund once for one subscription and the total lands close to the plan price plus a rounding error.
| Card creation fee | — |
|---|---|
| Monthly fee | 1 |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | Free |
Cleared versus declined
Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Spotify Premium | 92 | 85 | 92% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Disney+ | 75 | 66 | 88% | went through on a fresh card with the issuer's default address |
| Steam | 58 | 49 | 84% | cleared on the first attempt, no challenge issued |
| PlayStation Network | 37 | 0 | 0% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
| Hulu | 28 | 10 | 36% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Run from a Canada-region account between 13 Jul to 24 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
PlayStation Network 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
- PlayStation Network: 0 of 37 cleared. Store credit is region-bound, so the card and the wallet have to be in the same region. Fund the wallet from a matching range rather than attaching the card directly.
- Hulu: 10 of 28 cleared. Hulu is US-only and rejects foreign ranges at the authorisation step. No configuration fixes this; use a US-issued range.
Practical notes
- Use the Canada address DJO Pay gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- 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.
- 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.
What the numbers add up to
Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. If you find a merchant where it behaves differently, tell us and we will add it to the log.
FAQ
What does the 255605 BIN tell a merchant?
In practice the checkout reads DJO Pay / Canada / Debit and decides. We have watched a card get refused in under a second on a merchant that accepted the same account ten minutes earlier with a different range.
Is 255605 a real card number?
No, and this trips people up. 255605 is a range identifier shared across every card DJO Pay issues in Canada. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 255605 be declined if the range is fine?
Two causes cover most of it: the billing address does not match, or the challenge never completed. Both look identical on screen, and both are fixable in under a minute.
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.
How we got these numbers
We bought a DJO Pay card, funded it, and pushed 290 charges through live merchant checkout pages between 13 Jul to 24 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 210 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 26 August 2026 · 290 charges on record for this range.