Kripicard vs WaldenPay
WaldenPay has the higher grade on both axes: Safety 4.4 against 4.0, and Privacy 3.8 against 2.1.
Kripicard
Virtual Visa and Mastercard cards funded with crypto, issued through partners
Privacy
2.1/ 10
Poor
Safety
4.0/ 10
Caution
ID on risk flag KYC 3 Docs reviewed Full review →
WaldenPay
Virtual prepaid card loaded with crypto, run by a Dutch company
Privacy
3.8/ 10
Poor
Safety
4.4/ 10
Caution
ID in rare cases KYC 2 Docs reviewed Full review →
Side by side
| Kripicard | WaldenPay | |
|---|---|---|
| Category | Crypto Cards | Crypto Cards |
| KYC policy | ID on risk flag | ID in rare cases |
| Custody | Custodial | Custodial |
| Sign-up | Not published | Email required |
| Open source | No | No |
| Tor onion address | No | No |
| Coins | USDT, BTC, ETH, SOL, USDC, TON, LTC, XMR | USDT, USDC, BTC, ETH, SOL, TRX, LTC |
| Pay with | Crypto, Monero | Crypto |
| Fees | Fees are published on the fees page and shown at purchase; figures were not reviewed | $10 card issuance; top-up fee 5%, falling to 3% with 30-day spend volume; no monthly fee |
| Limits | Card and operational limits are disclosed during purchase or top-up | User-to-user transfers: $10,000 per transfer, $20,000 per rolling 24 hours; card load limits not stated |
| Jurisdiction | Brazil | Netherlands |
| Not available in | Not published | Restricted jurisdictions listed on the countries page, including Belarus, Afghanistan, Myanmar and the Crimea, Donetsk and Luhansk regions |
| Incidents on record | 0 | 0 |
| Published tests (180 days) | 0 | 0 |
Only Kripicard
Accepts MoneroMay request ID
Both
CustodialClosed sourceAML screeningLegal entity disclosed
Only WaldenPay
Requires email
Where they sit among crypto cards
Questions
Is Kripicard or WaldenPay safer?
WaldenPay has the higher Safety grade: Kripicard 4.0, WaldenPay 4.4, out of 10.
Does Kripicard or WaldenPay require KYC?
Kripicard is KYC level 3 (ID on risk flag). WaldenPay is KYC level 2 (ID in rare cases).
Which has more incidents on record?
Kripicard has 0 and WaldenPay has 0 documented incidents in the registry.