Bitcoin Card Tax Records

Updated 2026-10-05 · facts checked 2026-10-05 · methodology

table of contents

1. What the taxable event is
2. What your card gives you - and what it doesn't
3. What to keep
4. The funding-model trap
5. One payment, worked end to end
6. Cashback and rewards: income, then basis
7. Multiple cards, one tax file
8. If the program dies
9. Practical setup
10. What this guide is not

What the taxable event is

When your card sells BTC to fund a payment, that's a disposal. The documented rules:

• US: each payment is a disposal with capital gain or loss treatment (IRS FAQ A4 [1]); short-term vs long-term depends on holding the specific coins for more or less than one year (FAQ A6 [1]).
• Germany: §23 EStG taxes private disposals of assets held one year or less; gains on coins held longer than a year are tax-free, and calendar-year gains under the 1,000-euro Freigrenze are also tax-free [3]. Which funding model your card uses therefore changes the tax outcome.
• UK: disposals of exchange tokens - including paying for goods - are Capital Gains Tax events; the annual exempt amount applies on top (HMRC CRYPTO22100 [2]).

The general rule underneath all three: if you cannot prove cost basis, the tax authority may treat the entire proceeds as gain.

What your card gives you - and what it doesn't

Most card apps export CSV/Excel statements with: date/time, merchant, amount in spend currency, amount in card currency, and (sometimes) the crypto amount converted. What they usually don't give you is the cost basis of the coins sold - that comes from your wallet/exchange history. Conversion records are also product-specific: Xapo documents its BTC-spend spread (0.29%) in its FAQ [4], Goblin puts a 1% markup inside the rate [5] - both belong in the record as the conversion's actual terms.

What to keep

1. The card statement export - monthly, as issued. Re-downloads can disappear when programs end (see the custody guide for how programs end).
2. The exchange/wallet record of the bitcoin that funded the card: purchase dates, amounts, prices.
3. The conversion timestamps - when the BTC was sold (at load vs at spend). This determines which holding period applies (US: FAQ A6 [1]; Germany: the one-year line [3]).
4. Fee rows - load fees, FX fees and the like are often deductible costs in capital-gains calculations; keep them attached to the transaction.
5. Reward receipts. BTC cashback is measured at fair market value on the date of receipt in the US [1] and can be taxable income elsewhere (jurisdiction-dependent). Note the value at receipt - it is also the start of that coin's holding period.

The funding-model trap

Cards that sell BTC at load create a clean record: one disposal per top-up, easy to match against your wallet history. Cards that sell per transaction create many small disposals - your records need to tie each card payment to the specific coins sold, each with its own holding period. That matching is the actual work; choose your funding model partly for the paperwork you can sustain.

One payment, worked end to end

Take a single $40 restaurant payment on a card that sells BTC per transaction, funded from coins bought 14 months earlier:

1. The card converts and sells, say, 0.00042 BTC at the network rate plus a documented fee - the statement row shows the fiat amount and (on good products) the crypto amount at conversion.
2. Your wallet record shows those coins were bought at $62,000 per BTC, 14 months ago. In the US that makes it a long-term disposal (FAQ A6 [1]); in Germany the one-year line has already passed, so the disposal is tax-free [3].
3. The fee row attaches to the transaction as a cost.
4. The statement row plus the wallet row together prove basis and proceeds. Either one alone proves nothing.

Multiply by a month of card use - and by the top-ups in between, which are acquisitions for the next round of disposals - and you have the full record-keeping job. The structure never changes: every disposal needs a matching acquisition, and the dates decide everything.

Cashback and rewards: income, then basis

BTC cashback has two lives. At receipt it is measured at fair market value (in the US, FAQ A10 extends this treatment to service income; rewards follow the same date-of-receipt valuation logic [1]) and may be taxable income depending on your jurisdiction. From that day it is also a capital asset with its own basis and holding period - so when you later spend the cashback coins, the disposal rules apply on top. A record that tracks the cashback value at receipt and never again misses both halves: keep the receipt value and the eventual disposal.

Multiple cards, one tax file

Running two or three cards is common - a travel card, a domestic spend card, a Lightning-funded one - but each export uses its own format, currency conventions and fee presentation. Three habits keep the combined file workable:

