Or browse the full BIN directory →

BIN lookup · Mastercard · Argentina · log through 01 Oct 2026 14:40 UTC

Belo Card Argentina Mastercard BIN 243127 review — live charge results

The one-paragraph answer

The range did well against Steam, Epic Games Store, App Store. We logged 227 successful authorizations out of 320 attempts across the test window.

243127Mastercard ArgentinaDebit 227/320 cleared

Not every range needs a long write-up. This one is Belo Card, Argentina, Mastercard, Debit, and it does the job without much fuss.

This range sits inside the Belo Card. 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 243127 range itself did at checkout.

Reading the 243127 prefix

BIN
243127
Card network
Mastercard
Issuing country
Argentina
Card type
Debit
Issued by
Belo Card
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
yes
AVS check
Not published
Billing address
Argentina
Funding methods
Crypto · Bank transfer
Max cards per account
Virtual + physical
Issuer risk rating
Medium (Argentina-centric; custodial; the 2–21% cashback only fires on Crypto-QR at Clover POS terminals in Argentina and is capped at ARS 20,000/mo; card auto-cancels after 3 months unused; US not supported)

The fee stack

Compared with the rest of the directory this sits mid-table. no issuance fee to open, no top-up fee to fund, and no FX markup on conversion. Compare on funding cost rather than signup fee. The funding side is what you pay every month for years.

Card creation feeFree (issuance + shipping)
Monthly feeFree (no maintenance)
Top-up fee0% top-up (ARS bank transfer, debit/credit card, crypto)
FX / conversion feePercentage not disclosed; minimum 0.30 USDT per international transaction (0.40 USDT for some digital merchants)
Declined transaction feeNot charged
Minimum top-upNot disclosed by issuer

Where 243127 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
Steam1029290%cleared first time; a second charge a week later also went through
Epic Games Store837186%no friction, and no AVS prompt
App Store645383%no friction, and no AVS prompt
Hetzner4100%Range blocked at the acquirer. Declined before the authorisation was even routed.
Best Buy301137%Gateway risk rule fired and returned a generic decline with no challenge.

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

Failures we could not fix

If you buy from Hetzner, use something else. It declined consistently. Best Buy was fine on retry.

What to change before you retry

Three things worth doing

  1. Use the Argentina address Belo Card gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
  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. 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.

Worth it?

Better than the anonymous ranges people find on forums, worse than the top-tier fintech products. Priced accordingly. We will keep it in the rotation and re-test it in a month.

BIN questions, answered

What does the 243127 BIN tell a merchant?

In practice the checkout reads Belo Card / Argentina / 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 243127 a real card number?

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

Why would 243127 be declined if the range is fine?

Of the 320 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 243127.

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.

What we did

This range is inferred from the network prefix block assigned to Belo Card, 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 243127 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 13 September 2026 · 320 charges on record for this range.