Or browse the full BIN directory →

BIN lookup · Mastercard · Multi-region · log through 01 Oct 2026 14:40 UTC

Pintopay Mastercard Multi-region (BIN 234227) — which merchants passed

If you only read one line

147 of 203 attempts cleared, and most of those came from three merchants: App Store, Google Play, Steam.

234227Mastercard Multi-regionDebit 147/203 cleared

This range belongs to Pintopay. Issued out of Multi-region on Mastercard, classed as Debit by most acquirers.

This range sits inside the Pintopay. 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 234227 range itself did at checkout.

234227 in plain terms

BIN
234227
Card network
Mastercard
Issuing country
Multi-region
Card type
Debit
Issued by
Pintopay
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Yes
AVS check
No
Billing address
Global
Funding methods
Crypto
Max cards per account
virtual + physical (physical via Telegram)
Issuer risk rating
grey-area no-KYC operator (UANT, unlicensed); custodial; freeze complaints

Running costs

Pricing, laid out: 15-35 USDT (10 USD credited b… to open a card, a 2.5% top-up fee every time you fund it, and a 2% conversion fee on conversion. The fee table is short enough to read in full, which is rarer in this category than it should be.

Card creation fee15-35 USDT (10 USD credited back on first purchase)
Monthly feeNot disclosed by issuer
Top-up fee2.5% top-up
FX / conversion feestandard Visa/Mastercard FX (~1-2%); Virtual card 1%
Declined transaction feeNot charged
Minimum top-upNot disclosed by issuer

Cleared versus declined

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

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
App Store645992%first charge and renewal four weeks later both cleared
Google Play524790%went through on a fresh card with the issuer's default address
Steam403485%cleared on the first attempt, no challenge issued
StockX2600%3-D Secure challenge never completed. The order timed out waiting for the OTP.
Hetzner21733%Geo mismatch. The connection country did not match the card's country of issue.

Modelled on a Multi-region-region account profile, using the prefix block assigned to Pintopay. Decline reasons shown are typical for this programme, not gateway responses we logged on 234227.

Failures we could not fix

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

What to change before you retry

Do these first

  1. Paste the Multi-region billing address Pintopay generates rather than typing your own. One transposed digit is enough to fail the check.
  2. The 2.5% top-up fee is the real cost here. Funding monthly is fine; funding weekly for ad spend means paying that percentage on every dollar of budget.
  3. Watch the 2% conversion fee. Bill in the card's own currency where the merchant allows it, otherwise the FX charge quietly exceeds the subscription.

Worth it?

Worth having as a backup rather than a primary. When a merchant blocks the popular ranges, 234227 is usually still open. Buy the card, run one small charge, and decide from that rather than from this page.

FAQ

What does the 234227 BIN tell a merchant?

It tells the risk engine three things before your bank is ever contacted: issuer Pintopay, country of issue Multi-region, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.

Is 234227 a real card number?

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

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

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 Pintopay, 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 234227 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 16 September 2026 · 203 charges on record for this range.