341306 BIN Check - Germany Amex Debit Card
Straight runs on Epic Games Store, App Store, Steam. No 3-D Secure loops, no AVS rejections, no manual review flags.
This range belongs to Mobipaid. Issued out of Germany on Amex, classed as Debit by most acquirers.
341306, decoded
- BIN
- 341306
- Card network
- Amex
- Issuing country
- Germany
- Card type
- Debit
- Issued by
- Mobipaid
- 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 it costs to run
Budget for an undisclosed issuance fee, no top-up fee, and a no decline fee penalty on declined authorizations. That last one only matters if you are pushing a lot of small charges. Everything is quoted in USD. Fund the card in the same currency wherever the issuer allows it.
| Card creation fee | — |
|---|---|
| Monthly fee | — |
| Top-up fee | — |
| FX / conversion fee | 3.5% |
| Declined transaction fee | — |
| Minimum top-up | — |
Results by merchant
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Epic Games Store | 89 | 83 | 93% | cleared on the first attempt, no challenge issued |
| App Store | 72 | 64 | 89% | no friction, and no AVS prompt |
| Steam | 55 | 47 | 85% | went through on a fresh card with the issuer's default address |
| Target | 36 | 0 | 0% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
| Walmart | 27 | 10 | 37% | Soft decline on the retry after an earlier failure on the same account. |
Run from a Germany-region account between 04 Jun to 20 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
One honest caveat: Target returned a generic decline on all attempts, and we could not determine the cause. Treat it as untested rather than blocked.
What to change before you retry
- Target: 0 of 36 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.
- Walmart: 10 of 27 cleared. Walmart re-authorises on partial shipments and its fraud rules treat non-domestic ranges as high risk. A US-issued range with a billing ZIP that matches the account city is what cleared for us; topping up the balance changed nothing.
Three things worth doing
- Set the billing address to exactly what Mobipaid generates for Germany. Copy and paste rather than retyping it; a single wrong character fails the AVS 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.
- This is an anonymous-account product. There is no meaningful account recovery, so export the card details and the billing address the moment you create them.
Our call
The 3-D Secure behaviour is the reason we keep it. It completes the challenge in-app without an SMS fallback, which matters if your number is not on the account. Worth keeping if your merchants sit in Germany. Worth ignoring if they do not.
What people ask us
What does the 341306 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Mobipaid, country of issue Germany, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 341306 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 341306 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.
How this test was run
We bought a Mobipaid card, funded it, and pushed 279 charges through live merchant checkout pages between 04 Jun to 20 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 204 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 28 August 2026 · 279 charges on record for this range.