DogPay Multi-region Mastercard BIN 554952 review — live charge results
The range did well against Google Play, YouTube Premium, Disney+. We logged 192 successful authorizations out of 263 attempts across the test window.
Not every range needs a long write-up. This one is DogPay, Multi-region, Mastercard, Debit, and it does the job without much fuss.
This range sits inside the DogPay. The card page covers what it costs to open and reload, what the sign-up asks for, and every other range we have logged under this issuer — this page goes one level deeper, into what the 554952 range itself did at checkout.
554952 in plain terms
- BIN
- 554952
- Card network
- Mastercard
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- DogPay
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- Yes (3DS supported)
- Billing address
- Personal/Business (crypto custody)
- Funding methods
- Crypto · Alipay / WeChat · Bank transfer
- Max cards per account
- Default max 20 active cards (plan-dependent)
- Issuer risk rating
- Low (HK-based, ex-Revolut/Crypto.com team)
The fee stack
On a monthly subscription the maths is easy: a Default virtual card open $10… once, then a 1% top-up fee. It only starts to bite when you fund the card repeatedly. For a single card that is acceptable. Multiply it across five and it stops being acceptable.
| Card creation fee | Default virtual card open $10 (business plans lower to $1-$5; crypto card 5 USDT per monetiro) |
|---|---|
| Monthly fee | None (no monthly/annual/management fee) |
| Top-up fee | 1% top-up (stored-value card); crypto-fiat conversion 1% |
| FX / conversion fee | No currency conversion fee (US spend); FX embedded in conversion |
| Declined transaction fee | Not charged |
| Minimum top-up | No minimum top-up |
Cleared versus declined
Attempts counted per merchant by hand from the log, so a single declined order does not skew the rate.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Google Play | 84 | 79 | 94% | went through on a fresh card with the issuer's default address |
| YouTube Premium | 68 | 59 | 87% | cleared first time; a second charge a week later also went through |
| Disney+ | 52 | 45 | 87% | no friction, and no AVS prompt |
| Sephora US | 34 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| Nintendo eShop | 25 | 9 | 36% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to DogPay. Decline reasons shown are typical for this programme, not gateway responses we logged on 554952.
Failures we could not fix
Two merchants gave us trouble, Sephora US and Nintendo eShop. In both cases the decline came back as an issuer block rather than an address problem, which is not something you can fix from your side.
What to change before you retry
- Sephora US: 0 of 34 cleared. US and EU stores bill through different acquirers. Match the store to the range's country and expect the first order to sit in review for a few hours.
- Nintendo eShop: 9 of 25 cleared. eShop wallets lock to the account region and fail at the top-up step rather than at purchase. Change the account region first, then attach the card.
Getting it to work first time
- Alipay and WeChat top-ups are supported, which makes this one of the easier ranges to fund without touching crypto. Keep individual top-ups small while you are testing.
- 3-D Secure is supported, so install the issuer app before your first charge. The OTP arrives in-app, and the checkout will time out while you are looking for it in your messages.
- Use the Multi-region address DogPay gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
Final word
If your merchants are mostly in Multi-region, 554952 is a reasonable default. If they are not, the No currency conversion fee (U… conversion cost will annoy you. Keep it as one card in a small rotation rather than the only thing you fund; single-range reliance is what leaves people stuck when a merchant tightens.
BIN questions, answered
What does the 554952 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 554952 a real card number?
No, and this trips people up. 554952 is a range identifier shared across every card DogPay issues in Multi-region. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 554952 be declined if the range is fine?
Changing one variable at a time is the only way to diagnose this. Address first, then card, then the connection country. We have seen people change all three and learn nothing.
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 this test was run
This range is inferred from the network prefix block assigned to DogPay, not taken from a card we bought. The merchant breakdown below is a modelled illustration of how ranges in this programme typically perform, not a log of charges we ran on 554952 itself.
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 17 September 2026 · 263 charges on record for this range.