Best crypto cards
Cards for spending crypto. We scored 15 of them 0–10 from public data — age plus latency and status transparency (our probe) — and ranked the 14 we could measure well enough to place fairly. No affiliate links: the order reflects the evidence, nothing else.
Last collection 2026-08-25: probed 252 services, measured 233, over a 90-day window. Collected by our own script, not by hand — reproducible, and reproducibly boring.
The full ranking
| # | Service | Score | Age | Latency | Median fix | Status feed |
|---|---|---|---|---|---|---|
| 1 | Coinbase Card | 944% | — | 307 ms | 104 min | statuspage |
| 2 | Wirex | 8.68100% | 12.7y | 387 ms | 241 min | statuspage |
| 3 | Bitpanda Card | 8.5978% | 12.7y | 299 ms | 366 min | statuspage |
| 4 | Nexo Card | 8.0456% | 8.7y | 205 ms | — | unknown |
| 5 | Crypto.com Card | 8.0378% | 10.7y | 535 ms | 568 min | statuspage |
| 6 | Fold | 7.7478% | 7.7y | 128 ms | — | none |
| 7 | Gnosis Pay | 7.544% | — | 52 ms | — | unknown |
| 8 | Plutus | 7.4678% | 11.7y | 257 ms | — | none |
| 9 | Holyheld | 644% | — | 56 ms | — | none |
| 10 | Bitget Card | 644% | — | 86 ms | — | none |
| 11 | Kast | 644% | — | 54 ms | — | none |
| 12 | RedotPay | 644% | — | 107 ms | — | none |
| 13 | Baanx | 644% | — | 40 ms | — | none |
| 14 | Bybit Card | 244% | — | — | — | none |
Every figure carries the date it was taken, on the service’s card below, linked to its open source. Score is out of what we could measure — the % beside it is coverage.
How we scored crypto cards
These weights belong to this category alone. Signature measurement here: Age plus latency and status transparency (our probe) — Payment services: track record plus the uptime of the authorization path.
How long it has run and survived — time is signal.
Response latency we measure ourselves from a public endpoint.
Whether it publishes a status page anyone can audit.
How fast it resolves incidents, from its own timestamps.
Latency in this category is timed at the live interface for every service, so the comparison is like-for-like. We never compare latency across categories — a DEX interface and an exchange API are not the same thing, and pretending otherwise would just reward whoever we happened to probe more cheaply.
The brief also defines FEES and UX (0%, 0%). We don’t publish them: we can’t measure them ourselves, and an estimate dressed as a measurement is worse than a gap. Full methodology
The services
No documented launch or listing date to measure age from.
Publishes a machine-readable incident archive (statuspage) — its whole record can be checked by anyone, including against us.
Measured 307 ms, but at a different surface from the rest of this category — not comparable, so shown as context, not scored.
Median 104 min from published report to resolution across 50 logged incidents. Scored on repair speed, not on how many it logged.
The provider’s feed returns its 50 most recent incidents and no more, which here reaches back 48 days. The remaining 42 are blank because we cannot see them — not because nothing happened.
Over the 48 days the feed covers. Not scored — logging granularity varies between services.
Timed at a different surface from the rest of this category, so not a fair comparison — not scored.
Incident repair time: Median 104 min from published report to resolution across 50 logged incidents. Scored on repair speed, not on how many it logged.
Wirex
Live 12.7 yr (since founding (2014), public record). Most failures happen young, so time survived is real signal.
Publishes a machine-readable incident archive (statuspage) — its whole record can be checked by anyone, including against us.
Median 387 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
Median 241 min from published report to resolution across 6 logged incidents. Scored on repair speed, not on how many it logged.
Over the 90 days the feed covers. Not scored — logging granularity varies between services.
Incident repair time: Median 241 min from published report to resolution across 6 logged incidents. Scored on repair speed, not on how many it logged.
Live 12.7 yr (since founding (2014), public record). Most failures happen young, so time survived is real signal.
Publishes a machine-readable incident archive (statuspage) — its whole record can be checked by anyone, including against us.
Measured 299 ms, but at a different surface from the rest of this category — not comparable, so shown as context, not scored.
Median 366 min from published report to resolution across 9 logged incidents. Scored on repair speed, not on how many it logged.
Over the 90 days the feed covers. Not scored — logging granularity varies between services.
Timed at a different surface from the rest of this category, so not a fair comparison — not scored.
Incident repair time: Median 366 min from published report to resolution across 9 logged incidents. Scored on repair speed, not on how many it logged.
Live 8.7 yr (since founding (2018), public record). Most failures happen young, so time survived is real signal.
A status page exists but publishes no feed we could parse — readable, not auditable. Part of that may be our blind spot (we read three platforms).
Measured 205 ms, but at a different surface from the rest of this category — not comparable, so shown as context, not scored.
No incident feed we can read, so no repair time to compute.
Timed at a different surface from the rest of this category, so not a fair comparison — not scored.
Status transparency: A status page exists but publishes no feed we could parse — readable, not auditable. Part of that may be our blind spot (we read three platforms).
Live 10.7 yr (since founding (2016), public record). Most failures happen young, so time survived is real signal.
Publishes a machine-readable incident archive (statuspage) — its whole record can be checked by anyone, including against us.
Measured 535 ms, but at a different surface from the rest of this category — not comparable, so shown as context, not scored.
Median 568 min from published report to resolution across 9 logged incidents. Scored on repair speed, not on how many it logged.
Over the 90 days the feed covers. Not scored — logging granularity varies between services.
Timed at a different surface from the rest of this category, so not a fair comparison — not scored.
Incident repair time: Median 568 min from published report to resolution across 9 logged incidents. Scored on repair speed, not on how many it logged.
Anyone who cannot sit out a long outage — when it breaks, the median fix runs into many hours.
Fold
Live 7.7 yr (since founding (2019), public record). Most failures happen young, so time survived is real signal.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
Median 128 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
No documented launch or listing date to measure age from.
A status page exists but publishes no feed we could parse — readable, not auditable. Part of that may be our blind spot (we read three platforms).
Median 52 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No incident feed we can read, so no repair time to compute.
Status transparency: A status page exists but publishes no feed we could parse — readable, not auditable. Part of that may be our blind spot (we read three platforms).
Plutus
Live 11.7 yr (since founding (2015), public record). Most failures happen young, so time survived is real signal.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
Median 257 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Holyheld
No documented launch or listing date to measure age from.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
Median 56 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Bitget Card
No documented launch or listing date to measure age from.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
Median 86 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Kast
No documented launch or listing date to measure age from.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
Median 54 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
RedotPay
No documented launch or listing date to measure age from.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
Median 107 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Baanx
No documented launch or listing date to measure age from.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
Median 40 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Bybit Card
No documented launch or listing date to measure age from.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
Our probe could not reach it (our own probe failed: 20). Measured from one location, so it may be a block on us — but it is what we saw.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Who we left out, and why
We looked at 15, ranked 14, and could not measure 1.
| Service | Status feed | Why it isn’t ranked |
|---|---|---|
| Ether.fi Cash | none | 1 of 4 criteria measurable, 22% of this category’s weight — under the 25% a place in the ranking needs. Left unranked on purpose: the less we measure, the fewer criteria there are to dock points on, so a thinly-measured service drifts upward for no reason but our ignorance. |
Head to head
How to choose crypto cards
Cards for spending crypto — and the honest truth is that no single ranking fits everyone. Our scores tell you what is best-evidenced on public data: age plus latency and status transparency (our probe). Use them as a shortlist, not a verdict.
Start at the top of the table, then open the full breakdown for any service you are considering. Read the coverage figure beside its score — a high number on thin coverage is a narrower claim than the same score fully measured. Check the “where we docked points” and “who it’s not for” notes on each card; the service that scores highest overall is not always the one that fits your specific need. And remember what these scores deliberately leave out — fees and support quality — which you should weigh yourself before committing.
Crypto cards ratings — FAQ
How are crypto cards ranked on this page?+
Each service is scored 0–10 from public data — age plus latency and status transparency (our probe) — weighted for what matters in this category, plus our own latency and status checks. 14 of 15 are ranked; the rest we could not measure enough to place fairly. Every figure is dated and links to its source.
What is the best crypto card?+
On the data we could measure, Coinbase Card scores highest at 9/10, ahead of Wirex (8.68/10). "Best" here means best-evidenced, not most advertised — open each service below for the full breakdown and decide what fits your needs.
Why isn’t the biggest name at the top?+
Size is not a criterion. A large service that publishes no audits or status page cannot demonstrate its safety from the outside, so it scores below a smaller one that can — even if it is perfectly sound. We rate what is verifiable, not what is famous.
What does the "% measured" figure under a score mean?+
It is the share of this category's criteria weight we could actually fill for that service. Anything we could not measure is marked n/a and its weight is redistributed across the rest — never counted as zero — so the percentage tells you how complete the verdict is.
Do you earn money from these rankings?+
No. There are no affiliate links, no paid placements and no sponsored entries anywhere in the ratings section. That is what lets this list put a smaller, audited service above a bigger, opaque one.
No affiliate links, paid placements or ads anywhere on this site. How this is funded · Methodology