A coffee shop wants to accept Bitcoin and receive euros. Sounds simple, but it isn't.
Here's the gap 👇
In the EU, self-custody is the sane way for a business to accept Bitcoin payments. Routing customer payments into a CASP's custody is a compliance headache you don't want.
Great if you're stacking Bitcoin on your balance sheet.
But most businesses want something else: accept Bitcoin, settle in euros. No volatility on revenue. Predictable numbers for the accountant.
And honestly – it's better payment infrastructure. Cheaper than card rails even with a standard off-ramp fee. No chargebacks. Euros in the bank in seconds, not days.
So the flow looks obvious: Bitcoin → your own wallet → licensed euro off-ramp. And since it's your own verified wallet, even the 1k euro transfer rule stops being a blocker.
Now the huge but.
Who signs the forward transaction?
Deposit and sell manually every time – that's not a payment experience, that's a part-time job.
Let a third party sign for you – the moment someone else can move your funds, that's custody. Custody needs a CASP license under MiCA. Travel rule and all. You're back where you started.
For merchants running their own BTCPay server, we built a plugin that auto-forwards to euros while the keys stay with the merchant. Here's a demo: https://youtu.be/CQgmo2v9KG0
But the coffee shop doesn't run a BTCPay server.
That's exactly what we're building at Bringin – accept Bitcoin, settle in euros, dedicated IBAN, clean exports for your accountant. Without anyone but you touching your keys.
We're seeing the demand firsthand. One step at a time ⚡
Prashanth
npub1z3…f9gxr
2026-07-28 07:34:27 UTC
Author Public Key
npub1z3xsj7reuyjwvvm5g64ft5ju8u0x6jgskdd3u9dswrzxd7yt7dws6f9gxrPublished at
2026-07-28 07:34:27 UTCEvent JSON
{
"id": "afe0457a1812c87364dfe2c98b702aa1c2019dbc98056cfb6a1743c7e85aebe9",
"pubkey": "144d097879e124e6337446aa95d25c3f1e6d4910b35b1e15b070c466f88bf35d",
"created_at": 1785224067,
"kind": 1,
"tags": [
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://relay.snort.social/"
],
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://nostr.wine/"
],
[
"r",
"wss://relay.primal.net/"
],
[
"r",
"wss://rilo.nostria.app/"
],
[
"client",
"Primal Web"
]
],
"content": "A coffee shop wants to accept Bitcoin and receive euros. Sounds simple, but it isn't.\n\nHere's the gap 👇\n\nIn the EU, self-custody is the sane way for a business to accept Bitcoin payments. Routing customer payments into a CASP's custody is a compliance headache you don't want.\n\nGreat if you're stacking Bitcoin on your balance sheet.\n\nBut most businesses want something else: accept Bitcoin, settle in euros. No volatility on revenue. Predictable numbers for the accountant.\n\nAnd honestly – it's better payment infrastructure. Cheaper than card rails even with a standard off-ramp fee. No chargebacks. Euros in the bank in seconds, not days.\n\nSo the flow looks obvious: Bitcoin → your own wallet → licensed euro off-ramp. And since it's your own verified wallet, even the 1k euro transfer rule stops being a blocker.\n\nNow the huge but.\n\nWho signs the forward transaction?\n\nDeposit and sell manually every time – that's not a payment experience, that's a part-time job.\n\nLet a third party sign for you – the moment someone else can move your funds, that's custody. Custody needs a CASP license under MiCA. Travel rule and all. You're back where you started.\n\nFor merchants running their own BTCPay server, we built a plugin that auto-forwards to euros while the keys stay with the merchant. Here's a demo: https://youtu.be/CQgmo2v9KG0\n\nBut the coffee shop doesn't run a BTCPay server.\n\nThat's exactly what we're building at Bringin – accept Bitcoin, settle in euros, dedicated IBAN, clean exports for your accountant. Without anyone but you touching your keys.\n\nWe're seeing the demand firsthand. One step at a time ⚡",
"sig": "26aadf602d202f902ef1554b26edc0118d6c8694ce9b4de61abfa1db03fb2df4fbac649749b7649680a10237384621221d10c2eac042ddd323621b408846145b"
}