How can we help with your crypto card?

An email address and a password. That is the whole list. No name, no phone number, no document, no selfie, no address — none of it is asked for and none of it is stored.

Pick an address you can actually read: it is the only channel we have for you. It receives your 3-D Secure confirmation codes and your password reset link.

Yes. The account is an email address and a balance. We never ask for identity documents, and there is no verification tier that unlocks later — there is nothing to unlock.

Our guide to no-KYC crypto cards sets out what that does and does not protect. The trade-off is that we cannot recover an account for you. If you lose the email and the password and your recovery codes, there is no identity check we can fall back on. Keep your recovery codes.

The account is instant. The card activates on your first top-up, and the balance is credited automatically after one network confirmation — so the honest answer is "as long as the blockchain takes", usually a few minutes.

The first top-up is what activates your default card, and issuing a live card has a fixed cost on our side. Handling a deposit — the address, the network fee, the reconciliation — costs the same whatever the amount, so the same $100 minimum applies to every top-up after it.

Nothing is withheld: $100 in means $99 spendable, the difference being the 1% fee.

No. Everything runs in the browser. The card itself goes into Apple Pay or Google Pay, which you already have.

One email address, one account. If you want separate balances, use separate addresses — but remember that each one needs its own first top-up to activate a card.

If what you actually want is separate cards under one balance, create virtual cards instead: up to 5 at a time, each with its own label and its own monthly cap.

There is no residency check, because there is no identity check. The card itself works anywhere its network is accepted.

Bitcoin, Monero, Ethereum, Tether (ERC-20), Tether (TRC-20), Litecoin, TRON. Tether is available on both networks — pick the one your wallet is actually on, because they are not interchangeable.

1% on the way in, and nothing after that. No monthly fee, no inactivity fee, no fee to hold a balance, no fee to pay with the card.

On a $250 top-up: $2.50 fee, $247.50 spendable.

Minimum $100 per top-up, the first one and every one after. Maximum $100,000 per deposit.

It is credited automatically after one network confirmation. That is minutes on most chains. Nothing to click, nothing to confirm — the balance simply moves.

Yes. The deposit screen shows an exact figure — copy it with the button rather than retyping it. The amount is how your payment is matched to your deposit.

That is also why the amount is shown as text and not as a rounded number: the trailing digits matter.

An amount that does not match is not credited automatically. The funds are not lost, but they need a human to reconcile them — keep the transaction hash, it is what identifies your payment.

Some chains route every deposit to one shared address and tell them apart by a memo or tag. When the deposit screen shows one, it is not optional: a payment sent without it lands in the shared pool with nothing to attach it to.

When no tag is shown, there is nothing to add.

Do not send to it. Open a new deposit — you get a fresh address and a fresh amount. Expired addresses stop being watched, which is exactly why they expire.

No. Each deposit gets its own address, and it is valid for that deposit only. Reusing an old one means sending into an address nobody is watching.

USDT on the wrong network is the common one — ERC-20 sent to a TRC-20 address, or the reverse. Recovery depends entirely on the chains involved and is never automatic. Keep the transaction hash.

The reliable prevention: the deposit screen names the network in plain words. Read that line before you paste.

Give it a few minutes. Beyond that, a reconciliation pass runs regularly and catches deposits whose confirmation notice was lost in transit — so a payment that really landed is picked up even when the live notification failed.

In the dashboard, on the top-up itself. Over the API, GET /topups/{reference} returns the same thing: the field to watch is credited_at — when it stops being null, the money is spendable.

A virtual card exists the moment you create it and works online and in Apple / Google Pay. A physical card is the same thing in plastic, for terminals that still want something to tap or insert.

You never have to order plastic. Most people never do.

Up to 5 at a time. Delete one to free a slot — the slot comes back immediately.

Your first card is free — it is the one your first top-up activates. Every additional virtual card is $2, taken from the balance at the moment you create it.

If the balance does not cover it, nothing is created and nothing is charged.

It declines every authorisation on that card, instantly. It is reversible in one tap, and a frozen card does not free its slot — it is still one of your 5.

Freeze is the right move when a card might be compromised. Delete is the right move when you are done with it.

The card stops working for good and the slot is freed. Your transaction history keeps its entries — deleting a card does not erase what it spent.

