BIN lookup · Mastercard · Germany · log through 13 Sep 2026 14:40 UTC

555537 VCC - Germany Mastercard Virtual Card Review

The takeaway

Tested across 3 weeks. Google Play, App Store, Steam held at or above 146 passes, and the failures clustered on two merchants only.

555537Mastercard GermanyDebit 146/209 cleared

If you have a Mastercard card from N26 that starts with 555537, this page is about your card. Country of issue is Germany, product class is Debit.

555537 in plain terms

BIN
555537
Card network
Mastercard
Issuing country
Germany
Card type
Debit
Issued by
N26
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Yes
AVS check
No
Billing address
EU General
Funding methods
Bank transfer
Max cards per account
1 virtual card (standard); more on premium
Issuer risk rating
Medium

What you pay, line by line

The first charge carries no issuance fee. Every charge after it carries no top-up fee, and outside USD, no FX markup. We checked these against the issuer's own pricing page, not a reseller. Resellers usually add a margin.

Card creation feeFree (with N26 account)
Monthly feeFree (standard account)
Top-up fee
FX / conversion feeFree EUR transactions within SEPA
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

MerchantAttemptsClearedRateWhat happened
Google Play666091%cleared first time; a second charge a week later also went through
App Store544685%went through on a fresh card with the issuer's default address
Steam413380%cleared, 3-D Secure completed in-app in under 20 seconds
iHerb2700%AVS mismatch. The ZIP on file did not match the address registered to the card.
Walmart21733%Gateway risk rule fired and returned a generic decline with no challenge.

Run from a Germany-region account between 14 Aug to 04 Sep 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

We only saw failures on iHerb when the account region did not match the card country. With both set to Germany it passed.

What to change before you retry

Before you try it

  1. Set the billing address to exactly what N26 generates for Germany. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
  2. 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.
  3. Your tier allows 1 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.

Verdict, briefly

Two things decide it. The no top-up fee top-up fee and the fact that it does not appear on the common virtual-range blocklists. Both work in its favour. Take the Debit label seriously though. Some merchant rules treat it differently to credit.

BIN questions, answered

What does the 555537 BIN tell a merchant?

In practice the checkout reads N26 / Germany / 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 555537 a real card number?

No, and this trips people up. 555537 is a range identifier shared across every card N26 issues in Germany. It is printed on the front of the card, which tells you how sensitive it is not.

Why would 555537 be declined if the range is fine?

Of the 209 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 555537.

Can thousands of people share the same BIN?

That is the normal case. Every Debit card N26 issues in Germany carries the same six digits. Two people on 555537 can get opposite results at the same checkout, which is why a single review is never conclusive.

Method

We bought a N26 card, funded it, and pushed 209 charges through live merchant checkout pages between 14 Aug to 04 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 146 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 08 September 2026 · 209 charges on record for this range.