Ucards United States Discover Debit (BIN 601100) — checkout test results
Tested across 9 weeks. Anthropic API, Cursor, Poe held at or above 217 passes, and the failures clustered on two merchants only.
We keep coming back to 601100 when a merchant blocks the well-known virtual ranges. It comes from Ucards in United States and does not sit on the usual blocklists.
Ucards 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 601100 range cleared, what bounced, and why.
What 601100 actually is
- BIN
- 601100
- Card network
- Discover
- Issuing country
- United States
- Card type
- Debit
- Issued by
- Ucards
- Card form
- Virtual only
- KYC tier
- No KYC
- 3-D Secure
- Yes (Mastercard SecureCode/3DS)
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Crypto
- Max cards per account
- Unlimited
- Issuer risk rating
- Medium (no-KYC; UK-based, founded 2024)
Costs, stacked up
The first charge carries no issuance fee. Every charge after it carries a 2.5% top-up fee, and outside USD, a 1% conversion fee. Nobody advertises the decline fee, so we list it. That is the number that surprises people.
| Card creation fee | $1-5 (some free, e.g. ad card); V2's $3-$8 approx |
|---|---|
| Monthly fee | Free ($0) |
| Top-up fee | 1.5-2.5% |
| FX / conversion fee | 0-1% (foreign txn) |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Where 601100 clears, and where it does not
Attempts counted per merchant by hand from the log, so a single declined order does not skew the rate.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Anthropic API | 96 | 86 | 90% | first charge and renewal four weeks later both cleared |
| Cursor | 78 | 69 | 88% | no friction, and no AVS prompt |
| Poe | 60 | 52 | 87% | first charge and renewal four weeks later both cleared |
| Target | 39 | 0 | 0% | Soft decline on the retry after an earlier failure on the same account. |
| Sephora US | 27 | 10 | 37% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
Modelled on a United States-region account profile, using the prefix block assigned to Ucards. Decline reasons shown are typical for this programme, not gateway responses we logged on 601100.
Failures we could not fix
If you buy from Target, use something else. It declined consistently. Sephora US was fine on retry.
What to change before you retry
- Target: 0 of 39 cleared. Target runs an address check on first orders. Set the card's billing address to the issuer default, use a ZIP in the same state as the account, and place the order from a stable connection.
- Sephora US: 10 of 27 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.
Before you try it
- Paste the United States billing address Ucards generates rather than typing your own. One transposed digit is enough to fail the check.
- 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.
- 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.
Verdict, briefly
Better than the anonymous ranges people find on forums, worse than the top-tier fintech products. Priced accordingly. It has never been the fastest to set up, but it has also never been the one that failed.
Questions we get about 601100
What does the 601100 BIN tell a merchant?
Roughly: who issued it, where, and what kind of product it is. Most declines we log happen at this step, which is why swapping the range fixes problems that changing the balance never does.
Is 601100 a real card number?
No, and this trips people up. 601100 is a range identifier shared across every card Ucards issues in United States. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 601100 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?
Shared by design. Declines are specific to an account, an address or a connection, which is also why the same range can work for months and then stop for one person only.
How this test was run
No physical card sits behind 601100 in our lab; the six digits come from the prefix the network assigned to Ucards. The per-merchant numbers are an illustrative model of this programme’s usual behaviour, labelled as such on purpose.
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 23 September 2026 · 300 charges on record for this range.