That one is your default card. An account keeps one card at all times, so the default cannot be deleted. You can freeze it, rename it, cap it — just not remove it.

An optional ceiling per card. It is the cheapest protection there is for a subscription: give that merchant its own card, cap it just above the real price, and an unexpected renewal at ten times the amount simply declines.

A card with no cap spends up to your balance and no further.

In the dashboard, on the card. Over the API it takes a scope of its own, cards:pan, which is off by default.

The CVV is not stored anywhere — it is derived when you ask for it. A copy of our database does not contain it.

Nobody's. The cards read NO NAME REQUIRED. There is no name on the account to print.

Yes, virtual and physical alike. Once it is in the wallet you tap to pay like any other card.

Yes. Your balance earns 4% a year, calculated every day and paid every day. You do not have to move anything into a savings pot, opt in, or lock funds up — it applies to the balance you already hold, from the first day you hold it.

It is interest, not cashback. Cashback pays you a slice of what you spend; this pays you for what you keep. You earn it whether the card is used every day or sits untouched for a month.

At 00:00 UTC we take your closing balance for the day that has just ended, apply the annual rate divided by 365, and credit the result to your spendable balance. It shows up in your transactions as an Interest line, and the money is immediately available to spend.

An example on a $1,500 balance: 4% ÷ 365 = 0.010959% for the day, which is $0.16. That lands the next morning. Do nothing for a year and you would hold about $61.21 more.

4% is the nominal annual rate — the number we actually divide by 365 each day. 4.08% is the effective annual rate once daily payments are taken into account.

The difference is compounding. Each day's interest joins your balance, so the next day is calculated on a slightly larger total. Over a year those small increments add up to 4.08% rather than 4%. Both numbers describe the same thing; we publish both so nothing is hidden in the rounding.

You always earn every day. Whether a payment lands every day depends on the amount.

Interest is calculated to a fraction of a cent, but a balance can only move in whole cents. Anything below $0.01 is carried forward rather than rounded away, and paid on the first day the running total reaches a cent. Above roughly $92 held, one day of interest already exceeds a cent, so a payment arrives every morning.

On $30 held, for instance, you would see a payment about every 3 days — and over a year the total is exactly the same as if it had trickled in daily.

Nothing is locked and there is no penalty. Interest simply follows the balance.

Because the calculation uses your closing balance, a day on which you spend everything earns nothing. Top up again and interest resumes for that day's close. There is no term to break, no notice to give, and no minimum you have to keep parked.

From lending and staking the reserve that backs customer balances — not from your card spending, and not from other customers' fees.

We hold that reserve to be able to settle every card payment on demand. A portion sits in low-risk, short-duration positions that generate a yield, and we pass a fixed share of it to you as the published rate. That is why the rate is a promise about your balance rather than a share of a variable return: if those positions underperform, we absorb it, and your balance stays payable in full.

The rate is variable, and your balance is not a bank deposit. It is not covered by any deposit-guarantee or insurance scheme, here or anywhere else.

What that means in practice: we can change the rate. If we reduce it, we publish the new rate at least 14 days before it applies, on the homepage and in the Terms of Service. An increase can take effect immediately. We do not reduce a balance that has already been credited.

If you want the full picture of what backs the number, read how the 4% is generated.

Interest may be taxable where you live — that is between you and your tax authority, and we cannot advise you on it.

We do not withhold tax and we do not report interest to anyone. That is not a policy choice so much as a structural one: we hold no name, no address and no tax identifier for you, so there is nothing to report and no one to report it to. Your transaction history in the dashboard lists every payment with its date if you need a record.

Online on any site that takes the network, and in store with the physical card. There is no country list and no category blocklist on our side.

When a site asks for 3-D Secure, the six-digit code goes to your account email. Never SMS — we do not have your phone number and we do not want it.

If you automate checkouts, the API exposes the same code under the 3ds:read scope, and lets you approve or decline with 3ds:write. See the API reference.

Each challenge has a short life and expires on its own — that is what stops an old code from being replayed. Start the payment again and a fresh challenge is opened.

Almost always one of five things, in order of how often they happen:

• the balance does not cover the amount;
• the card is frozen;
• the card's monthly cap is already used up;
• the 3-D Secure challenge expired before it was answered;
• the merchant pre-authorises more than the ticket price — fuel pumps and hotels do this routinely.

