Swiss Bitcoin Pay

• Name: Swiss Bitcoin Pay
• URL: https://swiss-bitcoin-pay.ch/
• Category: bitcoin merchant-payments operator / non-custodial settlement workflow company / Lightning checkout and dashboard operator
• Tags: bitcoin-ecosystem
• Summary: Swiss Bitcoin Pay belongs in companies/ because the meaningful dependency is not only the merchant-facing POS or WooCommerce plugin, but the named operator that issues merchant accounts and dashboard credentials, chooses withdrawal cadence and conversion policy, manages staff and device access, and packages the checkout / API / Bolt Card sidecar into one live workflow shell. The practical leverage sits in who controls merchant onboarding, API-secret issuance, settlement timing defaults, optional fiat conversion, and the dashboard truth businesses actually inherit.
• What it does:
  • Operates the merchant-facing Swiss Bitcoin Pay apps across web, iOS, and Android for in-person Bitcoin acceptance
  • Packages a merchant dashboard and authenticated API surface for invoices, devices, redirects, payment details, and multi-employee account workflows
  • Defines the non-custodial operating model around free daily auto-withdrawal to merchant-controlled wallets rather than leaving settlement cadence entirely to merchant-side software
  • Offers optional total or partial fiat auto-conversion as part of the same company-run acceptance shell
  • Maintains the WooCommerce integration path, which depends on API keys and HMAC secrets issued from the Swiss Bitcoin Pay dashboard
  • Extends the stack with Bolt Card terminal tooling and an integrated swap path for paying onchain invoices, which makes the operator boundary broader than a simple QR point-of-sale app
• Key claims:
  • The main app README says Swiss Bitcoin Pay is an easy-to-use way to accept bitcoin payments in business, works across web/iOS/Android, supports no-KYC signup, uses free daily auto-withdrawal to the merchant’s own wallet, offers total or partial auto fiat conversion, and supports multiple employees
  • The merchant API docs expose invoice objects with status, payment-details arrays, Lightning payment requests, fiat and bitcoin amount fields, redirects, device metadata, and onchain confirmation fields, which is strong evidence that Swiss Bitcoin Pay is operating a real merchant workflow shell rather than only displaying addresses
  • The WooCommerce plugin README says merchants need a Swiss Bitcoin Pay account plus an API key and API secret from the dashboard, which makes merchant admission and credential issuance part of the live control surface
  • The BoltCard Terminal Tools README says users can scan a merchant invoice, tap a Bolt Card to pay peer-to-peer, and even pay onchain invoices through Swiss Bitcoin Pay’s integrated swap service, which shows the branded company shell reaches beyond the main cashier app
  • The source packet consistently makes the operator boundary more important than any hypothetical Swiss Bitcoin Pay protocol: dashboard access, credential issuance, conversion policy, staff permissions, and settlement defaults all resolve to one named company surface
• Whitepaper: No classic standalone company whitepaper is the key artifact here. The clearest primary materials remain the merchant API docs plus Swiss Bitcoin Pay’s own app, WooCommerce plugin, and Bolt Card tool 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

• Product-layer note: swiss-bitcoin-pay.
• Closest adjacent hosted merchant operators: ibex, opennode, and coingate.
• Useful self-hosted contrast when a merchant wants to own more of the stack directly: btcpay-server.

Protocol / company boundary

• swiss-bitcoin-pay remains the product-layer note for the merchant-facing POS, WooCommerce path, Bolt Card sidecar, and the narrow UX a merchant actually uses at checkout.
• This company note isolates the operator boundary: merchant-account issuance, dashboard and API-secret control, employee/device management, daily auto-withdrawal behavior, optional fiat-conversion policy, and the integrated swap path all sit with Swiss Bitcoin Pay as a named organization.
• That split matters because how does the checkout product behave? and who controls the onboarding, credentials, settlement cadence, and policy shell around that product? are related but not identical questions.

Control surface

• Practical leverage sits in merchant admission, API-key and HMAC-secret issuance, dashboard truth, employee/device permissions, invoice and redirect workflow, withdrawal cadence, fiat-conversion availability, and the extra Bolt Card / swap packaging the operator chooses to support.

• The sticky dependency is operational: once a merchant relies on Swiss Bitcoin Pay accounts, dashboard-managed credentials, conversion settings, and webhook-like API workflow, the real trust boundary is the company-run merchant stack rather than Bitcoin or Lightning alone.

• Read Swiss Bitcoin Pay as a merchant-operations company first and a checkout app second.

• Last reviewed: 2026-08-11 UTC