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