Swiss Bitcoin Pay

• Name: Swiss Bitcoin Pay
• URL: https://swiss-bitcoin-pay.ch/
• Category: non-custodial Bitcoin merchant shell / Lightning point-of-sale and ecommerce middleware / Bolt Card sidecar
• Tags: bitcoin-ecosystem
• Summary: Swiss Bitcoin Pay is still worth keeping as a product note because the merchant-facing surface is specific enough: POS, WooCommerce, API, auto-withdrawals, optional conversion, and a Bolt Card sidecar. The named operator boundary around merchant account issuance, dashboard credentials, employee/device access, withdrawal cadence, conversion policy, and the integrated swap path now lives in swiss-bitcoin-pay. Useful shell, but still not a merchant-stack center.
• What it does:
  • Provides merchant-facing apps for web, iOS, and Android to accept Bitcoin payments in physical businesses
  • Exposes a merchant API that models invoices, payment details, devices, redirects, fiat amounts, Lightning payment requests, and onchain settlement fields
  • Supports non-custodial settlement with free daily auto-withdrawal to a merchant-controlled wallet
  • Offers optional full or partial fiat auto-conversion while still positioning itself as a Bitcoin payment acceptance tool
  • Supports multiple employees and merchant account workflows
  • Provides ecommerce integration through a WooCommerce plugin that uses an API key plus HMAC secret from the Swiss Bitcoin Pay dashboard
  • Extends into Bolt Card payment tooling, including an app that can scan a merchant invoice and tap a Bolt Card to pay peer-to-peer, with an integrated swap service for onchain invoices
• Key claims:
  • The note is worth keeping because the merchant API is real: invoices, states, device metadata, redirects, and Lightning-versus-onchain settlement fields are all explicit.
  • Daily auto-withdrawal to a merchant-controlled wallet is the main operating-model distinction. That matters more than the broad convenience copy.
  • WooCommerce support and HMAC-authenticated API access make this more than a handheld POS app, but not much more.
  • The Bolt Card tooling is interesting extra packaging. It should not be mistaken for the center of the product.
• Whitepaper: No canonical standalone Swiss Bitcoin Pay whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the merchant API docs and the project’s own open-source application and integration repositories; see ../whitepapers/swiss-bitcoin-pay-primary-sources-2026-05-02.md.
• Sources:
  • https://swiss-bitcoin-pay.ch/
  • https://docs.swiss-bitcoin-pay.ch/
  • https://raw.githubusercontent.com/SwissBitcoinPay/app/main/README.md
  • https://raw.githubusercontent.com/SwissBitcoinPay/woocommerce-plugin/main/README.md
  • https://raw.githubusercontent.com/SwissBitcoinPay/boltcard-tools-terminal/main/README.md

Internal linkages

• Company / operator boundary for merchant-account issuance, dashboard and API-secret control, employee/device access, withdrawal cadence, conversion policy, and the integrated swap path: swiss-bitcoin-pay.
• Best upward product reads: btcpay-server and opennode.

Protocol / company boundary

• Keep this note on the product-layer merchant surface: in-person checkout, WooCommerce integration, invoice and redirect behavior, daily auto-withdrawal UX, and the Bolt Card sidecar.
• Use swiss-bitcoin-pay when the sharper question is who issues credentials, controls dashboard access, manages staff/device permissions, defines conversion and settlement policy, and packages the broader merchant workflow shell.
• That split matters because what does the cashier product do? and who controls the operational shell around that cashier product? are related but not identical questions.

Control surface

• At the product layer, power sits in checkout UX, invoice defaults, redirect handling, withdrawal presentation, and how much merchant complexity Swiss Bitcoin Pay hides behind its apps and plugins.

• At the company layer, the stickier dependency sits in account admission, API-key and HMAC-secret issuance, dashboard truth, employee/device management, settlement cadence, and optional fiat-conversion policy.

• Treat the card angle as extra packaging, not a reason to over-rank the note; for the named operator boundary behind that packaging, read swiss-bitcoin-pay.

• Last reviewed: 2026-08-11 UTC