1. Normalize the exports as you file them - same column order, one date format, amounts split into payment/fee/conversion columns. A year-end cleanup of five differently-formatted CSVs is where cost basis gets guessed instead of proven.
2. Record the operator's conversion terms once - Xapo's documented BTC-spend spread [5], Goblin's markup inside the rate [6]-style quotes - and reference it from each statement, instead of re-deriving it per row.
3. Keep the funding model per card visible. A per-transaction card and an at-load card produce different record structures; mixing them in one untagged file makes the matching step twice as hard.

If the program dies

Export everything before the program ends, not after. Cryptopay's retail closure is the current example: retail services ended on 1 January 2026 with balances only handled via manual withdrawal requests [7]. Dead card programs typically keep user statements available for only a limited window after shutdown - the most common reason people end up with unprovable transactions from years past.

Practical setup

• Export monthly, calendar recurring (the funding guide shows where a taxable sale happens in the card flow).
• Keep raw CSV plus a running summary (date, BTC in, BTC out, balance).
• Use your jurisdiction's standard cost-basis method (FIFO, specific ID) consistently - switching methods mid-year invites scrutiny [1].
• If you use a crypto tax tool, feed it the card statement, not just the exchange history - the card sales are the missing half of most people's records.

The tax estimator gives a rough first figure for the disposals a card generates.

What this guide is not

This is record-keeping guidance, not tax advice - rates, thresholds and exemptions change, and the rules above are snapshots from the primary sources on the date shown. For positions beyond simple spending, confirm against your jurisdiction's current guidance or a professional.

FAQ

Is paying with a bitcoin card really a taxable event?

Yes, in the three largest English- and German-speaking tax jurisdictions. The IRS FAQ treats selling virtual currency as a capital gain or loss event (Q4). HMRC's manual lists "using tokens to pay for goods or services" among disposals. Germany's §23 EStG applies too - but coins held over one year fall out of the taxable window.

What does my card export actually prove?

It proves the payment: date, merchant, fiat amount, and often the crypto amount converted. It does not prove cost basis - that comes from the wallet or exchange history of the coins that funded the card. Matching the two is the actual record-keeping work.

How does the funding model change my tax paperwork?

Cards that sell BTC at load create one disposal per top-up - easy to match. Cards that sell per transaction create one disposal per payment, each with its own holding period. Choose a funding model partly for the paperwork you can sustain.

Is bitcoin cashback taxable?

In the US, the IRS FAQ treats virtual currency received as income measured at fair market value on the date of receipt (FAQ 10 for contractors, and rewards are typically ordinary income). Note the value at receipt - the cashback is also the start of its own holding period.

What happens to my tax records if the card program dies?

Export everything before the program ends. Cryptopay's retail closure shows the pattern - services end on a date certain and statement access narrows afterwards. Programs keep user statements for only a limited window after shutdown, and an unprovable cost basis can mean the whole proceeds are treated as gain.

Which cost-basis method should I use?

Use your jurisdiction's standard method (FIFO or specific identification in the US; Germany follows acquisition-order rules in §23 EStG) and apply it consistently. Switching methods mid-year invites scrutiny. The method only works if your records tie specific coins to specific card payments.

Sources

1. IRS FAQ on virtual currency transactions - Q4 (sale = capital gain/loss), Q6 (holding period), Q10 (FMV as income on receipt) - accessed 2026-10-05
2. HMRC internal manual CRYPTO22100 - disposals include using tokens to pay for goods or services - accessed 2026-10-05
3. §23 EStG (Gesetze im Internet) - private disposals within one year; gains under 1,000 EUR/yr tax-free - accessed 2026-10-05
4. Fold terms of service - international transaction fee and Reserve terms as fee-row example - accessed 2026-10-05
5. Xapo Bank FAQ - BTC-spend spread and FX-free card spending as conversion-record example - accessed 2026-10-05
6. Goblin Cards FAQ - FX markup inside the rate as an example of unprinted conversion costs - accessed 2026-10-05
7. Cryptopay retail closure notice - card programs end; statements need exporting before they do - accessed 2026-10-05
8. IRS Publication 544 reference in FAQ - Sales and Other Dispositions of Assets - accessed 2026-10-05

Keep reading

Tools for this