~/notes / acquiring
Crypto Payment Processor: Settlement Models and What They Cost You
Instant conversion, scheduled settlement and holding a crypto balance are three different businesses. How each affects working capital, risk and reporting.
A crypto payment processor can settle you in three ways, and the choice has more effect on your business than the fee does. It determines your exposure, your working capital and how complicated your books are. A working reference for most of what follows is crypto acquiring for businesses, where the same variables are stated rather than implied.
Model one: convert everything immediately, settle fiat
The customer pays crypto, the processor converts at confirmation, you receive fiat on a schedule.
Exposure: none beyond the confirmation window. You priced in euros and you receive euros.
Working capital: determined by settlement frequency. Daily is close to card acquiring. Weekly means a week of revenue in transit permanently.
Books: simplest possible. Revenue in fiat, a fee, nothing else. No crypto appears on the balance sheet.
This is correct for the large majority of merchants. If accepting crypto is a payment method rather than a treasury strategy, take the fiat.
Model two: hold a crypto balance, settle on instruction
The processor credits you in crypto. You decide when to convert and settle.
Exposure: full price exposure on your revenue until you convert. A ten percent move against you is a ten percent revenue reduction.
Working capital: you control it, which is an advantage if you also have crypto-denominated costs.
Books: substantially more complex. Crypto on the balance sheet, revaluation at each reporting date, disposals when you convert, and a fiat value required at the moment of every receipt.
This makes sense when you have genuine crypto-denominated outgoings, or a deliberate treasury policy approved by whoever is accountable for it. It does not make sense as a default because nobody decided.
Model three: split
A fixed percentage converted immediately, the rest held. Commonly 80 or 90 percent converted.
Exposure: bounded to the held portion.
Working capital: predictable.
Books: the complexity of model two applied to a smaller number, which is the same complexity.
This is the reasonable middle for a business that wants some crypto exposure without betting its revenue on it. The percentage should be a decision with a rationale, not a default. For a business the calculation inverts, which is the gap a fintech payment gateway fills.
Settlement frequency, quantified
At a hundred thousand euros of monthly crypto revenue:
Daily settlement: roughly three thousand three hundred euros in transit at any time.
Weekly settlement: roughly twenty-three thousand euros in transit.
Monthly settlement: a hundred thousand euros in transit.
Whether that difference matters depends entirely on your cash position. For a business with comfortable reserves it is irrelevant. For one managing payroll tightly, weekly against daily is a real constraint.
The stablecoin variant
Some processors offer settlement in a stablecoin rather than fiat. This is worth considering when you have outgoings in the same stablecoin, because it removes a conversion in both directions.
It is not equivalent to fiat. A stablecoin carries issuer risk and, in a stress event, a de-peg. Treat it as a third category rather than as a fiat substitute, and size the balance accordingly.
Processors offering stablecoin settlement alongside fiat usually let you split between the two, which is the sensible configuration when you have both kinds of cost.
What to decide before signing
Which model, with a written rationale. Settlement frequency and whether it can change as volume grows. If holding any balance, who is accountable for the exposure and what the policy is for reducing it.
The last one is the part that gets skipped and then becomes an awkward conversation when a position that nobody decided to take moves against the company.
What I would do
Model one, daily settlement, unless there is a specific reason to hold crypto. Then revisit at the point where crypto revenue is large enough that a treasury policy is worth writing. Holding by default is a position taken by inattention, and those are the ones that are hardest to explain afterwards.
# Corrections and technical nitpicks are welcome. Send them over. They get published with the fix.