Guides · Before your first load

Before you load a crypto card: what to check

Documentation checked 22 September 2026. This guide is a decision checklist, not a hands-on card test.

You have found a card, created an account and reached the deposit screen. Before transferring crypto, write down three things: what you want to buy, how much you need to spend, and what happens to money left over. An easy signup answers none of those questions on its own.

Start with the exact programme in our Cards comparison. Keep the provider, tier, card currency and source date together. Two cards carrying the same brand can have different requirements.

Record what is requested at account creation, card issuance, mobile-wallet setup and withdrawal. Email-only registration does not establish that every later step is email-only. “No document upload” also leaves open whether a name, address or phone number is required.

Read the verification clauses before funding. For example, Kardpay’s terms describe manual mobile-wallet approval using a login email while separately permitting identity, address and source-of-funds requests. Those are different stages, not a promise of permanent no-ID access. Ask yourself whether you would accept the later requirements before committing money. Kardpay terms, Articles 4 and 6.

Check eligibility before merchant coverage

Write separate answers for “Can I obtain this card where I live?” and “Can I spend with it where I am going?” A worldwide acceptance claim does not answer the first question. Check residence eligibility, physical-location requirements, supported merchants and restrictions for the specific programme.

Laso’s desktop guide, for example, warns that its US/CAD non-reloadable cards require physical presence in the supported countries and that an unusable purchased card cannot be refunded. Its International product has a separate ordering process. Do not transfer one programme’s eligibility to another. Laso desktop guide.

If phone payments matter, check the exact card and device too. Apple says the issuer may require additional authentication before approving a card for Apple Pay. A logo is useful evidence of advertised support; successful setup is a separate observation. Apple setup requirements.

Price the purchase, not just the top-up

Choose one realistic spending amount and follow it through the whole route: buying or converting crypto, transferring it, issuing the card, loading, converting currency and paying the merchant. Add any membership or transaction charge that applies. Check whether declined attempts cost money. Mark missing charges as unknown rather than zero.

Ask whether each fee is added to the amount or deducted from it. In a fictional example, a 3% deducted loading fee leaves $97 from $100 before other charges. A 3% fee added to a $100 face value requires $103. Neither figure is a provider quote.

Record the amount sent, balance credited and final purchase debit in the same comparison currency, with the conversion rate and time. Separate temporary holds from settled charges. If a cost is missing, label your result a known subtotal. Our comparison methodology explains how we separate evidence and assumptions.

Follow the money after it leaves your wallet

Identify who controls the funding wallet and who controls the loaded card balance. Your private keys do not automatically give you a way to reclaim funds transferred into a separate provider balance. Ask what you could recover if the app or support team were unavailable.

For a wallet-linked product, inspect spending permissions as well as key ownership. MetaMask distinguishes disconnecting an app from revoking its token allowance; disconnecting alone does not remove that spending permission. Check the relevant network and revocation costs. MetaMask approval guidance.

Plan the exit before the entry

Find the rules for unused card funds, merchant refunds and account-wallet withdrawals separately. Can a remainder return to crypto, or only be spent? Where does a merchant refund go? What minimum, fee, waiting period, expiry or identity check applies?

Save the relevant terms and support route. A withdrawal button for the funding wallet does not establish that money already loaded onto a card can follow the same route. If the answer is missing, keep it marked unknown and resolve it before relying on recovery.

Make the first load useful and limited

Verify the deposit asset, network, destination and minimum in the official app, plus any separate activation step. Once the checks fit your needs, consider a small usable amount for a planned near-term purchase, allowing for fees and payment holds. Keep a working backup payment method. Compare the final debit with your estimate before increasing use. If funding is delayed or payment fails, retain the transaction reference and investigate through official support before sending more.

A successful purchase establishes that one payment worked at that time. Keep the evidence, recheck changed terms and fund around upcoming spending rather than treating the card as a place for savings or emergency money.

Save this pre-load checklist

Exact card: provider, programme, tier, currency and source date.
Data: signup, issuance, mobile-wallet and later verification requirements.
Access: residence, physical location and merchant coverage checked separately.
Cost: amount sent → credited balance → final purchase debit; unknowns listed.
Control: wallet permissions, card-balance holder and recovery dependencies.
Exit: unused funds, refunds, withdrawal minimums, fees and expiry.
First use: asset/network/destination/minimum, activation, planned small purchase, fee/hold allowance and working backup.

Compare exact card programmes →

Using your phone to pay? Read our Apple Pay card guide.

Read our methodology. General information, not a personal recommendation.