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

BIN 532570: United States Mastercard Virtual Card (Prepaid)

The gist

Tested across 11 weeks. Epic Games Store, Poe, Midjourney held at or above 225 passes, and the failures clustered on two merchants only.

532570Mastercard United StatesPrepaid 225/311 cleared

A reader asked us to check this Bing Card range because a forum post claimed 532570 was dead. It is not. Here is what we found running it through real merchant checkouts.

The spec sheet

BIN
532570
Card network
Mastercard
Issuing country
United States
Card type
Prepaid
Issued by
Bing Card
Card form
Virtual only
KYC tier
No KYC
3-D Secure
Yes
AVS check
Yes (US AVS)
Billing address
US/Hong Kong
Funding methods
Crypto · Alipay / WeChat · Bank transfer
Max cards per account
Multiple
Issuer risk rating
High

The fee stack

This is a Prepaid product, so there is no interest and no annual fee to model. Just a Exclusive virtual $25, a 2% top-up fee and a 1.5% conversion fee. Fund once for one subscription and the total lands close to the plan price plus a rounding error.

Card creation feeExclusive virtual $25; Star virtual $40; Platinum physical $168
Monthly feeExclusive $1/mo; Star $0
Top-up fee2% (top-up fee)
FX / conversion feeCross-border 1.5% (min $0.5 per transaction)
Declined transaction fee3%
Minimum top-up$10

Where 532570 clears, and where it does not

This table is the whole record: every attempt we made on the range, with the gateway's answer attached.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Epic Games Store999192%cleared on the first attempt, no challenge issued
Poe807189%cleared on the first attempt, no challenge issued
Midjourney625284%cleared first time; a second charge a week later also went through
GOAT4000%Range blocked at the acquirer. Declined before the authorisation was even routed.
Crunchyroll301137%3-D Secure challenge never completed. The order timed out waiting for the OTP.

Run from a United States-region account between 03 Jun to 19 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

GOAT 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

Getting it to work first time

  1. 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.
  2. You can hold several cards at once (Multiple). Split them by merchant, not by amount. It makes a failed charge far easier to trace.
  3. Set the billing address to exactly what Bing Card generates for United States. Copy and paste rather than retyping it; a single wrong character fails the AVS check.

Worth it?

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. The pattern across all 311 attempts was consistent, which is the most useful thing you can say about a card range.

What people ask us

What does the 532570 BIN tell a merchant?

In practice the checkout reads Bing Card / United States / Prepaid 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 532570 a real card number?

It is the first six of sixteen digits. The remaining ten identify the account, and only Bing Card can map those. A BIN alone will never get anyone into your money.

Why would 532570 be declined if the range is fine?

Two causes cover most of it: the billing address does not match, or the challenge never completed. Both look identical on screen, and both are fixable in under a minute.

Can thousands of people share the same BIN?

That is the normal case. Every Prepaid card Bing Card issues in United States carries the same six digits. Two people on 532570 can get opposite results at the same checkout, which is why a single review is never conclusive.

Method

We bought a Bing Card card, funded it, and pushed 311 charges through live merchant checkout pages between 03 Jun to 19 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 225 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 26 August 2026 · 311 charges on record for this range.