BTCPay Server vs Coinsnap

The same two networks, and nothing else#

Both cards carry Bitcoin on-chain and Lightning and stop there. Neither accepts a stablecoin, which removes both from consideration for most online checkouts and makes them directly comparable for the rest.

That shared boundary is why this pair is worth a page. Comparing either against a general processor mostly measures the boundary; comparing them against each other measures everything else.

Lightning is the reason the boundary is workable at all. Without it a four-euro payment costs more in network fee than it is worth, and both providers know that, which is why both support it.

One publishes zero, the other publishes nothing#

BTCPay Server states plainly that there are no fees and no middleman. Coinsnap states no transaction fee, no monthly fee and no plan pricing on any page we could reach.

Those are different failures of disclosure and only one of them is a failure. A stated zero is checkable; a silence is a question you have to ask before you can compare anything.

In a category where one percent is the norm, silence usually means at or above the norm. That is an inference and this comparison does not score on inferences, but it is the reason to send the email before the integration.

Euros in the bank, or no euros anywhere#

The hosted service offers settlement either to a Bitcoin wallet you control or as euros into a bank account, with the choice left to the merchant. The self-hosted software offers only the first.

For a German bakery or a Dutch web shop that single line decides the pair. Nobody in a small business wants a treasury policy attached to the card terminal, and euro payout removes the need for one.

For a business already holding bitcoin deliberately, the euro leg is a feature it will never enable, and the comparison moves entirely onto cost and control.

Plugins on both sides, aimed differently#

The self-hosted project names twenty-three integrations, the hosted service eleven shop platforms plus eight WordPress form and membership add-ons. Both shelves are unusually deep for this category.

The form plugins are the distinctive part of the hosted offering. Taking bitcoin through a donation form, a membership signup or a contact form is where small organisations get stuck, and almost nothing else in this index builds for it.

The self-hosted project wins on breadth of storefront platforms and loses on the form layer. Between the two, a WordPress site is well served either way and the deciding factor is who runs the server.

Custody is settled on one side and open on the other#

The software is non-custodial without qualification: invoices are built against a public key you supply and the private key never reaches the server.

The hosted service does not state a custody model, and cannot state a single one, because it depends on which settlement mode the merchant picks. Bitcoin to your own wallet is one shape; euros to your bank is necessarily another.

Ask which addresses in the payment path the provider controls and for how long. The custody guide covers why a short window is usually acceptable and why knowing beats assuming.

Who runs the thing#

One side is an open-source project that states it is not a company. The other is a brand operated by a named company whose jurisdiction is not published.

Neither answer would satisfy a procurement review, and for very different reasons. There is nobody to contract with in the first case and nobody identifiable in the second.

For a small merchant that matters less than it sounds, because the amounts at risk are one settlement cycle rather than a balance. It matters a great deal for anyone whose customers pay large invoices.

What to ask each of them#

To the hosted service: the transaction fee, the monthly fee if any, and the cost of the euro conversion. All three are missing from the public pages and all three change the comparison materially.

To the project: nothing, but budget an afternoon to read the deployment documentation before deciding. The install is well documented and the ongoing operation is the part people underestimate.

To both, if you take small payments: how Lightning liquidity is managed and what happens when a channel cannot route. That is the failure mode neither card discusses and the one a busy counter will meet.

Where this pair actually lands#

A European small business on WooCommerce or Shopware that wants bitcoin acceptance and euros in the bank takes the hosted service, having first established what it costs.

A Bitcoin-native operator with an engineer takes the software, pays nothing, keeps every key and accepts the operational load that comes with both.

A donation-taking organisation should look hard at the form plugins on the hosted side, because that specific piece of work is not available anywhere else in this index and it is usually the blocker.

What the total cost looks like over a year#

On the self-hosted side the bill is a virtual server and somebody’s attention, both of which are fixed and neither of which scales with revenue. At low volume that is the more expensive option and merchants routinely miss it.

On the hosted side the bill is unknown, which is a worse position to be in than an unfavourable known. A merchant cannot even establish whether the crossover exists, let alone where it sits.

Get the number, then model twelve months of both. It is a spreadsheet afternoon and it is the only honest way to compare a fixed cost against a percentage.