<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Cards — news and analysis - FogChain</title>
	<atom:link href="https://www.fogment.com/list/cards/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.fogment.com/list/cards/</link>
	<description>Blockchain news, exchange data and press releases — independently verified.</description>
	<lastBuildDate>Wed, 28 Oct 2026 01:28:03 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.2</generator>

<image>
	<url>https://www.fogment.com/wp-content/uploads/2026/10/cropped-39cb25f161f59e8c-raccoon-6-32x32.png</url>
	<title>Cards — news and analysis - FogChain</title>
	<link>https://www.fogment.com/list/cards/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>ATM Withdrawals With a Crypto Card</title>
		<link>https://www.fogment.com/card-atm-withdrawals/</link>
					<comments>https://www.fogment.com/card-atm-withdrawals/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Wed, 28 Oct 2026 01:28:03 +0000</pubDate>
				<category><![CDATA[Cards]]></category>
		<category><![CDATA[ATM Withdrawals]]></category>
		<category><![CDATA[Card Fees]]></category>
		<category><![CDATA[Card Mechanics]]></category>
		<category><![CDATA[Cash Access]]></category>
		<category><![CDATA[Conversion Spread]]></category>
		<category><![CDATA[Crypto Cards]]></category>
		<category><![CDATA[Fee Comparison]]></category>
		<category><![CDATA[Payment Rails]]></category>
		<category><![CDATA[Personal Finance]]></category>
		<category><![CDATA[Stablecoins]]></category>
		<guid isPermaLink="false">https://www.fogment.com/?p=209796</guid>

					<description><![CDATA[<p>Using a crypto card ATM works much like any bank debit card withdrawal, with one difference: the money leaves your account as crypto and arrives as local currency. The card [&#8230;]</p>
<p>The post <a href="https://www.fogment.com/card-atm-withdrawals/">ATM Withdrawals With a Crypto Card</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Using a crypto card ATM works much like any bank debit card withdrawal, with one difference: the money leaves your account as crypto and arrives as local currency. The card issuer converts at the moment of withdrawal, and that conversion is where most of the cost hides.</p>
<p>Whether a crypto card ATM is a sensible way to get cash depends on three things: the network your card settles on, the surcharge the machine operator adds, and whether your balance sits in a stablecoin or a volatile asset. Get those right and the cost is small. Get them wrong and a single withdrawal can quietly cost several percent before you have spent anything.</p>
<ul>
<li><strong>Two fees usually stack.</strong> The machine operator adds a flat surcharge; your issuer applies a conversion spread on top of it.</li>
<li><strong>Stablecoin balances are cheaper to withdraw.</strong> A pegged asset involves far less slippage than a volatile one.</li>
<li><strong>Failed attempts are not free.</strong> Pre-authorisation holds can block balance for days even when no cash comes out.</li>
<li><strong>Cash is a fallback, not a habit.</strong> ATM withdrawals are normally the most expensive way to move value off a card.</li>
</ul>
<h2>What happens inside a crypto card ATM withdrawal</h2>
<p>A crypto card ATM withdrawal is an ordinary card transaction that happens to be funded by crypto. The machine does not know or care what backs your card; it sees a card network authorisation request and answers it the way it would for any debit card.</p>
<p>Four things happen in sequence. The machine requests authorisation for the amount you asked for plus its own surcharge. Your issuer checks that available balance covers the total. The issuer converts enough crypto into local currency at its own rate to cover the request. Settlement between the machine operator and the issuer happens later, often the next business day.</p>
<h3>Authorisation is not settlement</h3>
<p>An authorisation is a hold, not a completed payment. If the machine fails to dispense cash after authorising, the hold can persist until it expires, which in many cases takes several business days. During that window your spendable balance is lower than your real balance, and a second withdrawal may be declined for no visible reason.</p>
<h3>Why the rate on screen is not the rate you get</h3>
<p>Some machines offer to convert the amount into your home currency at the terminal. That is dynamic currency conversion, and it is commonly priced worse than letting the issuer do the conversion. Decline it, and let the card handle the exchange at its own rate.</p>
<h2>The three costs stacked into one withdrawal</h2>
<p>Every withdrawal can carry up to three separate charges, and only one of them is usually visible before you commit. Treating them as a single &#8220;fee&#8221; is how people end up surprised by the total.</p>
<h3>Operator surcharge</h3>
<p>This is the machine owner&#8217;s cut, disclosed on screen before you confirm. It is normally a flat amount rather than a percentage, which makes small withdrawals disproportionately expensive. A fixed charge of a few units on a small withdrawal can be a large share of the cash you actually receive.</p>
<h3>Issuer conversion spread</h3>
<p>Your card provider converts crypto to fiat at a rate it sets, typically including a margin over the market mid-price. That margin is rarely shown as a line item. It appears as a slightly worse exchange rate than the one your wallet displayed a minute earlier.</p>
<h3>Out-of-network and cross-border charges</h3>
<p>Machines outside the card&#8217;s home network, and withdrawals in a currency other than the card&#8217;s billing currency, can attract further charges set by the issuer. These depend on the venue and on the programme terms, and they change more often than most users expect. Read the fee schedule before you travel, not after.</p>
<blockquote><p>If a withdrawal needs a spreadsheet to justify, it is usually the wrong withdrawal. The machine fee is visible, but the conversion spread is the number that decides whether the transaction was reasonable.</p></blockquote>
<div class="fog-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-200/70 bg-surface" data-fog-table><table>
<thead>
<tr>
<th>Channel</th>
<th>Cost structure</th>
<th>Speed</th>
<th>Suited to</th>
</tr>
</thead>
<tbody>
<tr>
<td>ATM in home currency</td>
<td>Flat operator surcharge plus issuer spread</td>
<td>Immediate</td>
<td>Small, occasional cash needs</td>
</tr>
<tr>
<td>ATM abroad</td>
<td>Operator surcharge, issuer spread, possible cross-border fee</td>
<td>Immediate</td>
<td>Emergencies while travelling</td>
</tr>
<tr>
<td>Over-the-counter cash</td>
<td>Provider spread, often wider than card conversion</td>
<td>Same day</td>
<td>Larger sums with documentation</td>
</tr>
<tr>
<td>Bank transfer out</td>
<td>Fixed network fee, no percentage spread</td>
<td>Hours to days</td>
<td>Rent, bills, large amounts</td>
</tr>
<tr>
<td>Direct card spending</td>
<td>Issuer spread only, no machine surcharge</td>
<td>Immediate</td>
<td>Everyday purchases</td>
</tr>
</tbody>
</table></div>
<h2>How crypto card ATM costs compare with alternatives</h2>
<p>Cash from a card is convenient and rarely the cheapest route. The table above is about structure rather than exact numbers, because every programme prices these layers differently.</p>
<p>A bank transfer carries a fixed cost that does not scale with the amount, so it wins on anything large. Direct card spending avoids the machine surcharge entirely because there is no machine involved. Cash sits in the middle: better than a rushed over-the-counter conversion, worse than planning one day ahead.</p>
<h2>A worked example with round numbers</h2>
<p>Suppose you withdraw 200 units and the machine charges a flat 3 units. Your balance is debited 203 units before any conversion. The issuer then applies a 1.5 percent spread to the converted amount, which comes to about 3.05 units. Total cost is roughly 6.05 units, or just over 3 percent of the cash in your hand.</p>
<p>Now withdraw 50 units four times from the same machine instead. Four surcharges cost 12 units, and the spread applies four times to a smaller base, so the effective cost rises above 7 percent. The fixed charge, not the exchange rate, is what punishes small withdrawals. That is why the same card can feel cheap one week and expensive the next.</p>
<h2>Before you tap: a short checklist</h2>
<ol>
<li>Read the surcharge on screen and compare it with the amount you actually need today.</li>
<li>Decline dynamic currency conversion if the terminal offers it.</li>
<li>Confirm your card&#8217;s billing currency and whether the machine accepts your card&#8217;s network.</li>
<li>Withdraw the full amount once rather than several small amounts.</li>
<li>Keep the receipt and note the rate so you can compare it with the market rate later.</li>
<li>Check the settled amount on your statement the next day, which is the only figure that includes every layer.</li>
</ol>
<p>The post <a href="https://www.fogment.com/card-atm-withdrawals/">ATM Withdrawals With a Crypto Card</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.fogment.com/card-atm-withdrawals/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Reading a Card&#8217;s Reward Terms</title>
		<link>https://www.fogment.com/card-reward-terms/</link>
					<comments>https://www.fogment.com/card-reward-terms/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Wed, 28 Oct 2026 01:28:03 +0000</pubDate>
				<category><![CDATA[Cards]]></category>
		<category><![CDATA[Card Agreements]]></category>
		<category><![CDATA[Card Reward Terms]]></category>
		<category><![CDATA[Cashback Caps]]></category>
		<category><![CDATA[Clawback Clauses]]></category>
		<category><![CDATA[Crypto Cashback]]></category>
		<category><![CDATA[Effective Reward Rate]]></category>
		<category><![CDATA[Merchant Category Codes]]></category>
		<category><![CDATA[Payout Currency]]></category>
		<category><![CDATA[Reward Exclusions]]></category>
		<category><![CDATA[Spending Audits]]></category>
		<guid isPermaLink="false">https://www.fogment.com/?p=209791</guid>

					<description><![CDATA[<p>Card reward terms are the part of a crypto card agreement that decides whether the cashback advertised at signup survives contact with a real transaction. The headline rate is a [&#8230;]</p>
<p>The post <a href="https://www.fogment.com/card-reward-terms/">Reading a Card&#8217;s Reward Terms</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Card reward terms are the part of a crypto card agreement that decides whether the cashback advertised at signup survives contact with a real transaction. The headline rate is a marketing number. The definitions, exclusions and settlement clauses are the contract.</p>
<p>Most people compare cards on that headline rate and stop there. That is a mistake, because card reward terms also govern what counts as a qualifying purchase, which asset the reward is paid in, when it lands, and whether the issuer can take it back. Two cards quoting the same percentage can pay amounts that differ by a third once those rules are applied to the same spending.</p>
<ul>
<li><strong>The headline rate is not the effective rate.</strong> Exclusions, caps and payout currency decide what actually arrives.</li>
<li><strong>Definitions beat percentages.</strong> &#8220;Purchase&#8221; is a defined term, and the definition is where most disputes begin.</li>
<li><strong>Timing is a cost.</strong> A reward paid weeks later in a volatile asset is not worth the number quoted at checkout.</li>
<li><strong>Rewards can be reversed.</strong> Refunds, chargebacks and account closures routinely claw back cashback already paid.</li>
</ul>
<h2>What card reward terms actually define</h2>
<p>They define four things: what qualifies, how much is paid, in what asset, and under what conditions the issuer can reclaim it. Everything else in the document is commentary on those four points. Read the agreement looking for them rather than reading top to bottom.</p>
<h3>The qualifying purchase definition</h3>
<p>A qualifying purchase is a transaction that satisfies every condition in the definition at the same time. Typical conditions include a minimum ticket size, a settled rather than merely authorised status, a merchant category that is not excluded, and a transaction that is not later refunded. A purchase that fails any single condition earns nothing, even when the other three are met.</p>
<p>The sequence matters more than people assume. An authorisation is a hold; a settlement is a transfer. Terms written around settlement mean a reward can appear to accrue at the point of sale and then fail to post, because the transaction settled at a different amount or through a different merchant record.</p>
<h3>Reward currency and payout timing</h3>
<p>The payout asset matters more than most readers expect. A reward paid into a fiat balance is worth its face value on the day it lands. A reward paid in a token is worth whatever that token is worth when the payout executes, which may be weeks after the purchase that generated it. Terms usually state the payout asset, the accrual period and a minimum threshold before withdrawal, and those three together determine what the percentage is really worth.</p>
<h2>Where card reward terms quietly reduce the payout</h2>
<p>Reductions come from three places: category exclusions, per-period caps and clawback clauses. None of them appear in the headline rate, and all of them apply automatically.</p>
<h3>Merchant category exclusions</h3>
<p>Exclusions are usually written by merchant category code rather than by merchant name. That means a purchase at a shop you think of as groceries can code as general merchandise and fall outside the reward, and a wallet top-up can code as a financial service, which is excluded on most cards. Categories that tend to be excluded are cash-like transactions, gambling, financial services, tax payments and person-to-person transfers.</p>
<p>Category coding is assigned by the acquiring side, not by you. If a purchase does not earn, the reason is usually the code rather than the merchant. Terms often state that the issuer&#8217;s categorisation is final, which means there is no appeal beyond the record they hold.</p>
<h3>Clawback and reversal windows</h3>
<p>Clawback clauses let the issuer reverse a reward after it has been paid. Common triggers are a refund, a chargeback, a returned transaction, or a balance that later falls below a required threshold. The window can extend well past the statement date, so a reward you have already spent may still be removed and offset against future earnings or a balance.</p>
<blockquote><p>A reward rate is a quote, and a quote is only worth the conditions attached to it. Treat the percentage as a claim to be tested, not as income to be budgeted.</p></blockquote>
<h2>Comparing reward structures</h2>
<p>The table sets out how four common structures behave once the terms are applied. The rates are described in relative terms because they vary by issuer, by programme and by jurisdiction.</p>
<div class="fog-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-200/70 bg-surface" data-fog-table><table>
<thead>
<tr>
<th>Structure</th>
<th>How the rate is applied</th>
<th>Main reduction risk</th>
<th>Payout asset</th>
</tr>
</thead>
<tbody>
<tr>
<td>Flat percentage</td>
<td>One rate on all qualifying spend</td>
<td>Broad exclusion list removes whole categories</td>
<td>Usually fiat balance</td>
</tr>
<tr>
<td>Category multiplier</td>
<td>Higher rate on named categories</td>
<td>Coding errors move spend out of the boosted category</td>
<td>Fiat or token</td>
</tr>
<tr>
<td>Tiered by spend</td>
<td>Rate rises with monthly volume</td>
<td>Cap resets monthly, so a single large month earns little</td>
<td>Fiat or token</td>
</tr>
<tr>
<td>Token cashback</td>
<td>Fixed token amount per unit spent</td>
<td>Value moves between accrual and payout</td>
<td>Token</td>
</tr>
<tr>
<td>Merchant-funded promo</td>
<td>Bonus at specific merchants</td>
<td>Ends without notice and often excludes returns</td>
<td>Statement credit</td>
</tr>
</tbody>
</table></div>
<h2>How to audit card reward terms before you commit</h2>
<p>An audit takes about twenty minutes and answers the only question that matters: what will this card actually pay on spending you already do?</p>
<ol>
<li>Export the last three months of card spending and group it by merchant category, not by merchant name.</li>
<li>Match those categories against the exclusion list and delete any spend that cannot earn.</li>
<li>Find the cap per statement period and calculate how much of your normal spend falls above it.</li>
<li>Identify the payout asset and schedule, then note how long the value sits exposed before it reaches you.</li>
<li>Read the clawback clause and record the reversal window in weeks, not in vague terms.</li>
<li>Apply the rate only to the eligible spend under the cap, and divide by total spend to get the effective rate.</li>
<li>Compare that effective rate across two or three cards using the same method and the same spending data.</li>
</ol>
<p>The post <a href="https://www.fogment.com/card-reward-terms/">Reading a Card&#8217;s Reward Terms</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.fogment.com/card-reward-terms/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Issuer or Network: Who Sets Your Card Limit</title>
		<link>https://www.fogment.com/card-issuer-vs-network/</link>
					<comments>https://www.fogment.com/card-issuer-vs-network/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Wed, 28 Oct 2026 01:27:59 +0000</pubDate>
				<category><![CDATA[Cards]]></category>
		<category><![CDATA[Card Acceptance]]></category>
		<category><![CDATA[Card Authorization]]></category>
		<category><![CDATA[Card Issuer Vs Network]]></category>
		<category><![CDATA[Consumer Payments]]></category>
		<category><![CDATA[Credit Limits]]></category>
		<category><![CDATA[Dispute Process]]></category>
		<category><![CDATA[Interchange Basics]]></category>
		<category><![CDATA[Payment Decline Codes]]></category>
		<category><![CDATA[Payment Rails]]></category>
		<category><![CDATA[Spending Caps]]></category>
		<guid isPermaLink="false">https://www.fogment.com/?p=209818</guid>

					<description><![CDATA[<p>A declined card is rarely one decision. At least two separate parties hold an opinion on every transaction: the institution that owns your account, and the network that carries the [&#8230;]</p>
<p>The post <a href="https://www.fogment.com/card-issuer-vs-network/">Issuer or Network: Who Sets Your Card Limit</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A declined card is rarely one decision. At least two separate parties hold an opinion on every transaction: the institution that owns your account, and the network that carries the authorization message between banks. The <strong>card issuer vs network</strong> split explains why the same card works at one merchant and fails at the next, and why the ceiling shown in your banking app is not always the ceiling that applies at the terminal.</p>
<p>Most confusion about limits comes from treating the <strong>card issuer vs network</strong> relationship as a single authority. It is not. One party sets your spending ceiling and your available balance. The other sets the rails, the message format, and the acceptance rules a merchant must follow to take the card at all. Neither can fully overrule the other, and either one can say no.</p>
<ul>
<li><strong>The issuer controls money.</strong> Credit lines, available balance, daily caps and risk rules live with the account, not the network.</li>
<li><strong>The network controls plumbing.</strong> Message standards, terminal certification, dispute reason codes and acceptance rules live with the scheme.</li>
<li><strong>A decline can come from either side.</strong> &#8220;Insufficient funds&#8221; and &#8220;amount exceeds limit&#8221; are different failures with different fixes.</li>
<li><strong>Limits stack.</strong> The effective ceiling is the lowest of several constraints, so raising one rarely helps if another is binding.</li>
</ul>
<h2>Who actually decides what</h2>
<p>The issuer decides money; the network decides plumbing. That single sentence resolves most disputes about who &#8220;set&#8221; a limit, but the details matter when a payment fails at an awkward moment.</p>
<p>Your issuer is the bank, credit union, or programme manager that opened the account and put its name on the plastic or the virtual number. It underwrites the risk, holds the ledger, and decides what you may spend. The network is the interchange layer between acquirers and issuers: it publishes the specification for authorization messages, certifies terminals and processors, defines the reason codes attached to declines, and enforces the rules merchants accept when they agree to take cards. It does not hold your money and does not extend you credit.</p>
<h3>What the issuer controls</h3>
<p>Everything that touches your balance. That includes the credit line or deposit balance, the available amount after pending authorizations, per-transaction and daily spending caps, cash-access sub-limits, merchant category blocks, geographic restrictions, and the fraud models that score each transaction in real time. A fraud rule can decline a purchase that fits inside every published limit, because the decision is about pattern rather than arithmetic.</p>
<h3>What the network controls</h3>
<p>The rules of the road rather than the balance. The network sets the message fields an authorization must carry, certifies that a terminal or payment gateway can speak the protocol correctly, and defines the codes used to explain a decline. It also runs the dispute and chargeback process that determines who absorbs a loss after the fact. When a merchant&#8217;s terminal rejects a card type entirely, that is an acceptance problem at the network or acquirer layer, not a statement about your account.</p>
<h2>Where the card issuer vs network boundary shows up</h2>
<p>The boundary becomes visible in three ordinary situations, and each looks identical to a customer staring at a failed payment.</p>
<h3>A decline with headroom available</h3>
<p>You have available credit, the merchant is legitimate, and the payment still fails. Common causes sit on the issuer side: a per-transaction cap, a category block, a velocity rule, or a fraud score triggered by an unusual country or amount. Occasionally the cause sits on the network side, when the terminal sends a malformed or incomplete authorization and the message is rejected before an issuer ever sees it.</p>
<h3>A decline that is really an acceptance problem</h3>
<p>Some merchants, especially online merchants using older gateways, do not support every card product or every regional scheme. The card is fine, the account is fine, and the transaction cannot be routed. Retrying produces the same result and a different card produces a different result. That asymmetry is the tell.</p>
<div class="fog-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-200/70 bg-surface" data-fog-table><table>
<thead>
<tr>
<th>Question</th>
<th>Issuer decides</th>
<th>Network decides</th>
</tr>
</thead>
<tbody>
<tr>
<td>How much can I spend today?</td>
<td>Yes — line, balance, daily cap</td>
<td>No</td>
</tr>
<tr>
<td>Is this merchant category allowed?</td>
<td>Usually, via issuer controls</td>
<td>Only through acceptance rules</td>
</tr>
<tr>
<td>Will this terminal accept the card at all?</td>
<td>No</td>
<td>Yes, via certification and scheme rules</td>
</tr>
<tr>
<td>Who owns the dispute process?</td>
<td>Files and funds it</td>
<td>Defines the codes and timelines</td>
</tr>
<tr>
<td>What does the decline code mean?</td>
<td>Sends it</td>
<td>Defines it</td>
</tr>
<tr>
<td>Does a foreign currency fee apply?</td>
<td>Typically set by the issuer</td>
<td>Supplies the conversion rate</td>
</tr>
</tbody>
</table></div>
<blockquote><p>A decline is a message, not a verdict. The code tells you which layer refused, and the layer tells you which fix is worth trying.</p></blockquote>
<h2>Limits stack: a worked example</h2>
<p>Effective spending power is the minimum of several constraints, so a single number in an app can mislead. Consider a hypothetical account with a 4,000 unit credit line, 900 units of pending authorizations, an issuer per-transaction cap of 1,500 units, and a 500 unit cash-access sub-limit of which 200 has been used.</p>
<p>Available credit is 4,000 − 900 = 3,100. A 1,650 unit purchase in a foreign currency arrives. It clears the available-credit test comfortably, with 1,450 units of headroom left, but it exceeds the 1,500 unit per-transaction cap, so the issuer declines and returns an amount-limit code. The fix is to split the purchase or raise that specific cap, not to pay down the balance.</p>
<p>Now change one variable. Suppose the same purchase is 1,400 units, inside the cap, but the merchant settles in another currency and the converted total lands at 1,442 after a conversion margin. Available credit is still sufficient, so the transaction settles, and the app shows a balance that moved by slightly more than the sticker price. That difference belongs to the issuer&#8217;s pricing, while the rate itself comes from the network. None of it is a limit problem, which is why reading the decline code before acting saves a phone call.</p>
<h2>How to isolate which party blocked you</h2>
<ol>
<li>Save the exact decline text and any code the app or terminal displays, plus a timestamp.</li>
<li>Check available balance and pending authorizations, not just the headline limit.</li>
<li>Compare the amount against per-transaction and daily caps, including currency conversion.</li>
<li>Test the same card at a different merchant, and a different card at the same merchant, to separate acceptance from account problems.</li>
<li>Check whether the merchant category or country sits under a block you or the issuer enabled.</li>
<li>If the pattern is unclear, ask the issuer for the decline reason rather than the balance; the reason names the layer.</li>
<li>Record the outcome, because repeated identical failures across merchants usually point at a rule you can change.</li>
</ol>
<p>The post <a href="https://www.fogment.com/card-issuer-vs-network/">Issuer or Network: Who Sets Your Card Limit</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.fogment.com/card-issuer-vs-network/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Card Fees Compared: Issuer, Network and FX</title>
		<link>https://www.fogment.com/card-fee-layers/</link>
					<comments>https://www.fogment.com/card-fee-layers/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Wed, 28 Oct 2026 01:21:52 +0000</pubDate>
				<category><![CDATA[Cards]]></category>
		<category><![CDATA[Card Fees]]></category>
		<category><![CDATA[Card Programs]]></category>
		<category><![CDATA[Consumer Finance]]></category>
		<category><![CDATA[Cost Analysis]]></category>
		<category><![CDATA[Crypto Cards]]></category>
		<category><![CDATA[Fee Structures]]></category>
		<category><![CDATA[FX Spread]]></category>
		<category><![CDATA[Interchange]]></category>
		<category><![CDATA[Payment Networks]]></category>
		<category><![CDATA[Rewards Economics]]></category>
		<guid isPermaLink="false">https://www.fogment.com/card-fee-layers/</guid>

					<description><![CDATA[<p>Crypto card fees are not one number. They are three: what the card programme charges you, what the card network charges the merchant, and what the currency conversion costs when [&#8230;]</p>
<p>The post <a href="https://www.fogment.com/card-fee-layers/">Card Fees Compared: Issuer, Network and FX</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Crypto card fees are not one number. They are three: what the card programme charges you, what the card network charges the merchant, and what the currency conversion costs when crypto becomes fiat. Most complaints about crypto card fees trace back to comparing one layer against another layer and concluding the card is cheap or expensive.</p>
<p>The distinction matters because only one of those three layers normally appears as a line on your statement. The other two show up as a slightly worse exchange rate and a slightly higher price at the till. Understanding which layer you are paying is the difference between a card that costs under one percent and one that costs five.</p>
<ul>
<li><strong>Fees stack, they do not replace each other.</strong> A zero-fee card can still be expensive through its conversion spread.</li>
<li><strong>Percentage fees punish large balances, fixed fees punish small ones.</strong> Match the fee shape to how you actually use the card.</li>
<li><strong>Interchange is usually invisible.</strong> It is paid by the merchant, not billed to you, but it shapes what perks a programme can afford.</li>
<li><strong>Read the spread, not the headline.</strong> The conversion margin is the number that decides the real annual cost.</li>
</ul>
<h2>Why crypto card fees come in layers</h2>
<p>Each layer exists because a different party is doing a different job. The programme issues the card and manages your balance. The network moves the authorisation between merchant and issuer. The market prices the conversion from crypto to fiat. None of them work for free, and each hides its charge in a different place.</p>
<h3>Charged by the programme</h3>
<p>Issuers bill for the account itself: issuance, an annual or monthly fee in some cases, top-up fees, and sometimes a fee per transaction. These are the easiest to see, which is why marketing focuses on them. They are also frequently zero, which makes the card look free.</p>
<h3>Charged by the network</h3>
<p>Card networks set interchange, a small percentage of each transaction paid by the merchant&#8217;s bank to the issuing bank. You never see this line, but it funds cashback and rewards. A programme offering generous rewards is usually capturing interchange and sharing part of it back.</p>
<h3>Charged by the currency market</h3>
<p>The conversion from crypto to fiat happens at a rate the issuer sets, typically with a margin over the mid-market rate. This is the largest and least visible layer for most users. It applies to every purchase and every ATM withdrawal, not just to the obvious conversion events.</p>
<blockquote><p>A card advertised as fee-free is usually a card whose fees have been moved into the exchange rate. The question is never whether you pay, but whether the amount you pay is disclosed.</p></blockquote>
<h2>Issuer fees: what the programme actually bills you</h2>
<p>Issuer fees are the ones that appear on a statement, and they come in two shapes: recurring and per-event. Comparing cards on recurring fees alone is the most common evaluation mistake.</p>
<h3>Recurring charges</h3>
<p>Annual or monthly account fees, card replacement fees and inactivity fees fall here. They are predictable and easy to budget, and in many jurisdictions they are modest or waived. A recurring fee is only poor value if your usage is too low to amortise it.</p>
<h3>Per-event charges</h3>
<p>Top-up fees, withdrawal fees, foreign transaction fees and declined-payment fees fall here. These scale with behaviour rather than time. A card with no annual fee but a top-up charge can cost more than a card with an annual fee if you fund it often in small amounts.</p>
<h2>Network costs: why interchange rarely reaches you</h2>
<p>Interchange is paid by the merchant, which is why it does not appear on your statement. It still affects you indirectly: it determines how much cashback a programme can fund, and it is one reason some merchants price card acceptance into their listed prices.</p>
<p>For most cardholders the practical implication is simple. Rewards funded by interchange are not free money; they are a partial refund of a cost embedded in prices. A programme offering unusually high cashback is either subsidising growth or capturing more of the spread elsewhere. Both are worth checking before you treat the reward rate as the main selection criterion.</p>
<h2>How the layers compare across fee models</h2>
<p>The table compares structures rather than amounts, since pricing differs by programme, region and card tier.</p>
<div class="fog-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-200/70 bg-surface" data-fog-table><table>
<thead>
<tr>
<th>Fee layer</th>
<th>Who sets it</th>
<th>Visible on statement</th>
<th>Scales with</th>
</tr>
</thead>
<tbody>
<tr>
<td>Issuance and annual fee</td>
<td>Card programme</td>
<td>Yes, itemised</td>
<td>Time</td>
</tr>
<tr>
<td>Top-up fee</td>
<td>Card programme</td>
<td>Yes, itemised</td>
<td>Number of funding events</td>
</tr>
<tr>
<td>Conversion spread</td>
<td>Card programme</td>
<td>Rarely, embedded in rate</td>
<td>Amount converted</td>
</tr>
<tr>
<td>Interchange</td>
<td>Card network</td>
<td>No, paid by merchant</td>
<td>Transaction value</td>
</tr>
<tr>
<td>ATM operator surcharge</td>
<td>Machine operator</td>
<td>Yes, on the machine</td>
<td>Number of withdrawals</td>
</tr>
</tbody>
</table></div>
<h2>A worked comparison over one month</h2>
<p>Take two hypothetical cards and 1,000 units of monthly spending, all in a currency other than the card&#8217;s billing currency.</p>
<p>Card A charges no annual fee, no top-up fee and a 2.5 percent conversion spread. Its monthly cost is 25 units, entirely invisible on the statement.</p>
<p>Card B charges 60 units a year, a 1 percent top-up fee on two funding events of 500 units each, and a 0.5 percent conversion spread. Annual fees work out to 5 units a month, top-ups to 10 units, and spread to 5 units: 20 units a month, or 240 units a year against Card A&#8217;s 300.</p>
<p>Now change the behaviour rather than the card. If you fund Card B ten times with 100 units instead of twice with 500, the top-up fee stays at 1 percent of the same total, so the cost holds at 10 units, while Card A remains at 25. The gap widens. Reverse the amounts, spending 200 units a month instead of 1,000, and Card B&#8217;s fixed annual fee dominates: 5 units plus 2 plus 1 equals 8, against Card A&#8217;s 5. The cheaper card depends entirely on your volume, which is why the comparison has to use your own numbers.</p>
<p>The same arithmetic, run in order, takes about twenty minutes and produces a number you can compare across cards:</p>
<ol>
<li>Find the conversion spread and write it down as a percentage.</li>
<li>List every per-event fee: top-up, withdrawal, foreign transaction, declined payment.</li>
<li>Estimate your monthly spend and your typical funding frequency.</li>
<li>Multiply the spread by monthly spend, then add per-event fees at your real frequency.</li>
<li>Add one twelfth of any annual fee.</li>
<li>Compare the totals, not the headline rates.</li>
</ol>
<p>The post <a href="https://www.fogment.com/card-fee-layers/">Card Fees Compared: Issuer, Network and FX</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.fogment.com/card-fee-layers/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Card Custody: Who Holds the Crypto Behind It</title>
		<link>https://www.fogment.com/card-custody/</link>
					<comments>https://www.fogment.com/card-custody/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Wed, 28 Oct 2026 01:21:47 +0000</pubDate>
				<category><![CDATA[Cards]]></category>
		<category><![CDATA[Account Freezes]]></category>
		<category><![CDATA[Asset Segregation]]></category>
		<category><![CDATA[Counterparty Risk]]></category>
		<category><![CDATA[Crypto Card Custody]]></category>
		<category><![CDATA[Custodial Wallets]]></category>
		<category><![CDATA[Custody Terms]]></category>
		<category><![CDATA[Key Management]]></category>
		<category><![CDATA[Self Custody Cards]]></category>
		<category><![CDATA[Settlement Partners]]></category>
		<category><![CDATA[Token Allowances]]></category>
		<guid isPermaLink="false">https://www.fogment.com/card-custody/</guid>

					<description><![CDATA[<p>Crypto card custody is the question of who controls the coins that back your card at the moment you tap it. Every card has an answer, and the answer determines [&#8230;]</p>
<p>The post <a href="https://www.fogment.com/card-custody/">Card Custody: Who Holds the Crypto Behind It</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Crypto card custody is the question of who controls the coins that back your card at the moment you tap it. Every card has an answer, and the answer determines what happens if the company behind the card stops operating, freezes accounts or loses access to its wallets.</p>
<p>The marketing framing hides this. A card is described by its cashback and its accepted networks, while crypto card custody sits in the terms and the architecture. This article separates the models, shows where each one puts your balance, and lists the specific clauses that tell you which model you are actually using.</p>
<ul>
<li><strong>Custody decides your legal position.</strong> A balance held by an issuer is a claim on that company, not coins in your name.</li>
<li><strong>Self-custody cards still touch a custodian.</strong> The fiat leg of the settlement almost always runs through a regulated partner.</li>
<li><strong>The freeze risk is real in both models.</strong> Custodians can freeze accounts; contracts can be paused by their administrators.</li>
<li><strong>Read the wallet flow, not the brochure.</strong> Where the coins sit between transactions is the whole answer.</li>
</ul>
<h2>What crypto card custody actually means</h2>
<p>It means identifying which entity holds the private keys to the funds that fund your spending, and on what terms. There are two broad models, and a number of hybrids that combine them in ways that are easy to misread.</p>
<h3>The custodial model</h3>
<p>In a custodial card, you deposit coins to an account controlled by the issuer or its banking partner. The balance you see is a liability of that entity, recorded in their ledger. When you spend, they debit your ledger entry and settle with the merchant through a normal card rail. The coins themselves may be held in cold storage, lent out, or converted immediately, depending on the programme.</p>
<p>The consequence is straightforward: you are an unsecured creditor of the operator for the duration of the deposit. In many jurisdictions, customer crypto held by a custodian is not covered by deposit insurance, and recovery in an insolvency depends on how the assets were segregated and recorded. Segregation is the thing to look for, and it is described in the custody terms rather than in the card terms.</p>
<h3>The self-custody model</h3>
<p>In a self-custody card, the coins stay in a wallet you control until the moment of a transaction. A smart contract is granted a limited permission to move a capped amount when an authorisation arrives. Between transactions, the balance is yours in the literal sense: the keys are in your wallet, and the issuer cannot move funds beyond the allowance you granted.</p>
<p>That does not make the card custody-free. The merchant still has to be paid in fiat, so a settlement partner funds the transaction and is reimbursed from your wallet. The permission you granted is also a standing risk: an allowance that is too broad, or a contract that is later upgraded, is a different exposure from a deposit account. Revoking unused allowances is part of the hygiene.</p>
<h2>Where crypto card custody changes your risk</h2>
<p>The model changes three things: what you own if the operator fails, what happens during a freeze, and who is exposed in the hours between authorisation and settlement.</p>
<h3>Counterparty and insolvency exposure</h3>
<p>A custodial balance is a claim. If the operator becomes insolvent, your position depends on segregation, on the jurisdiction of the entity that holds the assets, and on the priority your claim receives. Those three factors are usually disclosed in documents that are not the card agreement, which is why the card page rarely answers the question.</p>
<h3>The authorisation gap</h3>
<p>Card transactions are authorised before they settle. The authorisation holds an amount, the settlement arrives a day or more later at a final amount, and the difference has to be absorbed somewhere. In a custodial card the operator absorbs it and reconciles against your balance. In a self-custody card the contract usually locks the authorised amount and releases the remainder afterwards.</p>
<p>That gap is where most operational complaints originate. A declined authorisation, a double hold, or a settlement that exceeds the hold are all reconciliation events, not custody failures, but they look identical from a balance screen.</p>
<blockquote><p>Custody is not a feature you can infer from a logo on the card. It is a set of permissions and a legal relationship, and both are written down somewhere you have to ask for.</p></blockquote>
<h2>Comparing the two custody models</h2>
<p>The comparison below describes the general shape of each model. Specific terms vary by issuer and by jurisdiction, and hybrids exist that mix the two.</p>
<div class="fog-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-200/70 bg-surface" data-fog-table><table>
<thead>
<tr>
<th>Question</th>
<th>Custodial card</th>
<th>Self-custody card</th>
</tr>
</thead>
<tbody>
<tr>
<td>Who holds the keys</td>
<td>The issuer or its custody partner</td>
<td>You, in your own wallet</td>
</tr>
<tr>
<td>What your balance is</td>
<td>A ledger claim on the operator</td>
<td>Tokens in an address you control</td>
</tr>
<tr>
<td>What happens on operator failure</td>
<td>Claim in an insolvency process</td>
<td>Funds remain in your wallet</td>
</tr>
<tr>
<td>Who can freeze spending</td>
<td>Operator, and its banking partner</td>
<td>Operator can decline; contract admin can pause</td>
</tr>
<tr>
<td>Ongoing user duties</td>
<td>Monitor the operator&#8217;s disclosures</td>
<td>Manage allowances and key security</td>
</tr>
<tr>
<td>Typical failure mode</td>
<td>Withdrawal freeze during stress</td>
<td>Contract bug or excessive allowance</td>
</tr>
</tbody>
</table></div>
<h2>How to establish crypto card custody before you load a balance</h2>
<p>Ask in this order. Each step narrows the answer, and a provider that cannot answer step two is telling you something.</p>
<ol>
<li>Find the legal entity named in the card terms and check which jurisdiction it is registered in.</li>
<li>Ask whether customer assets are held in segregated accounts and whether that segregation is described in an audited document.</li>
<li>Identify who holds the keys: the issuer, a named custody partner, or your own wallet.</li>
<li>If self-custody, read the allowance mechanism and confirm you can revoke it without closing the card.</li>
<li>Read the freeze and closure clauses to see what triggers a suspension of spending or withdrawal.</li>
<li>Check what happens to a remaining balance on closure, and how long the payout takes.</li>
<li>Test with a small balance first, including one withdrawal, before moving meaningful funds.</li>
</ol>
<p>The post <a href="https://www.fogment.com/card-custody/">Card Custody: Who Holds the Crypto Behind It</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.fogment.com/card-custody/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Reward Caps: The Ceiling Nobody Reads</title>
		<link>https://www.fogment.com/card-reward-caps/</link>
					<comments>https://www.fogment.com/card-reward-caps/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 23:26:58 +0000</pubDate>
				<category><![CDATA[Cards]]></category>
		<category><![CDATA[Bonus Categories]]></category>
		<category><![CDATA[Card Reward Cap]]></category>
		<category><![CDATA[Card Terms]]></category>
		<category><![CDATA[Cash Back]]></category>
		<category><![CDATA[Effective Rate]]></category>
		<category><![CDATA[Merchant Codes]]></category>
		<category><![CDATA[Personal Finance]]></category>
		<category><![CDATA[Points]]></category>
		<category><![CDATA[Rewards Cards]]></category>
		<category><![CDATA[Spending Strategy]]></category>
		<guid isPermaLink="false">https://www.fogment.com/card-reward-caps/</guid>

					<description><![CDATA[<p>A card reward cap is a limit on how much of a bonus rate you can actually collect. The advertised rate applies to a defined bucket of spending, and once [&#8230;]</p>
<p>The post <a href="https://www.fogment.com/card-reward-caps/">Reward Caps: The Ceiling Nobody Reads</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A card reward cap is a limit on how much of a bonus rate you can actually collect. The advertised rate applies to a defined bucket of spending, and once that bucket is full the same purchase earns the base rate instead of the headline one.</p>
<p>The number is usually printed once, in small type, far from the rate itself. That is why a card reward cap costs the average cardholder more than the annual fee: the fee is fixed and visible, while a cap quietly turns a 5% category into a 1% one partway through the period.</p>
<ul>
<li><strong>Caps are per period, not per year.</strong> Monthly, quarterly, and annual limits reset on different dates, and the reset date is what determines whether a large purchase counts.</li>
<li><strong>The cap applies to eligible spend, not to your total spend.</strong> Only purchases that qualify for the bonus category consume it.</li>
<li><strong>Effective rate, not headline rate, is the comparison.</strong> Two cards advertising the same percentage can differ by more than a percentage point after caps.</li>
<li><strong>Caps are usually invisible until you hit one.</strong> Statements often show points earned rather than remaining allowance.</li>
</ul>
<h2>What a card reward cap looks like</h2>
<p>A card reward cap is a ceiling expressed in one of three units: dollars of eligible spending, points earned, or cash back paid. Read which unit applies, because a cap written as &#8220;up to 3,000 points per quarter&#8221; behaves differently from &#8220;5% on the first $1,000 per quarter&#8221; once you spend more than expected.</p>
<h3>Per-statement and per-quarter caps</h3>
<p>The most common structure is a bonus rate on a fixed amount of category spending per statement period or per quarter. Spending above that amount still earns, but at the base rate. Because the period is short, a single large purchase can consume the whole allowance in one transaction — which is fine if the purchase was planned and annoying if it was a grocery run in the first week.</p>
<h3>Annual caps and category pools</h3>
<p>Some cards publish an annual ceiling instead, often across a group of categories rather than one. A pooled cap is the harder version: groceries, transit, and streaming may share a single allowance, so heavy spending in one category silently reduces the bonus available in the others. If the categories are pooled, the cap is effectively lower than the per-category figure suggests.</p>
<h2>How a card reward cap changes your effective rate</h2>
<p>The effective rate is total rewards divided by total spending, and the cap is what pulls it below the advertised number. Two examples show the size of the gap.</p>
<p>Suppose a card pays 5% on the first $500 of groceries each quarter, then 1%. A household spending $900 a quarter earns $25 on the first $500 and $4 on the remaining $400 — $29 on $900, an effective 3.22%, not 5%. A flat 2% card pays $18, so the capped card still wins by $11 a quarter, or $44 a year.</p>
<p>Now find the crossover. Below $500 a quarter the capped card pays 5% against 2% and always wins. Above $500 its reward is 25 + 0.01 × (S − 500), while the flat card pays 0.02 × S. Setting them equal: 25 + 0.01S − 5 = 0.02S, so 20 = 0.01S and S = $2,000. Past that, the flat card overtakes.</p>
<p>The crossover is the useful number, not the headline rate: it marks where the cap stops being irrelevant and starts deciding the outcome, usually lower than people assume.</p>
<div class="fog-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-200/70 bg-surface" data-fog-table><table>
<thead>
<tr>
<th>Cap type</th>
<th>How it is usually written</th>
<th>What it costs you</th>
<th>Where to find it</th>
</tr>
</thead>
<tbody>
<tr>
<td>Per-statement bonus cap</td>
<td>&#8220;5% on up to $500 each billing cycle&#8221;</td>
<td>Spend above the cap earns the base rate for the rest of the cycle</td>
<td>Rewards terms, not the marketing page</td>
</tr>
<tr>
<td>Quarterly category cap</td>
<td>&#8220;3% in rotating categories, up to $1,500 per quarter&#8221;</td>
<td>Timing matters; a purchase in the wrong week earns less</td>
<td>Quarterly activation notice</td>
</tr>
<tr>
<td>Annual pooled cap</td>
<td>&#8220;4% on travel and dining combined, up to $10,000 per year&#8221;</td>
<td>One category can exhaust the other&#8217;s allowance</td>
<td>Full cardholder agreement</td>
</tr>
<tr>
<td>Bonus cap on sign-up offer</td>
<td>&#8220;Earn 60,000 points after $4,000 of spending&#8221;</td>
<td>Spending past the threshold adds nothing toward the bonus</td>
<td>Offer terms and expiry date</td>
</tr>
</tbody>
</table></div>
<blockquote><p>A cap does not reduce the rate on your spending. It reduces the rate on the spending that comes after a certain point, and the ordering of your purchases within the period is what decides which spending that is.</p></blockquote>
<h2>Why issuers put a card reward cap on the rate</h2>
<p>Because the bonus rate is funded from interchange and the issuer&#8217;s margin, and both are proportional to transaction size in ways that a percentage reward is not. A cap keeps the cost of the program bounded while the headline rate stays competitive in advertising.</p>
<p>It also limits adverse selection. Without a cap, a generous category rate becomes a tool for concentrating exactly the spending that loses the issuer money — the way a generous rebate attracts the traders who cost a venue most. The cap stops the program being arbitraged by its best-informed users.</p>
<p>A second reason is quieter. Caps keep the advertised rate technically true while lowering the realised rate for heavy spenders, who are the customers whose rewards cost the most. That is not an accident of drafting.</p>
<h2>Where card reward caps go wrong in practice</h2>
<p>Most of the loss happens in the gap between what a cap says and what the transaction data reports, and neither is visible on the rewards dashboard.</p>
<ul>
<li><strong>Merchant category coding.</strong> Bonus categories are matched by merchant category code, not by what you bought. A supermarket inside a department store, or a delivery app billed as a restaurant, may code differently than expected and earn the base rate.</li>
<li><strong>Period boundaries.</strong> A purchase made on the last day of a cycle may post in the next one. If the cap had room in the earlier period, the bonus is lost to a timing difference you cannot see.</li>
<li><strong>Clawbacks and reversals.</strong> Refunds and disputed charges commonly reverse the reward, and if the cap was consumed, the allowance may not come back.</li>
<li><strong>Tracking the remaining allowance.</strong> Few issuers display it. Most cardholders discover the cap by noticing a lower rate on a statement, weeks after the fact.</li>
</ul>
<h2>How to work around a card reward cap</h2>
<p>The practical response is to route spending rather than to spend more, and the ordering below keeps the comparison honest.</p>
<ol>
<li>List the caps that apply to you in dollars of eligible spend per period, converting points caps at a conservative value.</li>
<li>Sum your typical category spending for the same period and compare it with each cap to see which ones you actually reach.</li>
<li>Rank the cards by effective rate at your spending level, not by advertised rate.</li>
<li>Route the spending that fits inside a cap to the capped card and everything above it to the best flat-rate card.</li>
<li>Recalculate when your spending changes, because the crossover moves and a card that won last year may not win now.</li>
<li>Check one statement per quarter against the terms, since coding changes and category rotations shift the boundary without notice.</li>
</ol>
<p>The post <a href="https://www.fogment.com/card-reward-caps/">Reward Caps: The Ceiling Nobody Reads</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.fogment.com/card-reward-caps/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Closing a Crypto Card: What Happens to the Balance</title>
		<link>https://www.fogment.com/closing-a-crypto-card/</link>
					<comments>https://www.fogment.com/closing-a-crypto-card/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 23:21:53 +0000</pubDate>
				<category><![CDATA[Cards]]></category>
		<category><![CDATA[Account Closure]]></category>
		<category><![CDATA[Card Balance]]></category>
		<category><![CDATA[Consumer Rights]]></category>
		<category><![CDATA[Crypto Cards]]></category>
		<category><![CDATA[Custody Models]]></category>
		<category><![CDATA[Exit Routes]]></category>
		<category><![CDATA[Pending Holds]]></category>
		<category><![CDATA[Personal Finance]]></category>
		<category><![CDATA[Record Keeping]]></category>
		<category><![CDATA[Rewards Forfeiture]]></category>
		<guid isPermaLink="false">https://www.fogment.com/closing-a-crypto-card/</guid>

					<description><![CDATA[<p>A close crypto card request is mostly a balance question. Most programmes will not process one while any balance, pending authorisation or reward liability remains, so the practical sequence is [&#8230;]</p>
<p>The post <a href="https://www.fogment.com/closing-a-crypto-card/">Closing a Crypto Card: What Happens to the Balance</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A close crypto card request is mostly a balance question. Most programmes will not process one while any balance, pending authorisation or reward liability remains, so the practical sequence is to move value out, confirm the account reads zero, and only then ask in writing.</p>
<p>The complication is that &#8220;close crypto card&#8221; means different things at different providers. Some close the card but keep the account open. Some keep the account open for a set period in case of refunds. Some convert any residual balance to fiat and mail a cheque, while others simply freeze it. Knowing which model you are dealing with determines what you need to do before you ask.</p>
<ul>
<li><strong>Empty before you close.</strong> A residual balance is the most common reason a closure request stalls.</li>
<li><strong>Pending authorisations can outlive the card.</strong> Holds and refunds may land after the closure date.</li>
<li><strong>Get the closure in writing.</strong> A confirmed ticket or email is the only proof of the date and the terms.</li>
<li><strong>Keep statements.</strong> Tax and audit obligations usually outlast the account, sometimes by years.</li>
</ul>
<h2>What happens to the balance when you close a crypto card</h2>
<p>The balance follows whichever custody model the card uses. If the issuer holds your crypto, closure triggers a disposal process defined in the terms. If the card merely spends from a wallet you control, the balance never belonged to the issuer and closure has no effect on it.</p>
<h3>When the issuer holds the balance</h3>
<p>Most card programmes hold customer assets with a partner institution and record your entitlement in their ledger. On closure, the terms typically specify a deadline for you to withdraw, after which the balance may be converted to fiat, held for collection, or in some jurisdictions treated as unclaimed property after a statutory period. Read the closure clause before you initiate, because the default outcome is rarely the one you want.</p>
<h3>When the balance sits in a wallet you control</h3>
<p>If the card is a spending layer over a self-custody wallet, closing it is mostly an administrative act. Your funds stay where they are, and the only thing that disappears is the ability to spend them through that card. The risk here is different: you may lose access to historical statements that are useful for tax reporting.</p>
<h2>Exit routes for the remaining balance</h2>
<p>Four routes are common, and they differ in cost, speed and how much documentation they generate.</p>
<div class="fog-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-200/70 bg-surface" data-fog-table><table>
<thead>
<tr>
<th>Route</th>
<th>Cost shape</th>
<th>Speed</th>
<th>Main risk</th>
</tr>
</thead>
<tbody>
<tr>
<td>Spend the balance down</td>
<td>Conversion spread only, no exit fee</td>
<td>Weeks, depending on spend</td>
<td>Price moves while you wait</td>
</tr>
<tr>
<td>Convert to fiat and bank out</td>
<td>Conversion spread plus transfer fee</td>
<td>One to five business days</td>
<td>Bank may request source-of-funds evidence</td>
</tr>
<tr>
<td>Withdraw on-chain to your own wallet</td>
<td>Network fee, sometimes an issuer withdrawal fee</td>
<td>Minutes to an hour</td>
<td>Wrong address or wrong network</td>
</tr>
<tr>
<td>Transfer to another card programme</td>
<td>Depends on both providers</td>
<td>Days</td>
<td>Double conversion if currencies differ</td>
</tr>
<tr>
<td>Leave it and let the issuer dispose of it</td>
<td>Whatever the terms allow</td>
<td>Undefined</td>
<td>Worst rates and least control</td>
</tr>
</tbody>
</table></div>
<blockquote><p>A closure is a sequence, not a button. The sequence is: stop new activity, settle everything pending, move the balance, confirm zero, then request closure in writing and keep the confirmation.</p></blockquote>
<h2>How to close a crypto card without leaving value behind</h2>
<ol>
<li>Download every statement and transaction export you may need for tax or audit purposes.</li>
<li>Stop using the card for new purchases and cancel any recurring subscriptions billed to it.</li>
<li>Record outstanding rewards, cashback pending and referral credits, and check whether they survive closure.</li>
<li>Wait for pending authorisations to settle, then check the available balance rather than the total balance.</li>
<li>Move the remainder using the cheapest route from the table above, and keep the transaction references.</li>
<li>Confirm the balance reads zero in the currency the issuer settles in, not just your display currency.</li>
<li>Request closure in writing and ask for confirmation of the effective date and any residual obligations.</li>
<li>Re-check the account after thirty days for late refunds or trailing fees.</li>
</ol>
<h2>Why a zero balance is not always zero</h2>
<p>Displayed balances can hide three things: unsettled authorisations, pending refunds and currency rounding. Each can reopen a closed account or leave a small residual that blocks the process, which is why close crypto card requests often come back rejected when the balance looks empty.</p>
<h3>Authorisations and refunds</h3>
<p>A hotel or car rental hold can sit for weeks. A refund can arrive after the card is closed. Programmes usually handle these by keeping a settlement path open, but the mechanics vary: some reopen the account, some issue a transfer, and some hold the credit until you claim it. Ask which applies before you close, especially if you travel.</p>
<p>If you want to close crypto card accounts cleanly, the useful habit is to treat the last thirty days as part of the process rather than an afterthought.</p>
<h3>Fees charged after closure</h3>
<p>An inactivity fee, a closure fee or a final statement fee can be debited after the balance reaches zero, producing a negative balance. In many jurisdictions the issuer must tell you, but the notice may arrive by email you have stopped reading. Keep access to the account inbox until the closure is confirmed in writing.</p>
<h2>Timing the closure around fees and rewards</h2>
<p>The date you close changes the cost. Most programmes charge fees on a fixed cycle, and rewards are typically paid after a qualifying period. Closing the day before a payout forfeits it; closing a day after a monthly fee is debited wastes a month you paid for.</p>
<p>Three dates are worth noting before you act: the next reward payout, the next fee debit, and the end of the statement period. Closing just after a payout and just after a statement close gives you the most complete records and the least forfeited value. If a fee is charged in advance for a period you will not use, ask whether a pro-rata refund applies; the answer is often no, but the question is worth asking in writing.</p>
<p>There is also a liquidity consideration. If your balance is held in a volatile asset, the days between deciding to close and actually moving the funds are days of exposure. Converting to a stable asset first, then withdrawing, separates the price decision from the administrative one. It costs an extra spread, which is often cheaper than a week of waiting for a support ticket.</p>
<p>The post <a href="https://www.fogment.com/closing-a-crypto-card/">Closing a Crypto Card: What Happens to the Balance</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.fogment.com/closing-a-crypto-card/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Spending Crypto Without Selling It</title>
		<link>https://www.fogment.com/card-settlement/</link>
					<comments>https://www.fogment.com/card-settlement/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 23:21:48 +0000</pubDate>
				<category><![CDATA[Cards]]></category>
		<category><![CDATA[Authorisation Holds]]></category>
		<category><![CDATA[Card Settlement]]></category>
		<category><![CDATA[Conversion Spread]]></category>
		<category><![CDATA[Credit Line Cards]]></category>
		<category><![CDATA[Cross Border Spending]]></category>
		<category><![CDATA[Currency Risk]]></category>
		<category><![CDATA[Payment Mechanics]]></category>
		<category><![CDATA[Spend Crypto Without Selling]]></category>
		<category><![CDATA[Stablecoin Spending]]></category>
		<category><![CDATA[Taxable Disposals]]></category>
		<guid isPermaLink="false">https://www.fogment.com/card-settlement/</guid>

					<description><![CDATA[<p>To spend crypto without selling, a card has to do one of two things at the moment of the transaction: convert a slice of your balance into fiat, or lend [&#8230;]</p>
<p>The post <a href="https://www.fogment.com/card-settlement/">Spending Crypto Without Selling It</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>To spend crypto without selling, a card has to do one of two things at the moment of the transaction: convert a slice of your balance into fiat, or lend you fiat against that balance as collateral. There is no third mechanism. Everything the marketing calls &#8220;spending your crypto&#8221; is one of those two, and the difference decides your cost, your tax position and your exposure.</p>
<p>The phrase &#8220;spend crypto without selling&#8221; usually means the second option, where the balance stays intact and a credit line absorbs the purchase. That is a real mechanism, but it is not free and it is not risk-free. This article walks through what happens between the tap and the settlement, and who is holding the currency risk while the transaction clears.</p>
<ul>
<li><strong>Every card purchase is a sale or a loan.</strong> Identify which one before comparing costs.</li>
<li><strong>The rate is fixed at a moment you do not control.</strong> Authorisation and settlement can be days apart.</li>
<li><strong>FX risk sits with whoever holds the position in the gap.</strong> Read the clause, not the headline fee.</li>
<li><strong>&#8220;Without selling&#8221; often means borrowing.</strong> A loan against collateral carries a liquidation risk a debit card does not.</li>
</ul>
<h2>What happens at the moment you tap the card</h2>
<p>A card transaction starts with an authorisation, which is a request for funds that reserves an amount without moving it. Settlement follows, usually a day or more later, at the amount the merchant actually claims. The mechanism your card uses to fund that settlement is the thing worth understanding.</p>
<h3>Conversion: an economic sale</h3>
<p>In a conversion card, the issuer sells part of your balance when the transaction settles and uses the proceeds to pay the merchant. From your side the balance shrinks, and the sale is real even if the interface calls it a payment rather than a trade. In most jurisdictions that has the same tax and accounting character as selling on an exchange, which is why the record you keep matters.</p>
<p>Some issuers convert at authorisation, some at settlement, and some convert in bulk at the end of the day. The timing decides which price applies to your purchase and who carries the movement in between.</p>
<h3>Borrowing: a loan against your balance</h3>
<p>In a credit-line card, your balance is pledged as collateral and the issuer advances fiat to the merchant. Nothing is sold, so the coin count stays the same and no taxable disposal occurs at that point. What you have instead is a debt, usually with an interest rate, a loan-to-value limit and a maintenance threshold that can trigger a forced sale later.</p>
<p>The trade is explicit: you keep the asset exposure and take on leverage. If the asset rises, you did better than selling. If it falls far enough, the collateral is liquidated at the worst moment, which converts a paper loss into a realised one.</p>
<h2>Who takes the FX risk when you spend crypto without selling</h2>
<p>Currency risk sits with whoever is holding an unhedged position between the moment the rate is set and the moment the merchant is paid. That is a contractual question, and the answer is usually the cardholder.</p>
<h3>The authorisation-to-settlement window</h3>
<p>Authorisation reserves an amount based on a reference rate at that instant. Settlement arrives later, often one to three days, and the merchant claims the final amount in its own currency. If the terms say the conversion happens at settlement, you carry both the crypto price movement and the fiat exchange movement across that window. If the terms say the rate is locked at authorisation, the issuer carries it and prices that risk into the spread instead.</p>
<p>Neither arrangement is automatically cheaper. A locked rate is predictable and usually carries a wider spread. A settlement rate can be better or worse, and the variance is yours.</p>
<h3>Two currencies in one purchase</h3>
<p>A purchase abroad involves two conversions, not one. Your balance is denominated in one asset, the merchant bills in another, and the card network settles in a third. Each step can carry a spread, and a card that quotes a single &#8220;conversion fee&#8221; may still apply a network markup on the fiat leg. The only reliable measure is the total debited against the merchant&#8217;s receipt, compared over several transactions.</p>
<blockquote><p>&#8220;You never sell your crypto&#8221; describes the balance, not the transaction. Somebody sold something to pay the merchant, and the terms tell you whether it was you or the issuer.</p></blockquote>
<h2>Worked example: a 120 euro purchase from a dollar balance</h2>
<p>Assume a euro-area purchase of 120.00 EUR, a balance held in a dollar-denominated stablecoin, a 1.0 percent conversion spread, and settlement two days after authorisation.</p>
<div class="fog-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-200/70 bg-surface" data-fog-table><table>
<thead>
<tr>
<th>Step</th>
<th>Rate or charge</th>
<th>Amount</th>
</tr>
</thead>
<tbody>
<tr>
<td>Authorisation, day 0</td>
<td>1 EUR = 1.08 USD</td>
<td>129.60 USD</td>
</tr>
<tr>
<td>Spread applied</td>
<td>1.0 percent</td>
<td>130.90 USD held</td>
</tr>
<tr>
<td>Settlement, day 2</td>
<td>1 EUR = 1.10 USD</td>
<td>132.00 USD claimed</td>
</tr>
<tr>
<td>Spread on settlement</td>
<td>1.0 percent</td>
<td>133.32 USD debited</td>
</tr>
<tr>
<td>Cost of the two-day gap</td>
<td>2.42 USD</td>
<td>1.85 percent of the purchase</td>
</tr>
</tbody>
</table></div>
<p>Under a settlement-rate model the cardholder pays 133.32 USD, of which 2.42 USD exists only because the euro strengthened over two days. Under an authorisation-lock model the cardholder pays 130.90 USD and the issuer absorbs the remaining 1.10 USD of movement, having priced that possibility into the spread at the outset.</p>
<p>Scale it. At 4,000 USD of monthly foreign spending, a 1.85 percent gap is roughly 74 USD a month, and it does not appear as a fee line anywhere on the statement. It appears as a slightly larger debit than the receipt implies.</p>
<h2>How to spend crypto without selling and still control the cost</h2>
<p>Control comes from measuring the all-in debit rather than the advertised fee. Three habits do most of the work.</p>
<p>First, reconcile the merchant receipt against the amount debited, in the merchant&#8217;s currency, for ten transactions. The average gap is your real cost. Second, check whether your card locks the rate at authorisation or at settlement, because that single clause determines whether you or the issuer carries the gap. Third, if you are using a credit-line card rather than a conversion card, treat the loan-to-value ratio as the main risk variable rather than the interest rate, since a forced sale costs more than any plausible interest saving.</p>
<p>For large purchases, the choice between converting and borrowing should be made before the transaction, not after. Converting removes the position and the risk. Borrowing keeps the position and adds a liquidation threshold. Both are legitimate, but only one of them can be unwound slowly.</p>
<p>The post <a href="https://www.fogment.com/card-settlement/">Spending Crypto Without Selling It</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.fogment.com/card-settlement/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Card Limits and Why They Change</title>
		<link>https://www.fogment.com/card-limits/</link>
					<comments>https://www.fogment.com/card-limits/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 21:21:49 +0000</pubDate>
				<category><![CDATA[Cards]]></category>
		<category><![CDATA[ATM Withdrawals]]></category>
		<category><![CDATA[Card Programme Rules]]></category>
		<category><![CDATA[Collateral Ratios]]></category>
		<category><![CDATA[Crypto Card Limits]]></category>
		<category><![CDATA[Daily Limits]]></category>
		<category><![CDATA[Declined Payments]]></category>
		<category><![CDATA[Risk Scoring]]></category>
		<category><![CDATA[Spending Caps]]></category>
		<category><![CDATA[Top Up Limits]]></category>
		<category><![CDATA[Verification Tiers]]></category>
		<guid isPermaLink="false">https://www.fogment.com/card-limits/</guid>

					<description><![CDATA[<p>Crypto card limits are caps on how much you can move through the card in a given period, and they are usually the first thing that breaks a real payment [&#8230;]</p>
<p>The post <a href="https://www.fogment.com/card-limits/">Card Limits and Why They Change</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Crypto card limits are caps on how much you can move through the card in a given period, and they are usually the first thing that breaks a real payment plan. A card advertised for daily spending can still decline a rent payment because the single-transaction cap is lower than the balance.</p>
<p>Crypto card limits are not one number. A card typically applies several at once: per transaction, per day, per statement period, at ATMs, and on top-ups. Each has a different owner and a different trigger, which is why a support agent can raise one and leave the others untouched.</p>
<ul>
<li><strong>Limits are layered.</strong> The binding constraint is whichever cap you hit first, not the headline figure.</li>
<li><strong>Different caps have different owners.</strong> Some are set by the issuer, some by its banking partner, some by the card network.</li>
<li><strong>They move with risk, not with loyalty.</strong> A change in your profile or in market conditions can cut a limit overnight.</li>
<li><strong>Testing beats assuming.</strong> One small transaction reveals more than any published table.</li>
</ul>
<h2>The limits a crypto card actually applies</h2>
<p>A crypto card applies limits at three points: when you spend, when you load, and when you withdraw. Most users only learn about the first, because that is where the decline happens.</p>
<h3>Spending limits</h3>
<p>Spending caps are usually expressed per transaction, per day and per statement period, and they interact. A card with a generous daily cap and a low per-transaction cap will decline a large purchase and approve several smaller ones in the same hour. Some programmes also apply merchant-category caps, which block or restrict cash-like, gambling or financial-service transactions regardless of amount.</p>
<p>There is also a velocity dimension that rarely appears in documentation: the number of transactions per hour or per day, and the pattern of merchants. A card used in three countries within an hour can be frozen by fraud rules even when every individual transaction is within its cap.</p>
<h3>Loading and withdrawal limits</h3>
<p>Top-up limits govern how much you can add to a custodial balance, and they are often tighter than spending limits because they are the point where funds enter the operator&#8217;s control. Withdrawal limits are separate again, and they are the ones that matter most during stress: a card can spend freely while withdrawal is capped at a level that makes exit slow.</p>
<p>ATM limits are a third category, usually a daily count plus a daily amount, set with reference to the network&#8217;s rules rather than the issuer&#8217;s preference. They are the most commonly reduced limit when a programme tightens risk.</p>
<h2>Why crypto card limits change without warning</h2>
<p>Limits move because the risk behind them moves. The card is a credit exposure to somebody, whether that is the issuer, the banking partner or the collateral, and limits are the dial used to manage it.</p>
<h3>Risk-based changes</h3>
<p>Account-level risk scoring adjusts continuously. A new account, a recent address change, an unusual merchant mix, a disputed transaction or a failed identity re-check can all lower a limit. The reverse is also true: sustained, ordinary spending history usually raises caps over time, which is why a card that felt restrictive in month one can feel normal in month six.</p>
<p>Regulatory and scheme changes sit on top of this. When a jurisdiction tightens rules on a product category or a card network updates its rules for a programme, the operator has little choice but to pass the change through. In many jurisdictions these changes require notice, but the notice period is often short and the practical effect is immediate.</p>
<h3>Collateral-based changes</h3>
<p>On a card backed by pledged crypto, the limit is a function of collateral value and the permitted loan-to-value ratio. If the collateral falls, the spending limit falls with it, often automatically and without a human decision. That is the clearest difference between a crypto card and a debit card: the limit is not a fixed permission, it is a mark-to-market number.</p>
<blockquote><p>A debit card limit is a rule about you. A collateral-backed card limit is a rule about the market, applied to you.</p></blockquote>
<h2>Comparing limit types</h2>
<p>The table maps the caps a typical programme applies, what each one is measured in, and who usually controls it. Specific figures vary widely by issuer and jurisdiction.</p>
<div class="fog-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-200/70 bg-surface" data-fog-table><table>
<thead>
<tr>
<th>Limit type</th>
<th>Measured in</th>
<th>Usually set by</th>
<th>Common trigger for change</th>
</tr>
</thead>
<tbody>
<tr>
<td>Per transaction</td>
<td>Amount</td>
<td>Issuer and banking partner</td>
<td>Risk tier or merchant category</td>
</tr>
<tr>
<td>Daily spend</td>
<td>Amount per day</td>
<td>Issuer</td>
<td>Account history, fraud flags</td>
</tr>
<tr>
<td>Statement period</td>
<td>Amount per month</td>
<td>Programme manager</td>
<td>KYC level, product tier</td>
</tr>
<tr>
<td>ATM withdrawal</td>
<td>Amount and count per day</td>
<td>Card network and issuer</td>
<td>Scheme rule change, risk review</td>
</tr>
<tr>
<td>Top-up</td>
<td>Amount per deposit</td>
<td>Issuer or custody partner</td>
<td>Source-of-funds checks</td>
</tr>
<tr>
<td>Collateral-linked spend</td>
<td>Loan-to-value ratio</td>
<td>Issuer credit policy</td>
<td>Collateral price movement</td>
</tr>
</tbody>
</table></div>
<h2>How to work within crypto card limits</h2>
<p>The practical approach is to find the binding constraint before you need it, rather than during a payment.</p>
<ol>
<li>List the caps that apply to your card: per transaction, daily, monthly, ATM and top-up.</li>
<li>Compare each against your three largest recurring payments, not against your average spend.</li>
<li>Run one test transaction near the per-transaction cap to confirm the published figure is live.</li>
<li>If a payment exceeds a cap, ask whether a split payment is permitted before the transaction, not after a decline.</li>
<li>Submit any identity or source-of-funds documents in advance; limits often rise only after verification completes.</li>
<li>For a collateral-backed card, monitor the loan-to-value ratio weekly rather than the spending balance.</li>
<li>Keep a second funding route for the payments that must not fail, such as rent or tax.</li>
</ol>
<p>The post <a href="https://www.fogment.com/card-limits/">Card Limits and Why They Change</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.fogment.com/card-limits/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Crypto Card in a Downturn: Collateral and Liquidation</title>
		<link>https://www.fogment.com/card-collateral-liquidation/</link>
					<comments>https://www.fogment.com/card-collateral-liquidation/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 19:21:49 +0000</pubDate>
				<category><![CDATA[Cards]]></category>
		<category><![CDATA[Collateral Backed Cards]]></category>
		<category><![CDATA[Crypto Card Collateral]]></category>
		<category><![CDATA[Debit Card Comparison]]></category>
		<category><![CDATA[Downturn Mechanics]]></category>
		<category><![CDATA[Forced Selling]]></category>
		<category><![CDATA[Leverage Risk]]></category>
		<category><![CDATA[Liquidation Risk]]></category>
		<category><![CDATA[Loan To Value]]></category>
		<category><![CDATA[Maintenance Margin]]></category>
		<category><![CDATA[Margin Calls]]></category>
		<guid isPermaLink="false">https://www.fogment.com/card-collateral-liquidation/</guid>

					<description><![CDATA[<p>Crypto card collateral turns a spending tool into a leveraged position. When you pledge a balance to support a credit line, the card stops being a way to move money [&#8230;]</p>
<p>The post <a href="https://www.fogment.com/card-collateral-liquidation/">Crypto Card in a Downturn: Collateral and Liquidation</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Crypto card collateral turns a spending tool into a leveraged position. When you pledge a balance to support a credit line, the card stops being a way to move money you already own and becomes a loan secured by an asset whose price moves every minute.</p>
<p>That is a different risk from a debit card, and the difference only becomes visible in a downturn. A debit card that declines a payment is an inconvenience. A card secured by crypto card collateral that falls below its maintenance threshold will sell your coins, at the moment you least want to sell them, to repay a loan you may have intended to keep open.</p>
<ul>
<li><strong>Collateral changes the failure mode.</strong> The card does not just stop working; it liquidates the asset behind it.</li>
<li><strong>Liquidation is mechanical.</strong> Thresholds are calculated automatically and rarely wait for a human review.</li>
<li><strong>The sale happens into weakness.</strong> Forced selling coincides with thin liquidity and wider spreads.</li>
<li><strong>The risk is measurable in advance.</strong> A single ratio tells you how far the price can fall before the selling starts.</li>
</ul>
<h2>What crypto card collateral actually secures</h2>
<p>It secures an advance. The issuer lends fiat to pay merchants and holds your pledged balance as security, which means the balance is not yours to withdraw while the loan is outstanding. Understanding what is pledged, and at what ratio, is the whole of the risk assessment.</p>
<h3>Pledged balances versus sold balances</h3>
<p>On a conversion card, the balance is spent: coins are sold at settlement and the position shrinks. On a collateral card, the balance is locked: coins stay in place, a debt is created, and the position remains exposed to price. The second arrangement keeps your upside and adds a downside that did not previously exist.</p>
<p>Some programmes combine the two, converting for everyday spending and lending only above a threshold. The terms decide which mechanism applies to a given transaction, and the boundary is not always obvious from the interface.</p>
<h3>The loan-to-value ratio</h3>
<p>Loan-to-value is the debt divided by the value of the collateral. A 5,000 dollar advance against 10,000 dollars of collateral is a ratio of 50 percent. Two thresholds matter: the initial ratio, which caps how much you can borrow, and the maintenance ratio, which triggers a response when the debt becomes large relative to the collateral.</p>
<p>Because the denominator moves with the market, the ratio is not a fixed property of your account. It rises when the collateral falls, even if you never spend again.</p>
<h2>How a downturn turns crypto card collateral into a forced sale</h2>
<p>A downturn raises the ratio through the denominator. Nothing you do has to change for the liquidation condition to be met; the price does the work.</p>
<h3>Maintenance thresholds and margin calls</h3>
<p>When the ratio crosses the maintenance threshold, the programme either issues a margin call or liquidates automatically. Many crypto cards skip the call entirely, because the position is small and the monitoring is automated. Where a call exists, the notice period is often measured in hours rather than days, which makes it impractical to fund from a bank account.</p>
<h3>What gets sold, and in what order</h3>
<p>Liquidation sells collateral to repay part of the debt, usually until the ratio returns to a target below the threshold. The sale is executed at market, which during a drawdown means thin order books and wider spreads, so the realised price is worse than the quoted one. A penalty fee is commonly added, and it is charged in the same event.</p>
<p>The result is that you lose the coins at the low, keep a residual debt in some cases, and receive no benefit from any later recovery. That asymmetry is the cost of the leverage, and it is not covered by any cashback rate.</p>
<blockquote><p>A debit card can only spend what you have. A collateral-backed card can spend what you have and then sell the rest to cover the difference.</p></blockquote>
<h2>Worked example: a 35 percent drawdown on a 5,000 dollar advance</h2>
<p>Assume 10,000 dollars of pledged collateral, an initial limit of 60 percent, a 5,000 dollar advance, a maintenance threshold of 75 percent, and a 5 percent liquidation penalty.</p>
<div class="fog-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-200/70 bg-surface" data-fog-table><table>
<thead>
<tr>
<th>Stage</th>
<th>Collateral</th>
<th>Debt</th>
<th>Ratio</th>
</tr>
</thead>
<tbody>
<tr>
<td>At drawdown</td>
<td>10,000</td>
<td>5,000</td>
<td>50 percent</td>
</tr>
<tr>
<td>Price falls 20 percent</td>
<td>8,000</td>
<td>5,000</td>
<td>62.5 percent</td>
</tr>
<tr>
<td>Price falls 35 percent</td>
<td>6,500</td>
<td>5,000</td>
<td>76.9 percent, threshold breached</td>
</tr>
<tr>
<td>After liquidation sale</td>
<td>3,357</td>
<td>2,014</td>
<td>60 percent, restored</td>
</tr>
</tbody>
</table></div>
<p>The breach arrives at a fall of roughly 33 percent, not 35, because the threshold is met as soon as collateral drops below 6,667 dollars. The liquidation then sells about 3,143 dollars of collateral, repays roughly 2,986 dollars after the 5 percent penalty, and leaves 2,014 dollars of debt against 3,357 dollars of remaining collateral.</p>
<p>Compare the two cards on the same drawdown. A debit card holding the same 10,000 dollars would be worth 6,500 dollars and would still spend normally, with no debt and no forced sale. The collateral card ends the episode with 3,357 dollars of collateral, 2,014 dollars of debt, and a realised loss that a recovery in price cannot undo.</p>
<h2>How to reduce liquidation risk on a collateral-backed card</h2>
<p>The controls are simple and mostly about distance from the threshold.</p>
<ol>
<li>Calculate the price fall that would breach the maintenance ratio: one minus the ratio of your current loan-to-value to the maintenance threshold.</li>
<li>Decide whether that fall is plausible within your holding period, and borrow well below the initial limit if it is.</li>
<li>Keep the borrowed amount under half of the initial capacity, which doubles the cushion before a breach.</li>
<li>Hold additional collateral in reserve that you can add without selling anything else.</li>
<li>Repay a fixed amount each month so the debt falls even if the price does not.</li>
<li>Set a price alert at the level that produces the breach, not at a round number that feels comfortable.</li>
<li>Read the liquidation clause for the penalty, the target ratio and whether a margin call is issued at all.</li>
</ol>
<p>The post <a href="https://www.fogment.com/card-collateral-liquidation/">Crypto Card in a Downturn: Collateral and Liquidation</a> appeared first on <a href="https://www.fogment.com">FogChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.fogment.com/card-collateral-liquidation/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
