The Two-Page Policy That Settled Most Arguments
What our crypto payments policy says, why the auditor asked for one, and the sections we nearly left out.
Sep 26, 2026 · 2 minOne beginner, every mistake, written down
One beginner, every mistake, written down. Every entry here is something that actually happened, written down soon after, including the parts that were embarrassing.
What our crypto payments policy says, why the auditor asked for one, and the sections we nearly left out.
Sep 26, 2026 · 2 minWhat our accountant said at the second year end, and the three things that made it straightforward.
Sep 23, 2026 · 2 minSix questions in one email eliminated three of five venues before we compared a single fee.
Sep 17, 2026 · 2 minFifteen minutes with the relationship manager, before the first settlement, and we have had no questions since.
Sep 12, 2026 · 2 minIt was not about cost for them. Understanding why changed how I handle these conversations.
Sep 7, 2026 · 2 minA year of numbers: which invoices used it, what it saved, and where it made no difference at all.
Sep 1, 2026 · 2 minTwo had changed ownership. One had varied its permissions. Nobody had written to tell us.
Aug 28, 2026 · 2 minWho has access, which addresses are registered, and what the log shows. It has caught something every time.
Aug 23, 2026 · 2 minThe transfer would have cost fifty euros and taken four days. What I did instead and what I had to check first.
Aug 17, 2026 · 2 minA survey of people I know, and the pattern that explains who adopted and who did not.
Aug 13, 2026 · 2 minA counterparty who accepted our settlement terms at a small size and objected at a large one told us what we needed to know.
Aug 9, 2026 · 2 minNot for pricing, though that improved. For the week our usual desk stopped quoting.
Aug 4, 2026 · 2 minWe had several thousand in stablecoin for two months because nobody had chosen not to. Here is the policy we wrote.
Jul 29, 2026 · 2 minSeven lines, each one added after something specific went wrong.
Jul 25, 2026 · 2 minThe happy path took an afternoon. The thing I did not build caused every support ticket for a month.
Jul 19, 2026 · 2 minOne missed payout, an explanation that sounded reasonable, and the rule I made afterwards.
Jul 14, 2026 · 2 minNot the card rate. Everything, including the transactions we could not accept at all. The number was larger than I expected.
Jul 9, 2026 · 2 minNot because anything went wrong. Because working out what would happen if it did was uncomfortable.
Jul 4, 2026 · 2 minNine questions to three providers. The ones they would not answer told me more than the ones they would.
Jun 29, 2026 · 2 minIt worked fine. The tax record it generated was the problem, and one configuration change fixed it.
Jun 24, 2026 · 2 minFifteen minutes on a document nobody opens, and it told me more than a week of comparing features.
Jun 18, 2026 · 2 minFive minutes each. Two did not check out, and one of them was holding a balance for me.
Jun 14, 2026 · 2 minMy first attempt at comparing quotes was useless because I did it sequentially. Here is what changed.
Jun 10, 2026 · 2 minI placed a market order that was larger than the book could absorb, and watched it fill at progressively worse prices.
Jun 3, 2026 · 2 minA quarter of offering it, without a discount, and the split was not what I expected in either direction.
May 30, 2026 · 2 minThe customer had paid. Our system said unpaid. Nothing was wrong and it still cost us a support conversation.
May 24, 2026 · 2 minSame stablecoin, same amount, same client. The network choice changed the fee from under a dollar to over ten.
May 21, 2026 · 2 minHolding it felt harmless. Three reasons changed my mind, and one of them was the accounting.
May 15, 2026 · 2 minThe question that eliminated three of five before we looked at a single fee.
May 10, 2026 · 2 minA customer overpaid and asked for the difference sent somewhere else. Everything about it was polite and I said no anyway.
May 5, 2026 · 2 minWhat I had to decide before saying yes, and the two things I got wrong in the first month.
Apr 30, 2026 · 2 minThree questions decided it for us, and none of them were about technology.
Apr 25, 2026 · 2 minOne account for the whole team seemed practical until someone left and we could not tell what they had done.
Apr 20, 2026 · 2 minWhat changed: separate wallets by purpose, a mandatory reference field, and a platform whose export actually reconciles.
Apr 14, 2026 · 2 minApproval rules felt excessive for a team of four. The one we almost disabled is the one that would have mattered.
Apr 11, 2026 · 2 minTwo minutes of arithmetic showed I had been paying about four times more than necessary on routine conversions.
Apr 5, 2026 · 2 minThe most common expensive mistake in crypto, made by someone who knew about it, and what actually happened next.
Mar 31, 2026 · 2 minThe questions she asked, the records that satisfied them, and the export I now insist on before using a platform.
Mar 26, 2026 · 2 minWhat I put on the invoice, what I got wrong, and the six lines that stopped it happening again.
Mar 21, 2026 · 2 minWhat they asked, what answered it, and what a colleague did wrong that cost him the account.
Mar 16, 2026 · 2 minThe sale was instant. The bank transfer was not, and the first one triggered checks nobody had mentioned.
Mar 12, 2026 · 2 minThe full document list, the questions that were harder than expected, and what I would prepare in advance next time.
Mar 7, 2026 · 2 minA payment stalled because I hit a limit I did not know existed, during a week when it mattered.
Mar 1, 2026 · 2 minI compared providers on their fees and paid a larger one somewhere nobody told me about.
Feb 24, 2026 · 2 minThe transfer bounced, the invoice was useless and the limit was lower than I needed. What I would do differently.
Feb 20, 2026 · 2 min