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

229515 BIN Check - Germany Mastercard Debit Card

If you only read one line

Strongest results on Bing Ads, GitHub Copilot, OpenAI. Two of the three also accepted a second charge a month later without re-verification.

229515Mastercard GermanyDebit 92/132 cleared

229515 appears on Mastercard cards issued by Buvei to Germany customers. That is the whole identification. Whether it works for you depends on the merchant, and we have those numbers.

Reading the 229515 prefix

BIN
229515
Card network
Mastercard
Issuing country
Germany
Card type
Debit
Issued by
Buvei
Card form
Virtual only
KYC tier
Not published
3-D Secure
Not published
AVS check
No
Billing address
Multi-BIN (15+ BINs, 35+ currencies)
Funding methods
Crypto
Max cards per account
Unlimited
Issuer risk rating
Medium

What it costs to run

Nothing exotic in the pricing. $1/card (BIN 525797 & 238003), a 2% top-up fee, and on non-USD billing, no FX markup. Everything is quoted in USD. Fund the card in the same currency wherever the issuer allows it.

Card creation fee$1/card (BIN 525797 & 238003); $5/card (BIN 525847)
Monthly feeFree
Top-up fee2% (BIN 525797/238003); 4% (BIN 525847)
FX / conversion fee
Declined transaction fee$0.20/txn (BIN 525797/238003); 0% (BIN 525847)
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
Bing Ads423788%cleared on the first attempt, no challenge issued
GitHub Copilot343088%first charge and renewal four weeks later both cleared
OpenAI262181%first charge and renewal four weeks later both cleared
Walmart1700%3-D Secure challenge never completed. The order timed out waiting for the OTP.
Nike US13431%AVS mismatch. The ZIP on file did not match the address registered to the card.

Run from a Germany-region account between 11 Jul to 22 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

Walmart 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

Setup notes for Buvei

  1. 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.
  2. Set the billing address to exactly what Buvei generates for Germany. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
  3. Card issuance is effectively unlimited here. Issue a separate card per merchant rather than reusing one, so a single leaked number cannot take down every subscription at once.

Verdict, briefly

Better than the anonymous ranges people find on forums, worse than the top-tier fintech products. Priced accordingly. That was true on our accounts. Yours may sit in a different risk bucket, which changes the result.

FAQ

What does the 229515 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 229515 a real card number?

Six digits of a sixteen-digit number. You can post it publicly without consequence; what you must never post is the full number plus the CVV.

Why would 229515 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?

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.

Method

We bought a Buvei card, funded it, and pushed 132 charges through live merchant checkout pages between 11 Jul to 22 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 92 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 24 August 2026 · 132 charges on record for this range.