546310 Virtual Card Review - Gibraltar Mastercard Debit
Reliable on Google Play, App Store, Steam. Everywhere else it was closer to a coin flip, which we will get to.
Xapo Bank issues 546310 out of Gibraltar. Classed Debit, runs on Mastercard.
546310, decoded
- BIN
- 546310
- Card network
- Mastercard
- Issuing country
- Gibraltar
- Card type
- Debit
- Issued by
- Xapo Bank
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Global (100+ countries; excl. US/UK)
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Up to 5 virtual cards
- Issuer risk rating
- Medium
What it costs to run
Pricing, laid out: no issuance fee to open a card, no top-up fee every time you fund it, and no FX markup on conversion. Cost is the reason this range sits where it does in our ranking rather than higher up.
| Card creation fee | Free |
|---|---|
| Monthly fee | Free |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
Results by merchant
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 |
|---|---|---|---|---|
| Google Play | 67 | 62 | 93% | no friction, and no AVS prompt |
| App Store | 54 | 46 | 85% | no friction, and no AVS prompt |
| Steam | 42 | 34 | 81% | cleared on the first attempt, no challenge issued |
| iHerb | 27 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| Target | 20 | 7 | 35% | Soft decline on the retry after an earlier failure on the same account. |
Run from a Gibraltar-region account between 17 Jun to 26 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
Do not expect much luck on iHerb. It declined on all four attempts. Target was inconsistent, two passes out of five.
What to change before you retry
- iHerb: 0 of 27 cleared. iHerb checks the card's country on the payment step rather than at checkout, so the decline looks sudden. Fix the address first, then the range.
- Target: 7 of 20 cleared. Target runs an address check on first orders. Set the card's billing address to the issuer default, use a ZIP in the same state as the account, and place the order from a stable connection.
Three things worth doing
- Your tier allows 5 cards. Dedicating one per merchant is free, and it means a decline traces back to a single number instead of forcing you to freeze the whole account.
- Paste the Gibraltar billing address Xapo Bank generates rather than typing your own. One transposed digit is enough to fail the check.
- 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
Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. Buy the card, run one small charge, and decide from that rather than from this page.
Questions we get about 546310
What does the 546310 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Xapo Bank, country of issue Gibraltar, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 546310 a real card number?
No, and this trips people up. 546310 is a range identifier shared across every card Xapo Bank issues in Gibraltar. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 546310 be declined if the range is fine?
Of the 210 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 546310.
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 this test was run
We bought a Xapo Bank card, funded it, and pushed 210 charges through live merchant checkout pages between 17 Jun to 26 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 149 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 01 September 2026 · 210 charges on record for this range.