UltimoPay Card Visa Multi-region virtual card (BIN 461401): what cleared
Our log shows clean passes on Epic Games Store, Steam, Google Play, first charge and renewal both going through.
We added 461401 to the directory after it cleared a checkout that had already rejected two better-known ranges. It is a Debit Visa prefix from UltimoPay Card, issued in Multi-region.
UltimoPay Card issues this range. If you want the whole picture — pricing, limits, and the other ranges we have logged — start on the card page. Below is the narrower story: what the 461401 range cleared, what bounced, and why.
The spec sheet
- BIN
- 461401
- Card network
- Visa
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- UltimoPay Card
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- not published
- AVS check
- not published
- Billing address
- Offshore account; prepaid only, no IBAN
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- not published
- Issuer risk rating
- High - very high entry cost ($600 issuance plus $80/year); fully custodial; the issuer of record is Joint Development Bank (JDB), Laos, which was placed under EU sanctions in 2026 and has been linked by third-party reviewers to card payments and ATM withdrawals failing since May 2026 with funds reportedly frozen; limited public fee transparency
The money side
Nothing exotic in the pricing. $600 ($450 card issuance + $1…, a 1% top-up fee, and on non-USD billing, a 0.75% conversion fee. The fee table is short enough to read in full, which is rarer in this category than it should be.
| Card creation fee | $600 ($450 card issuance + $150 bank opening deposit) |
|---|---|
| Monthly fee | $80/year ($50 bank maintenance + $30 wallet) |
| Top-up fee | 1% instant crypto-to-USD conversion (free if you wait 72 hours) |
| FX / conversion fee | 0.75% merchant/ATM transaction fee |
| Declined transaction fee | not published |
| Minimum top-up | not published (no stated minimum) |
Cleared versus declined
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Epic Games Store | 65 | 60 | 92% | no friction, and no AVS prompt |
| Steam | 53 | 47 | 89% | went through on a fresh card with the issuer's default address |
| Google Play | 40 | 32 | 80% | no friction, and no AVS prompt |
| Tidal | 26 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| Sephora US | 20 | 7 | 35% | 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 UltimoPay Card. Decline reasons shown are typical for this programme, not gateway responses we logged on 461401.
Failures we could not fix
Failures were rare but real: Tidal declined on three attempts, and we never did get it through.
What to change before you retry
- Tidal: 0 of 26 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.
- Sephora US: 7 of 20 cleared. US and EU stores bill through different acquirers. Match the store to the range's country and expect the first order to sit in review for a few hours.
Do these first
- 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 range does not advertise 3-D Secure. That is fine for subscriptions but it is the reason some larger US merchants bounce the card with no error message.
- Paste the Multi-region billing address UltimoPay Card generates rather than typing your own. One transposed digit is enough to fail the check.
Our call
Verdict: worth keeping for Multi-region checkouts. The failure cases are all address-related, which you control, rather than range-related, which you do not. If you find a merchant where it behaves differently, tell us and we will add it to the log.
The things people actually ask
What does the 461401 BIN tell a merchant?
In practice the checkout reads UltimoPay Card / Multi-region / 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 461401 a real card number?
No, and this trips people up. 461401 is a range identifier shared across every card UltimoPay Card issues in Multi-region. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 461401 be declined if the range is fine?
Of the 204 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 461401.
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 UltimoPay 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 461401 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 11 September 2026 · 204 charges on record for this range.