Your balance is the limit, plus whatever monthly cap you set on that particular card. We do not impose a daily ceiling.

A merchant refund comes back to the balance, not to your wallet — the card is the rail, the balance is the account. It appears in your history as a refund.

Yes, and it is one of the better uses. One virtual card per subscription, capped just above the price: cancelling becomes a matter of deleting the card, and no merchant can quietly raise the amount.

USD. You top up in crypto, the balance is dollars, and the card converts at the point of sale like any other card.

$15 for the card and $20 for worldwide shipping — $35 in total. Priority shipping adds $25, bringing it to $60.

It is taken from your balance when you order.

184 countries. The order form adapts to the destination — the fields, their labels and their order follow the local postal convention rather than a US template, and countries without postal codes are not asked for one.

Yes, and it is the default. Plain envelope, no branding on the outside, no card issuer named. There is no name printed on the card itself either.

It depends entirely on the destination, so we would rather not print a number we cannot keep. Priority shipping is the lever if you are in a hurry.

Before dispatch, yes. After dispatch, no — and not for the reason you would expect: we delete the address at dispatch. See below.

Only until the card is dispatched. At that point the recipient name, street, city, region, postal code, phone and any note are erased from the order — what remains is that an order existed and was shipped.

It would be strange to build a no-KYC product and then keep a file of home addresses.

No. It is optional and always has been. A virtual card in Apple / Google Pay taps at the same terminals.

Dashboard → Settings → Two-factor authentication. Scan the QR code with any authenticator app, confirm one code, and it is on. From then on login asks for a six-digit code.

Use a recovery code. You were given 10 of them when you turned 2FA on, in the form XXXXX-XXXXX. Each one works exactly once, and any of them gets you in.

They are stored hashed, so we cannot read them back to you — which is the point.

Then the account cannot be opened again. There is no identity document to fall back on, because we never collected one. This is the real cost of no-KYC, and it is worth understanding before it happens: print the recovery codes, or put them in a password manager.

Use the reset link on the sign-in form; it arrives by email. If 2FA is on, you still need your authenticator afterwards — a reset link alone is not enough to take over an account.

Repeated failures are throttled: 8 attempts per email address and 20 per IP address within 15 minutes. It clears by itself — wait a quarter of an hour and try again.

A successful login clears the counter immediately.

The number, yes — the card would not work otherwise. The CVV, no: it is derived on demand from the number and a key, so it exists only in the response that asks for it.

Your email address, your password hash, your balance, your cards and your transaction history. That is the complete list.

No name, no phone, no document, no home address once a card has shipped, no browsing profile.

Treat it as the account itself: it can issue cards and spend the balance. Keep it server-side in an environment variable — never in a browser, a mobile app or a repository.

It is scoped: several capabilities, including reading full card numbers and reading 3-D Secure codes, are off by default and have to be granted deliberately. Rotating the key takes effect on the next request, with no grace period.

Yes, in Settings → Account. It asks for your password, because that address is the only way back into the account.

Yes — top-ups, card payments, refunds and fees, newest first, in the dashboard. The API returns the same ledger through GET /transactions.

Yes, in Settings → Notifications: top-ups, payments, security events and product news are separate switches. 3-D Secure codes are not on that list — those are part of paying, not a newsletter.

Settings → Close account. It is permanent: cards, balance and history all go, and the deposit addresses stop being watched.

Spend it first. A closed account cannot be reopened and the balance does not survive it.

No. There is no inactivity fee and no expiry. A balance sits there for as long as you leave it.

Dashboard → Developers. It stays hidden until the account has at least one active card: the key can issue cards and spend a balance, so an account that has activated nothing has no business holding one.

Everything the dashboard does: read the account and the ledger, open deposit addresses, issue and manage cards, read full card numbers, and read or resolve 3-D Secure challenges. The full reference documents every endpoint.

Per-capability switches on your key. Endpoints check them on every call, so a key without cards:write genuinely cannot create a card. The four sensitive ones — full card numbers, 3-D Secure read and write — are off until you turn them on.

120 requests per minute per key, measured over a calendar minute. Going over returns 429 and costs nothing else.

You can register endpoints today, but delivery is not live yet — nothing is dispatched to them for the moment. Until it ships, poll GET /topups/{reference} and GET /3ds?status=pending. We would rather tell you than let you wait for a call that never comes.