464073 BIN Check - Latin America Visa Debit Card
Straight runs on App Store, Steam, Epic Games Store. No 3-D Secure loops, no AVS rejections, no manual review flags.
We added 464073 to the directory after it cleared a checkout that had already rejected two better-known ranges. It is a Debit Visa prefix from MiniPay Card, issued in Latin America.
The spec sheet
- BIN
- 464073
- Card network
- Visa
- Issuing country
- Latin America
- Card type
- Debit
- Issued by
- MiniPay Card
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Europe/LATAM
- Funding methods
- Crypto
- Max cards per account
- Multiple
- Issuer risk rating
- Medium
Costs, stacked up
This is a Debit product, so there is no interest and no annual fee to model. Just no issuance fee, no top-up fee and no FX markup. Everything is quoted in USD. Fund the card in the same currency wherever the issuer allows it.
| Card creation fee | Free |
|---|---|
| Monthly fee | Free |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
Merchant by merchant
Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| App Store | 42 | 38 | 90% | cleared on the first attempt, no challenge issued |
| Steam | 34 | 30 | 88% | no friction, and no AVS prompt |
| Epic Games Store | 26 | 22 | 85% | cleared first time; a second charge a week later also went through |
| Hetzner | 17 | 0 | 0% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
| Tidal | 13 | 4 | 31% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Run from a Latin America-region account between 17 Jul to 14 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
The pattern in our failures is geographic. Hetzner accepted it once the account region matched Latin America, and refused it every time it did not.
What to change before you retry
- Hetzner: 0 of 17 cleared. Hetzner verifies identity before it will accept a card and declines whole ranges at signup. Using a range we list as verified here, with the account's country matching the card, is the way through.
- Tidal: 4 of 13 cleared. Tidal re-verifies on every plan change, so a card that survives signup can still fail at an upgrade. Keep the address static between changes.
Setup notes for MiniPay Card
- Set the billing address to exactly what MiniPay Card generates for Latin America. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- You can hold several cards at once (Multiple). Split them by merchant, not by amount. It makes a failed charge far easier to trace.
- 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?
Two things decide it. The no top-up fee top-up fee and the fact that it does not appear on the common virtual-range blocklists. Both work in its favour. That was true on our accounts. Yours may sit in a different risk bucket, which changes the result.
FAQ
What does the 464073 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer MiniPay Card, country of issue Latin America, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 464073 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 464073 be declined if the range is fine?
Of the 132 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 464073.
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
We bought a MiniPay Card card, funded it, and pushed 132 charges through live merchant checkout pages between 17 Jul to 14 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 94 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 20 August 2026 · 132 charges on record for this range.