Bitcoin Wiki - User contributions [en]

Bech32 adoption

2023-05-12T16:32:43Z

Btcto: /* Hardware Wallets */

[[Bech32]] is a bitcoin [[address]] format specified by [[BIP 0173]]. It is used for the native segwit version 0 output types, P2WPKH and P2WSH. The upcoming [[Taproot]] softfork will add another output type called Pay to Taproot (P2TR). P2TR outputs and future native segwit versions will be using an updated variant of [[Bech32]], called [[Bech32m]] (specified by [[BIP 0350]]). This page tracks the adoption of [[Bech32]] and [[Bech32m]].

Ideally wallets and services would first support ''sending to'' new addresses. When most wallets and services support sending to the new address type, people are more likely to adopt it for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Armory || {{Yes}} || {{No}} || {{Planned|Planned around activation}} || {{Evaluating|??}} ||
|-
| AQUA || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| bcoin || {{Yes}} || {{Yes}} || {{Yes|Since 2.2.0}} || {{Evaluating|??}} ||
|-
| Bisq || {{Yes}} || {{Yes}} || {{Evaluating|Dependent on BitcoinJ}} || {{Evaluating|??}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Bitcoin Core || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} || Uses P2WPKH as default address since version [https://bitcoin.org/en/release/v0.20.0 0.20.0]. Creating P2TR addresses requires manual import for now.
|-
| Bitcoin Knots || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} ||
|-
| Blockstream Green || {{Yes}} || {{Yes}} || {{Yes|Since Mobile 3.7.6+, Desktop 1.0.4+}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47]
|-
| Breadwallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/BRDapp/comments/9xx1hq/as_of_today_brd_fully_supports_native_segwit/
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} || {{Yes|Since 9.0}} || {{No}} || Tested as of v9.20 (October 2022)
|-
| BlueWallet || {{Yes}} || {{Yes}} || {{Yes|Since 6.2.14}} || {{No}} || Tested as of v6.3.1 (October 2022)
|-
| Breez || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Tested as of v0.12.1-beta (October 2022). Tracking issue: https://github.com/breez/breezmobile/issues/946. As of April 2023, the issue is still open.
|-
| BTC.com || {{No}} || {{No}} || {{No}} || {{No}} || wallet discontinued: https://wallet.btc.com/#/announcement
|-
| [https://github.com/unchained-capital/caravan Caravan] || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| Casa || {{Yes}} || {{No}} || {{Yes}} || {{Planned}} ||
|-
| C-Lightning || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Coinomi || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Tested as of v1.26.0 (October 2022)
|-
| Electrum || {{Yes}} || {{Yes}} || {{Yes|Since 4.1.0}} || {{Planned|Planned: Descriptor-based keypath spends}} || https://github.com/spesmilo/electrum/issues/7544
|-
| Exodus || {{Yes}} || {{Yes}} || {{Yes}} || {{No|Not yet planned}} || https://support.exodus.com/article/1480-bitcoin-faqs-learn-more-about-btc#
|-
| Fully Noded || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Since v0.2.26}} || https://twitter.com/FullyNoded/status/1438652812410298370
|-
| Guarda Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{No|Currently not planned}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
| Iris Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/cryptoquick/status/1585187190627528710
|-
| JoinMarket || {{Yes}} || {{Yes}} || {{Yes|Since v0.9.5}} || {{Evaluating|??}} ||
|-
| LND || {{Yes}} || {{Yes}} || {{Yes|Since v0.15}} || {{Yes|Since v0.15}} || The coming LND v0.15 release will introduce full P2TR support including scriptpath spends, PSBT signing, and a MuSig2 API.
|-
| Muun || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/MuunWallet/status/1459294066135474177
|-
| Mycelium || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Bech32m not supported as of version 3.16.0.13, tested on October 12th, 2022. https://github.com/mycelium-com/wallet-android/issues/645
|-
| Nunchuk || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/nunchuk_io/status/1511365917808103426
|-
| Phoenix || {{Yes}} || {{Yes}} || {{Evaluating|Support in iOS, but not Android}} || {{No}} ||
|-
| Samourai Wallet || {{Yes}} || {{Yes}} || {{Yes|Since v0.99.98}} || {{No|Currently not planned}} || https://twitter.com/SamouraiWallet/status/1415788631491497985?s=20
|-
| Sparrow Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/SparrowWallet/status/1415632270434705408
|-
| Specter Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benkaufman/status/1431293856675508228
|-
| Trust Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{No|Not planned}} || https://github.com/trustwallet/wallet-core/releases/tag/2.6.5, https://twitter.com/catenocrypt/status/1520152930065817601
|-
| Uniblow || {{Yes}} || {{Yes}} || {{Yes | Since v1.2.2}} || {{No|Not yet planned}} || [https://github.com/bitlogik/uniblow/releases/tag/v1.2.2 release1.2.2]
|-
| Wallet of Satoshi || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/walletofsatoshi/status/1459782761472872451
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} || {{Yes | Since Wasabi 2.0}} || {{Planned|Planned: via NBitcoin}} || https://twitter.com/NicolasDorier/status/1413693010236170241 https://mempool.space/testnet/tx/05a23151b6ad114fb71e851147861d6c992a438ad4f62d6f0749bc9f200ef254
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Trezor + Trezor Suite || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || since [https://blog.trezor.io/trezor-suite-and-firmware-updates-december-2021-d1e74c3ea283 Trezor Suite 21.12.2] + Trezor Firmware 1.10.4 (Model One) / 2.4.3 (Model T)
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Ledger Live Desktop 2.35 + Bitcoin App 2.0.0, Ledger Live Mobile support TBD. https://blockstream.info/tx/41d46e6f6e58a325eb6c913aa603f4db313f4a1db0649952f06fe2cd70546451
|-
| KeepKey chrome app || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benma_/status/1504455969631350792
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/_benma_/status/1504458280000761857
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://blog.coinkite.com/edge-firmware/
|-
| Ballet + app || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| SeedSigner || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| Tangem + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockstream Jade + Blockstream Green || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47] available via Blockstream Green mobile apps 3.7.6+ and desktop app 1.0.4+
|-
| Keystone || {{Yes}} || {{Acceptable|Yes, but only with BTC-only firmware}} || {{Planned|Planned for Q1 2022}} || {{Evaluating}} || https://twitter.com/KeystoneWallet/status/1460110906789031938
|}

=== Web Wallets / Wallet Service Providers ===

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Bitcoin Beach Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || https://twitter.com/nicolasburtey/status/1556659398365401088
|-
| [https://coin.space Coin Wallet] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Full native segwit support on v2 platform, no plans to add native segwit support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9, Taproot: https://blog.bitgo.com/taproot-support-for-bitgo-wallets-9ed97f412460
|-
| Bitnob || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/bernard_parah/status/1469962690483400706
|-
| blockchain.com web|| {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/Pellicceama/status/1563171639063629828
|-
| Fireblocks || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned for 2022}} ||
|-
| HolyTransaction || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{No|Currently not planned}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [[AgoraDesk]] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| Binance || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://twitter.com/colemaktypo/status/1460337599499882502
|-
| Bitaroo || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} ||
|-
| BitBargain.co.uk || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || {{No}} || {{No}} || https://twitter.com/Ben_deWaal/status/1460464528181936130
|-
| Bitfinex || {{Yes}} || {{No}} || {{Planned}} || {{No}} || https://twitter.com/paoloardoino/status/1460620727342796800
|-
| BitMEX || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/BitMEXResearch/status/1492152557044654082
|-
| Bitonic || {{Yes}} || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || https://twitter.com/BitcoinenNL/status/1460284373291384833
|-
| Bitpanda || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/christiant5r/status/1461369956252139520
|-
| Bittrex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Bitwage || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitwala || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bottlepay || {{Yes}} || {{Yes}} || {{No}} || {{Evaluating|??}} || https://help.bottlepay.com/en/articles/4909780-what-bitcoin-addresses-do-you-support-for-on-chain-withdrawals, https://twitter.com/Stack_Russel_UK/status/1460330265751044097
|-
| BSDEX || {{Yes}} || {{No}} || {{No}} || {{No}} || https://www.bsdex.de/en/faq/#deposit-and-withdrawal-options-which-cryptocurrency-address-formats-are-supported-in-bsdex
|-
| Bull Bitcoin || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} || https://twitter.com/francispouliot_/status/1464264391155666950
|-
| CardCoins.co || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/CardCoinsCo/status/1452680654030872589
|-
| CEX.IO || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinbase.com || {{Yes}} || {{No}} || {{No|Not a priority currently}} || {{No}} ||
|-
| CoinCorner || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/CoinCorner/status/1461360995746545667
|-
| CoinFalcon || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://coinmate.io Coinmate.io] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://coinmate.io/cz/taproot-revolucni-upgrade-bitcoinu/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinygram || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Flyp.me || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| FTX US Derivatives || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || Formerly LedgerX
|-
| GDax || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Globitex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| HitBTC || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Kraken || {{Yes}} || {{No}} || {{Yes}} || {{No}} || https://blog.kraken.com/post/16740/bitcoin-taproot-address-now-supported-on-kraken/
|-
| Liberalcoins || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Luno || {{Yes}} || {{No}} || {{Planned|Planned}} || {{Evaluating|??}} || https://www.luno.com/blog/en/post/luno-launches-support-for-bech32-addresses
|-
| Okcoin || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/Okcoin/status/1471563103049756672
|-
| Paxful.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://paxful.com/support/en-us/articles/360011766520-Can-I-Withdraw-Bitcoin-from-Paxful-Wallet-to-My-External-Wallet-
|-
| Purse.io || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Poloniex.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| River.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Robinhood.com || {{Yes}} || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || https://robinhood.com/us/en/support/articles/cryptocurrency-wallets/#Supportedaddressformatsforcryptowithdrawals
|-
| Square CashApp || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} || https://cash.app/help/us/en-us/20211114-bitcoin-taproot-upgrade
|-
| StackinSat.com || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/StackinSat_FR/status/1500898826416230401
|-
| Strike || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://twitter.com/BTCBoromir/status/1460373287792521232
|-
| Swan || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/SwanBitcoin/status/1468318386916663298
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| VBTC || {{Yes}} || {{Planned}} || {{Yes}} || {{Planned}} || https://twitter.com/VBTC_Vietnam/status/1460978196816416775
|-
| Walltime || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://walltime.info
|-
| Xapo || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Bitaccess BTM || {{Yes}} || {{Yes}} || {{Planned|Work in progress}} || {{Planned}} || https://twitter.com/DylanSeago/status/1520212294898274305
|-
| GenesisCoin || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu || {{Yes}} || {{Yes|Yes (optional)}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/LamassuBTC/status/1459918440303673349
|}

=== Blockchain Explorers ===

To investigate bech32 capability, you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code> or look up the addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

To verify bech32m readiness, you can look up the mainnet TXID <code>b10c007c60e14f9d087e0291d4d0c7869697c6681d979c6639dbd960792b4d41</code> on which the first output should be addressed as <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqsyjer9e</code>. Note that the superseded bech32 encoding only differs in the last six characters that encode the checksum: <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqs_3wf0qm_</code>.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display Bech32 !! Index Bech32 !! Display Bech32m !! Index Bech32m !! Notes
|-
| bitaps.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp
|-
| Blockbook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://btc1.trezor.io
|-
| blockchain.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.blockchain.com/explorer
|-
| Blockchair || {{Yes}} || {{Yes}} || {{Yes|Ready, but old txns not reindexed yet}} || {{Yes|Ready, but old txns not reindexed yet}} || https://github.com/Blockchair/Blockchair.Support/issues/567#issuecomment-966393097, https://twitter.com/Blockchair/status/1458817396433731585
|-
| Blockcypher || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/. [https://github.com/Blockstream/esplora/issues/323 Issue] for BIP350 support.
|-
| Insight || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| Mempool || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances include https://mempool.space https://mempool.ninja https://mempool.emzy.de https://mempool.bisq.services https://mempool.bitcoin.ninja https://mempool.bitaroo.net/
|-
| OKLink || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.oklink.com
|-
| OXT || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://oxt.me/
|-
| Tradeblock || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Yes, but search field rejects bech32m addresses}} || https://tradeblock.com/bitcoin
|-
| WalletExplorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://walletexplorer.com/
|-
| Bitcoin Explorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitcoinexplorer.org, https://twitter.com/BitcoinExplorer/status/1425148093977309187
|-
| BitRef || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitref.com
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! P2WPKH/P2WSH Invoices !! Bech32 Withdrawal addresses !! P2TR Invoices !! Bech32m Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://btcpayserver.org BTCPay Server] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Supported since 1.3.0}} || https://twitter.com/NicolasDorier/status/1432354289599451136, https://twitter.com/NicolasDorier/status/1457527754350415873
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://confirmo.net CONFIRMO] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Planned}} || Highly customizable Bitcoin and Lightning Network payment gateway and custodial wallets provider. TSS/HD wallets, API, SDK.
|-
| [https://github.com/nickfarrow/SatSale SatSale] || {{Yes}} || n/a || {{Yes}} || n/a || Supports any address format supported by backend Bitcoin Core. Invoices use address format configured as default there. Has no withdrawal functionality in itself, payments are received in Core wallet.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout to Bech32 !! Payout to Bech32m !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} || {{Evaluating|??}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://sbicrypto.com SBICrypto Pool] || {{Yes}} || {{Acceptable|Ready to release at activation}} ||
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} || {{Planned|At activation}} || [https://twitter.com/braiins_systems/status/1432376840484794375 Tweet]
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} || {{Evaluating|??}} ||
|}

=== Libraries ===

{| class="wikitable sortable"
|-
! Name !! Language !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [https://github.com/bitcoin/libbase58 libbase58] || C || {{No}} || n/a || {{No}} || n/a
|-
| [https://github.com/MetacoSA/NBitcoin NBitcoin] || .NET || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://github.com/bcoin-org/bcoin bcoin] || JS || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bcoin-org/bcoin/pull/1038
|-
| [https://github.com/btcsuite btcsuite/btcutil] || Go || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} ||
|-
| [https://github.com/bitcoinjs/bitcoinjs-lib bitcoinjs-lib] || JS || {{Yes}} || {{Yes}} || {{Yes|Yes, since v6.0.0}} || {{Acceptable|Supported but needs manual involvement}} || https://github.com/bitcoinjs/bitcoinjs-lib/issues/1522#issuecomment-887468902, https://twitter.com/junderwood4649/status/1459006392086372355
|-
| [https://bitcoinj.github.io/ bitcoinj] || Java || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bitcoinj/bitcoinj/commit/183986c9801f10f1bf46bd46621e535973d39ef8
|-
| [https://github.com/bitcoin-s/bitcoin-s-core bitcoin-s] || Scala || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned for 2021}} || https://twitter.com/Chris_Stewart_5/status/1459205497463136270
|-
| [https://github.com/rust-bitcoin/rust-bitcoin rust-bitcoin] || Rust || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/RCasatta/status/1423695925252329476
|-
| [https://lightningdevkit.org Lightning Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|Pending BOLT update}} ||
|-
| [https://bitcoindevkit.org Bitcoin Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/bitcoindevkit/bdk/releases/tag/v0.14.0 0.14.0]}} || {{Yes|Yes, since [https://github.com/bitcoindevkit/bdk/releases/tag/v0.19.0 0.19.0]}} || P2TR support is "experimental", see [https://github.com/bitcoindevkit/bdk/pull/593 PR #593]
|-
| [https://github.com/ElementsProject/libwally-core libwally-core] || C || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} || {{Yes|Yes, since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} ||
|-
| [https://github.com/Blockstream/gdk GDK] || C || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 0.0.47]}} || {{Evaluating|??}} ||
|-
| [https://github.com/Simplexum/python-bitcointx python-bitcointx] || Python || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://github.com/Simplexum/python-bitcointx/issues/57
|-
| [https://github.com/dgarage/NBXplorer/ NBXPlorer] || C# || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354822888431619
|-
| [https://github.com/acinq/bitcoin-kmp Kotlin Multiplatform Bitcoin Library] || Kotlin || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} || https://twitter.com/realtbast/status/1458533450919649284
|-
| [https://github.com/libbitcoin Libbitcoin] || C++ || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://github.com/libbitcoin/libbitcoin-system/blob/master/include/bitcoin/system/wallet/addresses/witness_address.hpp#L41
|-
| [https://github.com/chaintope/bitcoinrb Bitcoinrb] || Ruby || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://github.com/chaintope/bitcoinrb/wiki/Taproot
|}


=== References ===

[[Category:Software]]

Bech32 adoption

2022-05-12T16:44:19Z

Btcto: Coldcard added P2TR /* Hardware Wallets */

[[Bech32]] is a bitcoin [[address]] format specified by [[BIP 0173]]. It is used for the native segwit version 0 output types, P2WPKH and P2WSH. The upcoming [[Taproot]] softfork will add another output type called Pay to Taproot (P2TR). P2TR outputs and future native segwit versions will be using an updated variant of [[Bech32]], called [[Bech32m]] (specified by [[BIP 0350]]). This page tracks the adoption of [[Bech32]] and [[Bech32m]].

Ideally wallets and services would first support ''sending to'' new addresses. When most wallets and services support sending to the new address type, people are more likely to adopt it for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Armory || {{Yes}} || {{No}} || {{Planned|Planned around activation}} || {{Evaluating|??}} ||
|-
| AQUA || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| bcoin || {{Yes}} || {{Yes}} || {{Yes|Since 2.2.0}} || {{Evaluating|??}} ||
|-
| Bisq || {{Yes}} || {{Yes}} || {{Evaluating|Dependent on BitcoinJ}} || {{Evaluating|??}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Bitcoin Core || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} || Uses P2WPKH as default address since version [https://bitcoin.org/en/release/v0.20.0 0.20.0]. Creating P2TR addresses requires manual import for now.
|-
| Bitcoin Knots || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} ||
|-
| Blockstream Green || {{Yes}} || {{Yes}} || {{Yes|Mobile 3.7.6+, Desktop 1.0.4+}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47]
|-
| Breadwallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/BRDapp/comments/9xx1hq/as_of_today_brd_fully_supports_native_segwit/
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} || {{Yes|Since 9.0}} || {{Evaluating|??}} ||
|-
| BlueWallet || {{Yes}} || {{Yes}} || {{Yes|Since 6.2.14}} || {{Evaluating|??}} ||
|-
| Breez || {{Yes}} || {{Yes}} || {{No}} || {{Evaluating|??}} ||
|-
| BTC.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/unchained-capital/caravan Caravan] || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| Casa || {{Yes}} || {{No}} || {{Planned}} || {{Planned}} ||
|-
| C-Lightning || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Coinomi || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| Electrum || {{Yes}} || {{Yes}} || {{Yes|Since 4.1.0}} || {{Planned|Descriptor-based keypath spends planned}} || https://github.com/spesmilo/electrum/issues/7544
|-
| Exodus || {{Yes}} || {{Yes}} || {{Yes}} || {{No|Not yet planned}} || https://support.exodus.com/article/1480-bitcoin-faqs-learn-more-about-btc#
|-
| Fully Noded || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Since v0.2.26}} || https://twitter.com/FullyNoded/status/1438652812410298370
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
| JoinMarket || {{Yes}} || {{Yes}} || {{Yes|Since v0.9.5}} || {{Evaluating|??}} ||
|-
| LND || {{Yes}} || {{Yes}} || {{Acceptable|Coming with v0.15}} || {{Acceptable|Coming with v0.15}} || The coming LND v0.15 release will introduce full P2TR support including scriptpath spends, PSBT signing, and a MuSig2 API.
|-
| Muun || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/MuunWallet/status/1459294066135474177
|-
| Mycelium || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Nunchuk || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/nunchuk_io/status/1511365917808103426
|-
| Phoenix || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Samourai Wallet || {{Yes}} || {{Yes}} || {{Yes|Since v0.99.98}} || {{No|Currently not planned}} || https://twitter.com/SamouraiWallet/status/1415788631491497985?s=20
|-
| Sparrow Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/SparrowWallet/status/1415632270434705408
|-
| Specter Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benkaufman/status/1431293856675508228
|-
| Trust Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{No|Not planned}} || https://github.com/trustwallet/wallet-core/releases/tag/2.6.5, https://twitter.com/catenocrypt/status/1520152930065817601
|-
| Uniblow || {{Yes}} || {{Yes}} || {{Yes | Since v1.2.2}} || {{No|Not yet planned}} || [https://github.com/bitlogik/uniblow/releases/tag/v1.2.2 release1.2.2]
|-
| Wallet of Satoshi || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/walletofsatoshi/status/1459782761472872451
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} || {{Yes | Works in Wasabi 2.0 (release soon)}} || {{Planned|Planned: via NBitcoin}} || https://twitter.com/NicolasDorier/status/1413693010236170241 https://mempool.space/testnet/tx/05a23151b6ad114fb71e851147861d6c992a438ad4f62d6f0749bc9f200ef254
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Trezor + Trezor Suite || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || since [https://blog.trezor.io/trezor-suite-and-firmware-updates-december-2021-d1e74c3ea283 Trezor Suite 21.12.2] + Trezor Firmware 1.10.4 (Model One) / 2.4.3 (Model T)
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Ledger Live Desktop 2.35 + Bitcoin App 2.0.0, Ledger Live Mobile support TBD. https://blockstream.info/tx/41d46e6f6e58a325eb6c913aa603f4db313f4a1db0649952f06fe2cd70546451
|-
| KeepKey chrome app || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benma_/status/1504455969631350792
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/_benma_/status/1504458280000761857
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} || Work already in progress
|-
| Ballet + app || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| SeedSigner || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| Tangem + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockstream Jade + Blockstream Green || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47] available via Blockstream Green mobile apps 3.7.6+ and desktop app 1.0.4+
|-
| Keystone || {{Yes}} || {{Acceptable|Yes, but only with BTC-only firmware}} || {{Planned|Planned for Q1 2022}} || {{Evaluating}} || https://twitter.com/KeystoneWallet/status/1460110906789031938
|}

=== Web Wallets / Wallet Service Providers ===

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Full native segwit support on v2 platform, no plans to add native segwit support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9, Taproot: https://blog.bitgo.com/taproot-support-for-bitgo-wallets-9ed97f412460
|-
| Bitnob || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/bernard_parah/status/1469962690483400706
|-
| blockchain.com web|| {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/Pellicceama/status/1436324051803414535
|-
| Fireblocks || {{Yes}} || {{Yes}} || {{Planned|Nov 18, 2021}} || {{Planned|Planned for 2022}} ||
|-
| HolyTransaction || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://1fox.com/?c=en/content/blog&id=12
|-
| [[AgoraDesk]] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| Binance || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://twitter.com/colemaktypo/status/1460337599499882502
|-
| Bitaroo || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} ||
|-
| BitBargain.co.uk || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || {{No}} || {{No}} || https://twitter.com/Ben_deWaal/status/1460464528181936130
|-
| Bitfinex || {{Yes}} || {{No}} || {{Planned}} || {{No}} || https://twitter.com/paoloardoino/status/1460620727342796800
|-
| BitMEX || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/BitMEXResearch/status/1492152557044654082
|-
| Bitonic || {{Yes}} || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || https://twitter.com/BitcoinenNL/status/1460284373291384833
|-
| Bitpanda || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/christiant5r/status/1461369956252139520
|-
| Bittrex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bitso/status/1203784055340314624
|-
| Bottlepay || {{Yes}} || {{Yes}} || {{No}} || {{Evaluating|??}} || https://help.bottlepay.com/en/articles/4909780-what-bitcoin-addresses-do-you-support-for-on-chain-withdrawals, https://twitter.com/Stack_Russel_UK/status/1460330265751044097
|-
| Bitwage || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BSDEX || {{Yes}} || {{No}} || {{Yes}} || {{No}} ||
|-
| CardCoins.co || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/CardCoinsCo/status/1452680654030872589
|-
| CEX.IO || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinbase.com || {{Yes}} || {{No}} || {{No|Currently not a priority}} || {{No}} ||
|-
| CoinFalcon || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| CoinCorner || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/CoinCorner/status/1461360995746545667
|-
| [https://coinmate.io Coinmate.io] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinmate.io/blog/important-coinmate-update/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinygram || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Flyp.me || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| FTX US Derivatives || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || Formerly LedgerX
|-
| GDax || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Globitex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| HitBTC || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Kraken || {{Yes}} || {{No}} || {{No}} || {{No}} || https://twitter.com/murchandamus/status/1460399767830380564

|-
| Liberalcoins || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Luno || {{Yes}} || {{No}} || {{Planned|Planned}} || {{Evaluating|??}} || https://www.luno.com/blog/en/post/luno-launches-support-for-bech32-addresses
|-
| Okcoin || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/Okcoin/status/1471563103049756672
|-
| Paxful.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://paxful.com/support/en-us/articles/360011766520-Can-I-Withdraw-Bitcoin-from-Paxful-Wallet-to-My-External-Wallet-
|-
| Poloniex.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| River.com || {{Yes}} || {{Yes}} || {{Planned|Planned}} || {{Evaluating|??}} ||
|-
| Square CashApp || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} || https://cash.app/help/us/en-us/20211114-bitcoin-taproot-upgrade
|-
| StackinSat.com || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/StackinSat_FR/status/1500898826416230401
|-
| Strike || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://twitter.com/BTCBoromir/status/1460373287792521232
|-
| Swan || {{Yes}} || {{Yes|No deposits}} || {{Yes}} || {{Yes|No deposits}} || https://twitter.com/SwanBitcoin/status/1468318386916663298
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| Walltime || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://walltime.info
|-
| Purse.io || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| VBTC || {{Yes}} || {{Planned}} || {{Yes}} || {{Planned}} || https://twitter.com/VBTC_Vietnam/status/1460978196816416775
|-
| www.bitwala.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Xapo || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Bitaccess BTM || {{Yes}} || {{Yes}} || {{Planned|Work in progress}} || {{Planned}} || https://twitter.com/DylanSeago/status/1520212294898274305
|-
| GenesisCoin || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu || {{Yes}} || {{Yes|Yes (optional)}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/LamassuBTC/status/1459918440303673349
|}

=== Blockchain Explorers ===

To investigate bech32 capability, you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code> or look up the addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

To verify bech32m readiness, you can look up the mainnet TXID <code>b10c007c60e14f9d087e0291d4d0c7869697c6681d979c6639dbd960792b4d41</code> on which the first output should be addressed as <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqsyjer9e</code>. Note that the superseded bech32 encoding only differs in the last six characters that encode the checksum: <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqs_3wf0qm_</code>.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display Bech32 !! Index Bech32 !! Display Bech32m !! Index Bech32m !! Notes
|-
| bitaps.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp
|-
| Blockbook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://btc1.trezor.io
|-
| blockchain.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.blockchain.com/explorer
|-
| Blockchair || {{Yes}} || {{Yes}} || {{Yes|Ready, but old txns not reindexed yet}} || {{Yes|Ready, but old txns not reindexed yet}} || https://github.com/Blockchair/Blockchair.Support/issues/567#issuecomment-966393097, https://twitter.com/Blockchair/status/1458817396433731585
|-
| Blockcypher || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || {{Planned|Planned for 2022Q1}} || {{Planned|Planned for 2022Q1}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/. [https://github.com/Blockstream/esplora/issues/323 Issue] for BIP350 support.
|-
| Insight || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| Mempool || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances include https://mempool.space https://mempool.ninja https://mempool.emzy.de https://mempool.bisq.services https://mempool.bitcoin.ninja https://mempool.bitaroo.net/
|-
| OKLink || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.oklink.com
|-
| OXT || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://oxt.me/
|-
| Tradeblock || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|-
| WalletExplorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://walletexplorer.com/
|-
| Bitcoin Explorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitcoinexplorer.org, https://twitter.com/BitcoinExplorer/status/1425148093977309187
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! P2WPKH/P2WSH Invoices !! Bech32 Withdrawal addresses !! P2TR Invoices !! Bech32m Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://btcpayserver.org BTCPay Server] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Supported since 1.3.0}} || https://twitter.com/NicolasDorier/status/1432354289599451136, https://twitter.com/NicolasDorier/status/1457527754350415873
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://confirmo.net CONFIRMO] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Planned}} || Highly customizable Bitcoin and Lightning Network payment gateway and custodial wallets provider. TSS/HD wallets, API, SDK.
|-
| [https://github.com/nickfarrow/SatSale SatSale] || {{Yes}} || n/a || {{Yes}} || n/a || Supports any address format supported by backend Bitcoin Core. Invoices use address format configured as default there. Has no withdrawal functionality in itself, payments are received in Core wallet.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout to Bech32 !! Payout to Bech32m !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} || {{Evaluating|??}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://sbicrypto.com SBICrypto Pool] || {{Yes}} || {{Acceptable|Ready to release at activation}} ||
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} || {{Planned|At activation}} || [https://twitter.com/braiins_systems/status/1432376840484794375 Tweet]
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} || {{Evaluating|??}} ||
|}

=== Libraries ===

{| class="wikitable sortable"
|-
! Name !! Language !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [https://github.com/bitcoin/libbase58 libbase58] || C || {{No}} || n/a || {{No}} || n/a
|-
| [https://github.com/MetacoSA/NBitcoin NBitcoin] || .NET || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://github.com/bcoin-org/bcoin bcoin] || JS || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bcoin-org/bcoin/pull/1038
|-
| [https://github.com/btcsuite btcsuite/btcutil] || Go || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/btcsuite/btcutil/pull/202
|-
| [https://github.com/bitcoinjs/bitcoinjs-lib bitcoinjs-lib] || JS || {{Yes}} || {{Yes}} || {{Yes|Yes, since v6.0.0}} || {{Acceptable|Supported but needs manual involvement}} || https://github.com/bitcoinjs/bitcoinjs-lib/issues/1522#issuecomment-887468902, https://twitter.com/junderwood4649/status/1459006392086372355
|-
| [https://bitcoinj.github.io/ bitcoinj] || Java || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bitcoinj/bitcoinj/commit/183986c9801f10f1bf46bd46621e535973d39ef8
|-
| [https://github.com/bitcoin-s/bitcoin-s-core bitcoin-s] || Scala || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned for 2021}} || https://twitter.com/Chris_Stewart_5/status/1459205497463136270
|-
| [https://github.com/rust-bitcoin/rust-bitcoin rust-bitcoin] || Rust || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/RCasatta/status/1423695925252329476
|-
| [https://lightningdevkit.org Lightning Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|Pending BOLT update}} ||
|-
| [https://bitcoindevkit.org Bitcoin Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/bitcoindevkit/bdk/releases/tag/v0.14.0 0.14.0]}} || {{Planned|WIP}} || https://docs.rs/bdk https://bitcoindevkit.org/blog/2021/11/first-bdk-taproot-tx-look-at-the-code-part-1/)
|-
| [https://github.com/ElementsProject/libwally-core libwally-core] || C || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} || {{Yes|Yes, since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} ||
|-
| [https://github.com/Blockstream/gdk GDK] || C || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 0.0.47]}} || {{Evaluating|??}} ||
|-
| [https://github.com/Simplexum/python-bitcointx python-bitcointx] || Python || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://github.com/Simplexum/python-bitcointx/issues/57
|-
| [https://github.com/dgarage/NBXplorer/ NBXPlorer] || C# || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354822888431619
|-
| [https://github.com/acinq/bitcoin-kmp Kotlin Multiplatform Bitcoin Library] || Kotlin || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} || https://twitter.com/realtbast/status/1458533450919649284
|-
| [https://github.com/libbitcoin Libbitcoin] || C++ || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/chaintope/bitcoinrb Bitcoinrb] || Ruby || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://github.com/chaintope/bitcoinrb/wiki/Taproot
|}


=== References ===

[[Category:Software]]

Bech32 adoption

2022-05-03T13:45:34Z

Btcto: /* Hardware Wallets */

[[Bech32]] is a bitcoin [[address]] format specified by [[BIP 0173]]. It is used for the native segwit version 0 output types, P2WPKH and P2WSH. The upcoming [[Taproot]] softfork will add another output type called Pay to Taproot (P2TR). P2TR outputs and future native segwit versions will be using an updated variant of [[Bech32]], called [[Bech32m]] (specified by [[BIP 0350]]). This page tracks the adoption of [[Bech32]] and [[Bech32m]].

Ideally wallets and services would first support ''sending to'' new addresses. When most wallets and services support sending to the new address type, people are more likely to adopt it for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Armory || {{Yes}} || {{No}} || {{Planned|Planned around activation}} || {{Evaluating|??}} ||
|-
| AQUA || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| bcoin || {{Yes}} || {{Yes}} || {{Yes|Since 2.2.0}} || {{Evaluating|??}} ||
|-
| Bisq || {{Yes}} || {{Yes}} || {{Evaluating|Dependent on BitcoinJ}} || {{Evaluating|??}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Bitcoin Core || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} || Uses P2WPKH as default address since version [https://bitcoin.org/en/release/v0.20.0 0.20.0]. Creating P2TR addresses requires manual import for now.
|-
| Bitcoin Knots || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} ||
|-
| Blockstream Green || {{Yes}} || {{Yes}} || {{Yes|Mobile 3.7.6+, Desktop 1.0.4+}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47]
|-
| Breadwallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/BRDapp/comments/9xx1hq/as_of_today_brd_fully_supports_native_segwit/
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} || {{Yes|Since 9.0}} || {{Evaluating|??}} ||
|-
| BlueWallet || {{Yes}} || {{Yes}} || {{Yes|Since 6.2.14}} || {{Evaluating|??}} ||
|-
| Breez || {{Yes}} || {{Yes}} || {{No}} || {{Evaluating|??}} ||
|-
| BTC.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/unchained-capital/caravan Caravan] || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| Casa || {{Yes}} || {{No}} || {{Planned}} || {{Planned}} ||
|-
| C-Lightning || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Coinomi || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| Electrum || {{Yes}} || {{Yes}} || {{Yes|Since 4.1.0}} || {{Planned|Descriptor-based keypath spends planned}} || https://github.com/spesmilo/electrum/issues/7544
|-
| Exodus || {{Yes}} || {{Yes}} || {{Yes}} || {{No|Not yet planned}} || https://support.exodus.com/article/1480-bitcoin-faqs-learn-more-about-btc#
|-
| Fully Noded || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Since v0.2.26}} || https://twitter.com/FullyNoded/status/1438652812410298370
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
| JoinMarket || {{Yes}} || {{Yes}} || {{Yes|Since v0.9.5}} || {{Evaluating|??}} ||
|-
| LND || {{Yes}} || {{Yes}} || {{Acceptable|Coming with v0.15}} || {{Acceptable|Coming with v0.15}} || The coming LND v0.15 release will introduce full P2TR support including scriptpath spends, PSBT signing, and a MuSig2 API.
|-
| Muun || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/MuunWallet/status/1459294066135474177
|-
| Mycelium || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Nunchuk || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/nunchuk_io/status/1511365917808103426
|-
| Phoenix || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Samourai Wallet || {{Yes}} || {{Yes}} || {{Yes|Since v0.99.98}} || {{No|Currently not planned}} || https://twitter.com/SamouraiWallet/status/1415788631491497985?s=20
|-
| Sparrow Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/SparrowWallet/status/1415632270434705408
|-
| Specter Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benkaufman/status/1431293856675508228
|-
| Trust Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{No|Not planned}} || https://github.com/trustwallet/wallet-core/releases/tag/2.6.5, https://twitter.com/catenocrypt/status/1520152930065817601
|-
| Uniblow || {{Yes}} || {{Yes}} || {{Yes | Since v1.2.2}} || {{No|Not yet planned}} || [https://github.com/bitlogik/uniblow/releases/tag/v1.2.2 release1.2.2]
|-
| Wallet of Satoshi || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/walletofsatoshi/status/1459782761472872451
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} || {{Yes | Works in Wasabi 2.0 (release soon)}} || {{Planned|Planned: via NBitcoin}} || https://twitter.com/NicolasDorier/status/1413693010236170241 https://mempool.space/testnet/tx/05a23151b6ad114fb71e851147861d6c992a438ad4f62d6f0749bc9f200ef254
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Trezor + Trezor Suite || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || since [https://blog.trezor.io/trezor-suite-and-firmware-updates-december-2021-d1e74c3ea283 Trezor Suite 21.12.2] + Trezor Firmware 1.10.4 (Model One) / 2.4.3 (Model T)
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Ledger Live Desktop 2.35 + Bitcoin App 2.0.0, Ledger Live Mobile support TBD. https://blockstream.info/tx/41d46e6f6e58a325eb6c913aa603f4db313f4a1db0649952f06fe2cd70546451
|-
| KeepKey chrome app || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benma_/status/1504455969631350792
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/_benma_/status/1504458280000761857
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} || {{Planned}} || {{Planned}} || Work already in progress
|-
| Ballet + app || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| SeedSigner || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| Tangem + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockstream Jade + Blockstream Green || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47] available via Blockstream Green mobile apps 3.7.6+ and desktop app 1.0.4+
|-
| Keystone || {{Yes}} || {{Acceptable|Yes, but only with BTC-only firmware}} || {{Planned|Planned for Q1 2022}} || {{Evaluating}} || https://twitter.com/KeystoneWallet/status/1460110906789031938
|}

=== Web Wallets / Wallet Service Providers ===

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Full native segwit support on v2 platform, no plans to add native segwit support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9, Taproot: https://blog.bitgo.com/taproot-support-for-bitgo-wallets-9ed97f412460
|-
| Bitnob || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/bernard_parah/status/1469962690483400706
|-
| blockchain.com web|| {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/Pellicceama/status/1436324051803414535
|-
| Fireblocks || {{Yes}} || {{Yes}} || {{Planned|Nov 18, 2021}} || {{Planned|Planned for 2022}} ||
|-
| HolyTransaction || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://1fox.com/?c=en/content/blog&id=12
|-
| [[AgoraDesk]] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| Binance || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://twitter.com/colemaktypo/status/1460337599499882502
|-
| Bitaroo || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} ||
|-
| BitBargain.co.uk || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || {{No}} || {{No}} || https://twitter.com/Ben_deWaal/status/1460464528181936130
|-
| Bitfinex || {{Yes}} || {{No}} || {{Planned}} || {{No}} || https://twitter.com/paoloardoino/status/1460620727342796800
|-
| BitMEX || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/BitMEXResearch/status/1492152557044654082
|-
| Bitonic || {{Yes}} || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || https://twitter.com/BitcoinenNL/status/1460284373291384833
|-
| Bitpanda || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/christiant5r/status/1461369956252139520
|-
| Bittrex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bitso/status/1203784055340314624
|-
| Bottlepay || {{Yes}} || {{Yes}} || {{No}} || {{Evaluating|??}} || https://help.bottlepay.com/en/articles/4909780-what-bitcoin-addresses-do-you-support-for-on-chain-withdrawals, https://twitter.com/Stack_Russel_UK/status/1460330265751044097
|-
| Bitwage || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BSDEX || {{Yes}} || {{No}} || {{Yes}} || {{No}} ||
|-
| CardCoins.co || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/CardCoinsCo/status/1452680654030872589
|-
| CEX.IO || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinbase.com || {{Yes}} || {{No}} || {{No|Currently not a priority}} || {{No}} ||
|-
| CoinFalcon || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| CoinCorner || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/CoinCorner/status/1461360995746545667
|-
| [https://coinmate.io Coinmate.io] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinmate.io/blog/important-coinmate-update/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinygram || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Flyp.me || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| FTX US Derivatives || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || Formerly LedgerX
|-
| GDax || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Globitex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| HitBTC || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Kraken || {{Yes}} || {{No}} || {{No}} || {{No}} || https://twitter.com/murchandamus/status/1460399767830380564

|-
| Liberalcoins || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Luno || {{Yes}} || {{No}} || {{Planned|Planned}} || {{Evaluating|??}} || https://www.luno.com/blog/en/post/luno-launches-support-for-bech32-addresses
|-
| Okcoin || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/Okcoin/status/1471563103049756672
|-
| Paxful.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://paxful.com/support/en-us/articles/360011766520-Can-I-Withdraw-Bitcoin-from-Paxful-Wallet-to-My-External-Wallet-
|-
| Poloniex.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| River.com || {{Yes}} || {{Yes}} || {{Planned|Planned}} || {{Evaluating|??}} ||
|-
| Square CashApp || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} || https://cash.app/help/us/en-us/20211114-bitcoin-taproot-upgrade
|-
| StackinSat.com || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/StackinSat_FR/status/1500898826416230401
|-
| Strike || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://twitter.com/BTCBoromir/status/1460373287792521232
|-
| Swan || {{Yes}} || {{Yes|No deposits}} || {{Yes}} || {{Yes|No deposits}} || https://twitter.com/SwanBitcoin/status/1468318386916663298
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| Walltime || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://walltime.info
|-
| Purse.io || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| VBTC || {{Yes}} || {{Planned}} || {{Yes}} || {{Planned}} || https://twitter.com/VBTC_Vietnam/status/1460978196816416775
|-
| www.bitwala.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Xapo || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Bitaccess BTM || {{Yes}} || {{Yes}} || {{Planned|Work in progress}} || {{Planned}} || https://twitter.com/DylanSeago/status/1520212294898274305
|-
| GenesisCoin || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu || {{Yes}} || {{Yes|Yes (optional)}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/LamassuBTC/status/1459918440303673349
|}

=== Blockchain Explorers ===

To investigate bech32 capability, you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code> or look up the addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

To verify bech32m readiness, you can look up the mainnet TXID <code>b10c007c60e14f9d087e0291d4d0c7869697c6681d979c6639dbd960792b4d41</code> on which the first output should be addressed as <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqsyjer9e</code>. Note that the superseded bech32 encoding only differs in the last six characters that encode the checksum: <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqs_3wf0qm_</code>.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display Bech32 !! Index Bech32 !! Display Bech32m !! Index Bech32m !! Notes
|-
| bitaps.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp
|-
| Blockbook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://btc1.trezor.io
|-
| blockchain.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.blockchain.com/explorer
|-
| Blockchair || {{Yes}} || {{Yes}} || {{Yes|Ready, but old txns not reindexed yet}} || {{Yes|Ready, but old txns not reindexed yet}} || https://github.com/Blockchair/Blockchair.Support/issues/567#issuecomment-966393097, https://twitter.com/Blockchair/status/1458817396433731585
|-
| Blockcypher || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || {{Planned|Planned for 2022Q1}} || {{Planned|Planned for 2022Q1}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/. [https://github.com/Blockstream/esplora/issues/323 Issue] for BIP350 support.
|-
| Insight || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| Mempool || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances include https://mempool.space https://mempool.ninja https://mempool.emzy.de https://mempool.bisq.services https://mempool.bitcoin.ninja https://mempool.bitaroo.net/
|-
| OKLink || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.oklink.com
|-
| OXT || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://oxt.me/
|-
| Tradeblock || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|-
| WalletExplorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://walletexplorer.com/
|-
| Bitcoin Explorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitcoinexplorer.org, https://twitter.com/BitcoinExplorer/status/1425148093977309187
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! P2WPKH/P2WSH Invoices !! Bech32 Withdrawal addresses !! P2TR Invoices !! Bech32m Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://btcpayserver.org BTCPay Server] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Supported since 1.3.0}} || https://twitter.com/NicolasDorier/status/1432354289599451136, https://twitter.com/NicolasDorier/status/1457527754350415873
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://confirmo.net CONFIRMO] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Planned}} || Highly customizable Bitcoin and Lightning Network payment gateway and custodial wallets provider. TSS/HD wallets, API, SDK.
|-
| [https://github.com/nickfarrow/SatSale SatSale] || {{Yes}} || n/a || {{Yes}} || n/a || Supports any address format supported by backend Bitcoin Core. Invoices use address format configured as default there. Has no withdrawal functionality in itself, payments are received in Core wallet.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout to Bech32 !! Payout to Bech32m !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} || {{Evaluating|??}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://sbicrypto.com SBICrypto Pool] || {{Yes}} || {{Acceptable|Ready to release at activation}} ||
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} || {{Planned|At activation}} || [https://twitter.com/braiins_systems/status/1432376840484794375 Tweet]
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} || {{Evaluating|??}} ||
|}

=== Libraries ===

{| class="wikitable sortable"
|-
! Name !! Language !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [https://github.com/bitcoin/libbase58 libbase58] || C || {{No}} || n/a || {{No}} || n/a
|-
| [https://github.com/MetacoSA/NBitcoin NBitcoin] || .NET || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://github.com/bcoin-org/bcoin bcoin] || JS || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bcoin-org/bcoin/pull/1038
|-
| [https://github.com/btcsuite btcsuite/btcutil] || Go || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/btcsuite/btcutil/pull/202
|-
| [https://github.com/bitcoinjs/bitcoinjs-lib bitcoinjs-lib] || JS || {{Yes}} || {{Yes}} || {{Yes|Yes, since v6.0.0}} || {{Acceptable|Supported but needs manual involvement}} || https://github.com/bitcoinjs/bitcoinjs-lib/issues/1522#issuecomment-887468902, https://twitter.com/junderwood4649/status/1459006392086372355
|-
| [https://bitcoinj.github.io/ bitcoinj] || Java || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bitcoinj/bitcoinj/commit/183986c9801f10f1bf46bd46621e535973d39ef8
|-
| [https://github.com/bitcoin-s/bitcoin-s-core bitcoin-s] || Scala || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned for 2021}} || https://twitter.com/Chris_Stewart_5/status/1459205497463136270
|-
| [https://github.com/rust-bitcoin/rust-bitcoin rust-bitcoin] || Rust || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/RCasatta/status/1423695925252329476
|-
| [https://lightningdevkit.org Lightning Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|Pending BOLT update}} ||
|-
| [https://bitcoindevkit.org Bitcoin Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/bitcoindevkit/bdk/releases/tag/v0.14.0 0.14.0]}} || {{Planned|WIP}} || https://docs.rs/bdk https://bitcoindevkit.org/blog/2021/11/first-bdk-taproot-tx-look-at-the-code-part-1/)
|-
| [https://github.com/ElementsProject/libwally-core libwally-core] || C || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} || {{Yes|Yes, since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} ||
|-
| [https://github.com/Blockstream/gdk GDK] || C || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 0.0.47]}} || {{Evaluating|??}} ||
|-
| [https://github.com/Simplexum/python-bitcointx python-bitcointx] || Python || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://github.com/Simplexum/python-bitcointx/issues/57
|-
| [https://github.com/dgarage/NBXplorer/ NBXPlorer] || C# || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354822888431619
|-
| [https://github.com/acinq/bitcoin-kmp Kotlin Multiplatform Bitcoin Library] || Kotlin || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} || https://twitter.com/realtbast/status/1458533450919649284
|-
| [https://github.com/libbitcoin Libbitcoin] || C++ || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/chaintope/bitcoinrb Bitcoinrb] || Ruby || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://github.com/chaintope/bitcoinrb/wiki/Taproot
|}


=== References ===

[[Category:Software]]

Bech32 adoption

2021-11-23T04:36:31Z

Btcto: /* Hardware Wallets */

[[Bech32]] is a bitcoin [[address]] format specified by [[BIP 0173]]. It is used for the native segwit version 0 output types, P2WPKH and P2WSH. The upcoming [[Taproot]] softfork will add another output type called Pay to Taproot (P2TR). P2TR outputs and future native segwit versions will be using an updated variant of [[Bech32]], called [[Bech32m]] (specified by [[BIP 0350]]). This page tracks the adoption of [[Bech32]] and [[Bech32m]].

Ideally wallets and services would first support ''sending to'' new addresses. When most wallets and services support sending to the new address type, people are more likely to adopt it for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Armory || {{Yes}} || {{No}} || {{Planned|Planned around activation}} || {{Evaluating|??}} ||
|-
| AQUA || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| bcoin || {{Yes}} || {{Yes}} || {{Yes|Since 2.2.0}} || {{Evaluating|??}} ||
|-
| Bisq || {{Yes}} || {{Yes}} || {{Evaluating|Dependent on BitcoinJ}} || {{Evaluating|??}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Bitcoin Core || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} || Uses P2WPKH as default address since version [https://bitcoin.org/en/release/v0.20.0 0.20.0]. Creating P2TR addresses requires manual import for now.
|-
| Bitcoin Knots || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Acceptable|Starting with 22.0}} ||
|-
| Blockstream Green || {{Yes}} || {{Yes}} || {{Yes|Mobile 3.7.6+, Desktop 1.0.4+}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47]
|-
| Breadwallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/BRDapp/comments/9xx1hq/as_of_today_brd_fully_supports_native_segwit/
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} || {{Yes|Since 9.0}} || {{Evaluating|??}} ||
|-
| BlueWallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Breez || {{Yes}} || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} ||
|-
| BTC.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/unchained-capital/caravan Caravan] || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| Casa || {{Yes}} || {{No}} || {{Planned}} || {{Planned}} ||
|-
| C-Lightning || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Coinomi || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| Electrum || {{Yes}} || {{Yes}} || {{Yes|Since 4.1.0}} || {{Planned|Descriptor-based keypath spends planned}} || https://github.com/spesmilo/electrum/issues/7544
|-
| Exodus || {{Yes}} || {{Yes}} || {{Planned|Planned before activation, depends on bitcoinjs}} || {{No|Not yet planned}} ||
|-
| Fully Noded || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Since v0.2.26}} || https://twitter.com/FullyNoded/status/1438652812410298370
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
| JoinMarket || {{Yes}} || {{Yes}} || {{Evaluating|Depends on python-bitcointx}} || {{Evaluating|??}} ||
|-
| LND || {{Yes}} || {{Yes}} || {{Planned|Planned: via btcsuite}} || {{Evaluating|??}} ||
|-
| Muun || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/MuunWallet/status/1459294066135474177
|-
| Mycelium || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Samourai Wallet || {{Yes}} || {{Yes}} || {{Acceptable|Planned by Dec 1}} || {{No|Currently not planned}} || https://twitter.com/SamouraiWallet/status/1415788631491497985?s=20
|-
| Sparrow Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/SparrowWallet/status/1415632270434705408
|-
| Specter Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benkaufman/status/1431293856675508228
|-
| Trust Wallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
| Wallet of Satoshi || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/walletofsatoshi/status/1459782761472872451
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned: via NBitcoin before Activation}} || {{Planned|Planned: via NBitcoin before Activation}} || https://twitter.com/NicolasDorier/status/1413693010236170241
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Trezor + Trezor Suite || {{Yes}} || {{Yes}} || {{Planned|Planned: in December update}} || {{Planned|Planned: in December update}} || https://btc1.trezor.io/tx/350bb4ff380240fee0d2b7e1f7b90e719086de263cd02aedca105aec0c0bccc1
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Ledger Live Desktop 2.35 + Bitcoin App 2.0.0, Ledger Live Mobile support TBD. https://blockstream.info/tx/41d46e6f6e58a325eb6c913aa603f4db313f4a1db0649952f06fe2cd70546451
|-
| KeepKey chrome app || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|Preplanning stage}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} || {{Planned}} || {{Planned}} ||
|-
| Ballet + app || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| SeedSigner || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| Tangem + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockstream Jade + Blockstream Green || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47] available via Blockstream Green mobile apps 3.7.6+ and desktop app 1.0.4+
|-
| Keystone || {{Yes}} || {{Acceptable|Yes, but only with BTC-only firmware}} || {{Planned|Planned for Q1 2022}} || {{Evaluating}} || https://twitter.com/KeystoneWallet/status/1460110906789031938
|}

=== Web Wallets / Wallet Service Providers ===

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Full native segwit support on v2 platform, no plans to add native segwit support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9, Taproot: https://blog.bitgo.com/taproot-support-for-bitgo-wallets-9ed97f412460
|-
| blockchain.com web|| {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/Pellicceama/status/1436324051803414535
|-
| Fireblocks || {{Yes}} || {{Yes}} || {{Planned|Nov 18, 2021}} || {{Planned|Planned for 2022}} ||
|-
| HolyTransaction || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://1fox.com/?c=en/content/blog&id=12
|-
| [[AgoraDesk]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| Binance || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://twitter.com/colemaktypo/status/1460337599499882502
|-
| Bitaroo || {{Yes}} || {{Yes}} || {{Planned}} || {{No}} ||
|-
| BitBargain.co.uk || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || {{No}} || {{No}} || https://twitter.com/Ben_deWaal/status/1460464528181936130
|-
| Bitfinex || {{Yes}} || {{No}} || {{Planned}} || {{No}} || https://twitter.com/paoloardoino/status/1460620727342796800
|-
| BitMEX || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://blog.bitmex.com/introducing-bech32-deposits-on-bitmex-to-deepen-bitcoin-integration-lower-fees/
|-
| Bitonic || {{Yes}} || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || https://twitter.com/BitcoinenNL/status/1460284373291384833
|-
| Bitpanda || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/christiant5r/status/1461369956252139520
|-
| Bittrex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bitso/status/1203784055340314624
|-
| Bottlepay || {{Yes}} || {{Yes}} || {{No}} || {{Evaluating|??}} || https://help.bottlepay.com/en/articles/4909780-what-bitcoin-addresses-do-you-support-for-on-chain-withdrawals, https://twitter.com/Stack_Russel_UK/status/1460330265751044097
|-
| Bitwage || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BSDEX || {{Yes}} || {{No}} || {{Evaluating|??}} || {{No}} ||
|-
| CardCoins.co || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/CardCoinsCo/status/1452680654030872589
|-
| CEX.IO || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinbase.com || {{Yes}} || {{No}} || {{No}} || {{No}} || https://twitter.com/diogorsergio/status/983052769262292992 (Note that Coinbase commerce does not support sending to bech32)
|-
| CoinFalcon || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| CoinCorner || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/CoinCorner/status/1461360995746545667
|-
| [https://coinmate.io Coinmate.io] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinmate.io/blog/important-coinmate-update/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinygram || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Flyp.me || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| FTX US Derivatives || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || Formerly LedgerX
|-
| GDax || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Globitex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| HitBTC || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Kraken || {{Yes}} || {{No}} || {{No}} || {{No}} || https://twitter.com/murchandamus/status/1460399767830380564

|-
| Liberalcoins || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Luno || {{Yes}} || {{No}} || {{Planned|Planned}} || {{Evaluating|??}} || https://www.luno.com/blog/en/post/luno-launches-support-for-bech32-addresses
|-
| Paxful.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://paxful.com/support/en-us/articles/360011766520-Can-I-Withdraw-Bitcoin-from-Paxful-Wallet-to-My-External-Wallet-
|-
| Poloniex.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| River.com || {{Yes}} || {{Yes}} || {{Planned|Planned}} || {{Evaluating|??}} ||
|-
| Square CashApp || {{Yes}} || {{No}} || {{Acceptable|Coming on 2021-12-01}} || {{Evaluating|??}} || https://cash.app/help/us/en-us/20211114-bitcoin-taproot-upgrade
|-
| Strike || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://twitter.com/BTCBoromir/status/1460373287792521232
|-
| Swan || {{Yes}} || {{Yes|No deposits}} || {{Planned}} || {{Evaluating|No deposits}} || https://twitter.com/skwp/status/1460326688685019138
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| Walltime || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://walltime.info
|-
| Purse.io || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| VBTC || {{Yes}} || {{Planned}} || {{Yes}} || {{Planned}} || https://twitter.com/VBTC_Vietnam/status/1460978196816416775
|-
| www.bitwala.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Xapo || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| GenesisCoin || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu Douro || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@LamassuSupport/announcing-crafty-chnemu-v7-3-9522fe2868
|}

=== Blockchain Explorers ===

To investigate bech32 capability, you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code> or look up the addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

To verify bech32m readiness, you can look up the mainnet TXID <code>b10c007c60e14f9d087e0291d4d0c7869697c6681d979c6639dbd960792b4d41</code> on which the first output should be addressed as <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqsyjer9e</code>. Note that the superseded bech32 encoding only differs in the last six characters that encode the checksum: <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqs_3wf0qm_</code>.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display Bech32 !! Index Bech32 !! Display Bech32m !! Index Bech32m !! Notes
|-
| bitaps.com || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp
|-
| Blockbook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://btc1.trezor.io
|-
| blockchain.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.blockchain.com/explorer
|-
| Blockchair || {{Yes}} || {{Yes}} || {{Yes|Ready, but old txns not reindexed yet}} || {{Yes|Ready, but old txns not reindexed yet}} || https://github.com/Blockchair/Blockchair.Support/issues/567#issuecomment-966393097, https://twitter.com/Blockchair/status/1458817396433731585
|-
| Blockcypher || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || {{Planned|Planned for 2020Q1}} || {{Planned|Planned for 2020Q1}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/. [https://github.com/Blockstream/esplora/issues/323 Issue] for BIP350 support.
|-
| Insight || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| Mempool || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances include https://mempool.space https://mempool.ninja https://mempool.emzy.de https://mempool.bisq.services https://mempool.bitcoin.ninja https://mempool.bitaroo.net/
|-
| OKLink || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.oklink.com
|-
| OXT || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://oxt.me/
|-
| Tradeblock || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|-
| WalletExplorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://walletexplorer.com/
|-
| Bitcoin Explorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitcoinexplorer.org, https://twitter.com/BitcoinExplorer/status/1425148093977309187
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! P2WPKH/P2WSH Invoices !! Bech32 Withdrawal addresses !! P2TR Invoices !! Bech32m Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://btcpayserver.org BTCPay Server] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Supported since 1.3.0}} || https://twitter.com/NicolasDorier/status/1432354289599451136, https://twitter.com/NicolasDorier/status/1457527754350415873
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://confirmo.net CONFIRMO] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Planned}} || Highly customizable Bitcoin and Lightning Network payment gateway and custodial wallets provider. TSS/HD wallets, API, SDK.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout to Bech32 !! Payout to Bech32m !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} || {{Evaluating|??}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://sbicrypto.com SBICrypto Pool] || {{Yes}} || {{Acceptable|Ready to release at activation}} ||
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} || {{Planned|At activation}} || [https://twitter.com/braiins_systems/status/1432376840484794375 Tweet]
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} || {{Evaluating|??}} ||
|}

=== Libraries ===

{| class="wikitable sortable"
|-
! Name !! Language !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [https://github.com/bitcoin/libbase58 libbase58] || C || {{No}} || n/a || {{No}} || n/a
|-
| [https://github.com/MetacoSA/NBitcoin NBitcoin] || .NET || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://github.com/bcoin-org/bcoin bcoin] || JS || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bcoin-org/bcoin/pull/1038
|-
| [https://github.com/btcsuite btcsuite/btcutil] || Go || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/btcsuite/btcutil/pull/202
|-
| [https://github.com/bitcoinjs/bitcoinjs-lib bitcoinjs-lib] || JS || {{Yes}} || {{Yes}} || {{Yes|Yes, since v6.0.0}} || {{Acceptable|Supported but needs manual involvement}} || https://github.com/bitcoinjs/bitcoinjs-lib/issues/1522#issuecomment-887468902, https://twitter.com/junderwood4649/status/1459006392086372355
|-
| [https://bitcoinj.github.io/ bitcoinj] || Java || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bitcoinj/bitcoinj/commit/183986c9801f10f1bf46bd46621e535973d39ef8
|-
| [https://github.com/bitcoin-s/bitcoin-s-core bitcoin-s] || Scala || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned for 2021}} || https://twitter.com/Chris_Stewart_5/status/1459205497463136270
|-
| [https://github.com/rust-bitcoin/rust-bitcoin rust-bitcoin] || Rust || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/RCasatta/status/1423695925252329476
|-
| [https://lightningdevkit.org Lightning Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|Pending BOLT update}} ||
|-
| [https://bitcoindevkit.org Bitcoin Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Planned|WIP}} || {{Planned|WIP}} || https://docs.rs/bdk
|-
| [https://github.com/ElementsProject/libwally-core libwally-core] || C || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} || {{Yes|Yes, since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} ||
|-
| [https://github.com/Blockstream/gdk GDK] || C || {{Yes}} || {{Yes}} || {{Yes|Yes, since [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 0.0.47]}} || {{Evaluating|??}} ||
|-
| [https://github.com/Simplexum/python-bitcointx python-bitcointx] || Python || {{Yes}} || {{Yes}} || {{Planned|WIP}} || {{Planned|WIP}} || https://github.com/Simplexum/python-bitcointx/issues/57
|-
| [https://github.com/dgarage/NBXplorer/ NBXPlorer] || C# || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354822888431619
|-
| [https://github.com/acinq/bitcoin-kmp Kotlin Multiplatform Bitcoin Library] || Kotlin || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} || https://twitter.com/realtbast/status/1458533450919649284
|-
| [https://github.com/libbitcoin Libbitcoin] || C++ || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/chaintope/bitcoinrb Bitcoinrb] || Ruby || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://github.com/chaintope/bitcoinrb/wiki/Taproot
|}


=== References ===

[[Category:Software]]

PayJoin adoption

2021-01-17T02:01:33Z

Btcto: /* Hardware Wallets */ HW only sign, no point in receiving column

[[PayJoin]] is a privacy improvement for bitcoin. In the case where a customer pays a merchant, they both together co-operate to create a single bitcoin transaction which mixes both their coins and masks the payment amount.

[[Transaction surveillance company|Transaction surveillance companies]] heavily depend on the [[Common-input-ownership heuristic|common input ownershipassumption]] which is broken by PayJoin transactions. So if those transactions became even a little bit widespread they could massively decrease the reliability of blockchain surveillance. Merchants and customers who adopt PayJoin would find their privacy improved from anyone analyzing the blockchain, for example a surveillance company spy would find it much harder to figure out which addresses and transactions belonged to a particular merchant that was using PayJoin, or who else transacted to them.

PayJoin transactions are indistinguishable from regular bitcoin transactions by design, so it's very hard to get an accurate number for how common they are.

The PayJoin protocol standard most likely to get adoption is [[BIP 0078]].

Like any new feature, PayJoin requires a little bit of time to first set up. But if your business suffers from being spied on (for example you're a p2p exchange or bitcoin casino, and regulated exchanges keep banning your customers) then that cost is well worth it.

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Weak|Non-BIP78}} || Implements a form of PayJoin but not BIP78
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Sending !! Receiving !! Notes
|-
| Wasabi Wallet || {{Yes}} || {{No}} || https://docs.wasabiwallet.io/using-wasabi/PayJoin.html
|-
| JoinMarket || {{Yes}} || {{Yes}} || https://old.reddit.com/r/Bitcoin/comments/idhrak/new_release_of_joinmarket_070_includes_bip78/
|-
| Bluewallet || {{Yes}} || {{Evaluating|??}} || https://old.reddit.com/r/Bitcoin/comments/j6qswf/bluewallet_releases_payjoin_bip78/
|-
| Sparrow Wallet || {{Yes}} || {{Evaluating|??}} || https://github.com/sparrowwallet/sparrow/releases/tag/0.9.7
|-
| Samourai Wallet || {{Weak|Non-BIP78}} || {{Weak|Non-BIP78}} || https://samouraiwallet.com/stowaway
|-
| Bitcoin Core || {{No}} || {{No}} ||
|-
| Bitcoin Knots || {{No}} || {{No}} ||
|-
| Electrum || {{No}} || {{No}} ||
|-
| bcoin || {{No}} || {{No}} ||
|-
| Armory || {{No}} || {{No}} ||
|-
| Blockstream Green || {{No}} || {{No}} ||
|-
| Breadwallet || {{No}} || {{No}} ||
|-
| Coinomi || {{No}} || {{No}} ||
|-
| BTC.com || {{No}} || {{No}} ||
|-
| Casa || {{No}} || {{No}} ||
|-
| Mycelium || {{No}} || {{No}} ||
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{No}} || {{No}} ||
|-
| Trust Wallet || {{No}} || {{No}} ||
|-
| Guarda Wallet || {{No}} || {{No}} ||
|-
|}

=== Hardware Wallets ===

{| class="wikitable sortable"
|-
! Name !! Signing !! Notes
|-
| Coldcard || {{Yes}} || Hardware can sign bip78 payjoins and also http://ckbunker.com/
|-
|}

=== Payment processors ===


{| class="wikitable sortable"
|-
! Name !! Receive !! Notes
|-
| [[BTCPay]] || {{Yes}} || First implementer of BIP78 payjoin for merchants.
|-
| Nurails || {{Evaluating|??}} || https://nurails.com/ "Our infrastructure is open source and community driven using Payjoin security framework".
|}

=== Exchanges ===

P2P exchanges make the most sense as early adoptors of PayJoin. All exchanges are welcome on this list of course.


{| class="wikitable sortable"
|-
! Name !! Send to exchange !! Receive from exchange !! Notes
|-
| [[AgoraDesk]] || {{No}} || {{No}} ||
|-
| Bisq || {{No}} || {{No}} ||
|-
| Hodl Hodl || {{No}} || {{No}} ||
|-
| LocalBitcoins || {{No}} || {{No}} ||
|-
| LocalCoinSwap || {{No}} || {{No}} ||
|-
| LocalCryptos || {{No}} || {{No}} ||
|-
| Paxful.com || {{No}} || {{No}} ||
|-
| Sideshift.ai || {{Yes}} || {{No}} || For "To send" choose "Bitcoin PayJoin"
|}

=== Non-profits ===


{| class="wikitable sortable"
|-
! Name !! Receive !! URL !! Notes
|-
| Human Rights Foundation || {{Yes}} || https://hrf.org/donate-bitcoin/payjoin/ ||
|-
| Waxwing's personal donation page || {{Yes}} || https://joinmarket.me/donations/ ||
|}

=== Casinos ===

Bitcoin casinos are very natural early-adopters of PayJoin. An early protocol specification for it, called bustapay, was created by the owner of a bitcoin casino.


{| class="wikitable sortable"
|-
! Name !! Send to !! Receive !! Notes
|-
| Bustabit || {{No}} || {{No}} ||
|-
|}

=== Stores ===


{| class="wikitable sortable"
|-
! Name !! Receive !! Notes
|-
| The Kratom Syndicate || {{Yes}} || https://thekratomsyndicate.com/blog/buying-kratom-with-payjoin.html
|}

Hardware wallet

2020-08-21T13:57:32Z

Btcto: /* Opendime: Bitcoin Credit Stick */

A '''hardware wallet''' is a special type of [[wallet|bitcoin wallet]] which stores the user's private keys in a secure hardware device.

They have major advantages over standard software wallets:

* private keys are often stored in a protected area of a microcontroller, and cannot be transferred out of the device in plaintext
* immune to computer viruses that steal from software wallets
* can be used securely and interactively, private keys never need to touch potentially-vulnerable software
* much of the time, the software is open source, allowing a user to validate the entire operation of the device

This page is an attempt to summarize all the known developments of hardware wallets that can use Bitcoin as part of their operation.

== Security risks ==

To date there have been no verifiable incidents of Bitcoins stolen from hardware wallets. Hardware wallets are relatively new, but at least for the time being they have maintained a good track record, unlike the numerous incidents of Bitcoin theft from Internet-connected computers.

However, it's important to understand that hardware wallets are a high value target and depend on various assumptions holding true to maintain security. They are not a silver bullet, and there are several realistic ways in which a hardware wallet can fail to protect your Bitcoin. These risks need to be carefully considered when deciding how much trust to place in a hardware wallet, and which hardware wallet to buy.

How a hardware wallet could fail to protect your Bitcoin:

# '''Malware swaps recipient Bitcoin addresses''': a hardware wallet won't protect you from being tricked into sending Bitcoin to the wrong address. For example, malware on a PC could monitor for high value transactions and then swap out the recipient's authentic Bitcoin address for an address controlled by the attacker. When the stakes are high, multi factor (e.g., over the phone) confirmation of a recipient's Bitcoin address is recommended.
# '''Insecure RNG ([https://en.wikipedia.org/wiki/Random_number_generation Random Number Generator])''': hardware wallets rely on the security of an RNG, often embedded in hardware, to generate your wallet's private keys securely. Unfortunately, it is notoriously difficult to verify the true randomness of the RNG. An insecure RNG may create wallet keys that can later be recreated by an attacker, by generating psuedo-randomness that would seem statistically indistinguishable from true randomness yet still be predictable to an advanced attacker. An RNG may become insecure as a result of malicious weakening or an unintentional mistake. This failure mode is common to any wallet generation procedure in which the true randomness of the source of entropy being used can not be verified.
# '''Imperfect implementation''': the security of all computing devices relies on the quality of their implementation. Hardware wallets are no exception. Bugs at the software, firmware or hardware level may allow attackers to break into a hardware wallet and gain unauthorized access to secrets. Even if the design is perfect, proving the security of a hardware or software implementation is a very hard, mostly unsolved problem. To date, no wallet in existence is implemented using provably correct software.
# '''Compromised production process''': even a perfect software and hardware implementation of a hardware wallet would be vulnerable to a corrupt production process that introduces intentional or unintentional holes into the final product. The introduction of hardware backdoors is a [https://www.wired.com/2016/06/demonically-clever-backdoor-hides-inside-computer-chip/ real concern] for high risk financial and military applications.
# '''Compromised shipping process''': a compromised fulfillment process may substitute or modify secure devices for superficially identical but insecure replacements. Government programs that intercept hardware and modify them in route to insert backdoors [https://arstechnica.com/.../photos-of-an-nsa-upgrade-factory-show-cisco-router-getting-implant/ are known to exist].

In summary:

* While not a silver bullet hardware wallets can still be extremely useful, assuming you take care to use a good one: an authentic device manufactured by trustworthy, technically competent security experts with a good reputation (e.g., [[TREZOR]]).

* [[Cold storage]] solutions implemented with open source software and general purpose hardware (e.g., [[BitKey]], Pi Wallet), using a verifiable source of entropy such as physical dice may provide superior security for some use cases (e.g., long term savings).

== Connecting to a full node ==

By default, most hardware wallets instruct the user to connect to the manufacturer's own web interface. The web page cannot steal the user's private keys but can spy on them or trick them into accept fake payments.

Hardware wallets only keep the [[private keys]] safe and create spending transactions; they cannot tell you if you have actually received coins and in what quantity. Bitcoin's security model also requires that [[full node]] wallets are used. If not, somebody could pay you with a transaction of something other than bitcoin. If bitcoin is digital gold then a full node wallet is your own personal goldsmith who checks that the incoming payments are actually real. Also the third-party wallet will see all your [[Address|bitcoin addresses]] so this is very damaging to your privacy.

Most hardware wallets can be connected to [[Electrum]] bitcoin wallet. Electrum can be connected to your own [[Electrum#Electrum Personal Server|full node via a server]].

See also: [[Full node#Why should you use a full node wallet]]

== Commercial hardware wallets (ordered chronologically) ==

=== [[Trezor|Trezor One]] ===
[[File:Trezor-tx.jpg|300px|thumb|left|Confirming the transaction with Trezor]]

[[Trezor]] is a secure bitcoin storage and a transaction signing tool with open source hardware and software. The private keys are generated by the device and never leave it thus they cannot be accessed by a malware.

It uses a deterministic wallet structure which means it can hold an unlimited number of keys ([[BIP 0032]]/[[BIP 0044]]). A recovery seed is generated when the device is initialized. In case Trezor gets lost or stolen, all its contents can be recovered using this seed (private keys, bitcoin balance and transaction history) into a new device or another [[BIP 0039]]/[[BIP 0044]] compatible wallet.

Trezor also introduced a unique way of PIN entering preventing keyloggers from recording it even when entered on a compromised computer. An encryption passphrase can be set on top of the PIN protection. More passphrases can be used for plausible deniability.

Trezor One offers everything needed to protect cryptocurrency funds together with advanced features like [https://wiki.trezor.io/User_manual:Password_Manager Password manager] or [https://wiki.trezor.io/User_manual:Two-factor_Authentication_with_U2F U2F two-factor authorization].

''See also [[Hardware wallet#Trezor Model T|Trezor Model T - next-generation cryptocurrency hardware wallet]]''

[https://shop.trezor.io Trezor E-shop] | [https://wiki.trezor.io Trezor Wiki] | [https://trezor.io Trezor Homepage]

 

=== KeepKey: Your Private Bitcoin Vault ===
[[File:keepkey.jpg|300px|thumb|left|KeepKey showing a bitcoin transaction that needs to be manually approved.]]

KeepKey is a USB device that stores and secures your bitcoins. When you entrust KeepKey with your money, each and every bitcoin transaction you make must be reviewed and approved via it's OLED display and confirmation button.

KeepKey has a unique recovery feature utilizing a rotating cipher to restore private keys with a [[BIP 0039]] recovery seed. This means it is not necessary to store your private keys on KeepKey: the recovery process is secure enough so that KeepKey can be used as a transaction device for paper backups.

[https://www.keepkey.com keepkey.com]

 

=== Opendime: Bitcoin Credit Stick ===

[[file:Opendime.jpeg|300px|thumb|left|Opendime Package]]

The 1st Bitcoin Bearer Bond or just call it a "Bitcoin Stick"

Opendime is a small USB stick that allows you to spend Bitcoin like a dollar bill. Pass it along multiple times.
Connect to any USB to check balance. Unseal anytime to spend online. Trust no one.

It comes in the shape of a mini USB, and [[Opendime-ui.png|setting it up is astonishingly quick and simple]]. You plug OpenDime into a USB port, and it behaves just like a USB drive with a tiny amount of storage. In its folder, is a web page. You open the webpage in your browser, and there’s only one instruction to follow: “Drop a file onto the drive”. Once you do that, the OpenDime automagically generates a unique address for you to receive Bitcoin with.

[https://opendime.com Opendime.com]

* [https://opendime.com/#faq Opendime FAQ]
* You can watch a [https://www.youtube.com/watch?v=9UFF9d3Y1BY video here]
* Read this [https://medium.com/@beautyon_/exquisite-opendime-ad1195a2790e review]
* Multi-language user interface: 中文 • 日本語 • English • Portuguese • Français • Deutsch • Русский
* Works as USB drive with no need for software
* [https://github.com/opendime/electrum Opendime Electrum plugin]
* [https://github.com/opendime/ Opendime source files and key verification]

 

=== Coldcard: Ultra-secure Bitcoin Hardware Wallet ===

[[file:Coldcard.png|300px|thumb|left|Coldcard Front and Back]]

* Coldcard is an easy to use, ultra-secure, open-source and affordable hardware wallet that is easy to back up via an encrypted microSD card. Your private key is stored in a dedicated security chip. MicroPython software design allows you to make changes.
* BIP39 based, which means you can backup the secret words onto paper, and have lots of sub-accounts and unlimited independent payment addresses. Now with BIP39 passphrase support, unlocking up to 5.9e197 additional wallets from the same seed words! It knows how to understand transactions, so you can see what you are approving.
* The first "Partially Signed Bitcoin Transaction Format" - PSBT (BIP 174) native wallet which can be used completely offline for its entire lifecycle. See HWI for Bitcoin Core support!
* True air-gap cold operation via MicroSD sneakernet or standard via USB

[http://www.coldcardwallet.com Coldcardwallet.com]

* [https://coldcardwallet.com/faq Coldcard FAQ]
* [https://coldcardwallet.com/docs Coldcard Docs]
* [https://github.com/coldcard/firmware Coldcard Source Code]

 

=== CoolWallet: The Ultimate Bitcoin Safe ===


[[File:CoolWallet in the box.jpeg|300px|thumb|left|CoolWallet showing Launch App, waiting for user to connect with smartphone via Bluetooth]]

CoolWallet is a credit card sized Bluetooth device that stores and secures your bitcoins and private keys. It fits in your wallet and works wirelessly.

Every Bitcoin transaction must be manually confirmed and approved through its e-paper display and button.

CoolWallet only acknowledges the paired smartphone. Whoever stole the CoolWallet are not able to steal any bitcoins. Using recovery Seed can restore all your bitcoins in case you lost the device.

[https://coolbitx.com coolbitx.com] | [https://github.com/CoolBitX-Technology/coolwallet-ios Source and specifications]

 

=== BlochsTech card: Your user friendly Bitcoin wallet ===


[[file:BlochsTech Bitcoin card hardware wallet.jpg|300px|thumb|left|Graphic printed on front of BlochsTech cards.]]

The BlochsTech open Bitcoin card is an open protocol secure hardware Bitcoin wallet your grandmother could use.
For shops it's faster to accept than slow QR code based wallets and more reliable as it works offline.

Currently it's of course in a novelty phase like Casascius coins (of which thousands were sold),
however in the long run it is fully capable of functionally replacing the VISA system in all nations.

[http://www.BlochsTech.com BlochsTech.com]

 

=== BitLox Bitcoin Hardware Wallet ===
[[file:Bitlox.jpg|300px|thumb|left|BitLox Bitcoin Hardware Wallet]]

BitLox is a metal cased (aluminum or titanium) bitcoin hardware wallet that works with their own web based wallet by USB and apps for iPhone and Android using Bluetooth LE.

At present it is the only bitcoin hardware wallet you can buy that works with iPhone. The device weighs one ounce and is the size of a credit card 4 mm thick.

Bitlox allows you to set up hidden wallets. Unlike other hardware wallets your seed is never displayed on a connected computer or phone but only on the Bitlox. All your wallet, device and transaction PINs are only entered on the BitLox and never on any app.

BitLox has also implemented several advanced security features not available on any other bitcoin hardware wallet.

[http://www.bitlox.com bitlox.com]

 

=== Ledger Nano S - USB Smartcard Hardware Wallet ===
[[File:ledger_wallet_nanos_photo.png|300px|thumb|left|Ledger Wallet Nano S]]

Ledger Nano S is a secure Bitcoin hardware wallet. It connects to any computer through USB and embeds a built-in OLED display to double-check and confirm each transaction with a single tap on its buttons. It is architectured around a Secure Element (ST31 family) and built on top of the BOLOS platform, a powerful and flexible Operating System allowing the secure execution of multiple Open Source applications in full isolation.

Main features:
* cryptographic secrets protected by a secure chip
* open source embedded Bitcoin app
* Confirmation of transactions on the embedded screen
* Built-in 4 digits PIN security lock
* Built-in onboarding (seed generation and recovery)
* BIP39 seed (12/18/24 words), easy backup and restoration
* Multi-apps support: FIDO U2F, GPG, SSH…
* USB connectivity
* Foldable and compact casing

[https://www.ledgerwallet.com/products/12-ledger-nano-s Ledger Nano S product page]

 

=== Secalot ===
[[File:secalot_wallet.png|300px|thumb|left|Secalot]]

Main features:
* Software and hardware are fully open sourced.
* Utilizes a secure microcontroller with a high performance dedicated cryptographic co-processor.
* Integrates with the popular Electrum wallet.
* PIN-code protected.
* Confirm transactions with a touch button press on the device.
* Supports P2PKH, P2SH, and segWit transactions.
* Updatable firmware.
* Extra functionality: OpenPGP smart card, FIDO U2F authenticator, one-time password generator.

Website: [https://www.secalot.com www.secalot.com]

 

=== ELLIPAL - Airgapped hardware wallet with mobile support ===
[[File:Ellipal wallet.png|300px|thumb|left|ELLIPAL]]

ELLIPAL hardware wallet secures keys in cold storage without connections except for LCD screen. It works with companion mobile App via QR code.

Main features:
* Working with mobile phone via QR code
* Internet Isolated Cold Wallet
* Multi-currency, cross-chain
* Supports P2PKH, P2SH, and segWit transactions
* 4" Screen with touch panel
* Support private key import
* PIN-code and gesture pattern protect
* Confirmation of transactions details on the screen
* BIP32/BIP39/BIP44
* iPhone and Android companion App: account management, market info and coin exchange.

Website: [https://www.ellipal.com www.ellipal.com]

 

=== ELLIPAL Titan Cold Wallet ===
[[File:Ellipaltitan.jpg|300px|thumb|left|ELLIPAL Titan]]

ELLIPAL Titan is the upgraded version of the ELLIPAL EC01 hardware wallet. Main upgrades are within the hardware which improves protection against physical attacks while keeping absolute protection against remote attacks. ELLIPAL Titan works with ELLIPAL mobile App to secure and manage your cryptocurrency. Information is transferred between the cold wallet and App via QR code only.

New additional features:
* IP65 metal sealed frame - Light water jet & dust protection
* Disassembly test: [https://www.youtube.com/watch?v=DuPcJudtd2o Video]
* Fully isolated components, can never be connected to another device
* USB port removed - no ports on the device
* Anti-Tamper feature - data automatically deleted upon detection of a breach
* Decentralized Finance functions and coin exchange [https://www.ellipal.com/pages/ellipal-cold-wallet-finance ELLIPAL Finance]
* Verifiable and secure QR code [https://github.com/ELLIPAL?tab=repositories Github]

ELLIPAL Titan Website: [https://www.ellipal.com/pages/ellipal-titan ELLIPAL Titan full info]

 

=== [[Trezor|Trezor Model T]] ===
[[File:Trezor-model-t-photo-front.jpg|300px|thumb|left|Trezor Model T]]

Trezor Model T is the premium version and next-generation cryptocurrency hardware wallet. In addition to the functionalities of Trezor One, it has a colored touchscreen for secure on-device input, modern design, an SD card slot, and some other more advanced features.
For more information see [https://wiki.trezor.io/Trezor_Model_T Trezor Model T] and this [https://trezor.io/#comparison comparison table]

[https://shop.trezor.io Trezor E-shop] | [https://wiki.trezor.io Trezor Wiki] | [https://trezor.io Trezor Homepage]

 

=== D'CENT Biometric Wallet - BLE enabled Hardware Wallet ===
[[File:Dcent wallet photo.png|300px|thumb|left|D'CENT Biometric Wallet]]

D'CENT Biometric Wallet is a secure multi-cryptocurrency hardware wallet. It connects by using Bluetooth or USB to any mobile devices. The wallet is based on multi-IC architecture built on Secure Element(EAL5+) embedded with the SecureOS to provide robust security for the secure execution of multiple wallet applications.

Main features:
* Cryptographic secrets protected by a secure chip
* Large OLED (128x128) display for confirmation of transactions and QR Code for P2P transactions
* Built-in biometric sensor for authentication and also supports the PIN
* Built-in onboarding (seed and key generation in Secure Element)
* BIP39 seed (24 words), easy backup and recovery
* Easy and convenient FW update (no recovery is required after update)
* Bluetooth and USB connectivity

[https://dcentwallet.com D'CENT Wallet Homepage] | [https://medium.com/dcentwallet D'CENT on Medium] | [https://www.youtube.com/channel/UCKnYqiM3g3iaaAKcRZf-kbA D'CENT Youtube]

 

=== Cobo Vault - Air-gapped with QR code and Secure Element ===
[[File:Vault_pro.png|300px|thumb|left|Cobo Vault Essential/Pro/Ultimate]]

Cobo Vault is a completely air-gapped hardware wallet that uses verifiable QR codes to transmit transaction information back and forth with a mobile app. It houses an FIPS 140-2 Secure Element that uses four superimposed physical sources for true random number generation (TRNG). Private keys never leave the Secure Element when transactions are signed. Cobo Vault’s innovative Web Authentication process helps prevent supply chain attacks through double asymmetric encryption implementing our backend HSM server. Cobo Vault’s Secure Element’s BIP 32, 39, and 44 compliant firmware is open source ([https://github.com/CoboVault Github]).

Cobo Vault Essential, Pro & Ultimate Features:
* Air-gapped through auditable QR code data transmissions
* Secure Element physical entropy private key generation and side-channel attack prevention
* Open source Secure Element firmware (industry first)
* Detachable battery (industry first)
* MicroSD firmware upgrading
* 4-inch touchscreen

Cobo Vault Essential and Pro Features:
* AAA battery support to prevent battery failure
* Bitcon-only firmware version compatibility
* Better camera for smoother QR code transactions
* Features we will be adding (see the full product roadmap list in [https://medium.com/cobo-vault/second-gen-hardware-wallets-feature-support-c0aaf00a4216 our launch article])

Cobo Vault Pro Features:
* Fingerprint sensor for device unlock and transaction signing
* Upgraded self-destruct mechanism
* Rechargeable battery

[https://cobo.com/hardware-wallet Cobo Vault Homepage] | [https://medium.com/cobo-vault Cobo Vault on Medium] | [https://shop.cobo.com Cobo Vault Shop]

 

=== BitBox02: Swiss made open source ===
[[File:BitBox02.png.jpg|300px|thumb|left|BitBox02]]

The BitBox02 is a Swiss made, fully open source hardware wallet that enables you to independently generate and securely store your private keys to access and transact crypto assets. It has a dual-chip design and the security architecture has been independently audited.

* Easy backup and restore on microSD card
* OLED display and invisible touch sensors
* Plug in directly to computer/mobile with USB-C
* USB-C to A adapter and extension cable included
* Multiple cryptocurrency support: Bitcoin and [[altcoin]]s.
* U2F function for secure logins
* Bitcoin-only edition available; the limited firmware reduces the attack surface
* BIP-39 compatible
* Bech32 (Native segwit) compatible
* Sleek and minimalist design
* Made in Switzerland

[https://shiftcrypto.ch/bitbox02 BitBox02 product page] | [https://github.com/digitalbitbox Source code]

 

== Not purchasable hardware wallets ==

=== Ledger HW.1 - USB Smartcard Hardware Wallet ===
[[File:Btchip_dongle.jpg|220px|thumb|left|HW.1 inserted in a laptop]]

HW.1 is an implementation of a deterministic ([[BIP 0032]]) Hardware Wallet on a USB smartcard.

It is typically used as a blind secure device for multi signature transactions - holding a set of derived private keys and signing transactions without requiring user confirmation.

Power users can rely on it to confirm all transactions with a second factor scheme turning the dongle into a keyboard typing what the user is supposed to have signed, as a protection against malware.

It is also possible to customize HW.1 for more specific needs, such as creating a prepaid card without revealing the deterministic seed before it is received by the user, or securing bitcoin transactions on a server.

[https://www.ledgerwallet.com/products/3-ledger-hw-1 E-shop] | [https://ledgerhq.github.io/btchip-doc/bitcoin-technical.html Technical Documentation]

 

=== Ledger Nano - USB Smartcard Hardware Wallet ===
[[File:ledger_wallet_photo.jpg|300px|thumb|left|Ledger Wallet USB]]

Ledger Nano protects your Bitcoin data within a smartcard. Its micro-processor certified against all types of attacks (both physical and logical), and has been used in the banking industry for decades (think credit card chips). The device connects to your computer through the USB port and will do all the Bitcoin cryptographic heavy lifting such as signing transactions inside its secure environment. You can therefore use your Bitcoin account with maximum trust, even on an insecure or compromised computer.

The second factor verification of the transaction signature can be done either with a paired smartphone (Android, iOS) or a physical security card.

The Ledger Wallet Chrome application (available also on Chromium) provides an easy onboarding as well as a seamless user experience, and the Nano is compatible with numerous third party software: [[Electrum]], [[Mycelium]], [[GreenAddress]], Greenbits, [[Coinkite]] and Copay.

[https://www.ledgerwallet.com/products/1-ledger-nano Ledger Nano product page] | [https://github.com/LedgerHQ Source and specifications]

 

=== Ledger Unplugged - NFC Smartcard Hardware Wallet ===
[[File:ledger_unplugged_photo.jpg|300px|thumb|left|Ledger Unplugged NFC]]

The Ledger Unplugged is a credit card sized NFC hardware wallet. It embeds an open source Java Card app and is compatible with all NFC enabled Android phones.

The device can be used with Mycelium or Greenbits. In case of loss, you can restore it on any Ledger Wallet (Nano or another one) or all other compatible solutions (BIP 39).

[https://www.ledgerwallet.com/products/6-ledger-unplugged Ledger Unplugged product page] | [https://github.com/LedgerHQ/ledger-javacard Source code]

 

=== BWALLET TREZOR clone ===

[[File:BWALLET_Trezor_Clone.jpeg|200px|thumb|left|Chinese clone of Trezor]]

BWALLET is a clone of Trezor by a Chinese company.
Trezor code is open source and this device operates like a Trezor.
However, this product has been [https://www.reddit.com/r/Bitcoin/comments/2tyier/bwallet_review_by_trezor_developer/ reviewed by Marek aka Slush(Trezor developer)] and he has found some problems which makes this device less than 100% compatible, for example it doesn't work with [http://mytrezor.com myTREZOR.com] website and it does not work with Trezor official firmware.

[http://mybwallet.com MyBWALLET.com] | [http://www.bidingxing.com/en/bwallet Buy BWALLET]

 

=== Pi Wallet - cold storage ===
[[File:Piwallet.jpeg|300px|thumb|left|Pi-Wallet]]

The Pi-Wallet is a small computer with the [[Armory]] bitcoin client.

Transactions are signed offline, then transferred on a USB stick via [https://en.wikipedia.org/wiki/Sneakernet Sneakernet] to an online system for broadcasting.

[https://www.pi-wallet.com/ pi-wallet.com]

 

=== BitcoinCard Megion Technologies-Card based wallet ===
[[File:Bitcoincard-medley-large.jpg|400px|thumb|left|Bitcoin Card]]
[http://www.bitcoincard.org/ Bitcoincard Home Page]

[http://blog.bitinstant.com/blog/2012/6/19/our-discovery-in-vienna-the-bitcoin-card.html Excellent review by evoorhees]

Incorporates a e-paper display, keypad, and radio (custom ISM band protocol.) Unfortunately it is fairly limited in terms of transaction I/O, requiring a radio gateway or another bitcoincard wherever funds need to be transferred.

 

=== BitSafe - allten/someone42's hardware wallet ===
[[File:Bitsafe-wallet-sizecompare.jpg|200px|thumb|left|Bitsafe wallet]]
[https://bitcointalk.org/index.php?topic=152517.0 Final BitSafe announcement]

Signing transactions only, requires USB host software for transactions & USB power. Has a OLED display and Confirm/Cancel buttons. Evolved out of someone42's prototype below, and has significant contributions from someone42 as well.
 

=== Swiss Bank in Your Pocket - Hardware wallet ===
[[File:SBIYP.png|300px|thumb|left|Swiss Bank In Your Pocket]]

The Swiss Bank in Your Pocket is a Windows Desktop Application providing functionality for 5 Bitcoin Wallets and a Bitcoin Vault.

The Bitcoin Vault can only send Bitcoins to the Bitcoin Wallets with in the application. Each Bitcoin wallet can have up to 5 Receive addresses. The intuitive user interface is designed for ease of use. USB security key is required to make any type of transaction. frontend software is installed on windows. Package includes secure USB key, and an additional recovery USB key. So in case of an accident, customer will have an additional backup to access their wallets.

[https://swissbankinyourpocket.com/ swissbankinyourpocket.com]

 

=== BitBox 01 (Digital Bitbox) ===
[[file:Digital-bitbox.png|thumb|left|Digital Bitbox Hardware Wallet]]

* Secure hardware RNG & key storage using [http://www.atmel.com/Images/Atmel-8914-CryptoAuth-ATAES132A-Datasheet.pdf crypto element] with 50 year lifespan and an epoxy-filled case.
* Offline backup and recovery of [[BIP_0032|BIP-32]] seed with a micro SD card rather than [[BIP_0039|BIP-39]] phrase written on paper as in Trezor.
* Native software wallet client and ability to use a mobile phone for 2FA and to verify transaction details.
* Multisig out-of-the-box including Copay support.
* [https://github.com/digitalbitbox Open Source] ([https://github.com/digitalbitbox/mcu#digital-bitbox-firmware firmware], [https://github.com/digitalbitbox/mcu/blob/bf48984fd4a47d9ebf6814f7d01b078964587c7c/src/bootloader.c bootloader], [https://github.com/digitalbitbox/dbb-app desktop client]).
* Full FIDO U2F support (https://en.wikipedia.org/wiki/Universal_2nd_Factor)
* Made in Switzerland (a country with strong privacy laws) by [[Bitcoin Core]] developer Jonas Schnelli.

[https://digitalbitbox.com digitalbitbox.com]

 

=== someone42's original prototype ===
[[File:Someone42-wallet-prototype.jpg|300px|thumb|left|someone42's original prototype]]
[https://bitcointalk.org/index.php?topic=78614.0 Hardware Bitcoin wallet - a minimal Bitcoin wallet for embedded devices]

Signing transactions only, requires USB host software for transactions & USB power. All work is rolled into the above BitSafe wallet currently.
 
=== Other/Defunct but with good discussion: ===
* natman3400's BitClip Jun 2011 [https://bitcointalk.org/index.php?topic=24852.0 https://bitcointalk.org/index.php?topic=24852.0]
:Seems to have gone defunct around Dec 2011. Some good ideas though and seemed to have started on execution.
* jim618 hardware wallet proposal Apr 2012 [https://bitcointalk.org/index.php?topic=77553.0 Dedicated bitcoin devices - dealing with untrusted networks]
:Great discussion and good ideas from jim618. Also linked the following video:
* Prof. Clemens Cap's hardware wallet? (video:)[https://www.youtube.com/watch?v=IavQ-Wc8S1U Clemens Cap about electronic bitcoin wallet at EuroBit]
:Clemens Cap of Uni Rostock explains the Electronic Bitcoin wallet device he's working on. It's based on adafruit microtouch device.
* ripper234's discussion based on Yubikeys Aug 2012 [https://bitcointalk.org/index.php?topic=99492 Having a YUBIKEY as one of the parties for m-of-n signatures]
:The use of Yubikeys. They only support symmetric crypto, so you'd have to trust the host device.
* kalleguld's hardware wallet proposal Oct 2012 [https://bitcointalk.org/index.php?topic=115294.0 Proposal: Hardware wallet (Win 3 BTC)]
* Vaporware: Matthew N Wright's ellet [https://bitcointalk.org/index.php?topic=85931.0 ANN The world's first handheld Bitcoin device, the Ellet!] (Vaporware)

== Smart Card based wallets ==
This type of device requires complete trust in the host device, as there is no method for user input.
See [[Smart card wallet]]

== Related Resources ==
* [https://bitcoinnewsmagazine.com/best-bitcoin-hardware-wallet-2015/ Best Bitcoin Hardware Wallet 2015] - reviews of all bitcoin hardware wallets.
* [http://99bitcoins.com/trezor-vs-ledger-hands-hardware-wallets-review/ TREZOR vs. Ledger] - User reviews and Reddit feedback
* [https://bitcointalk.org/index.php?topic=125383.0 Hardware wallet wire protocol]: slush's Hardware wallet wire protocol discussion
* [https://bitcointalk.org/index.php?topic=19080.msg272348#msg272348 Re: Split private keys]: kjj's Todo List discussion for client protocol requirements
* [https://bitcointalk.org/index.php?topic=134277.0 Hardware Wallet Roundup]
* [https://www.buybitcoinworldwide.com/wallets/ Bitcoin Hardware Wallet Comparison] - information about using Bitcoin hardware wallets for cold storage.
* [https://www.weusecoins.com/bitcoin-ledger-wallet-review/ Ledger Wallet Review]

== See Also ==

* [[Storing bitcoins]]
* [[How to set up a secure offline savings wallet]]
* [[Cold storage]]

[[Category:Security]]
[[Category:Wallets| ]]
[[Category:Hardware]]

Hardware wallet

2019-08-30T21:03:18Z

Btcto: Added Coldcard

A '''hardware wallet''' is a special type of [[wallet|bitcoin wallet]] which stores the user's private keys in a secure hardware device.

They have major advantages over standard software wallets:

* private keys are often stored in a protected area of a microcontroller, and cannot be transferred out of the device in plaintext
* immune to computer viruses that steal from software wallets
* can be used securely and interactively, private keys never need to touch potentially-vulnerable software
* much of the time, the software is open source, allowing a user to validate the entire operation of the device

This page is an attempt to summarize all the known developments of hardware wallets that can use Bitcoin as part of their operation.

== Security risks ==

To date there have been no verifiable incidents of Bitcoins stolen from hardware wallets. Hardware wallets are relatively new, but at least for the time being they have maintained a good track record, unlike the numerous incidents of Bitcoin theft from Internet-connected computers.

However, it's important to understand that hardware wallets are a high value target and depend on various assumptions holding true to maintain security. They are not a silver bullet, and there are several realistic ways in which a hardware wallet can fail to protect your Bitcoin. These risks need to be carefully considered when deciding how much trust to place in a hardware wallet, and which hardware wallet to buy.

How a hardware wallet could fail to protect your Bitcoin:

# '''Malware swaps recipient Bitcoin addresses''': a hardware wallet won't protect you from being tricked into sending Bitcoin to the wrong address. For example, malware on a PC could monitor for high value transactions and then swap out the recipient's authentic Bitcoin address for an address controlled by the attacker. When the stakes are high, multi factor (e.g., over the phone) confirmation of a recipient's Bitcoin address is recommended.
# '''Insecure RNG ([https://en.wikipedia.org/wiki/Random_number_generation Random Number Generator])''': hardware wallets rely on the security of an RNG, often embedded in hardware, to generate your wallet's private keys securely. Unfortunately, it is notoriously difficult to verify the true randomness of the RNG. An insecure RNG may create wallet keys that can later be recreated by an attacker, by generating psuedo-randomness that would seem statistically indistinguishable from true randomness yet still be predictable to an advanced attacker. An RNG may become insecure as a result of malicious weakening or an unintentional mistake. This failure mode is common to any wallet generation procedure in which the true randomness of the source of entropy being used can not be verified.
# '''Imperfect implementation''': the security of all computing devices relies on the quality of their implementation. Hardware wallets are no exception. Bugs at the software, firmware or hardware level may allow attackers to break into a hardware wallet and gain unauthorized access to secrets. Even if the design is perfect, proving the security of a hardware or software implementation is a very hard, mostly unsolved problem. To date, no wallet in existence is implemented using provably correct software.
# '''Compromised production process''': even a perfect software and hardware implementation of a hardware wallet would be vulnerable to a corrupt production process that introduces intentional or unintentional holes into the final product. The introduction of hardware backdoors is a [https://www.wired.com/2016/06/demonically-clever-backdoor-hides-inside-computer-chip/ real concern] for high risk financial and military applications.
# '''Compromised shipping process''': a compromised fulfillment process may substitute or modify secure devices for superficially identical but insecure replacements. Government programs that intercept hardware and modify them in route to insert backdoors [https://arstechnica.com/.../photos-of-an-nsa-upgrade-factory-show-cisco-router-getting-implant/ are known to exist].

In summary:

* While not a silver bullet hardware wallets can still be extremely useful, assuming you take care to use a good one: an authentic device manufactured by trustworthy, technically competent security experts with a good reputation (e.g., [[TREZOR]]).

* [[Cold storage]] solutions implemented with open source software and general purpose hardware (e.g., [[BitKey]], Pi Wallet), using a verifiable source of entropy such as physical dice may provide superior security for some use cases (e.g., long term savings).

== Connecting to a full node ==

By default, most hardware wallets instruct the user to connect to the manufacturer's own web interface. The web page cannot steal the user's private keys but can spy on them or trick them into accept fake payments.

Hardware wallets only keep the [[private keys]] safe and create spending transactions; they cannot tell you if you have actually received coins and in what quantity. Bitcoin's security model also requires that [[full node]] wallets are used. If not, somebody could pay you with a transaction of something other than bitcoin. If bitcoin is digital gold then a full node wallet is your own personal goldsmith who checks that the incoming payments are actually real. Also the third-party wallet will see all your [[Address|bitcoin addresses]] so this is very damaging to your privacy.

Most hardware wallets can be connected to [[Electrum]] bitcoin wallet. Electrum can be connected to your own [[Electrum#Electrum Personal Server|full node via a server]].

See also: [[Full node#Why should you use a full node wallet]]

== Commercial hardware wallets (ordered chronologically) ==

=== [[Trezor|Trezor One]] ===
[[File:Trezor-tx.jpg|300px|thumb|left|Confirming the transaction with Trezor]]

[[Trezor]] is a secure bitcoin storage and a transaction signing tool. The private keys are generated by the device and never leave it thus they cannot be accessed by a malware.

It uses a deterministic wallet structure which means it can hold an unlimited number of keys ([[BIP 0032]]/[[BIP 0044]]). A recovery seed is generated when the device is initialized. In case Trezor gets lost or stolen, all its contents can be recovered using this seed (private keys, bitcoin balance and transaction history) into a new device or another [[BIP 0039]]/[[BIP 0044]] compatible wallet.

Trezor also introduced a unique way of PIN entering preventing keyloggers from recording it even when entered on a compromised computer. An encryption passphrase can be set on top of the PIN protection. More passphrases can be used for plausible deniability.

Trezor One offers everything needed to protect cryptocurrency funds together with advanced features like [https://wiki.trezor.io/User_manual:Password_Manager Password manager] or [https://wiki.trezor.io/User_manual:Two-factor_Authentication_with_U2F U2F two-factor authorization].

''See also [[Hardware wallet#Trezor Model T|Trezor Model T - next-generation cryptocurrency hardware wallet]]''

[https://shop.trezor.io Trezor E-shop] | [https://wiki.trezor.io Trezor Wiki] | [https://trezor.io Trezor Homepage]

 

=== KeepKey: Your Private Bitcoin Vault ===
[[File:keepkey.jpg|300px|thumb|left|KeepKey showing a bitcoin transaction that needs to be manually approved.]]

KeepKey is a USB device that stores and secures your bitcoins. When you entrust KeepKey with your money, each and every bitcoin transaction you make must be reviewed and approved via it's OLED display and confirmation button.

KeepKey has a unique recovery feature utilizing a rotating cipher to restore private keys with a [[BIP 0039]] recovery seed. This means it is not necessary to store your private keys on KeepKey: the recovery process is secure enough so that KeepKey can be used as a transaction device for paper backups.

[https://www.keepkey.com keepkey.com]

 

=== Opendime: Bitcoin Credit Stick ===

[[file:Opendime.jpeg|400px|thumb|left|Opendime Package]]

The 1st Bitcoin Bearer Bond or just call it a "Bitcoin Stick"

Opendime is a small USB stick that allows you to spend Bitcoin like a dollar bill. Pass it along multiple times.
Connect to any USB to check balance. Unseal anytime to spend online. Trust no one.

It comes in the shape of a mini USB, and [[Opendime-ui.png|setting it up is astonishingly quick and simple]]. You plug OpenDime into a USB port, and it behaves just like a USB drive with a tiny amount of storage. In its folder, is a web page. You open the webpage in your browser, and there’s only one instruction to follow: “Drop a file onto the drive”. Once you do that, the OpenDime automagically generates a unique address for you to receive Bitcoin with.

[http://www.opendime.com Opendime.com]

* [https://opendime.com/#faq Opendime FAQ]
* You can watch a [https://www.youtube.com/watch?v=9UFF9d3Y1BY video here]
* Read this [https://medium.com/@beautyon_/exquisite-opendime-ad1195a2790e review]
* Multi-language user interface: 中文 • 日本語 • English • Portuguese • Français • Deutsch • Русский
* Works as USB drive with no need for software
* [https://github.com/opendime/electrum Opendime Electrum plugin]
* [https://github.com/opendime/ Opendime source files and key verification]

 

=== Coldcard: Ultra-secure Bitcoin Hardware Wallet ===

[[file:Coldcard.png|524px|thumb|left|Coldcard Front and Back]]

* Coldcard is an easy to use, ultra-secure, open-source and affordable hardware wallet that is easy to back up via an encrypted microSD card. Your private key is stored in a dedicated security chip. MicroPython software design allows you to make changes.
* BIP39 based, which means you can backup the secret words onto paper, and have lots of sub-accounts and unlimited independent payment addresses. Now with BIP39 passphrase support, unlocking up to 5.9e197 additional wallets from the same seed words! It knows how to understand transactions, so you can see what you are approving.
* The first "Partially Signed Bitcoin Transaction Format" - PSBT (BIP 174) native wallet which can be used completely offline for its entire lifecycle. See HWI for Bitcoin Core support!
* True air-gap cold operation via MicroSD sneakernet or standard via USB

[http://www.coldcardwallet.com Coldcardwallet.com]

* [https://coldcardwallet.com/faq Coldcard FAQ]
* [https://coldcardwallet.com/docs Coldcard Docs]
* [https://github.com/coldcard/firmware Coldcard Source Code]

 

=== CoolWallet: The Ultimate Bitcoin Safe ===


[[File:CoolWallet in the box.jpeg|300px|thumb|left|CoolWallet showing Launch App, waiting for user to connect with smartphone via Bluetooth]]

CoolWallet is a credit card sized Bluetooth device that stores and secures your bitcoins and private keys. It fits in your wallet and works wirelessly.

Every Bitcoin transaction must be manually confirmed and approved through its e-paper display and button.

CoolWallet only acknowledges the paired smartphone. Whoever stole the CoolWallet are not able to steal any bitcoins. Using recovery Seed can restore all your bitcoins in case you lost the device.

[https://coolbitx.com coolbitx.com] | [https://github.com/CoolBitX-Technology/coolwallet-ios Source and specifications]

 

=== BlochsTech card: Your user friendly Bitcoin wallet ===


[[file:BlochsTech Bitcoin card hardware wallet.jpg|300px|thumb|left|Graphic printed on front of BlochsTech cards.]]

The BlochsTech open Bitcoin card is an open protocol secure hardware Bitcoin wallet your grandmother could use.
For shops it's faster to accept than slow QR code based wallets and more reliable as it works offline.

Currently it's of course in a novelty phase like Casascius coins (of which thousands were sold),
however in the long run it is fully capable of functionally replacing the VISA system in all nations.

[http://www.BlochsTech.com BlochsTech.com]

 

=== BitLox Bitcoin Hardware Wallet ===
[[file:Bitlox.jpg|300px|thumb|left|BitLox Bitcoin Hardware Wallet]]

BitLox is a metal cased (aluminum or titanium) bitcoin hardware wallet that works with their own web based wallet by USB and apps for iPhone and Android using Bluetooth LE.

At present it is the only bitcoin hardware wallet you can buy that works with iPhone. The device weighs one ounce and is the size of a credit card 4 mm thick.

Bitlox allows you to set up hidden wallets. Unlike other hardware wallets your seed is never displayed on a connected computer or phone but only on the Bitlox. All your wallet, device and transaction PINs are only entered on the BitLox and never on any app.

BitLox has also implemented several advanced security features not available on any other bitcoin hardware wallet.

[http://www.bitlox.com bitlox.com]

 

=== Digital Bitbox ===
[[file:Digital-bitbox.png|thumb|left|Digital Bitbox Hardware Wallet]]

* Secure hardware RNG & key storage using [http://www.atmel.com/Images/Atmel-8914-CryptoAuth-ATAES132A-Datasheet.pdf crypto element] with 50 year lifespan and an epoxy-filled case.
* Offline backup and recovery of [[BIP_0032|BIP-32]] seed with a micro SD card rather than [[BIP_0039|BIP-39]] phrase written on paper as in Trezor.
* Native software wallet client and ability to use a mobile phone for 2FA and to verify transaction details.
* Multisig out-of-the-box including Copay support.
* [https://github.com/digitalbitbox Open Source] ([https://github.com/digitalbitbox/mcu#digital-bitbox-firmware firmware], [https://github.com/digitalbitbox/mcu/blob/bf48984fd4a47d9ebf6814f7d01b078964587c7c/src/bootloader.c bootloader], [https://github.com/digitalbitbox/dbb-app desktop client]).
* Full FIDO U2F support (https://en.wikipedia.org/wiki/Universal_2nd_Factor)
* Made in Switzerland (a country with strong privacy laws) by [[Bitcoin Core]] developer Jonas Schnelli.

[https://digitalbitbox.com digitalbitbox.com]

 

=== Ledger Nano S - USB Smartcard Hardware Wallet ===
[[File:ledger_wallet_nanos_photo.png|300px|thumb|left|Ledger Wallet Nano S]]

Ledger Nano S is a secure Bitcoin hardware wallet. It connects to any computer through USB and embeds a built-in OLED display to double-check and confirm each transaction with a single tap on its buttons. It is architectured around a Secure Element (ST31 family) and built on top of the BOLOS platform, a powerful and flexible Operating System allowing the secure execution of multiple Open Source applications in full isolation.

Main features:
* cryptographic secrets protected by a secure chip
* open source embedded Bitcoin app
* Confirmation of transactions on the embedded screen
* Built-in 4 digits PIN security lock
* Built-in onboarding (seed generation and recovery)
* BIP39 seed (12/18/24 words), easy backup and restoration
* Multi-apps support: FIDO U2F, GPG, SSH…
* USB connectivity
* Foldable and compact casing

[https://www.ledgerwallet.com/products/12-ledger-nano-s Ledger Nano S product page]

 

=== Secalot ===
[[File:secalot_wallet.png|300px|thumb|left|Secalot]]

Main features:
* Software and hardware are fully open sourced.
* Utilizes a secure microcontroller with a high performance dedicated cryptographic co-processor.
* Integrates with the popular Electrum wallet.
* PIN-code protected.
* Confirm transactions with a touch button press on the device.
* Supports P2PKH, P2SH, and segWit transactions.
* Updatable firmware.
* Extra functionality: OpenPGP smart card, FIDO U2F authenticator, one-time password generator.

Website: [https://www.secalot.com www.secalot.com]

 

=== ELLIPAL ===
[[File:Ellipal wallet.png|300px|thumb|left|ELLIPAL]]

ELLIPAL hardware wallet secures keys in cold storage without connections except LCD screen. It works with companion mobile App via QR code.

Main features:
* Working with mobile phone via QR code
* Internet Isolated Cold Wallet
* Multi-currency, cross-chain
* Supports P2PKH, P2SH, and segWit transactions
* 4" Screen with touch panel
* Support private key import
* PIN-code and gesture pattern protect
* Confirmation of transactions details on screen
* BIP32/BIP39/BIP44
* iPhone and Android companion App: account management, market info and coin exchange.

Website: [https://www.ellipal.com www.ellipal.com]

 

=== [[Trezor|Trezor Model T]] ===
[[File:Trezor-model-t-photo-front.jpg|300px|thumb|left|Trezor Model T]]

Trezor Model T is the premium version and next-generation cryptocurrency hardware wallet. In addition to the functionalities of Trezor One, it has a colored touchscreen for secure on-device input, modern design, an SD card slot, and some other more advanced features.
For more information see [https://wiki.trezor.io/Trezor_Model_T Trezor Model T] and this [https://trezor.io/#comparison comparison table]

[https://shop.trezor.io Trezor E-shop] | [https://wiki.trezor.io Trezor Wiki] | [https://trezor.io Trezor Homepage]

 

== Not purchasable hardware wallets ==

=== Ledger HW.1 - USB Smartcard Hardware Wallet ===
[[File:Btchip_dongle.jpg|220px|thumb|left|HW.1 inserted in a laptop]]

HW.1 is an implementation of a deterministic ([[BIP 0032]]) Hardware Wallet on a USB smartcard.

It is typically used as a blind secure device for multi signature transactions - holding a set of derived private keys and signing transactions without requiring user confirmation.

Power users can rely on it to confirm all transactions with a second factor scheme turning the dongle into a keyboard typing what the user is supposed to have signed, as a protection against malware.

It is also possible to customize HW.1 for more specific needs, such as creating a prepaid card without revealing the deterministic seed before it is received by the user, or securing bitcoin transactions on a server.

[https://www.ledgerwallet.com/products/3-ledger-hw-1 E-shop] | [https://ledgerhq.github.io/btchip-doc/bitcoin-technical.html Technical Documentation]

 

=== Ledger Nano - USB Smartcard Hardware Wallet ===
[[File:ledger_wallet_photo.jpg|300px|thumb|left|Ledger Wallet USB]]

Ledger Nano protects your Bitcoin data within a smartcard. Its micro-processor certified against all types of attacks (both physical and logical), and has been used in the banking industry for decades (think credit card chips). The device connects to your computer through the USB port and will do all the Bitcoin cryptographic heavy lifting such as signing transactions inside its secure environment. You can therefore use your Bitcoin account with maximum trust, even on an insecure or compromised computer.

The second factor verification of the transaction signature can be done either with a paired smartphone (Android, iOS) or a physical security card.

The Ledger Wallet Chrome application (available also on Chromium) provides an easy onboarding as well as a seamless user experience, and the Nano is compatible with numerous third party software: [[Electrum]], [[Mycelium]], [[GreenAddress]], Greenbits, [[Coinkite]] and Copay.

[https://www.ledgerwallet.com/products/1-ledger-nano Ledger Nano product page] | [https://github.com/LedgerHQ Source and specifications]

 

=== Ledger Unplugged - NFC Smartcard Hardware Wallet ===
[[File:ledger_unplugged_photo.jpg|300px|thumb|left|Ledger Unplugged NFC]]

The Ledger Unplugged is a credit card sized NFC hardware wallet. It embeds an open source Java Card app and is compatible with all NFC enabled Android phones.

The device can be used with Mycelium or Greenbits. In case of loss, you can restore it on any Ledger Wallet (Nano or another one) or all other compatible solutions (BIP 39).

[https://www.ledgerwallet.com/products/6-ledger-unplugged Ledger Unplugged product page] | [https://github.com/LedgerHQ/ledger-javacard Source code]

 

=== BWALLET TREZOR clone ===

[[File:BWALLET_Trezor_Clone.jpeg|200px|thumb|left|Chinese clone of Trezor]]

BWALLET is a clone of Trezor by a Chinese company.
Trezor code is open source and this device operates like a Trezor.
However, this product has been [https://www.reddit.com/r/Bitcoin/comments/2tyier/bwallet_review_by_trezor_developer/ reviewed by Marek aka Slush(Trezor developer)] and he has found some problems which makes this device less than 100% compatible, for example it doesn't work with [http://mytrezor.com myTREZOR.com] website and it does not work with Trezor official firmware.

[http://mybwallet.com MyBWALLET.com] | [http://www.bidingxing.com/en/bwallet Buy BWALLET]

 

=== Pi Wallet - cold storage ===
[[File:Piwallet.jpeg|300px|thumb|left|Pi-Wallet]]

The Pi-Wallet is a small computer with the [[Armory]] bitcoin client.

Transactions are signed offline, then transferred on a USB stick via [https://en.wikipedia.org/wiki/Sneakernet Sneakernet] to an online system for broadcasting.

[https://www.pi-wallet.com/ pi-wallet.com]

 

=== BitcoinCard Megion Technologies-Card based wallet ===
[[File:Bitcoincard-medley-large.jpg|400px|thumb|left|Bitcoin Card]]
[http://www.bitcoincard.org/ Bitcoincard Home Page]

[http://blog.bitinstant.com/blog/2012/6/19/our-discovery-in-vienna-the-bitcoin-card.html Excellent review by evoorhees]

Incorporates a e-paper display, keypad, and radio (custom ISM band protocol.) Unfortunately it is fairly limited in terms of transaction I/O, requiring a radio gateway or another bitcoincard wherever funds need to be transferred.

 

=== BitSafe - allten/someone42's hardware wallet ===
[[File:Bitsafe-wallet-sizecompare.jpg|200px|thumb|left|Bitsafe wallet]]
[https://bitcointalk.org/index.php?topic=152517.0 Final BitSafe announcement]

Signing transactions only, requires USB host software for transactions & USB power. Has a OLED display and Confirm/Cancel buttons. Evolved out of someone42's prototype below, and has significant contributions from someone42 as well.
 

=== Swiss Bank in Your Pocket - Hardware wallet ===
[[File:SBIYP.png|300px|thumb|left|Swiss Bank In Your Pocket]]

The Swiss Bank in Your Pocket is a Windows Desktop Application providing functionality for 5 Bitcoin Wallets and a Bitcoin Vault.

The Bitcoin Vault can only send Bitcoins to the Bitcoin Wallets with in the application. Each Bitcoin wallet can have up to 5 Receive addresses. The intuitive user interface is designed for ease of use. USB security key is required to make any type of transaction. frontend software is installed on windows. Package includes secure USB key, and an additional recovery USB key. So in case of an accident, customer will have an additional backup to access their wallets.

[https://swissbankinyourpocket.com/ swissbankinyourpocket.com]

 

=== someone42's original prototype ===
[[File:Someone42-wallet-prototype.jpg|300px|thumb|left|someone42's original prototype]]
[https://bitcointalk.org/index.php?topic=78614.0 Hardware Bitcoin wallet - a minimal Bitcoin wallet for embedded devices]

Signing transactions only, requires USB host software for transactions & USB power. All work is rolled into the above BitSafe wallet currently.
 
=== Other/Defunct but with good discussion: ===
* natman3400's BitClip Jun 2011 [https://bitcointalk.org/index.php?topic=24852.0 https://bitcointalk.org/index.php?topic=24852.0]
:Seems to have gone defunct around Dec 2011. Some good ideas though and seemed to have started on execution.
* jim618 hardware wallet proposal Apr 2012 [https://bitcointalk.org/index.php?topic=77553.0 Dedicated bitcoin devices - dealing with untrusted networks]
:Great discussion and good ideas from jim618. Also linked the following video:
* Prof. Clemens Cap's hardware wallet? (video:)[https://www.youtube.com/watch?v=IavQ-Wc8S1U Clemens Cap about electronic bitcoin wallet at EuroBit]
:Clemens Cap of Uni Rostock explains the Electronic Bitcoin wallet device he's working on. It's based on adafruit microtouch device.
* ripper234's discussion based on Yubikeys Aug 2012 [https://bitcointalk.org/index.php?topic=99492 Having a YUBIKEY as one of the parties for m-of-n signatures]
:The use of Yubikeys. They only support symmetric crypto, so you'd have to trust the host device.
* kalleguld's hardware wallet proposal Oct 2012 [https://bitcointalk.org/index.php?topic=115294.0 Proposal: Hardware wallet (Win 3 BTC)]
* Vaporware: Matthew N Wright's ellet [https://bitcointalk.org/index.php?topic=85931.0 ANN The world's first handheld Bitcoin device, the Ellet!] (Vaporware)

== Smart Card based wallets ==
This type of device requires complete trust in the host device, as there is no method for user input.
See [[Smart card wallet]]

== Related Resources ==
* [https://bitcoinnewsmagazine.com/best-bitcoin-hardware-wallet-2015/ Best Bitcoin Hardware Wallet 2015] - reviews of all bitcoin hardware wallets.
* [http://99bitcoins.com/trezor-vs-ledger-hands-hardware-wallets-review/ TREZOR vs. Ledger] - User reviews and Reddit feedback
* [https://bitcointalk.org/index.php?topic=125383.0 Hardware wallet wire protocol]: slush's Hardware wallet wire protocol discussion
* [https://bitcointalk.org/index.php?topic=19080.msg272348#msg272348 Re: Split private keys]: kjj's Todo List discussion for client protocol requirements
* [https://bitcointalk.org/index.php?topic=134277.0 Hardware Wallet Roundup]
* [https://www.buybitcoinworldwide.com/wallets/ Bitcoin Hardware Wallet Comparison] - information about using Bitcoin hardware wallets for cold storage.
* [https://www.weusecoins.com/bitcoin-ledger-wallet-review/ Ledger Wallet Review]

== See Also ==

* [[Storing bitcoins]]
* [[How to set up a secure offline savings wallet]]
* [[Cold storage]]

[[Category:Security]]
[[Category:Wallets| ]]
[[Category:Hardware]]

File:Coldcard.png

2019-08-30T20:55:25Z

Btcto:

Bitcore

2017-08-18T14:16:49Z

Btcto: /* External links */

'''bitcore''' is a complete, native interface to the Bitcoin network, and provides the core functionality needed to develop apps for bitcoin. It is open-source and developed by [[BitPay]].

==External links==
http://bitcore.io

Alternative fork running Bitcoin Core https://github.com/satoshilabs/bitcore-node

Hardware wallet

2016-09-12T16:35:21Z

Btcto: /* Purchasable hardware wallets (ordered chronologically) */

File:Opendime.jpeg

2016-09-12T16:01:17Z

Btcto: Btcto uploaded a new version of File:Opendime.jpeg

Wallet

2016-09-12T15:22:50Z

Btcto:

A Bitcoin '''wallet''' is a collection of private keys but may also refer to [[Clients|client software]] used to manage those keys and to make transactions on the Bitcoin network.

This page covers various wallet formats in use.

=== [[Bitcoin Core]] ===

The original Bitcoin client stores private key information in a file named '''wallet.dat''' following the so called [https://bitcointalk.org/index.php?topic=4448.0 "bitkeys"] format.

It contains:

* keypairs for each of your [[address|addresses]]
* transactions done from/to your addresses
* user preferences
* default key
* reserve keys
* [[Accounts_explained|accounts]]
* a version number
* [[Key pool]]
* Since 0.3.21: information about the current best chain, to be able to rescan automatically when restoring from a backup.

The wallet.dat file is located in the [[data directory|Bitcoin data directory]].

It is intended that a wallet file be used on only one installation of Bitcoin at a time. Attempting to clone a wallet file for use on multiple computers will result in "weird behavior"<ref>[http://forum.bitcoin.org/index.php?topic=5324.msg77896#msg77896 Multiple instance of bitcoin with the same wallet]</ref>.

The format of this file is Berkeley DB. Tools that can manipulate wallet files include [[pywallet]].

=== [[Armory]] ===

The Armory client uses a custom [[Deterministic wallet]] format [https://www.bitcoinarmory.com/wallet-format/ described here] and runs on top of [[Bitcoin Core]].

=== [[Blockchain.info#Wallet|Blockchain.info]] ===

Blockchain.info offers a [[Browser-based_wallet#Hybrid_e-wallets|hybrid eWallet]] called "My Wallet". It use a plain text [https://blockchain.info/wallet/wallet-format JSON wallet format]. Private keys Keys are stored in base58.

=== [[Denarium.com]] ===

Denarium is Physical Bitcoin coin manufacturer. Denarium produces easy, handy and secure wallets in a coin form. The private key is stored under a security seal without password protection. Denarium also offers a trustless multisignature coins, which eliminates the need to trust the manufacturer.

=== [[Ledger Wallet]] ===

Ledger Wallet manufactures various hardware wallets.

=== [[Multibit]] ===

Multibit HD (the current version) uses a [[BIP 0032]] (type 2) [[Deterministic wallet]] with the [https://www.multibit.org/en/help/hd0.1/files.html format described here]. The "Classic" version used the bitcoinj [https://github.com/google/protobuf protobuf] wallet file.

=== [[Blocktrail]] ===

Blocktrail offers a [[BIP 0032]] (type 2) [[Deterministic wallet]] and for added security also implements [[Multisignature]] wallet technology.

=== [[TREZOR]] ===

TREZOR is an isolated hardware environment for offline transaction signing and using a small display you can visually verify the transaction contents.

=== [https://opendime.com Opendime] ===

Opendime is a small USB stick that allows you to spend Bitcoin like a dollar bill. Pass it along multiple times. Connect to any USB to check balance. Unseal anytime to spend online. Trust no one.

==See Also==

* [[Transaction fees]]
* [[Securing your wallet]]
* [[EWallet]]
* [[Deterministic Wallet]]
* [https://bitcoin.org/en/choose-your-wallet Choose your wallet]

==References==
<references />

Hardware wallet

2016-09-12T15:21:04Z

Btcto: /* Added Opendime*/

File:Opendime-ui.png

2016-09-12T15:18:43Z

Btcto: Opendime UI

Opendime UI

File:Opendime.jpeg

2016-09-12T15:08:38Z

Btcto:

How to accept Bitcoin, for small businesses

2015-07-06T15:07:05Z

Btcto: /* Utilize a merchant solution */ added picture

{{merge|Merchant Howto}}

This guide is intended for small business owners who wish to help promote Bitcoin by accepting it as payment for goods and services. It's written with the assumption that you operate a regular business that sells goods or services for regular national currency such as dollars, and that you wish to accept Bitcoin as another legal way to pay, and that you intend to pay taxes on your Bitcoin income just like any other income.

With Bitcoin being touted as a way to conduct anonymous transactions and as way to compete with government currency, many small business owners wonder what's the right way to accept and account Bitcoin, or if it's legal or ethical, or whether and how they should pay taxes on income received through Bitcoin.

As far as we know, Bitcoin isn't yet formally recognized by governments and authorities as a "currency". But in practice, Bitcoin is likely no different than accepting payment in other forms, such as cash, or gold, or scrip, or gift cards or foreign currency. We think that it is pretty much the same as the local businesses of Great Barrington, Massachusetts choosing to accept their locally-printed [http://www.reuters.com/article/2007/06/19/us-usa-economy-berkshares-idUSN0530157720070619 "Berkshire Bucks"] to support their local economy.

====Starting to accept Bitcoin for transactions====
Accepting Bitcoin at a small business is best started in whichever manner keeps the accounting simple for you. This will vary by the type of business you are operating.

===Start with a sign===
[[{{ns:file}}:WeAcceptBitcoin.png‎]]

If you expect that the number of people interested in using Bitcoin is small, you might simply start by posting a sign or a note: "We Accept Bitcoin", and ask people to contact you directly in order to make a payment. Even if hardly anybody uses Bitcoin as a payment method, you're helping Bitcoin in two ways: one, by increasing awareness, and two, by making your customers more willing to accept Bitcoin as payment from others in the future, because now they know somewhere they can spend it.

===Utilize a merchant solution===
If you sell things on your website (goods or services), you'll want to use a [[#Merchant Services|Bitcoin merchant solution]] to accept the Bitcoins (you can usually opt to have them converted to USD or other currencies automatically with some services).

If you sell things in a brick and mortar shop, customers can pay using hardware terminals, touch screen apps or simple wallet addresses through QR Codes.

[[File:Easybitz bitcoin pointofsale.png|400 px|alt=Accept Bitcoin without internet|EasyBitz ZeroClick System|link=https://easybitz.com/merchant]][[File:Coinktie Bitcoin Payment Buttons.png|alt=Coinkite Bitcoin Payment Buttons|link=https://coinkite.com/merchants]]

[[File:Bitcoin-pos-terminal.png|200 px|alt=Bitcoin POS Terminal|Coinkite terminal]] [[File:Mobile_Web_App_Bitcoin_Register.jpeg|100 px|alt=Bitcoin POS Terminal|CoinBox terminal]]

[[File:Mobile_Checkout_Phone.png|200 px|alt=Bitcoin Mobile Checkout|Coinify Mobile Checkout|link=https://coinify.com]]

===Smart Phone or Tablet===
You can use a wallet address with any wallet. For that it's best if you can place a QR code near your cash register to which the customers can scan with their phone and pay (use http://ma.eatgold.com/accept to make a QR code sign). For a more convenient solution you can use a dedicated app or webapp that generates a QR code on the fly including the amount.

==== Examples ====
Solutions for smart phones and tablets:
* [https://bitcoin.co.th/merchants/ bitcoin.co.th] mobile Bitcoin Point of Sale for Thailand
* [[File:favicon_bp.png|20px|link=https://bitcoinpay.com/static/img/]] [https://bitcoinpay.com BitcoinPay], Mobile payment terminal with EUR, USD, PLN and CZK settlements.
* [[File:BitKassa_favicon.png|20px|link=https://www.BitKassa.nl]] [https://www.BitKassa.nl BitKassa] accept Bitcoin on mobile phone, tablet, computer; converts to Euro/Bitcoin (any percentage)
* [https://bitpay.com/bitcoin-for-retail BitPay] Mobile Checkout
* [https://bitpos.me/demo.html BitPOS] Merchant POS solution for Australia
* [https://play.google.com/store/apps/details?id=info.blockchain.merchant Blockchain] Merchant for Android
* [http://www.btcxpos.com/ BTCX] POS for Sweden
* [https://coinify.com Coinify] Bitcoin Point Of Sale
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/faq/pay Coinkite] Web Pay/Buy/Donate buttons with exchange rate and timers. Customizable via API and works over Tor.
* [[File:Coin_Of_Sale_logo.png|20px|link=https://coinofsale.com]] [https://coinofsale.com Coin Of Sale] - device-independent Bitcoin POS payment system
* [https://coinbase.com/docs/merchant_tools/point_of_sale Coinbase] Point Of Sale for Android
* [[File:BitcoinRegister.gif|20px|link=http://coinbox.it/merchant]][http://coinbox.it/merchant CoinBox] Bitcoin point of sale for Android
* [http://acceptbitcoin.coinpip.com CoinPip] - Bitcoin Payment Processor for Asia
* [https://cryptopay.me/products/ Cryptopay] HTML5-based bitcoin POS
* [[File:Paxful_how-to-buy-bitcoin.png |20px|link=https://paxful.com]] [https://paxful.com Paxful] Simplest Point of Sale, No Fees and a peer to peer market to buy bitcoin instantly
* [[File:Payful.png|20px|link=http://payful.io]] [http://payful.io Payful] Accept bitcoin - point of sale, shopping cart plugins and API. Supports USA, Europe and Canada.
* [https://pocketpos.ca/ PocketPOS] Bitcoin Point of Sale for Canadians, with exchange integration
* [https://gourl.io/ GoUrl] Bitcoin Mobile Checkout

===Point-of-Sale hardware terminal===
With custom hardware you can integrate with existing registers and point-of-sales solutions (examples: [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite], [https://xbterminal.com/ XBTerminal], [http://www.bitstraat.nl BitStraat]).

===Accounting===
When a customer makes a payment, you might simply issue a credit to their account. Ideally, you want to enter it in a way that suggests you received a payment. You could consider entering it as a "discount", but you may want to consider whether this inappropriately disguises the nature of the transaction. If on the other hand, you're giving "discounts" for Bitcoins, but then you are selling the Bitcoins for currency and then counting that as income, then chances are good that your calculation of income is making up for it. Ask your accountant.

===Businesses that offer gift cards===
If your business sells gift cards or gift certificates, you may find that the easiest way to accept Bitcoin is to accept it only for the purchase of gift cards, and then require the gift cards to be used for actual purchases of goods or services. This way, the accounting practices you already have in place for processing gift cards can be put to use. The accounting for Bitcoins would then be minimized to tracking sales of a single SKU.

This method is also ideal for retail food establishments and convenience stores, where the payment of Bitcoins through a mobile phone for a small daily food purchase might be cumbersome or disruptive, especially in front of a line of other customers. Bitcoins in this case would be best used to reload prepaid cards that can then be swiped at point-of-sale.

If you don't accept gift cards, but you already accept credit cards through a swipe terminal, consider the possibility that you could add a retail gift card system through the swipe terminal you already own. Many point-of-sale terminals, including ones from VeriFone®, are designed around the ability to support multiple applications on the same terminal. Gift cards are also highly profitable because of "breakage", or in other words, the fact that a significant percentage of them never get redeemed.

You could consider adding a private label gift card program from a provider who specializes in this, not just as a jumpstart to accepting Bitcoins, but as an extra boost to income. A private label gift card service provider necessarily have to handle your funds - they can simply provide a solution that keeps track of the balance on the cards on your behalf, including features that allow users to check their balances by phone or by web. Such a solution, of course, is also what makes the cards swipeable through the card reader.

===Businesses that mail invoices===
Does your business send out invoices to customers? Adding one line may make a huge impact for the Bitcoin economy. Perhaps you list it as a payment option just after Visa, MasterCard, and American Express, even if that means your customer must call or e-mail to make a payment.

If you have access to the programming expertise such that you can generate Bitcoin addresses programmatically, consider generating a brand new Bitcoin address for each invoice, and print it on the invoice. When a Bitcoin payment arrives, you'll automatically know where it should arrive.

Customers might wonder how much BTC they should pay in order to satisfy an invoice in full. Your invoice might suggest an amount. For example, if your invoice is for $100 and BTC's are currently worth $1.24 each, your invoice might suggest that it can be paid in full ''"with a payment of 80.65 BTC if paid by (date)"''.

You might be able to anticipate the possibility that even though a Bitcoin address can be printed on an invoice or payment stub, that they are very cumbersome for most people to type, especially being a mix of uppercase and lowercase letters. However, you should probably still do it anyway. The customer is probably going to want some paper trail for his payment. Giving him a pre-printed payment stub with a pre-printed address will satisfy that, because the customer can independently and publicly prove through [[Block Explorer]] that the payment took place.

Does your business have a website? On your invoice, consider allowing them to go to a special URL to get the address to make a Bitcoin payment just by typing in their invoice number. For example, ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc'' with a form they can enter their invoice number, or just ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc/60365'' for paying invoice #60365. This way, they can see the Bitcoin address, copy and paste it directly into their Bitcoin client.

Use a brand new address for each invoice whenever possible, and use it only once. This benefits the customer as it removes any ambiguity as to which customer is making which payment and for which invoice.

Known payment systems supporting invoicing, and recurring invoice setup, [https://coinify.com/checkout/invoice/cb/bb Coinify]

Online wallet supporting invoicing, subscriptions and recurrent payments, [https://www.xcoinmoney.com/info/sending-paying-invoices xCoinMoney]

===Avoiding fraud===

You should also consider the possible risk that fraudsters could send counterfeit invoices to your customers, and entice them to make a payment to a Bitcoin address they control, instead of you. While that isn't likely in general - it depends on how well a fraudster could find out who your customers are in the first place - it would certainly be an unpleasant situation if it ever happened. One way you could control that is, whenever possible, never let people try to type Bitcoin addresses off payment stubs - instead, force people to get the full Bitcoin address from your website via secure SSL. But, still print ''most'' of the address on the payment stub (perhaps with four or five characters starred out), so that the customer's need for a paper trail can be satisfied, so they can prove they paid if there is ever a dispute. Merchants can also use the IP address geolocation to understand the close proximity of users. There is automated solution such as [https://www.fraudlabspro.com FraudLabs Pro] that automates the screening of Bitcoin transactions to determine risk level.

==Setting Prices==

When a business accepts bitcoins for payment, there generally is the need to convert them to the currencies used for paying suppliers, employees and shareholders. Some merchants set prices based on the current market rate at the time the price quote is presented to the customer (merchant services like [[File:Polycoin_favicon.png|20px|link=http://www.polycoin.io]] [http://www.polycoin.io Polycoin], [https://coinify.com Coinify], [[File:Favicon-32x32_.png|20px|link=https://bitcoinpay.com]] [https://bitcoinpay.com BitcoinPay], [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase] or [http://paysius.com Paysius] do this automatically).

[[Bitcoin Prices]] lists the exchange rate for many currencies on multiple exchanges.

When prices are determined using an automated process, the current market rate can be based on either a current price or on a weighted average basis. [[Bitcoin Charts]] provides a [http://bitcoincharts.com/about/markets-api data feed that provides weighted prices]. [[Bitcoin Average]] also offers a weighted average price index, featuring average price across all exchanges reachable in the world and in over 150 currencies. 24h sliding average price index is also available and all data is [https://bitcoinaverage.com/api.htm reachable through the API].

When bitcoin funds for purchases are received, some merchants instantly exchange those proceeds into the preferred currency used (again done automatically by [[File:Polycoin_favicon.png|20px|link=http://www.polycoin.io]] [http://www.polycoin.io Polycoin], [https://coinify.com Coinify], [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase] or [[File:Favicon-32x32_.png|20px|link=https://bitcoinpay.com]] [https://bitcoinpay.com BitcoinPay]. Hedging for each transaction can nearly entirely eliminate exchange rate risk that the business is exposed to when accepting bitcoins for payment.

==Contract==

A sales contract might be used to ensure that specific terms are met to lessen the chances of a misunderstanding. For instance, the party sending payment is responsible for paying any [[transaction fee]] that might be necessary. A contract might specify that a transaction fee must be paid and what amount, so as to prevent the situation where the transaction is considered a low priority transaction and thus isn't confirmed quickly.

Other items that might be addressed in a contract:

* Requirement and handling of escrow through an [[:Category:Escrow_services|escrow service]].
* Jurisdiction for disputes.
* Refund policy (particularly with the exchange rate being volatile)

==Paying taxes on Bitcoin income==
[[Tax compliance]] is a topic of concern for small businesses. We aren't accountants or lawyers, and can't give legal or accounting advice.

But in many respects, Bitcoin transactions work very much like cash. Just like Bitcoin, cash is anonymous and doesn't leave a paper trail, yet is widely used in commerce every day.

Ask yourself how you would handle a cash transaction. Do you accept cash transactions? Do you normally pay taxes on cash transactions? The answer for Bitcoin should probably be the same.

As for how to decide what a Bitcoin transaction is worth... the IRS, as far as we know, has never issued a guide mentioning how to value Bitcoin transactions. But they probably have rules and guidelines on how to value transactions made in foreign currency or "cash equivalents". We imagine the accounting would be similar.

With Bitcoins, there's likely to be some difference between the value of BTC when you received them as payment, versus when you go to exchange them for another currency like USD, should you decide to do so. This scenario, likewise, would be no different if you accepted foreign currency or gold as payment. Under some scenarios, it might make sense to book the dollar value of BTC income as it is received, and then to book any difference incurred when it is exchanged for fiat currency. Under others, it might make sense to book the whole thing at the time of exchange.

Perhaps you might talk to your accountant. You don't need to get into a discussion with your accountant about block chains and private keys or the philosophy behind a decentralized currency. By comparing the fundamentals of Bitcoins to accounting concepts already well understood by the public, you can probably get all the answers you need. What would you ask your accountant if you decided that you wanted to accept ''Berkshire Bucks'' or 1-ounce gold coins as payment?

== Merchant Services ==
* [https://apicoin.io Apicoin.io] A robust, secure api to connect to the bitcoin network.
* [http://www.btc4erp.com Bitcoin Transaction Coordinator] Full Merchant Solution for organizations using the NetSuite Global ERP and eCommerce Platform
* [[File:favicon_bp.png|20px|link=https://bitcoinpay.com/static/img/]] [https://bitcoinpay.com BitcoinPay] Payment gateway for virtual currencies with direct settlement to PLN, CZK, EUR and USD. POS + API.
* [[File:Bitfavicon.png|20px|link=http://www.bitcoinpaygate.com]] [http://www.bitcoinpaygate.com Bitcoinpaygate] Bitcoin payment processing for the web & in store payments
* [[File:BitKassa_favicon.png|20px|link=https://www.BitKassa.nl]] [https://www.BitKassa.nl BitKassa] Merchant solution for accepting Bitcoin, getting Euro or Euro/Bitcoin percentage. The Netherlands.
* [https://bitmerch.com BitMerch] Provides HTML buttons to start accepting bitcoins instantly. No server side setup required.
* [https://www.bitpagos.net BitPagos] Bitcoin and Credit Card payment processor
* [https://www.bitpay.com BitPay] Bitcoin payment processor with mobile checkout solution
* [https://bitpos.me BitPOS] Bitcoin payment processor for online and brick and mortar stores
* [http://www.bitstraat.nl BitStraat] Merchant POS solution for accepting Bitcoin
* [http://blockchain.info/api/api_receive Blockchain.info] Free APIs to process bitcoin payments. No sign up or account needed.
* [https://www.btcmerch.com BTCMerch] Payment processor for bitcoins and other cryptocurrencies. 0.5% transaction fee. Sandbox is available.
* [https://coinbase.com/docs/merchant_tools/payment_buttons Coinbase] Offers payment buttons, checkout pages, shopping cart integration, and daily cash out to USD.
* [[File:BitcoinRegister.gif|20px|link=http://coinbox.it/merchant]] [http://coinbox.it/merchant CoinBox] Bitcoin Point of Sales application for Android, with integration into various exchanges. Similar to Square.
* [https://coinify.com Coinify] Payment Service Provider (PSP) specializing in the technical aspects of accepting cryptocurrencies - such as bitcoin. Supports Bitcoin Web Payments, Mobile Checkout, In-store Bitcoin Payments and Bitcoin Invoicing with recurring billing in bitcoin.
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/faq/terminal Coinkite] Secure wallet multisig, payment buttons, invoice pages, hardware POS terminals, and Debit-Cards.
* [https://coinpip.com/ CoinPip] Online and POS bitcoin payment processor for Asia.
* [https://coinvoice.com/ Coinvoice] Invoice in USD or BTC, Get paid in USD or BTC.
* [https://coinvoy.net Coinvoy] Free Payment Gateway with built-in exchange
* [https://cryptopay.me Cryptopay] European payment gateway with daily payouts in GBP, EUR and USD. Exchange and wallet integrated.
* [https://cubits.com Cubits] Platform with multisignature wallets and merchant system Cubits Pay.
* [[File:Paxful_how-to-buy-bitcoin.png |20px|link=https://paxful.com]] [https://paxful.com Paxful] Accept Bitcoin with no internet then sell bitcoin for profit on our peer to peer exchange.
* [http://fasterco.in Fasterco.in] Bitcoin payment processing for merchants and day-traders
* [[File:gocoin-logo.png|20px|link=https://www.gocoin.com]] [https://www.gocoin.com/docs GoCoin International payment gateway and processing platform for Merchants]
* [https://gourl.io Gourl.io] Bitcoin Payment processor with ready to use php scripts - Pay-Per-Download, Pay-Per-Product, Pay-Per-Membership, Pay-Per-Registration.
* [[File:inpay_favicon.png|link=https://inpay.pl/?lang=en]] [https://inpay.pl/?lang=en InPay.pl] InPay was created to enable entrepreneurs to accept Bitcoin in PLN, EUR and USD.
* [[File:MCS_200by200_logo-01.png|20px|link=http://www.mycoinsolution.com]][http://www.mycoinsolution.com My Coin Solution] - Bitcoin consulting services and solutions
* [https://www.okpay.com/en/services/accept-payments/index.html OKPAY] Bitcoin payment processing for merchants
* [[File:Payful.png|20px|link=http://payful.io]] [http://payful.io Payful] Accept bitcoin - point of sale, shopping cart plugins and API. Supports payment processing in US dollars, Euros and Canadian dollars.
* [[File:Polycoin_favicon.png|20px|link=http://www.polycoin.io]] [http://www.polycoin.io Polycoin] Bitcoin payment processing platform with solutions for the financial sector
* [https://pocketpos.ca/ PocketPOS] Bitcoin Point of Sale for Canadians, including merchant integration for CAD / BTC exchange.
* [http://snowcron.com Snowcron] Bitcoin Store Engine: Handles payments, sends your customers information they ordered (reg. codes, passwords...) No web programming required.
* [https://xbterminal.com/ XBTerminal] Brick-and-mortar hardware POS terminals with payment processing integrations.
* [https://www.xcoinmoney.com/ xCoinMoney] Online wallet for instant payment and subscriptions.

==See Also==

* [[Merchant Howto]]
* [[In-store Transactions]]
* [[Tax compliance]]
* [[Securing online services]]
* [[BitCoins Mobile]] provides accurate up to date pricing from multiple exchanges from your Apple iPad, iPhone, or iPod Touch.
* [[Bitcoin PayFlow]] automates the process for accepting bitcoins
* [[Lazy API]] The lazy (and possibly easiest?) way to accept bitcoin payments on your website

[[Category:ECommerce]]
[[Category:Local]]

[[de:Bitcoin_als_Geschäft_akzeptieren]]

File:Coinktie Bitcoin Payment Buttons.png

2015-07-06T15:02:11Z

Btcto: Example of Coinkite's Pay/Buy/Donate bitcoin buttons.

== Summary ==
Example of Coinkite's Pay/Buy/Donate bitcoin buttons.
== Licensing ==
{{subst:nld}}

How to accept Bitcoin, for small businesses

2015-07-06T14:56:32Z

Btcto: /* Examples */

{{merge|Merchant Howto}}

This guide is intended for small business owners who wish to help promote Bitcoin by accepting it as payment for goods and services. It's written with the assumption that you operate a regular business that sells goods or services for regular national currency such as dollars, and that you wish to accept Bitcoin as another legal way to pay, and that you intend to pay taxes on your Bitcoin income just like any other income.

With Bitcoin being touted as a way to conduct anonymous transactions and as way to compete with government currency, many small business owners wonder what's the right way to accept and account Bitcoin, or if it's legal or ethical, or whether and how they should pay taxes on income received through Bitcoin.

As far as we know, Bitcoin isn't yet formally recognized by governments and authorities as a "currency". But in practice, Bitcoin is likely no different than accepting payment in other forms, such as cash, or gold, or scrip, or gift cards or foreign currency. We think that it is pretty much the same as the local businesses of Great Barrington, Massachusetts choosing to accept their locally-printed [http://www.reuters.com/article/2007/06/19/us-usa-economy-berkshares-idUSN0530157720070619 "Berkshire Bucks"] to support their local economy.

====Starting to accept Bitcoin for transactions====
Accepting Bitcoin at a small business is best started in whichever manner keeps the accounting simple for you. This will vary by the type of business you are operating.

===Start with a sign===
[[{{ns:file}}:WeAcceptBitcoin.png‎]]

If you expect that the number of people interested in using Bitcoin is small, you might simply start by posting a sign or a note: "We Accept Bitcoin", and ask people to contact you directly in order to make a payment. Even if hardly anybody uses Bitcoin as a payment method, you're helping Bitcoin in two ways: one, by increasing awareness, and two, by making your customers more willing to accept Bitcoin as payment from others in the future, because now they know somewhere they can spend it.

===Utilize a merchant solution===
If you sell things on your website (goods or services), you'll want to use a [[#Merchant Services|Bitcoin merchant solution]] to accept the Bitcoins (you can usually opt to have them converted to USD or other currencies automatically with some services).

If you sell things in a brick and mortar shop, customers can pay using hardware terminals, touch screen apps or simple wallet addresses through QR Codes.

[[File:Easybitz bitcoin pointofsale.png|400 px|alt=Accept Bitcoin without internet|EasyBitz ZeroClick System|link=https://easybitz.com/merchant]]

[[File:Bitcoin-pos-terminal.png|200 px|alt=Bitcoin POS Terminal|Coinkite terminal]] [[File:Mobile_Web_App_Bitcoin_Register.jpeg|100 px|alt=Bitcoin POS Terminal|CoinBox terminal]]

[[File:Mobile_Checkout_Phone.png|200 px|alt=Bitcoin Mobile Checkout|Coinify Mobile Checkout|link=https://coinify.com]]

===Smart Phone or Tablet===
You can use a wallet address with any wallet. For that it's best if you can place a QR code near your cash register to which the customers can scan with their phone and pay (use http://ma.eatgold.com/accept to make a QR code sign). For a more convenient solution you can use a dedicated app or webapp that generates a QR code on the fly including the amount.

==== Examples ====
Solutions for smart phones and tablets:
* [https://bitcoin.co.th/merchants/ bitcoin.co.th] mobile Bitcoin Point of Sale for Thailand
* [[File:favicon_bp.png|20px|link=https://bitcoinpay.com/static/img/]] [https://bitcoinpay.com BitcoinPay], Mobile payment terminal with EUR, USD, PLN and CZK settlements.
* [[File:BitKassa_favicon.png|20px|link=https://www.BitKassa.nl]] [https://www.BitKassa.nl BitKassa] accept Bitcoin on mobile phone, tablet, computer; converts to Euro/Bitcoin (any percentage)
* [https://bitpay.com/bitcoin-for-retail BitPay] Mobile Checkout
* [https://bitpos.me/demo.html BitPOS] Merchant POS solution for Australia
* [https://play.google.com/store/apps/details?id=info.blockchain.merchant Blockchain] Merchant for Android
* [http://www.btcxpos.com/ BTCX] POS for Sweden
* [https://coinify.com Coinify] Bitcoin Point Of Sale
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/faq/pay Coinkite] Web Pay/Buy/Donate buttons with exchange rate and timers. Customizable via API and works over Tor.
* [[File:Coin_Of_Sale_logo.png|20px|link=https://coinofsale.com]] [https://coinofsale.com Coin Of Sale] - device-independent Bitcoin POS payment system
* [https://coinbase.com/docs/merchant_tools/point_of_sale Coinbase] Point Of Sale for Android
* [[File:BitcoinRegister.gif|20px|link=http://coinbox.it/merchant]][http://coinbox.it/merchant CoinBox] Bitcoin point of sale for Android
* [http://acceptbitcoin.coinpip.com CoinPip] - Bitcoin Payment Processor for Asia
* [https://cryptopay.me/products/ Cryptopay] HTML5-based bitcoin POS
* [[File:Paxful_how-to-buy-bitcoin.png |20px|link=https://paxful.com]] [https://paxful.com Paxful] Simplest Point of Sale, No Fees and a peer to peer market to buy bitcoin instantly
* [[File:Payful.png|20px|link=http://payful.io]] [http://payful.io Payful] Accept bitcoin - point of sale, shopping cart plugins and API. Supports USA, Europe and Canada.
* [https://pocketpos.ca/ PocketPOS] Bitcoin Point of Sale for Canadians, with exchange integration
* [https://gourl.io/ GoUrl] Bitcoin Mobile Checkout

===Point-of-Sale hardware terminal===
With custom hardware you can integrate with existing registers and point-of-sales solutions (examples: [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite], [https://xbterminal.com/ XBTerminal], [http://www.bitstraat.nl BitStraat]).

===Accounting===
When a customer makes a payment, you might simply issue a credit to their account. Ideally, you want to enter it in a way that suggests you received a payment. You could consider entering it as a "discount", but you may want to consider whether this inappropriately disguises the nature of the transaction. If on the other hand, you're giving "discounts" for Bitcoins, but then you are selling the Bitcoins for currency and then counting that as income, then chances are good that your calculation of income is making up for it. Ask your accountant.

===Businesses that offer gift cards===
If your business sells gift cards or gift certificates, you may find that the easiest way to accept Bitcoin is to accept it only for the purchase of gift cards, and then require the gift cards to be used for actual purchases of goods or services. This way, the accounting practices you already have in place for processing gift cards can be put to use. The accounting for Bitcoins would then be minimized to tracking sales of a single SKU.

This method is also ideal for retail food establishments and convenience stores, where the payment of Bitcoins through a mobile phone for a small daily food purchase might be cumbersome or disruptive, especially in front of a line of other customers. Bitcoins in this case would be best used to reload prepaid cards that can then be swiped at point-of-sale.

If you don't accept gift cards, but you already accept credit cards through a swipe terminal, consider the possibility that you could add a retail gift card system through the swipe terminal you already own. Many point-of-sale terminals, including ones from VeriFone®, are designed around the ability to support multiple applications on the same terminal. Gift cards are also highly profitable because of "breakage", or in other words, the fact that a significant percentage of them never get redeemed.

You could consider adding a private label gift card program from a provider who specializes in this, not just as a jumpstart to accepting Bitcoins, but as an extra boost to income. A private label gift card service provider necessarily have to handle your funds - they can simply provide a solution that keeps track of the balance on the cards on your behalf, including features that allow users to check their balances by phone or by web. Such a solution, of course, is also what makes the cards swipeable through the card reader.

===Businesses that mail invoices===
Does your business send out invoices to customers? Adding one line may make a huge impact for the Bitcoin economy. Perhaps you list it as a payment option just after Visa, MasterCard, and American Express, even if that means your customer must call or e-mail to make a payment.

If you have access to the programming expertise such that you can generate Bitcoin addresses programmatically, consider generating a brand new Bitcoin address for each invoice, and print it on the invoice. When a Bitcoin payment arrives, you'll automatically know where it should arrive.

Customers might wonder how much BTC they should pay in order to satisfy an invoice in full. Your invoice might suggest an amount. For example, if your invoice is for $100 and BTC's are currently worth $1.24 each, your invoice might suggest that it can be paid in full ''"with a payment of 80.65 BTC if paid by (date)"''.

You might be able to anticipate the possibility that even though a Bitcoin address can be printed on an invoice or payment stub, that they are very cumbersome for most people to type, especially being a mix of uppercase and lowercase letters. However, you should probably still do it anyway. The customer is probably going to want some paper trail for his payment. Giving him a pre-printed payment stub with a pre-printed address will satisfy that, because the customer can independently and publicly prove through [[Block Explorer]] that the payment took place.

Does your business have a website? On your invoice, consider allowing them to go to a special URL to get the address to make a Bitcoin payment just by typing in their invoice number. For example, ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc'' with a form they can enter their invoice number, or just ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc/60365'' for paying invoice #60365. This way, they can see the Bitcoin address, copy and paste it directly into their Bitcoin client.

Use a brand new address for each invoice whenever possible, and use it only once. This benefits the customer as it removes any ambiguity as to which customer is making which payment and for which invoice.

Known payment systems supporting invoicing, and recurring invoice setup, [https://coinify.com/checkout/invoice/cb/bb Coinify]

Online wallet supporting invoicing, subscriptions and recurrent payments, [https://www.xcoinmoney.com/info/sending-paying-invoices xCoinMoney]

===Avoiding fraud===

You should also consider the possible risk that fraudsters could send counterfeit invoices to your customers, and entice them to make a payment to a Bitcoin address they control, instead of you. While that isn't likely in general - it depends on how well a fraudster could find out who your customers are in the first place - it would certainly be an unpleasant situation if it ever happened. One way you could control that is, whenever possible, never let people try to type Bitcoin addresses off payment stubs - instead, force people to get the full Bitcoin address from your website via secure SSL. But, still print ''most'' of the address on the payment stub (perhaps with four or five characters starred out), so that the customer's need for a paper trail can be satisfied, so they can prove they paid if there is ever a dispute. Merchants can also use the IP address geolocation to understand the close proximity of users. There is automated solution such as [https://www.fraudlabspro.com FraudLabs Pro] that automates the screening of Bitcoin transactions to determine risk level.

==Setting Prices==

When a business accepts bitcoins for payment, there generally is the need to convert them to the currencies used for paying suppliers, employees and shareholders. Some merchants set prices based on the current market rate at the time the price quote is presented to the customer (merchant services like [[File:Polycoin_favicon.png|20px|link=http://www.polycoin.io]] [http://www.polycoin.io Polycoin], [https://coinify.com Coinify], [[File:Favicon-32x32_.png|20px|link=https://bitcoinpay.com]] [https://bitcoinpay.com BitcoinPay], [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase] or [http://paysius.com Paysius] do this automatically).

[[Bitcoin Prices]] lists the exchange rate for many currencies on multiple exchanges.

When prices are determined using an automated process, the current market rate can be based on either a current price or on a weighted average basis. [[Bitcoin Charts]] provides a [http://bitcoincharts.com/about/markets-api data feed that provides weighted prices]. [[Bitcoin Average]] also offers a weighted average price index, featuring average price across all exchanges reachable in the world and in over 150 currencies. 24h sliding average price index is also available and all data is [https://bitcoinaverage.com/api.htm reachable through the API].

When bitcoin funds for purchases are received, some merchants instantly exchange those proceeds into the preferred currency used (again done automatically by [[File:Polycoin_favicon.png|20px|link=http://www.polycoin.io]] [http://www.polycoin.io Polycoin], [https://coinify.com Coinify], [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase] or [[File:Favicon-32x32_.png|20px|link=https://bitcoinpay.com]] [https://bitcoinpay.com BitcoinPay]. Hedging for each transaction can nearly entirely eliminate exchange rate risk that the business is exposed to when accepting bitcoins for payment.

==Contract==

A sales contract might be used to ensure that specific terms are met to lessen the chances of a misunderstanding. For instance, the party sending payment is responsible for paying any [[transaction fee]] that might be necessary. A contract might specify that a transaction fee must be paid and what amount, so as to prevent the situation where the transaction is considered a low priority transaction and thus isn't confirmed quickly.

Other items that might be addressed in a contract:

* Requirement and handling of escrow through an [[:Category:Escrow_services|escrow service]].
* Jurisdiction for disputes.
* Refund policy (particularly with the exchange rate being volatile)

==Paying taxes on Bitcoin income==
[[Tax compliance]] is a topic of concern for small businesses. We aren't accountants or lawyers, and can't give legal or accounting advice.

But in many respects, Bitcoin transactions work very much like cash. Just like Bitcoin, cash is anonymous and doesn't leave a paper trail, yet is widely used in commerce every day.

Ask yourself how you would handle a cash transaction. Do you accept cash transactions? Do you normally pay taxes on cash transactions? The answer for Bitcoin should probably be the same.

As for how to decide what a Bitcoin transaction is worth... the IRS, as far as we know, has never issued a guide mentioning how to value Bitcoin transactions. But they probably have rules and guidelines on how to value transactions made in foreign currency or "cash equivalents". We imagine the accounting would be similar.

With Bitcoins, there's likely to be some difference between the value of BTC when you received them as payment, versus when you go to exchange them for another currency like USD, should you decide to do so. This scenario, likewise, would be no different if you accepted foreign currency or gold as payment. Under some scenarios, it might make sense to book the dollar value of BTC income as it is received, and then to book any difference incurred when it is exchanged for fiat currency. Under others, it might make sense to book the whole thing at the time of exchange.

Perhaps you might talk to your accountant. You don't need to get into a discussion with your accountant about block chains and private keys or the philosophy behind a decentralized currency. By comparing the fundamentals of Bitcoins to accounting concepts already well understood by the public, you can probably get all the answers you need. What would you ask your accountant if you decided that you wanted to accept ''Berkshire Bucks'' or 1-ounce gold coins as payment?

== Merchant Services ==
* [https://apicoin.io Apicoin.io] A robust, secure api to connect to the bitcoin network.
* [http://www.btc4erp.com Bitcoin Transaction Coordinator] Full Merchant Solution for organizations using the NetSuite Global ERP and eCommerce Platform
* [[File:favicon_bp.png|20px|link=https://bitcoinpay.com/static/img/]] [https://bitcoinpay.com BitcoinPay] Payment gateway for virtual currencies with direct settlement to PLN, CZK, EUR and USD. POS + API.
* [[File:Bitfavicon.png|20px|link=http://www.bitcoinpaygate.com]] [http://www.bitcoinpaygate.com Bitcoinpaygate] Bitcoin payment processing for the web & in store payments
* [[File:BitKassa_favicon.png|20px|link=https://www.BitKassa.nl]] [https://www.BitKassa.nl BitKassa] Merchant solution for accepting Bitcoin, getting Euro or Euro/Bitcoin percentage. The Netherlands.
* [https://bitmerch.com BitMerch] Provides HTML buttons to start accepting bitcoins instantly. No server side setup required.
* [https://www.bitpagos.net BitPagos] Bitcoin and Credit Card payment processor
* [https://www.bitpay.com BitPay] Bitcoin payment processor with mobile checkout solution
* [https://bitpos.me BitPOS] Bitcoin payment processor for online and brick and mortar stores
* [http://www.bitstraat.nl BitStraat] Merchant POS solution for accepting Bitcoin
* [http://blockchain.info/api/api_receive Blockchain.info] Free APIs to process bitcoin payments. No sign up or account needed.
* [https://www.btcmerch.com BTCMerch] Payment processor for bitcoins and other cryptocurrencies. 0.5% transaction fee. Sandbox is available.
* [https://coinbase.com/docs/merchant_tools/payment_buttons Coinbase] Offers payment buttons, checkout pages, shopping cart integration, and daily cash out to USD.
* [[File:BitcoinRegister.gif|20px|link=http://coinbox.it/merchant]] [http://coinbox.it/merchant CoinBox] Bitcoin Point of Sales application for Android, with integration into various exchanges. Similar to Square.
* [https://coinify.com Coinify] Payment Service Provider (PSP) specializing in the technical aspects of accepting cryptocurrencies - such as bitcoin. Supports Bitcoin Web Payments, Mobile Checkout, In-store Bitcoin Payments and Bitcoin Invoicing with recurring billing in bitcoin.
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/faq/terminal Coinkite] Secure wallet multisig, payment buttons, invoice pages, hardware POS terminals, and Debit-Cards.
* [https://coinpip.com/ CoinPip] Online and POS bitcoin payment processor for Asia.
* [https://coinvoice.com/ Coinvoice] Invoice in USD or BTC, Get paid in USD or BTC.
* [https://coinvoy.net Coinvoy] Free Payment Gateway with built-in exchange
* [https://cryptopay.me Cryptopay] European payment gateway with daily payouts in GBP, EUR and USD. Exchange and wallet integrated.
* [https://cubits.com Cubits] Platform with multisignature wallets and merchant system Cubits Pay.
* [[File:Paxful_how-to-buy-bitcoin.png |20px|link=https://paxful.com]] [https://paxful.com Paxful] Accept Bitcoin with no internet then sell bitcoin for profit on our peer to peer exchange.
* [http://fasterco.in Fasterco.in] Bitcoin payment processing for merchants and day-traders
* [[File:gocoin-logo.png|20px|link=https://www.gocoin.com]] [https://www.gocoin.com/docs GoCoin International payment gateway and processing platform for Merchants]
* [https://gourl.io Gourl.io] Bitcoin Payment processor with ready to use php scripts - Pay-Per-Download, Pay-Per-Product, Pay-Per-Membership, Pay-Per-Registration.
* [[File:inpay_favicon.png|link=https://inpay.pl/?lang=en]] [https://inpay.pl/?lang=en InPay.pl] InPay was created to enable entrepreneurs to accept Bitcoin in PLN, EUR and USD.
* [[File:MCS_200by200_logo-01.png|20px|link=http://www.mycoinsolution.com]][http://www.mycoinsolution.com My Coin Solution] - Bitcoin consulting services and solutions
* [https://www.okpay.com/en/services/accept-payments/index.html OKPAY] Bitcoin payment processing for merchants
* [[File:Payful.png|20px|link=http://payful.io]] [http://payful.io Payful] Accept bitcoin - point of sale, shopping cart plugins and API. Supports payment processing in US dollars, Euros and Canadian dollars.
* [[File:Polycoin_favicon.png|20px|link=http://www.polycoin.io]] [http://www.polycoin.io Polycoin] Bitcoin payment processing platform with solutions for the financial sector
* [https://pocketpos.ca/ PocketPOS] Bitcoin Point of Sale for Canadians, including merchant integration for CAD / BTC exchange.
* [http://snowcron.com Snowcron] Bitcoin Store Engine: Handles payments, sends your customers information they ordered (reg. codes, passwords...) No web programming required.
* [https://xbterminal.com/ XBTerminal] Brick-and-mortar hardware POS terminals with payment processing integrations.
* [https://www.xcoinmoney.com/ xCoinMoney] Online wallet for instant payment and subscriptions.

==See Also==

* [[Merchant Howto]]
* [[In-store Transactions]]
* [[Tax compliance]]
* [[Securing online services]]
* [[BitCoins Mobile]] provides accurate up to date pricing from multiple exchanges from your Apple iPad, iPhone, or iPod Touch.
* [[Bitcoin PayFlow]] automates the process for accepting bitcoins
* [[Lazy API]] The lazy (and possibly easiest?) way to accept bitcoin payments on your website

[[Category:ECommerce]]
[[Category:Local]]

[[de:Bitcoin_als_Geschäft_akzeptieren]]

Bitcoin API Services

2015-07-06T14:53:33Z

Btcto: /* Services */

Bitcoin API Services makes accepting Bitcoin payments as easy as handling HTTP requests.

Unlike most online payment notification services, payments are not actually sent to Bitcoin API Services, so there is no need of entrusting someone else with your wallet, or letting someone else manage one for you. Payments go directly from a customer to the merchant

Bitcoin API Services also delivers HTTP POST notifications about Bitcoin exchange rates, and difficulty rates.

== How it works ==
Bitcoin API Services works by monitoring the Bitcoin network for transactions sent to addresses you can specify in your account. Bitcoin API Services can currently:

* POST amounts for variable price transactions.
* POST amounts for fixed price transactions.
* Make POSTs on Mt Gox currency and difficulty updates.

== Integration Details ==
* Merchant generates a number of Bitcoin addresses and enters them into his account. At the same time, merchant places these addresses into his store.
* The store software assigns one of these addresses to each order, or session. Once the user sends bitcoins to this address, the order is completed for the user.
* Meanwhile, the back-end of the merchants store waits for the confirmation from Bitcoin API Services. Once a confirmation is received the merchants store can either display the product to the user, or send the user an e-mail letting them know that the payment has been accepted. The address used can be released again for future use.

==History==
The service was proposed in mid-December as a redundancy to [[BitcoinNotify]]. The service officially went into beta on Wednesday, December 21st.

==Services==
* [http://blockchain.info/api Blockchain.info] - has a developer API
* [https://coinbase.com/docs/api/overview Coinbase] Features an API that lets you send, request, buy, sell, and accept bitcoin through a RESTful JSON interface.
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/developers Coinkite] Features an API that lets you send, request, buy, sell, and accept bitcoin through a RESTful JSON interface.
* [https://apicoin.io/api/ apicoin.io] Features a robust, and secure blockchain API, and watch wallet features on an enterprise scale.
* [http://www.blockcypher.com/ BlockCypher] Get address and transaction information, notifications (WebHooks, WebSockets), issue your transactions easily, etc. all through a simple web API.

==See Also==
* [[:Category:ECommerce|eCommerce]]

==External Links==
* [http://www.bitcoinapiservices.com BitcoinAPIServices web site]

==References==
<references />

[[Category:Shopping Cart Interfaces]]
[[Category:Services]]

Merchant Howto

2015-07-06T14:52:12Z

Btcto: /* Services */

{{merge|How to accept Bitcoin, for small businesses}}

Accepting Bitcoins is easy, and there are several ways to do it.

==Manually==
# Download a bitcoin client
# When a customer wants to buy something, send them a Bitcoin address where their payment should be sent.
#* You can do this by clicking "New.." next to your address in the Bitcoin client and sending that address to the customer.
# When payment comes in to that address, send the goods to your customer. Depending on the value of what you're selling, you may wish to wait until the payment shows Confirmed.
# To issue a refund, obtain from the customer the [[Address|bitcoin address]] where the refund payment should be sent. The refund address will likely be different from the address used when the customer sent payment, especially if an [[EWallet]] was used by the customer.

==Automated==
===Pre-generating Bitcoin addresses===
You can accept Bitcoins on your website without needing to use Bitcoin APIs or third party services if you pre-generate a large number of receiving Bitcoin addresses and store them in a database on your web server, and dispense them one-by-one to customers when they are ready to pay. This way, your web server never actually handles the bitcoins - it simply gives out addresses belonging to a wallet you maintain elsewhere. By using a unique address per order, you will always know which payment belongs to which order. [https://www.casascius.com Example of website using this method]

To pre-generate addresses, use a tool such as [[Pywallet]] (which can generate a wallet.dat file) or [[Bitcoin Address Utility]] (which can generate a CSV file). In both cases, you will be generating a list of [[Address|Bitcoin address]]es along with their corresponding [[private key]]s. Only the Bitcoin addresses (not the private keys) should be loaded on the web server.

If you are shipping goods manually, you can use the Bitcoin software to check for incoming payments, or alternately consider using [[Block Explorer]] or [[Abe]] to verify payment when you're about to ship. To make this easy, make your website provide you a full hyperlink that includes the proper receiving address: ht<nowiki>tp://www</nowiki>.blockexplorer.com/address/ADDRESSGOESHERE.

If you are delivering digital goods or services and want to be able to deliver instantly upon payment and/or confirmation, you can use a third-party service such as [[Bitcoin Notify]] to tell your website when a payment has been received. This sort of service requires no significant API implementation - they will simply make a POST to your website or send you an e-mail when a payment has been received on one of your addresses.

If you keep Bitcoins off your web server, this ensures your wallet cannot be stolen if your web server experiences a security intrusion. Your risk becomes limited to the possibility that a successful intruder could add his own addresses to your address pool and steal funds from a few incoming orders until you detect the problem, however, this is a [[Deterministic_wallet|relatively controllable risk]].

===Using offchain payment networks===

[[Off-Chain_Transactions|Off chain]] networks provides various benefits to Bitcoin, such as instant confirmations and protection against double spending.

===Using a third-party plugin===
You can use an existing [[:Category:Shopping Cart Interfaces|shopping cart interface]] from a 3rd party to automatically handle all Bitcoin payments on your website. If you want to develop the system yourself, you can utilize the Bitcoin client's [[API tutorial (JSON-RPC)|JSON-RPC API]] to automatically accept payments.

Things to note if you build it yourself:
# When a customer orders something on your website it records:
#* Bitcoin address that payment should be sent to
#* Order details (delivery address etc.)
#* Customer's refund address (optional - if you wish you can ask for this later, only in cases a refund is required)
#* Payment amount
# When payment arrives, checks that they have paid the correct amount or not, and informs you
#* You dispatch the goods to the customer and mark the order as fulfilled
#* If you cannot dispatch the goods you mark the order as denied and ask the customer for a refund address (unless you already have it from earlier) to send a refund.
# Forwards the funds to bitcoin address of your choice

===If You have a retail business and do not have internet or smart phone===
You can still accept Bitcoin. [https://easybitz.com/merchant] EasyBitz.com has a very simple way to accept bitcoin with just a print out and a phone that gets sms text messages.

[[File:Easybitz bitcoin pointofsale.png|400 px|alt=Accept Bitcoin without internet|EasyBitz ZeroClick System|link=https://easybitz.com/merchant]]

===Businesses that mail invoices===
Does your business send out invoices to customers? Adding one line may make a huge impact for the Bitcoin economy. Perhaps you list it as a payment option just after Visa, MasterCard, and American Express, even if that means your customer must call or e-mail to make a payment. However it is possible to create automated invoices by using known payment systems supporting invoicing, and recurring invoice setup.

==Common Errors==
It has been observed on occasion that a business funnels all its orders through the same Bitcoin address, and asks people to send some BTC, then send email describing the timing and the amount of the transaction to 'claim' it. This is '''not''' secure, since anyone can see the transaction details using a tool such as [[Block Explorer]], and then try to claim someone else's transaction as theirs.

Do not do this. Give each customer a unique Bitcoin address.

==Listing your business on the Bitcoin Trade page==

Anyone can add and update a listing on the [[Trade|trade]] page. Just register if you haven't and add to the appropriate category. If you'ld like assistance, perhaps someone in the [http://webchat.freenode.net/?channels=#bitcoin-marketing #bitcoin-marketing] IRC channel would be willing to assist. If you have a brick and mortar business that accepts bitcoin you can add it to the bitcoin directories. [https://easybitz.com] [http://coinmap.org]

==Services==
* [[File:Bitfavicon.png|20px|link=http://www.bitcoinpaygate.com]] [http://www.bitcoinpaygate.com Bitcoinpaygate] Bitcoin payment processing for the web & in store payments
* [https://bitcoinpay.com BitcoinPay] Merchant solution for Bitcoin specialized in Middle Europe (Germany, Poland, Slovakia, Czech republic)
* [https://www.BitKassa.nl BitKassa] Merchant solution for accepting bitcoins, getting euro's. No fee. The Netherlands.
* [[BitPay]] Merchant solutions for Bitcoin
* [http://www.bitpagos.net BitPagos] Payments Gateway for Latin America
* [https://coinbase.com/merchants Coinbase] Offers payment buttons, pages, iframes, shopping cart integration, subscription/recurring billing, micro-transactions, and cash out to your local currency for 1%.
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/faq/terminal Coinkite] Secure wallet multisig, payment buttons, invoice pages, hardware POS terminals, and Debit-Cards.
* [https://cryptopay.me/ Cryptopay] Bitcoin merchant payment processing. UK-based, serving UK and EU clients.
* [http://www.dcpos.com DC POS] A Bitcoin browser-based Point-of-Sale app. It is hardware, OS, wallet, and browser agnostic. 0.5% transaction fee.
* [[Coinify]] Merchant solutions for Bitcoin
* [[File:Easybitz.png|20px|link=https://easybitz.com]] [https://easybitz.com EasyBitz] Bitcoin for Retail worldwide. ZeroClick requires only SMS. POS works on SmartPhones and Tablets. Live Transaction Global Map. No fees.
* [http://www.fraudlabspro.com/ FraudLabs Pro] Fraud screening service for online merchants. Support transactions using Bitcoin as payment method.
* [[File:gocoin-logo.png|20px|link=https://www.gocoin.com]] [[GoCoin]] International Payment Processing for Bitcoin
* [https://gourl.io Gourl.io] Bitcoin Payment Gateway with ready to use php scripts - Pay-Per-Download, Pay-Per-Product, Pay-Per-Registration.
* [[File:inpay_favicon.png|link=https://inpay.pl/?lang=en]] [https://inpay.pl/?lang=en InPay.pl] InPay was created to enable entrepreneurs to accept Bitcoin in PLN, EUR and USD.
* [[File:MCS_200by200_logo-01.png|20px|link=http://www.mycoinsolution.com]][http://www.mycoinsolution.com My Coin Solution] - Bitcoin consulting services and solutions
* [https://xbterminal.com/ XBTerminal] Brick-and-mortar hardware POS terminals with payment processing integrations.
* [[File:Payful.png|20px|link=http://payful.io]] [http://payful.io Payful] Accept bitcoin - point of sale, shopping cart plugins and API. Supports payment processing in US dollars, Euros and Canadian dollars.
* [http://paysius.com Paysius] Allows merchants to easily and securely accept Bitcoin payments on their website

==See Also==
* [[In-store Transactions]]
* [[:Category:Shopping Cart Interfaces|Shopping Cart Interfaces]]
* [[Securing online services]]
* [[Bitcoin Evolution]] handles sales tracking and order forms; requires Bitcoin client for actual payment
* [[Bitcoin API Services]] an easy solution for securely accepting Bitcoins and updating BTC prices
* [[Converter|Bitcoin Javascript Converter]] displays a price in BTCs after converting from USDs.
* [[How to accept Bitcoin, for small businesses]]
* [[:Category:Marketing|Marketing]]
* [[URI Scheme]]
* [[Promotional graphics]], buttons and logos
* [https://github.com/cryptoapi/Payment-Gateway GoUrl Bitcoin Payment API] open source php payment api on Github.com
* [[Lazy API]] The lazy (and possibly easiest?) way to accept bitcoin payments on your website
* [http://snowcron.com Snowcron] Bitcoin Store Engine: Handles payments, sends your customers information they ordered (reg. codes, passwords...) No web programming required.
[[Category:ECommerce]]

Category:Clients

2015-07-06T14:49:40Z

Btcto: /* See Also */ Dead Link

'''Bitcoin clients''' are software that can connect to the network (implement the p2p protocol), download the [[blockchain]], manages wallets, and send or receive bitcoins, these clients intend to be alternatives to the original Bitcoin client.

Software or API wrappers that merely connects to an already running bitcoind to provide an alternative user interface or language binding is found in the category [[:Category:Frontends|Frontends]].

==See Also==

* [[:Category:Frontends|Frontends]]
* [[Protocol rules]]
* [[:Category:User Interfaces|User Interfaces]]
* [[:Category:Wallets|Wallets]]
* [[:Category:Nodes|Nodes]]
* [https://bitcoin.org/en/choose-your-wallet Choose your Bitcoin wallet] on [[Bitcoin.org]]
* [http://dre.tx0.org/compare.htm Open-Source Bitcoin Clients for the Desktop]

[[fr:Catégorie:Clients Bitcoin]]
[[de:Kategorie:Client-Anwendungen]]
[[Category:Software]]

Coinkite

2015-07-06T14:47:40Z

Btcto: Article deleted

==Coinkite==

Coinkite<ref> (12/11/2013). [http://www.thestar.com/news/gta/2013/11/12/bitcoin_entrepreneurs_want_to_put_virtual_coins_in_your_wallet.html "Bitcoin entrepreneurs want to put virtual coins in your wallet".] ''[[Toronto Star]]''.</ref><ref> (11/11/2013). [http://bitcoinmagazine.com/7449/exploring-the-bitcoin-alliance-of-canada-part-i/ "Bitcoin in Canada, Part I: Introducing the Bitcoin Alliance of Canada".] ''[[Bitcoin Magazine]]''.</ref><ref>nvK (10/11/2013). [https://bitcointalk.org/index.php?topic=309431.0 "(ANN) Coinkite.com (Bitcoin Wallet+Debit Card+POS Terminals)accepting invites re".] ''[[bitcointalk.org]]''.</ref><ref>KYT DOTSON (22/10/2013). [http://siliconangle.com/blog/2013/09/25/bitcoin-weekly-2013-september-25-lucky-gambler-makes-11k-btc-coinsetter-to-launch-soon-coinkite-brings-pos-solution/ "Bitcoin Weekly 2013 September 25: Lucky Gambler Makes 11k BTC, Coinsetter to Launch Soon, Coinkite Brings POS Solution".] ''[[Silicon Angle]]''.</ref><ref> (5/11/2013). [https://en.bitcoin.it/wiki/Coinkite "Coinkite".] ''[[Bitcoin Wiki]]''.</ref><ref> (5/11/2013). [https://www.coinforum.ca/discussion/461/accepting-invite-requests-for-coinkite-com "Accepting invite requests for Coinkite.com".] ''[[coinforum.ca]]''.</ref><ref> (1/11/2013). [http://www.thebitpages.com/merchants/1076 "Coinkite".] ''[[The Bit Pages]]''.</ref><ref> (2013). [http://www.linkedin.com/company/coinkite "Company: Coinkite".] ''[[LinkedIN]]''.</ref> offers a number of useful [[bitcoin]] services, including wallet and a hardware payment network.

==Main features==
* Powerful, easy to use web wallet. Receive and send bitcoin amounts from a web interface. Two factor authentication, memorable image (to resist phishing attempts) and many other security features are in place. Users are free of the burden of securing their own computer.

* [https://coinkite.com/faq/multisig Multi-Signature and shared wallets] with up to M-of-15 and options for any/all keys to be generated offline (Co-Sign Pages and Bitcoin Multisig API)

* Developers Platform, [https://coinkite.com/developers Bitkit Bitcoin API] provides simple and powerful REST integrations for adding bitcoin functions into your business / application.

* Payment Processing, customizable [https://coinkite.com/faq/pay Pay/Buy/Donate buttons] to integrate in your website or shopping cart. Works over Tor.

* Point-of-sale payment terminal. Coinkite sells a hardware device, complete with QR scanner and receipt printer that can be used to perform bitcoin transactions without a computer and in a retail setting.

* "Debit" Card. Coinkite offers all it's members a plastic card which can be used at the payment terminals, but is also useful anywhere as it was a bitcoin address in QR code on the back. Bitcoin sent to that address are linked to the user's Coinkite balance.

==Services==

* multiple sub-accounts for grouping funds (ie. "Savings", "Chequing")

* all transactions occur in the public blockchain, and there is no "internal bookkeeping" of funds.

* monthly, yearly and pay as you go membership plans are offered.

* detailed transaction logging, real-time on-screen alerts as funds as received

* multiple [[cryptocurrenies]]: bitcoin, litecoin, testnet coins are offered with equal features

====Services Links====

* [https://coinkite.com/faq/money Online wallets]

* [https://coinkite.com/faq/terminal Merchant Point-of-Sale terminals]

* [https://coinkite.com/faq/terminal Bitcoin debit cards]

==Unique [[BIP]] 32 Feature==

Coinkite is internally based on BIP 32 [[Hierarchical Deterministic]] (HD) wallets. Each new member receives a "welcome email" which contains the "xpubkey" (extended public key) for their deposits, and an *encrypted* copy of the corresponding xprivkey. The xpubkey can be used by the account owner to see all public keys associated with their account (both past and future). Combined with the "audit" feature, the user can fetch a list of all UTXO (unspent transaction outputs) associated with their account and verify the public key's subpath from the given xpubkey. Similarly, they can check the UTXO is correctly stored on the blockchain.

Coinkite has stated that in the event of the closure or other failure of the business, they will publicize the symmetric key protecting the xprivkey values that have been distributed to members. With that key, each user could recover their funds by re-generating the private keys for each UTXO.

The founders of Coinkite understood the inherent risk of trusting a third party with the private keys for your bitcoins, and this application of BIP 32 helps to address these concerns should the business disappear. The company calls this system "full reserve" since the users are in a position to verify that their funds are not being used for any other purpose than safe-keeping, while on deposit at Coinkite.

==Debit Card==

For a small fee (and included in some membership plans), Coinkite users may receive a physical card. This eases use of their Coinkite account at the POS terminal and the QR code on the rear is useful for making deposits.

==POS Terminal==

Coinkite sells a hardware device which can perform a number of transactions. It connects via GPRS (cell) or Wifi to Coinkite backend servers which perform the blockchain operations. It does not directly connect to the P2P network.

Users can log into their Coinkite account at the machine, using either their Coinkite card (and a 4-6 digit PIN, plus optionally a 2FA token) or use a one-time QR code from the Coinkite website. Once connected to their account, they can perform many types of transactions:

* print out their current balances

* scan a QR and pay it using their balance

* withdraw funds to cash (requires the retail to become the counter-party)

* deposit cash (buying coins from the retailer)

* make a printed invoice (ie. a unique bitcoin address for payment of a specific amount)

* verify a payment has been received (by scanning any receipt printed by a Coinkite terminal)

The POS terminal is also useful to enable the bitcoin-based retail business. Cashiers (authorized users) can print a receipt with QR code that maybe presented to customers as a bill in bitcoin to be paid. Once paid, using any bitcoin wallet of choice, the payment can be easily verified at the terminal by scanning it's QR code. The number of confirmations for the incoming funds is displayed and appropriate warnings are shown for zero confirmation transactions. It is up to the retailer to define their policy on number of required confirmations and presumably the size of the transaction will be a deciding factor.

Other "non account holder" transactions that are possible:

* print current exchange rates (Bitcoin vs. fiat) to a receipt

* deposit cash into bitcoin (ie. retailer is selling bitcoins)

* coins are delivered to a URL or private key.

* scan bitcoin QR to pay (retailer is selling bitcoins, paid directly to settle bitcoin debt)

* scan to verify transaction (prints amount received, and confirmation status for Coinkite transactions)

The POS terminal supports Bitcoin for all operations. Coins can be delivered as a paper wallet, directly into a Coinkite account (must be pre-existing) or into web voucher (PIN code and short URL).

==External Links==

* [https://www.coinkite.com Coinkite Home page]

* [https://www.coinkite.com/faq FAQ page]

* [https://coinkite.com/promo/wiki Sign-up]

* [http://expresscoin.com/wallets/bitcoin/coinkite How to Setup a Coinkite Bitcoin Wallet]

==References==
<references />

==Images==
[[File:Coinkite_interfaces.png|300 px|alt=Coinkite interfaces|Coinkite interfaces]]
[[File:Bitcoin-pos-terminal.png|300 px|alt=Bitcoin POs Terminal|Coinkite terminal]]
[[File:Coinkite_logo.png|300 px|alt=Coinkite logo|Coinkite logo]]
[[File:Http://i.imgur.com/AnrNck0.png|300 px|Coinkite's Bitcoin Payment Button]]

[[Category:Debit Cards]]
[[Category:Wallets]]
[[Category:EWallets]]
[[Category:HybridEWallets]]
[[Category:Mixing_Services]]
[[Category:Exchanges]]
[[Category:Shopping Cart Interfaces]]
[[Category:Services]]
[[Category:Frontends]]
[[Category:Clients]]
[[Category:Mobile]]
[[Category:Hardware Terminals]]
[[Category:Cryptobanks]]
[[Category:POS]]
[[Category:Bitcoin payment systems]]

Coinkite

2015-07-06T14:44:09Z

Btcto: /* Images */

==Coinkite==

Coinkite<ref> (15/10/2013). [https://en.wikipedia.org/wiki/Coinkite Coinkite.] ''[[Wikipedia]]''.</ref><ref> (12/11/2013). [http://www.thestar.com/news/gta/2013/11/12/bitcoin_entrepreneurs_want_to_put_virtual_coins_in_your_wallet.html "Bitcoin entrepreneurs want to put virtual coins in your wallet".] ''[[Toronto Star]]''.</ref><ref> (11/11/2013). [http://bitcoinmagazine.com/7449/exploring-the-bitcoin-alliance-of-canada-part-i/ "Bitcoin in Canada, Part I: Introducing the Bitcoin Alliance of Canada".] ''[[Bitcoin Magazine]]''.</ref><ref>nvK (10/11/2013). [https://bitcointalk.org/index.php?topic=309431.0 "(ANN) Coinkite.com (Bitcoin Wallet+Debit Card+POS Terminals)accepting invites re".] ''[[bitcointalk.org]]''.</ref><ref>KYT DOTSON (22/10/2013). [http://siliconangle.com/blog/2013/09/25/bitcoin-weekly-2013-september-25-lucky-gambler-makes-11k-btc-coinsetter-to-launch-soon-coinkite-brings-pos-solution/ "Bitcoin Weekly 2013 September 25: Lucky Gambler Makes 11k BTC, Coinsetter to Launch Soon, Coinkite Brings POS Solution".] ''[[Silicon Angle]]''.</ref><ref> (5/11/2013). [https://en.bitcoin.it/wiki/Coinkite "Coinkite".] ''[[Bitcoin Wiki]]''.</ref><ref> (5/11/2013). [https://www.coinforum.ca/discussion/461/accepting-invite-requests-for-coinkite-com "Accepting invite requests for Coinkite.com".] ''[[coinforum.ca]]''.</ref><ref> (1/11/2013). [http://www.thebitpages.com/merchants/1076 "Coinkite".] ''[[The Bit Pages]]''.</ref><ref> (2013). [http://www.linkedin.com/company/coinkite "Company: Coinkite".] ''[[LinkedIN]]''.</ref> offers a number of useful [[bitcoin]] services, including wallet and a hardware payment network.

==Main features==
* Powerful, easy to use web wallet. Receive and send bitcoin amounts from a web interface. Two factor authentication, memorable image (to resist phishing attempts) and many other security features are in place. Users are free of the burden of securing their own computer.

* [https://coinkite.com/faq/multisig Multi-Signature and shared wallets] with up to M-of-15 and options for any/all keys to be generated offline (Co-Sign Pages and Bitcoin Multisig API)

* Developers Platform, [https://coinkite.com/developers Bitkit Bitcoin API] provides simple and powerful REST integrations for adding bitcoin functions into your business / application.

* Payment Processing, customizable [https://coinkite.com/faq/pay Pay/Buy/Donate buttons] to integrate in your website or shopping cart. Works over Tor.

* Point-of-sale payment terminal. Coinkite sells a hardware device, complete with QR scanner and receipt printer that can be used to perform bitcoin transactions without a computer and in a retail setting.

* "Debit" Card. Coinkite offers all it's members a plastic card which can be used at the payment terminals, but is also useful anywhere as it was a bitcoin address in QR code on the back. Bitcoin sent to that address are linked to the user's Coinkite balance.

==Services==

* multiple sub-accounts for grouping funds (ie. "Savings", "Chequing")

* all transactions occur in the public blockchain, and there is no "internal bookkeeping" of funds.

* monthly, yearly and pay as you go membership plans are offered.

* detailed transaction logging, real-time on-screen alerts as funds as received

* multiple [[cryptocurrenies]]: bitcoin, litecoin, testnet coins are offered with equal features

====Services Links====

* [https://coinkite.com/faq/money Online wallets]

* [https://coinkite.com/faq/terminal Merchant Point-of-Sale terminals]

* [https://coinkite.com/faq/terminal Bitcoin debit cards]

==Unique [[BIP]] 32 Feature==

Coinkite is internally based on BIP 32 [[Hierarchical Deterministic]] (HD) wallets. Each new member receives a "welcome email" which contains the "xpubkey" (extended public key) for their deposits, and an *encrypted* copy of the corresponding xprivkey. The xpubkey can be used by the account owner to see all public keys associated with their account (both past and future). Combined with the "audit" feature, the user can fetch a list of all UTXO (unspent transaction outputs) associated with their account and verify the public key's subpath from the given xpubkey. Similarly, they can check the UTXO is correctly stored on the blockchain.

Coinkite has stated that in the event of the closure or other failure of the business, they will publicize the symmetric key protecting the xprivkey values that have been distributed to members. With that key, each user could recover their funds by re-generating the private keys for each UTXO.

The founders of Coinkite understood the inherent risk of trusting a third party with the private keys for your bitcoins, and this application of BIP 32 helps to address these concerns should the business disappear. The company calls this system "full reserve" since the users are in a position to verify that their funds are not being used for any other purpose than safe-keeping, while on deposit at Coinkite.

==Debit Card==

For a small fee (and included in some membership plans), Coinkite users may receive a physical card. This eases use of their Coinkite account at the POS terminal and the QR code on the rear is useful for making deposits.

==POS Terminal==

Coinkite sells a hardware device which can perform a number of transactions. It connects via GPRS (cell) or Wifi to Coinkite backend servers which perform the blockchain operations. It does not directly connect to the P2P network.

Users can log into their Coinkite account at the machine, using either their Coinkite card (and a 4-6 digit PIN, plus optionally a 2FA token) or use a one-time QR code from the Coinkite website. Once connected to their account, they can perform many types of transactions:

* print out their current balances

* scan a QR and pay it using their balance

* withdraw funds to cash (requires the retail to become the counter-party)

* deposit cash (buying coins from the retailer)

* make a printed invoice (ie. a unique bitcoin address for payment of a specific amount)

* verify a payment has been received (by scanning any receipt printed by a Coinkite terminal)

The POS terminal is also useful to enable the bitcoin-based retail business. Cashiers (authorized users) can print a receipt with QR code that maybe presented to customers as a bill in bitcoin to be paid. Once paid, using any bitcoin wallet of choice, the payment can be easily verified at the terminal by scanning it's QR code. The number of confirmations for the incoming funds is displayed and appropriate warnings are shown for zero confirmation transactions. It is up to the retailer to define their policy on number of required confirmations and presumably the size of the transaction will be a deciding factor.

Other "non account holder" transactions that are possible:

* print current exchange rates (Bitcoin vs. fiat) to a receipt

* deposit cash into bitcoin (ie. retailer is selling bitcoins)

* coins are delivered to a URL or private key.

* scan bitcoin QR to pay (retailer is selling bitcoins, paid directly to settle bitcoin debt)

* scan to verify transaction (prints amount received, and confirmation status for Coinkite transactions)

The POS terminal supports Bitcoin for all operations. Coins can be delivered as a paper wallet, directly into a Coinkite account (must be pre-existing) or into web voucher (PIN code and short URL).

==External Links==

* [https://www.coinkite.com Coinkite Home page]

* [https://www.coinkite.com/faq FAQ page]

* [https://coinkite.com/promo/wiki Sign-up]

* [http://expresscoin.com/wallets/bitcoin/coinkite How to Setup a Coinkite Bitcoin Wallet]

==References==
<references />

==Images==
[[File:Coinkite_interfaces.png|300 px|alt=Coinkite interfaces|Coinkite interfaces]]
[[File:Bitcoin-pos-terminal.png|300 px|alt=Bitcoin POs Terminal|Coinkite terminal]]
[[File:Coinkite_logo.png|300 px|alt=Coinkite logo|Coinkite logo]]
[[File:Http://i.imgur.com/AnrNck0.png|300 px|Coinkite's Bitcoin Payment Button]]

[[Category:Debit Cards]]
[[Category:Wallets]]
[[Category:EWallets]]
[[Category:HybridEWallets]]
[[Category:Mixing_Services]]
[[Category:Exchanges]]
[[Category:Shopping Cart Interfaces]]
[[Category:Services]]
[[Category:Frontends]]
[[Category:Clients]]
[[Category:Mobile]]
[[Category:Hardware Terminals]]
[[Category:Cryptobanks]]
[[Category:POS]]
[[Category:Bitcoin payment systems]]

Coinkite

2015-07-06T14:42:26Z

Btcto: /* Main features */ features update

==Coinkite==

Coinkite<ref> (15/10/2013). [https://en.wikipedia.org/wiki/Coinkite Coinkite.] ''[[Wikipedia]]''.</ref><ref> (12/11/2013). [http://www.thestar.com/news/gta/2013/11/12/bitcoin_entrepreneurs_want_to_put_virtual_coins_in_your_wallet.html "Bitcoin entrepreneurs want to put virtual coins in your wallet".] ''[[Toronto Star]]''.</ref><ref> (11/11/2013). [http://bitcoinmagazine.com/7449/exploring-the-bitcoin-alliance-of-canada-part-i/ "Bitcoin in Canada, Part I: Introducing the Bitcoin Alliance of Canada".] ''[[Bitcoin Magazine]]''.</ref><ref>nvK (10/11/2013). [https://bitcointalk.org/index.php?topic=309431.0 "(ANN) Coinkite.com (Bitcoin Wallet+Debit Card+POS Terminals)accepting invites re".] ''[[bitcointalk.org]]''.</ref><ref>KYT DOTSON (22/10/2013). [http://siliconangle.com/blog/2013/09/25/bitcoin-weekly-2013-september-25-lucky-gambler-makes-11k-btc-coinsetter-to-launch-soon-coinkite-brings-pos-solution/ "Bitcoin Weekly 2013 September 25: Lucky Gambler Makes 11k BTC, Coinsetter to Launch Soon, Coinkite Brings POS Solution".] ''[[Silicon Angle]]''.</ref><ref> (5/11/2013). [https://en.bitcoin.it/wiki/Coinkite "Coinkite".] ''[[Bitcoin Wiki]]''.</ref><ref> (5/11/2013). [https://www.coinforum.ca/discussion/461/accepting-invite-requests-for-coinkite-com "Accepting invite requests for Coinkite.com".] ''[[coinforum.ca]]''.</ref><ref> (1/11/2013). [http://www.thebitpages.com/merchants/1076 "Coinkite".] ''[[The Bit Pages]]''.</ref><ref> (2013). [http://www.linkedin.com/company/coinkite "Company: Coinkite".] ''[[LinkedIN]]''.</ref> offers a number of useful [[bitcoin]] services, including wallet and a hardware payment network.

==Main features==
* Powerful, easy to use web wallet. Receive and send bitcoin amounts from a web interface. Two factor authentication, memorable image (to resist phishing attempts) and many other security features are in place. Users are free of the burden of securing their own computer.

* [https://coinkite.com/faq/multisig Multi-Signature and shared wallets] with up to M-of-15 and options for any/all keys to be generated offline (Co-Sign Pages and Bitcoin Multisig API)

* Developers Platform, [https://coinkite.com/developers Bitkit Bitcoin API] provides simple and powerful REST integrations for adding bitcoin functions into your business / application.

* Payment Processing, customizable [https://coinkite.com/faq/pay Pay/Buy/Donate buttons] to integrate in your website or shopping cart. Works over Tor.

* Point-of-sale payment terminal. Coinkite sells a hardware device, complete with QR scanner and receipt printer that can be used to perform bitcoin transactions without a computer and in a retail setting.

* "Debit" Card. Coinkite offers all it's members a plastic card which can be used at the payment terminals, but is also useful anywhere as it was a bitcoin address in QR code on the back. Bitcoin sent to that address are linked to the user's Coinkite balance.

==Services==

* multiple sub-accounts for grouping funds (ie. "Savings", "Chequing")

* all transactions occur in the public blockchain, and there is no "internal bookkeeping" of funds.

* monthly, yearly and pay as you go membership plans are offered.

* detailed transaction logging, real-time on-screen alerts as funds as received

* multiple [[cryptocurrenies]]: bitcoin, litecoin, testnet coins are offered with equal features

====Services Links====

* [https://coinkite.com/faq/money Online wallets]

* [https://coinkite.com/faq/terminal Merchant Point-of-Sale terminals]

* [https://coinkite.com/faq/terminal Bitcoin debit cards]

==Unique [[BIP]] 32 Feature==

Coinkite is internally based on BIP 32 [[Hierarchical Deterministic]] (HD) wallets. Each new member receives a "welcome email" which contains the "xpubkey" (extended public key) for their deposits, and an *encrypted* copy of the corresponding xprivkey. The xpubkey can be used by the account owner to see all public keys associated with their account (both past and future). Combined with the "audit" feature, the user can fetch a list of all UTXO (unspent transaction outputs) associated with their account and verify the public key's subpath from the given xpubkey. Similarly, they can check the UTXO is correctly stored on the blockchain.

Coinkite has stated that in the event of the closure or other failure of the business, they will publicize the symmetric key protecting the xprivkey values that have been distributed to members. With that key, each user could recover their funds by re-generating the private keys for each UTXO.

The founders of Coinkite understood the inherent risk of trusting a third party with the private keys for your bitcoins, and this application of BIP 32 helps to address these concerns should the business disappear. The company calls this system "full reserve" since the users are in a position to verify that their funds are not being used for any other purpose than safe-keeping, while on deposit at Coinkite.

==Debit Card==

For a small fee (and included in some membership plans), Coinkite users may receive a physical card. This eases use of their Coinkite account at the POS terminal and the QR code on the rear is useful for making deposits.

==POS Terminal==

Coinkite sells a hardware device which can perform a number of transactions. It connects via GPRS (cell) or Wifi to Coinkite backend servers which perform the blockchain operations. It does not directly connect to the P2P network.

Users can log into their Coinkite account at the machine, using either their Coinkite card (and a 4-6 digit PIN, plus optionally a 2FA token) or use a one-time QR code from the Coinkite website. Once connected to their account, they can perform many types of transactions:

* print out their current balances

* scan a QR and pay it using their balance

* withdraw funds to cash (requires the retail to become the counter-party)

* deposit cash (buying coins from the retailer)

* make a printed invoice (ie. a unique bitcoin address for payment of a specific amount)

* verify a payment has been received (by scanning any receipt printed by a Coinkite terminal)

The POS terminal is also useful to enable the bitcoin-based retail business. Cashiers (authorized users) can print a receipt with QR code that maybe presented to customers as a bill in bitcoin to be paid. Once paid, using any bitcoin wallet of choice, the payment can be easily verified at the terminal by scanning it's QR code. The number of confirmations for the incoming funds is displayed and appropriate warnings are shown for zero confirmation transactions. It is up to the retailer to define their policy on number of required confirmations and presumably the size of the transaction will be a deciding factor.

Other "non account holder" transactions that are possible:

* print current exchange rates (Bitcoin vs. fiat) to a receipt

* deposit cash into bitcoin (ie. retailer is selling bitcoins)

* coins are delivered to a URL or private key.

* scan bitcoin QR to pay (retailer is selling bitcoins, paid directly to settle bitcoin debt)

* scan to verify transaction (prints amount received, and confirmation status for Coinkite transactions)

The POS terminal supports Bitcoin for all operations. Coins can be delivered as a paper wallet, directly into a Coinkite account (must be pre-existing) or into web voucher (PIN code and short URL).

==External Links==

* [https://www.coinkite.com Coinkite Home page]

* [https://www.coinkite.com/faq FAQ page]

* [https://coinkite.com/promo/wiki Sign-up]

* [http://expresscoin.com/wallets/bitcoin/coinkite How to Setup a Coinkite Bitcoin Wallet]

==References==
<references />

==Images==
[[File:Coinkite_interfaces.png|300 px|alt=Coinkite interfaces|Coinkite interfaces]]
[[File:Bitcoin-pos-terminal.png|300 px|alt=Bitcoin POs Terminal|Coinkite terminal]]
[[File:Coinkite_logo.png|300 px|alt=Coinkite logo|Coinkite logo]]

[[Category:Debit Cards]]
[[Category:Wallets]]
[[Category:EWallets]]
[[Category:HybridEWallets]]
[[Category:Mixing_Services]]
[[Category:Exchanges]]
[[Category:Shopping Cart Interfaces]]
[[Category:Services]]
[[Category:Frontends]]
[[Category:Clients]]
[[Category:Mobile]]
[[Category:Hardware Terminals]]
[[Category:Cryptobanks]]
[[Category:POS]]
[[Category:Bitcoin payment systems]]

How to accept Bitcoin, for small businesses

2015-07-06T14:35:08Z

Btcto: /* Merchant Services */

{{merge|Merchant Howto}}

This guide is intended for small business owners who wish to help promote Bitcoin by accepting it as payment for goods and services. It's written with the assumption that you operate a regular business that sells goods or services for regular national currency such as dollars, and that you wish to accept Bitcoin as another legal way to pay, and that you intend to pay taxes on your Bitcoin income just like any other income.

With Bitcoin being touted as a way to conduct anonymous transactions and as way to compete with government currency, many small business owners wonder what's the right way to accept and account Bitcoin, or if it's legal or ethical, or whether and how they should pay taxes on income received through Bitcoin.

As far as we know, Bitcoin isn't yet formally recognized by governments and authorities as a "currency". But in practice, Bitcoin is likely no different than accepting payment in other forms, such as cash, or gold, or scrip, or gift cards or foreign currency. We think that it is pretty much the same as the local businesses of Great Barrington, Massachusetts choosing to accept their locally-printed [http://www.reuters.com/article/2007/06/19/us-usa-economy-berkshares-idUSN0530157720070619 "Berkshire Bucks"] to support their local economy.

====Starting to accept Bitcoin for transactions====
Accepting Bitcoin at a small business is best started in whichever manner keeps the accounting simple for you. This will vary by the type of business you are operating.

===Start with a sign===
[[{{ns:file}}:WeAcceptBitcoin.png‎]]

If you expect that the number of people interested in using Bitcoin is small, you might simply start by posting a sign or a note: "We Accept Bitcoin", and ask people to contact you directly in order to make a payment. Even if hardly anybody uses Bitcoin as a payment method, you're helping Bitcoin in two ways: one, by increasing awareness, and two, by making your customers more willing to accept Bitcoin as payment from others in the future, because now they know somewhere they can spend it.

===Utilize a merchant solution===
If you sell things on your website (goods or services), you'll want to use a [[#Merchant Services|Bitcoin merchant solution]] to accept the Bitcoins (you can usually opt to have them converted to USD or other currencies automatically with some services).

If you sell things in a brick and mortar shop, customers can pay using hardware terminals, touch screen apps or simple wallet addresses through QR Codes.

[[File:Easybitz bitcoin pointofsale.png|400 px|alt=Accept Bitcoin without internet|EasyBitz ZeroClick System|link=https://easybitz.com/merchant]]

[[File:Bitcoin-pos-terminal.png|200 px|alt=Bitcoin POS Terminal|Coinkite terminal]] [[File:Mobile_Web_App_Bitcoin_Register.jpeg|100 px|alt=Bitcoin POS Terminal|CoinBox terminal]]

[[File:Mobile_Checkout_Phone.png|200 px|alt=Bitcoin Mobile Checkout|Coinify Mobile Checkout|link=https://coinify.com]]

===Smart Phone or Tablet===
You can use a wallet address with any wallet. For that it's best if you can place a QR code near your cash register to which the customers can scan with their phone and pay (use http://ma.eatgold.com/accept to make a QR code sign). For a more convenient solution you can use a dedicated app or webapp that generates a QR code on the fly including the amount.

==== Examples ====
Solutions for smart phones and tablets:
* [https://bitcoin.co.th/merchants/ bitcoin.co.th] mobile Bitcoin Point of Sale for Thailand
* [[File:favicon_bp.png|20px|link=https://bitcoinpay.com/static/img/]] [https://bitcoinpay.com BitcoinPay], Mobile payment terminal with EUR, USD, PLN and CZK settlements.
* [[File:BitKassa_favicon.png|20px|link=https://www.BitKassa.nl]] [https://www.BitKassa.nl BitKassa] accept Bitcoin on mobile phone, tablet, computer; converts to Euro/Bitcoin (any percentage)
* [https://bitpay.com/bitcoin-for-retail BitPay] Mobile Checkout
* [https://bitpos.me/demo.html BitPOS] Merchant POS solution for Australia
* [https://play.google.com/store/apps/details?id=info.blockchain.merchant Blockchain] Merchant for Android
* [http://www.btcxpos.com/ BTCX] POS for Sweden
* [https://coinify.com Coinify] Bitcoin Point Of Sale
* [[File:Coin_Of_Sale_logo.png|20px|link=https://coinofsale.com]] [https://coinofsale.com Coin Of Sale] - device-independent Bitcoin POS payment system
* [https://coinbase.com/docs/merchant_tools/point_of_sale Coinbase] Point Of Sale for Android
* [[File:BitcoinRegister.gif|20px|link=http://coinbox.it/merchant]][http://coinbox.it/merchant CoinBox] Bitcoin point of sale for Android
* [http://acceptbitcoin.coinpip.com CoinPip] - Bitcoin Payment Processor for Asia
* [https://cryptopay.me/products/ Cryptopay] HTML5-based bitcoin POS
* [[File:Paxful_how-to-buy-bitcoin.png |20px|link=https://paxful.com]] [https://paxful.com Paxful] Simplest Point of Sale, No Fees and a peer to peer market to buy bitcoin instantly
* [[File:Payful.png|20px|link=http://payful.io]] [http://payful.io Payful] Accept bitcoin - point of sale, shopping cart plugins and API. Supports USA, Europe and Canada.
* [https://pocketpos.ca/ PocketPOS] Bitcoin Point of Sale for Canadians, with exchange integration
* [https://gourl.io/ GoUrl] Bitcoin Mobile Checkout

===Point-of-Sale hardware terminal===
With custom hardware you can integrate with existing registers and point-of-sales solutions (examples: [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite], [https://xbterminal.com/ XBTerminal], [http://www.bitstraat.nl BitStraat]).

===Accounting===
When a customer makes a payment, you might simply issue a credit to their account. Ideally, you want to enter it in a way that suggests you received a payment. You could consider entering it as a "discount", but you may want to consider whether this inappropriately disguises the nature of the transaction. If on the other hand, you're giving "discounts" for Bitcoins, but then you are selling the Bitcoins for currency and then counting that as income, then chances are good that your calculation of income is making up for it. Ask your accountant.

===Businesses that offer gift cards===
If your business sells gift cards or gift certificates, you may find that the easiest way to accept Bitcoin is to accept it only for the purchase of gift cards, and then require the gift cards to be used for actual purchases of goods or services. This way, the accounting practices you already have in place for processing gift cards can be put to use. The accounting for Bitcoins would then be minimized to tracking sales of a single SKU.

This method is also ideal for retail food establishments and convenience stores, where the payment of Bitcoins through a mobile phone for a small daily food purchase might be cumbersome or disruptive, especially in front of a line of other customers. Bitcoins in this case would be best used to reload prepaid cards that can then be swiped at point-of-sale.

If you don't accept gift cards, but you already accept credit cards through a swipe terminal, consider the possibility that you could add a retail gift card system through the swipe terminal you already own. Many point-of-sale terminals, including ones from VeriFone®, are designed around the ability to support multiple applications on the same terminal. Gift cards are also highly profitable because of "breakage", or in other words, the fact that a significant percentage of them never get redeemed.

You could consider adding a private label gift card program from a provider who specializes in this, not just as a jumpstart to accepting Bitcoins, but as an extra boost to income. A private label gift card service provider necessarily have to handle your funds - they can simply provide a solution that keeps track of the balance on the cards on your behalf, including features that allow users to check their balances by phone or by web. Such a solution, of course, is also what makes the cards swipeable through the card reader.

===Businesses that mail invoices===
Does your business send out invoices to customers? Adding one line may make a huge impact for the Bitcoin economy. Perhaps you list it as a payment option just after Visa, MasterCard, and American Express, even if that means your customer must call or e-mail to make a payment.

If you have access to the programming expertise such that you can generate Bitcoin addresses programmatically, consider generating a brand new Bitcoin address for each invoice, and print it on the invoice. When a Bitcoin payment arrives, you'll automatically know where it should arrive.

Customers might wonder how much BTC they should pay in order to satisfy an invoice in full. Your invoice might suggest an amount. For example, if your invoice is for $100 and BTC's are currently worth $1.24 each, your invoice might suggest that it can be paid in full ''"with a payment of 80.65 BTC if paid by (date)"''.

You might be able to anticipate the possibility that even though a Bitcoin address can be printed on an invoice or payment stub, that they are very cumbersome for most people to type, especially being a mix of uppercase and lowercase letters. However, you should probably still do it anyway. The customer is probably going to want some paper trail for his payment. Giving him a pre-printed payment stub with a pre-printed address will satisfy that, because the customer can independently and publicly prove through [[Block Explorer]] that the payment took place.

Does your business have a website? On your invoice, consider allowing them to go to a special URL to get the address to make a Bitcoin payment just by typing in their invoice number. For example, ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc'' with a form they can enter their invoice number, or just ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc/60365'' for paying invoice #60365. This way, they can see the Bitcoin address, copy and paste it directly into their Bitcoin client.

Use a brand new address for each invoice whenever possible, and use it only once. This benefits the customer as it removes any ambiguity as to which customer is making which payment and for which invoice.

Known payment systems supporting invoicing, and recurring invoice setup, [https://coinify.com/checkout/invoice/cb/bb Coinify]

Online wallet supporting invoicing, subscriptions and recurrent payments, [https://www.xcoinmoney.com/info/sending-paying-invoices xCoinMoney]

===Avoiding fraud===

You should also consider the possible risk that fraudsters could send counterfeit invoices to your customers, and entice them to make a payment to a Bitcoin address they control, instead of you. While that isn't likely in general - it depends on how well a fraudster could find out who your customers are in the first place - it would certainly be an unpleasant situation if it ever happened. One way you could control that is, whenever possible, never let people try to type Bitcoin addresses off payment stubs - instead, force people to get the full Bitcoin address from your website via secure SSL. But, still print ''most'' of the address on the payment stub (perhaps with four or five characters starred out), so that the customer's need for a paper trail can be satisfied, so they can prove they paid if there is ever a dispute. Merchants can also use the IP address geolocation to understand the close proximity of users. There is automated solution such as [https://www.fraudlabspro.com FraudLabs Pro] that automates the screening of Bitcoin transactions to determine risk level.

==Setting Prices==

When a business accepts bitcoins for payment, there generally is the need to convert them to the currencies used for paying suppliers, employees and shareholders. Some merchants set prices based on the current market rate at the time the price quote is presented to the customer (merchant services like [[File:Polycoin_favicon.png|20px|link=http://www.polycoin.io]] [http://www.polycoin.io Polycoin], [https://coinify.com Coinify], [[File:Favicon-32x32_.png|20px|link=https://bitcoinpay.com]] [https://bitcoinpay.com BitcoinPay], [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase] or [http://paysius.com Paysius] do this automatically).

[[Bitcoin Prices]] lists the exchange rate for many currencies on multiple exchanges.

When prices are determined using an automated process, the current market rate can be based on either a current price or on a weighted average basis. [[Bitcoin Charts]] provides a [http://bitcoincharts.com/about/markets-api data feed that provides weighted prices]. [[Bitcoin Average]] also offers a weighted average price index, featuring average price across all exchanges reachable in the world and in over 150 currencies. 24h sliding average price index is also available and all data is [https://bitcoinaverage.com/api.htm reachable through the API].

When bitcoin funds for purchases are received, some merchants instantly exchange those proceeds into the preferred currency used (again done automatically by [[File:Polycoin_favicon.png|20px|link=http://www.polycoin.io]] [http://www.polycoin.io Polycoin], [https://coinify.com Coinify], [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase] or [[File:Favicon-32x32_.png|20px|link=https://bitcoinpay.com]] [https://bitcoinpay.com BitcoinPay]. Hedging for each transaction can nearly entirely eliminate exchange rate risk that the business is exposed to when accepting bitcoins for payment.

==Contract==

A sales contract might be used to ensure that specific terms are met to lessen the chances of a misunderstanding. For instance, the party sending payment is responsible for paying any [[transaction fee]] that might be necessary. A contract might specify that a transaction fee must be paid and what amount, so as to prevent the situation where the transaction is considered a low priority transaction and thus isn't confirmed quickly.

Other items that might be addressed in a contract:

* Requirement and handling of escrow through an [[:Category:Escrow_services|escrow service]].
* Jurisdiction for disputes.
* Refund policy (particularly with the exchange rate being volatile)

==Paying taxes on Bitcoin income==
[[Tax compliance]] is a topic of concern for small businesses. We aren't accountants or lawyers, and can't give legal or accounting advice.

But in many respects, Bitcoin transactions work very much like cash. Just like Bitcoin, cash is anonymous and doesn't leave a paper trail, yet is widely used in commerce every day.

Ask yourself how you would handle a cash transaction. Do you accept cash transactions? Do you normally pay taxes on cash transactions? The answer for Bitcoin should probably be the same.

As for how to decide what a Bitcoin transaction is worth... the IRS, as far as we know, has never issued a guide mentioning how to value Bitcoin transactions. But they probably have rules and guidelines on how to value transactions made in foreign currency or "cash equivalents". We imagine the accounting would be similar.

With Bitcoins, there's likely to be some difference between the value of BTC when you received them as payment, versus when you go to exchange them for another currency like USD, should you decide to do so. This scenario, likewise, would be no different if you accepted foreign currency or gold as payment. Under some scenarios, it might make sense to book the dollar value of BTC income as it is received, and then to book any difference incurred when it is exchanged for fiat currency. Under others, it might make sense to book the whole thing at the time of exchange.

Perhaps you might talk to your accountant. You don't need to get into a discussion with your accountant about block chains and private keys or the philosophy behind a decentralized currency. By comparing the fundamentals of Bitcoins to accounting concepts already well understood by the public, you can probably get all the answers you need. What would you ask your accountant if you decided that you wanted to accept ''Berkshire Bucks'' or 1-ounce gold coins as payment?

== Merchant Services ==
* [https://apicoin.io Apicoin.io] A robust, secure api to connect to the bitcoin network.
* [http://www.btc4erp.com Bitcoin Transaction Coordinator] Full Merchant Solution for organizations using the NetSuite Global ERP and eCommerce Platform
* [[File:favicon_bp.png|20px|link=https://bitcoinpay.com/static/img/]] [https://bitcoinpay.com BitcoinPay] Payment gateway for virtual currencies with direct settlement to PLN, CZK, EUR and USD. POS + API.
* [[File:Bitfavicon.png|20px|link=http://www.bitcoinpaygate.com]] [http://www.bitcoinpaygate.com Bitcoinpaygate] Bitcoin payment processing for the web & in store payments
* [[File:BitKassa_favicon.png|20px|link=https://www.BitKassa.nl]] [https://www.BitKassa.nl BitKassa] Merchant solution for accepting Bitcoin, getting Euro or Euro/Bitcoin percentage. The Netherlands.
* [https://bitmerch.com BitMerch] Provides HTML buttons to start accepting bitcoins instantly. No server side setup required.
* [https://www.bitpagos.net BitPagos] Bitcoin and Credit Card payment processor
* [https://www.bitpay.com BitPay] Bitcoin payment processor with mobile checkout solution
* [https://bitpos.me BitPOS] Bitcoin payment processor for online and brick and mortar stores
* [http://www.bitstraat.nl BitStraat] Merchant POS solution for accepting Bitcoin
* [http://blockchain.info/api/api_receive Blockchain.info] Free APIs to process bitcoin payments. No sign up or account needed.
* [https://www.btcmerch.com BTCMerch] Payment processor for bitcoins and other cryptocurrencies. 0.5% transaction fee. Sandbox is available.
* [https://coinbase.com/docs/merchant_tools/payment_buttons Coinbase] Offers payment buttons, checkout pages, shopping cart integration, and daily cash out to USD.
* [[File:BitcoinRegister.gif|20px|link=http://coinbox.it/merchant]] [http://coinbox.it/merchant CoinBox] Bitcoin Point of Sales application for Android, with integration into various exchanges. Similar to Square.
* [https://coinify.com Coinify] Payment Service Provider (PSP) specializing in the technical aspects of accepting cryptocurrencies - such as bitcoin. Supports Bitcoin Web Payments, Mobile Checkout, In-store Bitcoin Payments and Bitcoin Invoicing with recurring billing in bitcoin.
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/faq/terminal Coinkite] Secure wallet multisig, payment buttons, invoice pages, hardware POS terminals, and Debit-Cards.
* [https://coinpip.com/ CoinPip] Online and POS bitcoin payment processor for Asia.
* [https://coinvoice.com/ Coinvoice] Invoice in USD or BTC, Get paid in USD or BTC.
* [https://coinvoy.net Coinvoy] Free Payment Gateway with built-in exchange
* [https://cryptopay.me Cryptopay] European payment gateway with daily payouts in GBP, EUR and USD. Exchange and wallet integrated.
* [https://cubits.com Cubits] Platform with multisignature wallets and merchant system Cubits Pay.
* [[File:Paxful_how-to-buy-bitcoin.png |20px|link=https://paxful.com]] [https://paxful.com Paxful] Accept Bitcoin with no internet then sell bitcoin for profit on our peer to peer exchange.
* [http://fasterco.in Fasterco.in] Bitcoin payment processing for merchants and day-traders
* [[File:gocoin-logo.png|20px|link=https://www.gocoin.com]] [https://www.gocoin.com/docs GoCoin International payment gateway and processing platform for Merchants]
* [https://gourl.io Gourl.io] Bitcoin Payment processor with ready to use php scripts - Pay-Per-Download, Pay-Per-Product, Pay-Per-Membership, Pay-Per-Registration.
* [[File:inpay_favicon.png|link=https://inpay.pl/?lang=en]] [https://inpay.pl/?lang=en InPay.pl] InPay was created to enable entrepreneurs to accept Bitcoin in PLN, EUR and USD.
* [[File:MCS_200by200_logo-01.png|20px|link=http://www.mycoinsolution.com]][http://www.mycoinsolution.com My Coin Solution] - Bitcoin consulting services and solutions
* [https://www.okpay.com/en/services/accept-payments/index.html OKPAY] Bitcoin payment processing for merchants
* [[File:Payful.png|20px|link=http://payful.io]] [http://payful.io Payful] Accept bitcoin - point of sale, shopping cart plugins and API. Supports payment processing in US dollars, Euros and Canadian dollars.
* [[File:Polycoin_favicon.png|20px|link=http://www.polycoin.io]] [http://www.polycoin.io Polycoin] Bitcoin payment processing platform with solutions for the financial sector
* [https://pocketpos.ca/ PocketPOS] Bitcoin Point of Sale for Canadians, including merchant integration for CAD / BTC exchange.
* [http://snowcron.com Snowcron] Bitcoin Store Engine: Handles payments, sends your customers information they ordered (reg. codes, passwords...) No web programming required.
* [https://xbterminal.com/ XBTerminal] Brick-and-mortar hardware POS terminals with payment processing integrations.
* [https://www.xcoinmoney.com/ xCoinMoney] Online wallet for instant payment and subscriptions.

==See Also==

* [[Merchant Howto]]
* [[In-store Transactions]]
* [[Tax compliance]]
* [[Securing online services]]
* [[BitCoins Mobile]] provides accurate up to date pricing from multiple exchanges from your Apple iPad, iPhone, or iPod Touch.
* [[Bitcoin PayFlow]] automates the process for accepting bitcoins
* [[Lazy API]] The lazy (and possibly easiest?) way to accept bitcoin payments on your website

[[Category:ECommerce]]
[[Category:Local]]

[[de:Bitcoin_als_Geschäft_akzeptieren]]

Flexcoin

2014-03-05T06:06:49Z

Btcto:

{{delete| Hacked, may confuse new users }}
[[File:FlexcoinLogo.jpg]] 

Flexcoin is an [[EWallet]] run by Flexcoin Inc in Edmonton Alberta Canada.

Flexcoin differentiates itself from [[EWallet]](s) by providing a paid "discount" to account holders. It generates revenue by charging small transaction fees on outgoing bitcoins but no fees are charged from flexcoin to flexcoin accounts. These fees are for the most part forwarded back to the account holders via a "discount" payment.

Flexcoin has been running on an invite only process in June 2011, invites were filled within minutes of releasing them.
Flexcoin went live on August 4th 2011 to the general public.
Flexcoin was sold from [http://www.yooter.com Yooter] to a group of Edmonton based investors, headed by James Gray on March 14th 2012.

Flexcoin offers users an alternative to Bitcoin addresses in the form of personalized addresses:

Example :
 
Bitcoin: Pay for your coffee at bitcoin address 1555hjPG7pRwTHVMfukPvjXexQMHFE3qu6
 
flexcoin: Pay for your coffee with flexcoin id '''coffeeshop'''
 

As with most [[EWallet]]s, transfers within flexcoin are instant, meaning no next block wait.

Flexcoin was one of the first bitcoin eWallets based in the United States and is the first to label itself as a "bank" (though not legally registered as a bank).

==External links==
* [http://www.flexcoin.com flexcoin] website

[[Category:eWallets]]
[[Category:Financial]]

Deterministic wallet

2014-03-04T21:18:52Z

Btcto: /* Benefits */

A deterministic wallet is a system of deriving keys from a single starting point known as a seed. The seed allows a user to easily back up and restore a wallet without needing any other information and can in some cases allow the creation of public addresses without the knowledge of the private key.

== Benefits ==

Early clients such as the [[Satoshi client]] generate a buffer of fresh random private keys to be used as receiving and [[change|change addresses]] in the future. This has the effect of invalidating backups after a short period when the keypool buffer (typically 100 addresses) is exhausted, deterministic wallets can generate an unlimited number of addresses on the fly and as such don't suffer from this issue. As the addresses are generated in a known fashion rather than randomly some clients can be used on multiple devices without the risk of losing funds. Users can conveniently create a single backup of the seed in a human readable format that will last the life of the wallet, without the worry of this backup becoming stale.

Certain types of deterministic wallet (BIP0032, Armory and [[Coinkite]] ) additionally allow for the complete separation of private and public key creation for greater security and convenience. In this model a server can be set up to only know the Master Public Key of a particular deterministic wallet. This allows the server to create as many public keys as is necessary for receiving funds, but a compromise of the MPK will not allow an attacker to spend from the wallet. They can alternatively be used in [[Electrum]] and [[Armory]] to enable completely offline storage and spending, where an offline computer knows the private key and an online one knows only the MPK. Transactions spending coins are ferried between the two computers via USB storage which avoids exposing the offline computer to a network-based attack.

==Types==

===Type 1 deterministic wallet===
A type 1 deterministic wallet is a simple method of generating addresses from a known starting string, as such it does not allow advanced features such as a Master Public Key. To generate a private key take SHA256(string + n), where n is an ASCII-coded number that starts from 1 and increments as additional keys are needed.

This type of wallet can be created by Casascius Bitcoin Address Utility.

===Type 2 hierarchical deterministic wallet===
This wallet type is described in [[BIP 0032]] and is fully implemented in [[Electrum]] and [[CarbonWallet]]. The seed is a random 128 bit value presented to the user as a 12 word mnemonic using common English words. The seed is used after 100,000 rounds of SHA256 to slow down attacks against weak user-chosen strings. [https://bitcointalk.org/index.php?topic=330672.msg3547258#msg3547258].

The initial description and workings of this wallet type is credited to Gregory Maxwell. [https://bitcointalk.org/index.php?topic=19137.msg239768#msg239768]

===Armory deterministic wallet===
[[Armory]] has its own Type-2 deterministic wallet format based on a "root key" and a "chain code." Earlier versions of Armory required backing up both the "root key" and "chaincode," while newer versions start deriving the chaincode from the private key in a non-reversible way. These newer Armory wallets (0.89+) only require the single, 256-bit root key. This older format is intended to be phased out in favor of the standard BIP0032 format. [https://bitcointalk.org/index.php?topic=351099.msg3770818#msg3770818]

Coinkite

2013-12-05T16:32:41Z

Btcto:

==Coinkite==

Coinkite<ref> (15/10/2013). [https://en.wikipedia.org/wiki/Coinkite Coinkite.] ''[[Wikipedia]]''.</ref><ref> (12/11/2013). [http://www.thestar.com/news/gta/2013/11/12/bitcoin_entrepreneurs_want_to_put_virtual_coins_in_your_wallet.html "Bitcoin entrepreneurs want to put virtual coins in your wallet".] ''[[Toronto Star]]''.</ref><ref> (11/11/2013). [http://bitcoinmagazine.com/7449/exploring-the-bitcoin-alliance-of-canada-part-i/ "Bitcoin in Canada, Part I: Introducing the Bitcoin Alliance of Canada".] ''[[Bitcoin Magazine]]''.</ref><ref>nvK (10/11/2013). [https://bitcointalk.org/index.php?topic=309431.0 "(ANN) Coinkite.com (Bitcoin Wallet+Debit Card+POS Terminals)accepting invites re".] ''[[bitcointalk.org]]''.</ref><ref>KYT DOTSON (22/10/2013). [http://siliconangle.com/blog/2013/09/25/bitcoin-weekly-2013-september-25-lucky-gambler-makes-11k-btc-coinsetter-to-launch-soon-coinkite-brings-pos-solution/ "Bitcoin Weekly 2013 September 25: Lucky Gambler Makes 11k BTC, Coinsetter to Launch Soon, Coinkite Brings POS Solution".] ''[[Silicon Angle]]''.</ref><ref> (5/11/2013). [https://en.bitcoin.it/wiki/Coinkite "Coinkite".] ''[[Bitcoin Wiki]]''.</ref><ref> (5/11/2013). [https://www.coinforum.ca/discussion/461/accepting-invite-requests-for-coinkite-com "Accepting invite requests for Coinkite.com".] ''[[coinforum.ca]]''.</ref><ref> (1/11/2013). [http://www.thebitpages.com/merchants/1076 "Coinkite".] ''[[The Bit Pages]]''.</ref><ref> (2013). [http://www.linkedin.com/company/coinkite "Company: Coinkite".] ''[[LinkedIN]]''.</ref> offers a number of useful [[bitcoin]] and [[litecoin]] services, including wallet and a hardware payment network.

==Main features==
* Powerful, easy to use web wallet. Receive and send bitcoin amounts from a web interface. Two factor authentication, memorable image (to resist phishing attempts) and many other security features are in place. Users are free of the burden of securing their own computer.

* Point-of-sale payment terminal. Coinkite sells a hardware device, complete with QR scanner and receipt printer that can be used to perform bitcoin transactions without a computer and in a retail setting.

* "Debit" Card. Coinkite offers all it's members a plastic card which can be used at the payment terminals, but is also useful anywhere as it was a bitcoin address in QR code on the back. Bitcoin sent to that address are linked to the user's Coinkite balance.

==Services==

* multiple sub-accounts for grouping funds (ie. "Savings", "Chequing")

* all transactions occur in the public blockchain, and there is no "internal bookkeeping" of funds.

* monthly, yearly and pay as you go membership plans are offered.

* detailed transaction logging, real-time on-screen alerts as funds as received

* multiple [[cryptocurrenies]]: bitcoin, litecoin, testnet coins are offered with equal features

* Coinkite is the first Litecoin web wallet on the market (Oct 2013)

====Services Links====

* [https://coinkite.com/faq/money Online wallets]

* [https://coinkite.com/faq/terminal Merchant Point-of-Sale terminals]

* [https://coinkite.com/faq/terminal Bitcoin debit cards]

==Unique [[BIP]] 32 Feature==

Coinkite is internally based on BIP 32 [[Hierarchical Deterministic]] (HD) wallets. Each new member receives a "welcome email" which contains the "xpubkey" (extended public key) for their deposits, and an *encrypted* copy of the corresponding xprivkey. The xpubkey (used for both Litecoin and Bitcoin) can be used by the account owner to see all public keys associated with their account (both past and future). Combined with the "audit" feature, the user can fetch a list of all UTXO (unspent transaction outputs) associated with their account and verify the public key's subpath from the given xpubkey. Similarly, they can check the UTXO is correctly stored on the blockchain.

Coinkite has stated that in the event of the closure or other failure of the business, they will publicize the symmetric key protecting the xprivkey values that have been distributed to members. With that key, each user could recover their funds by re-generating the private keys for each UTXO.

The founders of Coinkite understood the inherent risk of trusting a third party with the private keys for your bitcoins, and this application of BIP 32 helps to address these concerns should the business disappear. The company calls this system "full reserve" since the users are in a position to verify that their funds are not being used for any other purpose than safe-keeping, while on deposit at Coinkite.

==Debit Card==

For a small fee (and included in some membership plans), Coinkite users may receive a physical card. This eases use of their Coinkite account at the POS terminal and the QR code on the rear is useful for making deposits.

==POS Terminal==

Coinkite sells a hardware device which can perform a number of transactions. It connects via GPRS (cell) or Wifi to Coinkite backend servers which perform the blockchain operations. It does not directly connect to the P2P network.

Users can log into their Coinkite account at the machine, using either their Coinkite card (and a 4-6 digit PIN, plus optionally a 2FA token) or use a one-time QR code from the Coinkite website. Once connected to their account, they can perform many types of transactions:

* print out their current balances

* scan a QR and pay it using their balance

* withdraw funds to cash (requires the retail to become the counter-party)

* deposit cash (buying coins from the retailer)

* make a printed invoice (ie. a unique bitcoin address for payment of a specific amount)

* verify a payment has been received (by scanning any receipt printed by a Coinkite terminal)

The POS terminal is also useful to enable the bitcoin-based retail business. Cashiers (authorized users) can print a receipt with QR code that maybe presented to customers as a bill in bitcoin to be paid. Once paid, using any bitcoin wallet of choice, the payment can be easily verified at the terminal by scanning it's QR code. The number of confirmations for the incoming funds is displayed and appropriate warnings are shown for zero confirmation transactions. It is up to the retailer to define their policy on number of required confirmations and presumably the size of the transaction will be a deciding factor.

Other "non account holder" transactions that are possible:

* print current exchange rates (Bitcoin vs. fiat) to a receipt

* deposit cash into bitcoin/litecoin (ie. retailer is selling bitcoins)

* coins are delivered to a URL or private key.

* scan bitcoin QR to pay (retailer is selling bitcoins, paid directly to settle bitcoin debt)

* scan to verify transaction (prints amount received, and confirmation status for Coinkite transactions)

The POS terminal supports both Litecoin and Bitcoin for all operations. Coins can be delivered as a paper wallet, directly into a Coinkite account (must be pre-existing) or into web voucher (PIN code and short URL).

==External Links==

* [https://www.coinkite.com Coinkite Home page]

* [https://www.coinkite.com/faq FAQ page]

* [https://coinkite.com/promo/wiki Sign-up]

==References==
<references />

==Images==
[[File:Coinkite_interfaces.png|300 px|alt=Coinkite interfaces|Coinkite interfaces]]
[[File:Bitcoin-pos-terminal.png|300 px|alt=Bitcoin POs Terminal|Coinkite terminal]]
[[File:Coinkite_logo.png|300 px|alt=Coinkite logo|Coinkite logo]]

[[Category:Debit Cards]]
[[Category:Wallets]]
[[Category:EWallets]]
[[Category:HybridEWallets]]
[[Category:Mixing_Services]]
[[Category:Exchanges]]
[[Category:Shopping Cart Interfaces]]
[[Category:Services]]
[[Category:Frontends]]
[[Category:Clients]]
[[Category:Mobile]]
[[Category:Block chain browsers]]
[[Category:Hardware Terminals]]
[[Category:Cryptobanks]]
[[Category:POS]]
[[Category:Bitcoin payment systems]]

Coinkite

2013-12-04T04:46:06Z

Btcto: /* Coinkite */ fix link

==Coinkite==

Coinkite<ref> (15/10/2013). [https://en.wikipedia.org/wiki/Coinkite Coinkite.] ''[[Wikipedia]]''.</ref><ref> (12/11/2013). [http://www.thestar.com/news/gta/2013/11/12/bitcoin_entrepreneurs_want_to_put_virtual_coins_in_your_wallet.html "Bitcoin entrepreneurs want to put virtual coins in your wallet".] ''[[Toronto Star]]''.</ref><ref> (11/11/2013). [http://bitcoinmagazine.com/7449/exploring-the-bitcoin-alliance-of-canada-part-i/ "Bitcoin in Canada, Part I: Introducing the Bitcoin Alliance of Canada".] ''[[Bitcoin Magazine]]''.</ref><ref>nvK (10/11/2013). [https://bitcointalk.org/index.php?topic=309431.0 "(ANN) Coinkite.com (Bitcoin Wallet+Debit Card+POS Terminals)accepting invites re".] ''[[bitcointalk.org]]''.</ref><ref>KYT DOTSON (22/10/2013). [http://siliconangle.com/blog/2013/09/25/bitcoin-weekly-2013-september-25-lucky-gambler-makes-11k-btc-coinsetter-to-launch-soon-coinkite-brings-pos-solution/ "Bitcoin Weekly 2013 September 25: Lucky Gambler Makes 11k BTC, Coinsetter to Launch Soon, Coinkite Brings POS Solution".] ''[[Silicon Angle]]''.</ref><ref> (5/11/2013). [https://en.bitcoin.it/wiki/Coinkite "Coinkite".] ''[[Bitcoin Wiki]]''.</ref><ref> (5/11/2013). [https://www.coinforum.ca/discussion/461/accepting-invite-requests-for-coinkite-com "Accepting invite requests for Coinkite.com".] ''[[coinforum.ca]]''.</ref><ref> (1/11/2013). [http://www.thebitpages.com/merchants/1076 "Coinkite".] ''[[The Bit Pages]]''.</ref><ref> (2013). [http://www.linkedin.com/company/coinkite "Company: Coinkite".] ''[[LinkedIN]]''.</ref> offers a number of useful [[bitcoin]] and [[litecoin]] services. It aims to become a full service [[cryptobank]] and safe place for holding coins for immediate use and long-term saving.

==Main features==
* Powerful, easy to use web wallet. Receive and send bitcoin amounts from a web interface. Two factor authentication, memorable image (to resist phishing attempts) and many other security features are in place. Users are free of the burden of securing their own computer.

* Point-of-sale payment terminal. Coinkite sells a hardware device, complete with QR scanner and receipt printer that can be used to perform bitcoin transactions without a computer and in a retail setting.

* "Debit" Card. Coinkite offers all it's members a plastic card which can be used at the payment terminals, but is also useful anywhere as it was a bitcoin address in QR code on the back. Bitcoin sent to that address are linked to the user's Coinkite balance.

==Services==

* multiple sub-accounts for grouping funds (ie. "Savings", "Chequing")

* all transactions occur in the public blockchain, and there is no "internal bookkeeping" of funds.

* monthly, yearly and pay as you go membership plans are offered.

* detailed transaction logging, real-time on-screen alerts as funds as received

* multiple [[cryptocurrenies]]: bitcoin, litecoin, testnet coins are offered with equal features

* Coinkite is the first Litecoin web wallet on the market (Oct 2013)

====Services Links====

* [https://coinkite.com/faq/money Online wallets]

* [https://coinkite.com/faq/terminal Merchant Point-of-Sale terminals]

* [https://coinkite.com/faq/terminal Bitcoin debit cards]

==Unique [[BIP]] 32 Feature==

Coinkite is internally based on BIP 32 [[Hierarchical Deterministic]] (HD) wallets. Each new member receives a "welcome email" which contains the "xpubkey" (extended public key) for their deposits, and an *encrypted* copy of the corresponding xprivkey. The xpubkey (used for both Litecoin and Bitcoin) can be used by the account owner to see all public keys associated with their account (both past and future). Combined with the "audit" feature, the user can fetch a list of all UTXO (unspent transaction outputs) associated with their account and verify the public key's subpath from the given xpubkey. Similarly, they can check the UTXO is correctly stored on the blockchain.

Coinkite has stated that in the event of the closure or other failure of the business, they will publicize the symmetric key protecting the xprivkey values that have been distributed to members. With that key, each user could recover their funds by re-generating the private keys for each UTXO.

The founders of Coinkite understood the inherent risk of trusting a third party with the private keys for your bitcoins, and this application of BIP 32 helps to address these concerns should the business disappear. The company calls this system "full reserve" since the users are in a position to verify that their funds are not being used for any other purpose than safe-keeping, while on deposit at Coinkite.

==Debit Card==

For a small fee (and included in some membership plans), Coinkite users may receive a physical card. This eases use of their Coinkite account at the POS terminal and the QR code on the rear is useful for making deposits.

==POS Terminal==

Coinkite sells a hardware device which can perform a number of transactions. It connects via GPRS (cell) or Wifi to Coinkite backend servers which perform the blockchain operations. It does not directly connect to the P2P network.

Users can log into their Coinkite account at the machine, using either their Coinkite card (and a 4-6 digit PIN, plus optionally a 2FA token) or use a one-time QR code from the Coinkite website. Once connected to their account, they can perform many types of transactions:

* print out their current balances

* scan a QR and pay it using their balance

* withdraw funds to cash (requires the retail to become the counter-party)

* deposit cash (buying coins from the retailer)

* make a printed invoice (ie. a unique bitcoin address for payment of a specific amount)

* verify a payment has been received (by scanning any receipt printed by a Coinkite terminal)

The POS terminal is also useful to enable the bitcoin-based retail business. Cashiers (authorized users) can print a receipt with QR code that maybe presented to customers as a bill in bitcoin to be paid. Once paid, using any bitcoin wallet of choice, the payment can be easily verified at the terminal by scanning it's QR code. The number of confirmations for the incoming funds is displayed and appropriate warnings are shown for zero confirmation transactions. It is up to the retailer to define their policy on number of required confirmations and presumably the size of the transaction will be a deciding factor.

Other "non account holder" transactions that are possible:

* print current exchange rates (Bitcoin vs. fiat) to a receipt

* deposit cash into bitcoin/litecoin (ie. retailer is selling bitcoins)

* coins are delivered to a URL or private key.

* scan bitcoin QR to pay (retailer is selling bitcoins, paid directly to settle bitcoin debt)

* scan to verify transaction (prints amount received, and confirmation status for Coinkite transactions)

The POS terminal supports both Litecoin and Bitcoin for all operations. Coins can be delivered as a paper wallet, directly into a Coinkite account (must be pre-existing) or into web voucher (PIN code and short URL).

==External Links==

* [https://www.coinkite.com Coinkite Home page]

* [https://www.coinkite.com/faq FAQ page]

* [https://coinkite.com/promo/wiki Sign-up]

==References==
<references />

==Images==
[[File:Coinkite_interfaces.png|300 px|alt=Coinkite interfaces|Coinkite interfaces]]
[[File:Bitcoin-pos-terminal.png|300 px|alt=Bitcoin POs Terminal|Coinkite terminal]]
[[File:Coinkite_logo.png|300 px|alt=Coinkite logo|Coinkite logo]]

[[Category:Debit Cards]]
[[Category:Wallets]]
[[Category:EWallets]]
[[Category:HybridEWallets]]
[[Category:Mixing_Services]]
[[Category:Exchanges]]
[[Category:Shopping Cart Interfaces]]
[[Category:Services]]
[[Category:Frontends]]
[[Category:Clients]]
[[Category:Mobile]]
[[Category:Block chain browsers]]
[[Category:Hardware Terminals]]
[[Category:Cryptobanks]]
[[Category:POS]]
[[Category:Bitcoin payment systems]]

Coinkite

2013-11-29T05:08:06Z

Btcto: /* Unique BIP 32 Feature */

==Coinkite==

Coinkite<ref> (15/10/2013). [https://en.wikipedia.org/wiki/Coinkite "Coinkite".] ''[[Wikipedia]]''.</ref><ref> (12/11/2013). [http://www.thestar.com/news/gta/2013/11/12/bitcoin_entrepreneurs_want_to_put_virtual_coins_in_your_wallet.html "Bitcoin entrepreneurs want to put virtual coins in your wallet".] ''[[Toronto Star]]''.</ref><ref> (11/11/2013). [http://bitcoinmagazine.com/7449/exploring-the-bitcoin-alliance-of-canada-part-i/ "Bitcoin in Canada, Part I: Introducing the Bitcoin Alliance of Canada".] ''[[Bitcoin Magazine]]''.</ref><ref>nvK (10/11/2013). [https://bitcointalk.org/index.php?topic=309431.0 "(ANN) Coinkite.com (Bitcoin Wallet+Debit Card+POS Terminals)accepting invites re".] ''[[bitcointalk.org]]''.</ref><ref>KYT DOTSON (22/10/2013). [http://siliconangle.com/blog/2013/09/25/bitcoin-weekly-2013-september-25-lucky-gambler-makes-11k-btc-coinsetter-to-launch-soon-coinkite-brings-pos-solution/ "Bitcoin Weekly 2013 September 25: Lucky Gambler Makes 11k BTC, Coinsetter to Launch Soon, Coinkite Brings POS Solution".] ''[[Silicon Angle]]''.</ref><ref> (5/11/2013). [https://en.bitcoin.it/wiki/Coinkite "Coinkite".] ''[[Bitcoin Wiki]]''.</ref><ref> (5/11/2013). [https://www.coinforum.ca/discussion/461/accepting-invite-requests-for-coinkite-com "Accepting invite requests for Coinkite.com".] ''[[coinforum.ca]]''.</ref><ref> (1/11/2013). [http://www.thebitpages.com/merchants/1076 "Coinkite".] ''[[The Bit Pages]]''.</ref><ref> (2013). [http://www.linkedin.com/company/coinkite "Company: Coinkite".] ''[[LinkedIN]]''.</ref> offers a number of useful [[bitcoin]] and [[litecoin]] services. It aims to become a full service [[cryptobank]] and safe place for holding coins for immediate use and long-term saving.

==Main features==
* Powerful, easy to use web wallet. Receive and send bitcoin amounts from a web interface. Two factor authentication, memorable image (to resist phishing attempts) and many other security features are in place. Users are free of the burden of securing their own computer.

* Point-of-sale payment terminal. Coinkite sells a hardware device, complete with QR scanner and receipt printer that can be used to perform bitcoin transactions without a computer and in a retail setting.

* "Debit" Card. Coinkite offers all it's members a plastic card which can be used at the payment terminals, but is also useful anywhere as it was a bitcoin address in QR code on the back. Bitcoin sent to that address are linked to the user's Coinkite balance.

==Services==

* multiple sub-accounts for grouping funds (ie. "Savings", "Chequing")

* all transactions occur in the public blockchain, and there is no "internal bookkeeping" of funds.

* monthly, yearly and pay as you go membership plans are offered.

* detailed transaction logging, real-time on-screen alerts as funds as received

* multiple [[cryptocurrenies]]: bitcoin, litecoin, testnet coins are offered with equal features

* Coinkite is the first Litecoin web wallet on the market (Oct 2013)

====Services Links====

* [https://coinkite.com/faq/money Online wallets]

* [https://coinkite.com/faq/terminal Merchant Point-of-Sale terminals]

* [https://coinkite.com/faq/terminal Bitcoin debit cards]

==Unique [[BIP]] 32 Feature==

Coinkite is internally based on BIP 32 [[Hierarchical Deterministic]] (HD) wallets. Each new member receives a "welcome email" which contains the "xpubkey" (extended public key) for their deposits, and an *encrypted* copy of the corresponding xprivkey. The xpubkey (used for both Litecoin and Bitcoin) can be used by the account owner to see all public keys associated with their account (both past and future). Combined with the "audit" feature, the user can fetch a list of all UTXO (unspent transaction outputs) associated with their account and verify the public key's subpath from the given xpubkey. Similarly, they can check the UTXO is correctly stored on the blockchain.

Coinkite has stated that in the event of the closure or other failure of the business, they will publicize the symmetric key protecting the xprivkey values that have been distributed to members. With that key, each user could recover their funds by re-generating the private keys for each UTXO.

The founders of Coinkite understood the inherent risk of trusting a third party with the private keys for your bitcoins, and this application of BIP 32 helps to address these concerns should the business disappear. The company calls this system "full reserve" since the users are in a position to verify that their funds are not being used for any other purpose than safe-keeping, while on deposit at Coinkite.

==Debit Card==

For a small fee (and included in some membership plans), Coinkite users may receive a physical card. This eases use of their Coinkite account at the POS terminal and the QR code on the rear is useful for making deposits.

==POS Terminal==

Coinkite sells a hardware device which can perform a number of transactions. It connects via GPRS (cell) or Wifi to Coinkite backend servers which perform the blockchain operations. It does not directly connect to the P2P network.

Users can log into their Coinkite account at the machine, using either their Coinkite card (and a 4-6 digit PIN, plus optionally a 2FA token) or use a one-time QR code from the Coinkite website. Once connected to their account, they can perform many types of transactions:

* print out their current balances

* scan a QR and pay it using their balance

* withdraw funds to cash (requires the retail to become the counter-party)

* deposit cash (buying coins from the retailer)

* make a printed invoice (ie. a unique bitcoin address for payment of a specific amount)

* verify a payment has been received (by scanning any receipt printed by a Coinkite terminal)

The POS terminal is also useful to enable the bitcoin-based retail business. Cashiers (authorized users) can print a receipt with QR code that maybe presented to customers as a bill in bitcoin to be paid. Once paid, using any bitcoin wallet of choice, the payment can be easily verified at the terminal by scanning it's QR code. The number of confirmations for the incoming funds is displayed and appropriate warnings are shown for zero confirmation transactions. It is up to the retailer to define their policy on number of required confirmations and presumably the size of the transaction will be a deciding factor.

Other "non account holder" transactions that are possible:

* print current exchange rates (Bitcoin vs. fiat) to a receipt

* deposit cash into bitcoin/litecoin (ie. retailer is selling bitcoins)

* coins are delivered to a URL or private key.

* scan bitcoin QR to pay (retailer is selling bitcoins, paid directly to settle bitcoin debt)

* scan to verify transaction (prints amount received, and confirmation status for Coinkite transactions)

The POS terminal supports both Litecoin and Bitcoin for all operations. Coins can be delivered as a paper wallet, directly into a Coinkite account (must be pre-existing) or into web voucher (PIN code and short URL).

==External Links==

* [https://www.coinkite.com Coinkite Home page]

* [https://www.coinkite.com/faq FAQ page]

* [https://coinkite.com/promo/wiki Sign-up]

==References==
<references />

==Images==
[[File:Coinkite_interfaces.png|300 px|alt=Coinkite interfaces|Coinkite interfaces]]
[[File:Bitcoin-pos-terminal.png|300 px|alt=Bitcoin POs Terminal|Coinkite terminal]]
[[File:Coinkite_logo.png|300 px|alt=Coinkite logo|Coinkite logo]]

[[Category:Debit Cards]]
[[Category:Wallets]]
[[Category:EWallets]]
[[Category:HybridEWallets]]
[[Category:Mixing_Services]]
[[Category:Exchanges]]
[[Category:Shopping Cart Interfaces]]
[[Category:Services]]
[[Category:Frontends]]
[[Category:Clients]]
[[Category:Mobile]]
[[Category:Block chain browsers]]
[[Category:Hardware Terminals]]
[[Category:Cryptobanks]]
[[Category:POS]]
[[Category:Bitcoin payment systems]]

Coinkite

2013-11-29T05:07:53Z

Btcto: /* Unique BIP32 Feature */ typo

==Coinkite==

Coinkite<ref> (15/10/2013). [https://en.wikipedia.org/wiki/Coinkite "Coinkite".] ''[[Wikipedia]]''.</ref><ref> (12/11/2013). [http://www.thestar.com/news/gta/2013/11/12/bitcoin_entrepreneurs_want_to_put_virtual_coins_in_your_wallet.html "Bitcoin entrepreneurs want to put virtual coins in your wallet".] ''[[Toronto Star]]''.</ref><ref> (11/11/2013). [http://bitcoinmagazine.com/7449/exploring-the-bitcoin-alliance-of-canada-part-i/ "Bitcoin in Canada, Part I: Introducing the Bitcoin Alliance of Canada".] ''[[Bitcoin Magazine]]''.</ref><ref>nvK (10/11/2013). [https://bitcointalk.org/index.php?topic=309431.0 "(ANN) Coinkite.com (Bitcoin Wallet+Debit Card+POS Terminals)accepting invites re".] ''[[bitcointalk.org]]''.</ref><ref>KYT DOTSON (22/10/2013). [http://siliconangle.com/blog/2013/09/25/bitcoin-weekly-2013-september-25-lucky-gambler-makes-11k-btc-coinsetter-to-launch-soon-coinkite-brings-pos-solution/ "Bitcoin Weekly 2013 September 25: Lucky Gambler Makes 11k BTC, Coinsetter to Launch Soon, Coinkite Brings POS Solution".] ''[[Silicon Angle]]''.</ref><ref> (5/11/2013). [https://en.bitcoin.it/wiki/Coinkite "Coinkite".] ''[[Bitcoin Wiki]]''.</ref><ref> (5/11/2013). [https://www.coinforum.ca/discussion/461/accepting-invite-requests-for-coinkite-com "Accepting invite requests for Coinkite.com".] ''[[coinforum.ca]]''.</ref><ref> (1/11/2013). [http://www.thebitpages.com/merchants/1076 "Coinkite".] ''[[The Bit Pages]]''.</ref><ref> (2013). [http://www.linkedin.com/company/coinkite "Company: Coinkite".] ''[[LinkedIN]]''.</ref> offers a number of useful [[bitcoin]] and [[litecoin]] services. It aims to become a full service [[cryptobank]] and safe place for holding coins for immediate use and long-term saving.

==Main features==
* Powerful, easy to use web wallet. Receive and send bitcoin amounts from a web interface. Two factor authentication, memorable image (to resist phishing attempts) and many other security features are in place. Users are free of the burden of securing their own computer.

* Point-of-sale payment terminal. Coinkite sells a hardware device, complete with QR scanner and receipt printer that can be used to perform bitcoin transactions without a computer and in a retail setting.

* "Debit" Card. Coinkite offers all it's members a plastic card which can be used at the payment terminals, but is also useful anywhere as it was a bitcoin address in QR code on the back. Bitcoin sent to that address are linked to the user's Coinkite balance.

==Services==

* multiple sub-accounts for grouping funds (ie. "Savings", "Chequing")

* all transactions occur in the public blockchain, and there is no "internal bookkeeping" of funds.

* monthly, yearly and pay as you go membership plans are offered.

* detailed transaction logging, real-time on-screen alerts as funds as received

* multiple [[cryptocurrenies]]: bitcoin, litecoin, testnet coins are offered with equal features

* Coinkite is the first Litecoin web wallet on the market (Oct 2013)

====Services Links====

* [https://coinkite.com/faq/money Online wallets]

* [https://coinkite.com/faq/terminal Merchant Point-of-Sale terminals]

* [https://coinkite.com/faq/terminal Bitcoin debit cards]

==Unique [[BIP]] 32 Feature==

Coinkite is internally based on BIP 32 [[Hierarchical Deterministic]] (HD) wallets. Each new member receives a "welcome email" which contains the "xpubkey" (extended public key) for their deposits, and an *encrypted* copy of the corresponding xprivkey. The xpubkey (used for both Litecoin and Bitcoin) can be used by the account owner to see all public keys associated with their account (both past and future). Combined with the "audit" feature, the user can fetch a list of all UTXO (unspent transaction outputs) associated with their account and verify the public key's subpath from the given xpubkey. Similarly, they can check the UTXO is correctly stored on the blockchain.

Coinkite has stated that in the event of the closure or other failure of the business, they will publicize the symmetric key protecting the xprivkey values that have been distributed to members. With that key, each user could recover their funds by re-generating the private keys for each UTXO.

The founders of Coinkite understood the inherent risk of trusting a third party with the private keys for your bitcoins, and this application of BIPS32 helps to address these concerns should the business disappear. The company calls this system "full reserve" since the users are in a position to verify that their funds are not being used for any other purpose than safe-keeping, while on deposit at Coinkite.

==Debit Card==

For a small fee (and included in some membership plans), Coinkite users may receive a physical card. This eases use of their Coinkite account at the POS terminal and the QR code on the rear is useful for making deposits.

==POS Terminal==

Coinkite sells a hardware device which can perform a number of transactions. It connects via GPRS (cell) or Wifi to Coinkite backend servers which perform the blockchain operations. It does not directly connect to the P2P network.

Users can log into their Coinkite account at the machine, using either their Coinkite card (and a 4-6 digit PIN, plus optionally a 2FA token) or use a one-time QR code from the Coinkite website. Once connected to their account, they can perform many types of transactions:

* print out their current balances

* scan a QR and pay it using their balance

* withdraw funds to cash (requires the retail to become the counter-party)

* deposit cash (buying coins from the retailer)

* make a printed invoice (ie. a unique bitcoin address for payment of a specific amount)

* verify a payment has been received (by scanning any receipt printed by a Coinkite terminal)

The POS terminal is also useful to enable the bitcoin-based retail business. Cashiers (authorized users) can print a receipt with QR code that maybe presented to customers as a bill in bitcoin to be paid. Once paid, using any bitcoin wallet of choice, the payment can be easily verified at the terminal by scanning it's QR code. The number of confirmations for the incoming funds is displayed and appropriate warnings are shown for zero confirmation transactions. It is up to the retailer to define their policy on number of required confirmations and presumably the size of the transaction will be a deciding factor.

Other "non account holder" transactions that are possible:

* print current exchange rates (Bitcoin vs. fiat) to a receipt

* deposit cash into bitcoin/litecoin (ie. retailer is selling bitcoins)

* coins are delivered to a URL or private key.

* scan bitcoin QR to pay (retailer is selling bitcoins, paid directly to settle bitcoin debt)

* scan to verify transaction (prints amount received, and confirmation status for Coinkite transactions)

The POS terminal supports both Litecoin and Bitcoin for all operations. Coins can be delivered as a paper wallet, directly into a Coinkite account (must be pre-existing) or into web voucher (PIN code and short URL).

==External Links==

* [https://www.coinkite.com Coinkite Home page]

* [https://www.coinkite.com/faq FAQ page]

* [https://coinkite.com/promo/wiki Sign-up]

==References==
<references />

==Images==
[[File:Coinkite_interfaces.png|300 px|alt=Coinkite interfaces|Coinkite interfaces]]
[[File:Bitcoin-pos-terminal.png|300 px|alt=Bitcoin POs Terminal|Coinkite terminal]]
[[File:Coinkite_logo.png|300 px|alt=Coinkite logo|Coinkite logo]]

[[Category:Debit Cards]]
[[Category:Wallets]]
[[Category:EWallets]]
[[Category:HybridEWallets]]
[[Category:Mixing_Services]]
[[Category:Exchanges]]
[[Category:Shopping Cart Interfaces]]
[[Category:Services]]
[[Category:Frontends]]
[[Category:Clients]]
[[Category:Mobile]]
[[Category:Block chain browsers]]
[[Category:Hardware Terminals]]
[[Category:Cryptobanks]]
[[Category:POS]]
[[Category:Bitcoin payment systems]]

How to accept Bitcoin, for small businesses

2013-11-28T15:24:17Z

Btcto: /* Smart Phone or Tablet */

{{merge|Merchant Howto}}

This guide is intended for small business owners who wish to help promote Bitcoin by accepting it as payment for goods and services. It's written with the assumption that you operate a regular business that sells goods or services for regular national currency such as dollars, and that you wish to accept Bitcoin as another legal way to pay, and that you intend to pay taxes on your Bitcoin income just like any other income.

With Bitcoin being touted as a way to conduct anonymous transactions and as way to compete with government currency, many small business owners wonder what's the right way to accept and account Bitcoin, or if it's legal or ethical, or whether and how they should pay taxes on income received through Bitcoin.

As far as we know, Bitcoin isn't yet formally recognized by governments and authorities as a "currency". But in practice, Bitcoin is likely no different than accepting payment in other forms, such as cash, or gold, or scrip, or gift cards or foreign currency. We think that it is pretty much the same as the local businesses of Great Barrington, Massachusetts choosing to accept their locally-printed [http://www.reuters.com/article/2007/06/19/us-usa-economy-berkshares-idUSN0530157720070619 "Berkshire Bucks"] to support their local economy.

====Starting to accept Bitcoin for transactions====
Accepting Bitcoin at a small business is best started in whichever manner keeps the accounting simple for you. This will vary by the type of business you are operating.

===Start with a sign===
[[{{ns:file}}:WeAcceptBitcoin.png‎]]

If you expect that the number of people interested in using Bitcoin is small, you might simply start by posting a sign or a note: "We Accept Bitcoin", and ask people to contact you directly in order to make a payment. Even if hardly anybody uses Bitcoin as a payment method, you're helping Bitcoin in two ways: one, by increasing awareness, and two, by making your customers more willing to accept Bitcoin as payment from others in the future, because now they know somewhere they can spend it.

===Utilize a merchant solution===
If you sell things on your website (goods or services), you'll want to use a [[#Merchant Services|Bitcoin merchant solution]] to accept the Bitcoins (you can usually opt to have them converted to USD or other currencies automatically with some services).

If you sell things in a brick and mortar shop, customers can pay using hardware terminals, touch screen apps or simple wallet addresses through QR Codes.

[[File:Bitcoin-pos-terminal.png|200 px|alt=Bitcoin POs Terminal|Coinkite terminal]] [[File:Mobile_Web_App_Bitcoin_Register.jpeg|100 px|alt=Bitcoin POs Terminal|Coinkite terminal]]

===Smart Phone or Tablet===
You can use a wallet address with any wallet. For that it's best if you can place a QR code near your register to which the customers can scan with their phone and pay (use http://ma.eatgold.com/accept to make a QR code sign).

==== Examples ====

* [[File:BitcoinRegister.gif|20px|link=http://phicorp.ca/Bitregister]][http://phicorp.ca/bitregister Bitcoin Register]
* [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS]
* [http://www.blockchain.info/wallet Blockchain.info]
* [https://coinbase.com/docs/merchant_tools/point_of_sale Coinbase]
* [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite]

===Point-of-Sale hardware terminal===
With custom hardware you can integrate with existing registers and point-of-sales solutions (example: [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite]).

===Accounting===
When a customer makes a payment, you might simply issue a credit to their account. Ideally, you want to enter it in a way that suggests you received a payment. You could consider entering it as a "discount", but you may want to consider whether this inappropriately disguises the nature of the transaction. If on the other hand, you're giving "discounts" for Bitcoins, but then you are selling the Bitcoins for currency and then counting that as income, then chances are good that your calculation of income is making up for it. Ask your accountant.

===Businesses that offer gift cards===
If your business sells gift cards or gift certificates, you may find that the easiest way to accept Bitcoin is to accept it only for the purchase of gift cards, and then require the gift cards to be used for actual purchases of goods or services. This way, the accounting practices you already have in place for processing gift cards can be put to use. The accounting for Bitcoins would then be minimized to tracking sales of a single SKU.

This method is also ideal for retail food establishments and convenience stores, where the payment of Bitcoins through a mobile phone for a small daily food purchase might be cumbersome or disruptive, especially in front of a line of other customers. Bitcoins in this case would be best used to reload prepaid cards that can then be swiped at point-of-sale.

If you don't accept gift cards, but you already accept credit cards through a swipe terminal, consider the possibility that you could add a retail gift card system through the swipe terminal you already own. Many point-of-sale terminals, including ones from VeriFone®, are designed around the ability to support multiple applications on the same terminal. Gift cards are also highly profitable because of "breakage", or in other words, the fact that a significant percentage of them never get redeemed.

You could consider adding a private label gift card program from a provider who specializes in this, not just as a jumpstart to accepting Bitcoins, but as an extra boost to income. A private label gift card service provider necessarily have to handle your funds - they can simply provide a solution that keeps track of the balance on the cards on your behalf, including features that allow users to check their balances by phone or by web. Such a solution, of course, is also what makes the cards swipeable through the card reader.

===Businesses that mail invoices===
Does your business send out invoices to customers? Adding one line may make a huge impact for the Bitcoin economy. Perhaps you list it as a payment option just after Visa, MasterCard, and American Express, even if that means your customer must call or e-mail to make a payment.

If you have access to the programming expertise such that you can generate Bitcoin addresses programmatically, consider generating a brand new Bitcoin address for each invoice, and print it on the invoice. When a Bitcoin payment arrives, you'll automatically know where it should arrive.

Customers might wonder how much BTC they should pay in order to satisfy an invoice in full. Your invoice might suggest an amount. For example, if your invoice is for $100 and BTC's are currently worth $1.24 each, your invoice might suggest that it can be paid in full ''"with a payment of 80.65 BTC if paid by (date)"''.

You might be able to anticipate the possibility that even though a Bitcoin address can be printed on an invoice or payment stub, that they are very cumbersome for most people to type, especially being a mix of uppercase and lowercase letters. However, you should probably still do it anyway. The customer is probably going to want some paper trail for his payment. Giving him a pre-printed payment stub with a pre-printed address will satisfy that, because the customer can independently and publicly prove through [[Block Explorer]] that the payment took place.

Does your business have a website? On your invoice, consider allowing them to go to a special URL to get the address to make a Bitcoin payment just by typing in their invoice number. For example, ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc'' with a form they can enter their invoice number, or just ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc/60365'' for paying invoice #60365. This way, they can see the Bitcoin address, copy and paste it directly into their Bitcoin client.

Use a brand new address for each invoice whenever possible, and use it only once. This benefits the customer as it removes any ambiguity as to which customer is making which payment and for which invoice.

Known payment systems supporting invoicing, and recurring invoice setup, [[File:BIPS.gif|20px|link=https://bips.me/checkout/invoice/cb/bb]] [https://bips.me/checkout/invoice/cb/bb BIPS]

===Avoiding fraud===

You should also consider the possible risk that fraudsters could send counterfeit invoices to your customers, and entice them to make a payment to a Bitcoin address they control, instead of you. While that isn't likely in general - it depends on how well a fraudster could find out who your customers are in the first place - it would certainly be an unpleasant situation if it ever happened. One way you could control that is, whenever possible, never let people try to type Bitcoin addresses off payment stubs - instead, force people to get the full Bitcoin address from your website via secure SSL. But, still print ''most'' of the address on the payment stub (perhaps with four or five characters starred out), so that the customer's need for a paper trail can be satisfied, so they can prove they paid if there is ever a dispute.

==Setting Prices==

When a business accepts bitcoins for payment, there generally is the need to convert them to the currencies used for paying suppliers, employees and shareholders. Some merchants set prices based on the current market rate at the time the price quote is presented to the customer (merchant services like [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS], [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase] or [http://paysius.com Paysius] do this automatically).

[[Bitcoin Prices]] lists the exchange rate for many currencies on multiple exchanges.

When prices are determined using an automated process, the current market rate can be based on either a current price or on a weighted average basis. [[Bitcoin Charts]] provides a [http://bitcoincharts.com/about/markets-api data feed that provides weighted prices].

When bitcoin funds for purchases are received, some merchants instantly exchange those proceeds into the preferred currency used (again done automatically by [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS], [http://www.bit-pay.com Bit-pay] or [https://coinbase.com Coinbase]. Hedging for each transaction can nearly entirely eliminate exchange rate risk that the business is exposed to when accepting bitcoins for payment.

==Contract==

A sales contract might be used to ensure that specific terms are met to lessen the chances of a misunderstanding. For instance, the party sending payment is responsible for paying any [[transaction fee]] that might be necessary. A contract might specify that a transaction fee must be paid and what amount, so as to prevent the situation where the transaction is considered a low priority transaction and thus isn't confirmed quickly.

Other items that might be addressed in a contract:

* Requirement and handling of escrow through an [[:Category:Escrow_services|escrow service]].
* Jurisdiction for disputes.
* Refund policy (particularly with the exchange rate being volatile)

==Paying taxes on Bitcoin income==
[[Tax compliance]] is a topic of concern for small businesses. We aren't accountants or lawyers, and can't give legal or accounting advice.

But in many respects, Bitcoin transactions work very much like cash. Just like Bitcoin, cash is anonymous and doesn't leave a paper trail, yet is widely used in commerce every day.

Ask yourself how you would handle a cash transaction. Do you accept cash transactions? Do you normally pay taxes on cash transactions? The answer for Bitcoin should probably be the same.

As for how to decide what a Bitcoin transaction is worth... the IRS, as far as we know, has never issued a guide mentioning how to value Bitcoin transactions. But they probably have rules and guidelines on how to value transactions made in foreign currency or "cash equivalents". We imagine the accounting would be similar.

With Bitcoins, there's likely to be some difference between the value of BTC when you received them as payment, versus when you go to exchange them for another currency like USD, should you decide to do so. This scenario, likewise, would be no different if you accepted foreign currency or gold as payment. Under some scenarios, it might make sense to book the dollar value of BTC income as it is received, and then to book any difference incurred when it is exchanged for fiat currency. Under others, it might make sense to book the whole thing at the time of exchange.

Perhaps you might talk to your accountant. You don't need to get into a discussion with your accountant about block chains and private keys or the philosophy behind a decentralized currency. By comparing the fundamentals of Bitcoins to accounting concepts already well understood by the public, you can probably get all the answers you need. What would you ask your accountant if you decided that you wanted to accept ''Berkshire Bucks'' or 1-ounce gold coins as payment?

== Merchant Services ==
* [http://blockchain.info/api/api_receive Blockchain.info] Free APIs to process bitcoin payments. No sign up or account needed.
* [[File:BitcoinRegister.gif|20px|link=http://phicorp.ca/bitregister]] [http://phicorp.ca/bitregister Bitcoin Register] Bitcoin Point of Sales application for Android, with integration into various exchanges. Similar to Square.
* [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS] Bitcoin Internet Payment System. A Bitcoin payment processor with mobile checkout, point of sale solutions.
* [https://www.bitpay.com BitPay] Bitcoin payment processor with mobile checkout solution
* [https://www.bitpagos.net BitPagos] Bitcoin and Credit Card payment processor
* [https://www.btcmerch.com BTCMerch] Payment processor for bitcoins and other cryptocurrencies. 0.5% transaction fee. Sandbox is available.
* [https://bitmerch.com BitMerch] Provides HTML buttons to start accepting bitcoins instantly. No server side setup required.
* [https://coinbase.com/docs/merchant_tools/payment_buttons Coinbase] Offers payment buttons, checkout pages, shopping cart integration, and daily cash out to USD.
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/faq/terminal Coinkite] Full-reserve banking, payment buttons, invoice pages, hardware POS terminals, and Debit-Cards.
* [https://mtgox.com/merchant MTGOX] Bitcoin payment processing
* [https://www.okpay.com/en/services/accept-payments/index.html OKPAY] Bitcoin payment processing for merchants
* [http://fasterco.in Fasterco.in] Bitcoin payment processing for merchants and day-traders
* [http://snowcron.com Snowcron] Bitcoin Store Engine: Handles payments, sends your customers information they ordered (reg. codes, passwords...) No web programming required.

== Help this article ==

This article is a stub, please add to it!

==See Also==

* [[Merchant Howto]]
* [[In-store Transactions]]
* [[Tax compliance]]
* [[Securing online services]]
* [[BitCoins Mobile]] provides accurate up to date pricing from multiple exchanges from your Apple iPad, iPhone, or iPod Touch.
* [[Bitcoin PayFlow]] automates the process for accepting bitcoins
* [[Lazy API]] The lazy (and possibly easiest?) way to accept bitcoin payments on your website

[[Category:ECommerce]]
[[Category:Local]]

[[de:Bitcoin_als_Geschäft_akzeptieren]]

How to accept Bitcoin, for small businesses

2013-11-28T15:23:16Z

Btcto: /* Point-of-Sale hardware terminal */

{{merge|Merchant Howto}}

This guide is intended for small business owners who wish to help promote Bitcoin by accepting it as payment for goods and services. It's written with the assumption that you operate a regular business that sells goods or services for regular national currency such as dollars, and that you wish to accept Bitcoin as another legal way to pay, and that you intend to pay taxes on your Bitcoin income just like any other income.

With Bitcoin being touted as a way to conduct anonymous transactions and as way to compete with government currency, many small business owners wonder what's the right way to accept and account Bitcoin, or if it's legal or ethical, or whether and how they should pay taxes on income received through Bitcoin.

As far as we know, Bitcoin isn't yet formally recognized by governments and authorities as a "currency". But in practice, Bitcoin is likely no different than accepting payment in other forms, such as cash, or gold, or scrip, or gift cards or foreign currency. We think that it is pretty much the same as the local businesses of Great Barrington, Massachusetts choosing to accept their locally-printed [http://www.reuters.com/article/2007/06/19/us-usa-economy-berkshares-idUSN0530157720070619 "Berkshire Bucks"] to support their local economy.

====Starting to accept Bitcoin for transactions====
Accepting Bitcoin at a small business is best started in whichever manner keeps the accounting simple for you. This will vary by the type of business you are operating.

===Start with a sign===
[[{{ns:file}}:WeAcceptBitcoin.png‎]]

If you expect that the number of people interested in using Bitcoin is small, you might simply start by posting a sign or a note: "We Accept Bitcoin", and ask people to contact you directly in order to make a payment. Even if hardly anybody uses Bitcoin as a payment method, you're helping Bitcoin in two ways: one, by increasing awareness, and two, by making your customers more willing to accept Bitcoin as payment from others in the future, because now they know somewhere they can spend it.

===Utilize a merchant solution===
If you sell things on your website (goods or services), you'll want to use a [[#Merchant Services|Bitcoin merchant solution]] to accept the Bitcoins (you can usually opt to have them converted to USD or other currencies automatically with some services).

If you sell things in a brick and mortar shop, customers can pay using hardware terminals, touch screen apps or simple wallet addresses through QR Codes.

[[File:Bitcoin-pos-terminal.png|200 px|alt=Bitcoin POs Terminal|Coinkite terminal]] [[File:Mobile_Web_App_Bitcoin_Register.jpeg|100 px|alt=Bitcoin POs Terminal|Coinkite terminal]]

===Smart Phone or Tablet===
You can use a wallet address with this services:

* [[File:BitcoinRegister.gif|20px|link=http://phicorp.ca/Bitregister]][http://phicorp.ca/bitregister Bitcoin Register]
* [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS]
* [http://www.blockchain.info/wallet Blockchain.info]
* [https://coinbase.com/docs/merchant_tools/point_of_sale Coinbase]
* [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite]

For that it's best if you can place a QR code near your register to which the customers can scan with their phone and pay (use http://ma.eatgold.com/accept to make a QR code sign).

===Point-of-Sale hardware terminal===
With custom hardware you can integrate with existing registers and point-of-sales solutions (example: [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite]).

===Accounting===
When a customer makes a payment, you might simply issue a credit to their account. Ideally, you want to enter it in a way that suggests you received a payment. You could consider entering it as a "discount", but you may want to consider whether this inappropriately disguises the nature of the transaction. If on the other hand, you're giving "discounts" for Bitcoins, but then you are selling the Bitcoins for currency and then counting that as income, then chances are good that your calculation of income is making up for it. Ask your accountant.

===Businesses that offer gift cards===
If your business sells gift cards or gift certificates, you may find that the easiest way to accept Bitcoin is to accept it only for the purchase of gift cards, and then require the gift cards to be used for actual purchases of goods or services. This way, the accounting practices you already have in place for processing gift cards can be put to use. The accounting for Bitcoins would then be minimized to tracking sales of a single SKU.

This method is also ideal for retail food establishments and convenience stores, where the payment of Bitcoins through a mobile phone for a small daily food purchase might be cumbersome or disruptive, especially in front of a line of other customers. Bitcoins in this case would be best used to reload prepaid cards that can then be swiped at point-of-sale.

If you don't accept gift cards, but you already accept credit cards through a swipe terminal, consider the possibility that you could add a retail gift card system through the swipe terminal you already own. Many point-of-sale terminals, including ones from VeriFone®, are designed around the ability to support multiple applications on the same terminal. Gift cards are also highly profitable because of "breakage", or in other words, the fact that a significant percentage of them never get redeemed.

You could consider adding a private label gift card program from a provider who specializes in this, not just as a jumpstart to accepting Bitcoins, but as an extra boost to income. A private label gift card service provider necessarily have to handle your funds - they can simply provide a solution that keeps track of the balance on the cards on your behalf, including features that allow users to check their balances by phone or by web. Such a solution, of course, is also what makes the cards swipeable through the card reader.

===Businesses that mail invoices===
Does your business send out invoices to customers? Adding one line may make a huge impact for the Bitcoin economy. Perhaps you list it as a payment option just after Visa, MasterCard, and American Express, even if that means your customer must call or e-mail to make a payment.

If you have access to the programming expertise such that you can generate Bitcoin addresses programmatically, consider generating a brand new Bitcoin address for each invoice, and print it on the invoice. When a Bitcoin payment arrives, you'll automatically know where it should arrive.

Customers might wonder how much BTC they should pay in order to satisfy an invoice in full. Your invoice might suggest an amount. For example, if your invoice is for $100 and BTC's are currently worth $1.24 each, your invoice might suggest that it can be paid in full ''"with a payment of 80.65 BTC if paid by (date)"''.

You might be able to anticipate the possibility that even though a Bitcoin address can be printed on an invoice or payment stub, that they are very cumbersome for most people to type, especially being a mix of uppercase and lowercase letters. However, you should probably still do it anyway. The customer is probably going to want some paper trail for his payment. Giving him a pre-printed payment stub with a pre-printed address will satisfy that, because the customer can independently and publicly prove through [[Block Explorer]] that the payment took place.

Does your business have a website? On your invoice, consider allowing them to go to a special URL to get the address to make a Bitcoin payment just by typing in their invoice number. For example, ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc'' with a form they can enter their invoice number, or just ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc/60365'' for paying invoice #60365. This way, they can see the Bitcoin address, copy and paste it directly into their Bitcoin client.

Use a brand new address for each invoice whenever possible, and use it only once. This benefits the customer as it removes any ambiguity as to which customer is making which payment and for which invoice.

Known payment systems supporting invoicing, and recurring invoice setup, [[File:BIPS.gif|20px|link=https://bips.me/checkout/invoice/cb/bb]] [https://bips.me/checkout/invoice/cb/bb BIPS]

===Avoiding fraud===

You should also consider the possible risk that fraudsters could send counterfeit invoices to your customers, and entice them to make a payment to a Bitcoin address they control, instead of you. While that isn't likely in general - it depends on how well a fraudster could find out who your customers are in the first place - it would certainly be an unpleasant situation if it ever happened. One way you could control that is, whenever possible, never let people try to type Bitcoin addresses off payment stubs - instead, force people to get the full Bitcoin address from your website via secure SSL. But, still print ''most'' of the address on the payment stub (perhaps with four or five characters starred out), so that the customer's need for a paper trail can be satisfied, so they can prove they paid if there is ever a dispute.

==Setting Prices==

When a business accepts bitcoins for payment, there generally is the need to convert them to the currencies used for paying suppliers, employees and shareholders. Some merchants set prices based on the current market rate at the time the price quote is presented to the customer (merchant services like [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS], [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase] or [http://paysius.com Paysius] do this automatically).

[[Bitcoin Prices]] lists the exchange rate for many currencies on multiple exchanges.

When prices are determined using an automated process, the current market rate can be based on either a current price or on a weighted average basis. [[Bitcoin Charts]] provides a [http://bitcoincharts.com/about/markets-api data feed that provides weighted prices].

When bitcoin funds for purchases are received, some merchants instantly exchange those proceeds into the preferred currency used (again done automatically by [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS], [http://www.bit-pay.com Bit-pay] or [https://coinbase.com Coinbase]. Hedging for each transaction can nearly entirely eliminate exchange rate risk that the business is exposed to when accepting bitcoins for payment.

==Contract==

A sales contract might be used to ensure that specific terms are met to lessen the chances of a misunderstanding. For instance, the party sending payment is responsible for paying any [[transaction fee]] that might be necessary. A contract might specify that a transaction fee must be paid and what amount, so as to prevent the situation where the transaction is considered a low priority transaction and thus isn't confirmed quickly.

Other items that might be addressed in a contract:

* Requirement and handling of escrow through an [[:Category:Escrow_services|escrow service]].
* Jurisdiction for disputes.
* Refund policy (particularly with the exchange rate being volatile)

==Paying taxes on Bitcoin income==
[[Tax compliance]] is a topic of concern for small businesses. We aren't accountants or lawyers, and can't give legal or accounting advice.

But in many respects, Bitcoin transactions work very much like cash. Just like Bitcoin, cash is anonymous and doesn't leave a paper trail, yet is widely used in commerce every day.

Ask yourself how you would handle a cash transaction. Do you accept cash transactions? Do you normally pay taxes on cash transactions? The answer for Bitcoin should probably be the same.

As for how to decide what a Bitcoin transaction is worth... the IRS, as far as we know, has never issued a guide mentioning how to value Bitcoin transactions. But they probably have rules and guidelines on how to value transactions made in foreign currency or "cash equivalents". We imagine the accounting would be similar.

With Bitcoins, there's likely to be some difference between the value of BTC when you received them as payment, versus when you go to exchange them for another currency like USD, should you decide to do so. This scenario, likewise, would be no different if you accepted foreign currency or gold as payment. Under some scenarios, it might make sense to book the dollar value of BTC income as it is received, and then to book any difference incurred when it is exchanged for fiat currency. Under others, it might make sense to book the whole thing at the time of exchange.

Perhaps you might talk to your accountant. You don't need to get into a discussion with your accountant about block chains and private keys or the philosophy behind a decentralized currency. By comparing the fundamentals of Bitcoins to accounting concepts already well understood by the public, you can probably get all the answers you need. What would you ask your accountant if you decided that you wanted to accept ''Berkshire Bucks'' or 1-ounce gold coins as payment?

== Merchant Services ==
* [http://blockchain.info/api/api_receive Blockchain.info] Free APIs to process bitcoin payments. No sign up or account needed.
* [[File:BitcoinRegister.gif|20px|link=http://phicorp.ca/bitregister]] [http://phicorp.ca/bitregister Bitcoin Register] Bitcoin Point of Sales application for Android, with integration into various exchanges. Similar to Square.
* [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS] Bitcoin Internet Payment System. A Bitcoin payment processor with mobile checkout, point of sale solutions.
* [https://www.bitpay.com BitPay] Bitcoin payment processor with mobile checkout solution
* [https://www.bitpagos.net BitPagos] Bitcoin and Credit Card payment processor
* [https://www.btcmerch.com BTCMerch] Payment processor for bitcoins and other cryptocurrencies. 0.5% transaction fee. Sandbox is available.
* [https://bitmerch.com BitMerch] Provides HTML buttons to start accepting bitcoins instantly. No server side setup required.
* [https://coinbase.com/docs/merchant_tools/payment_buttons Coinbase] Offers payment buttons, checkout pages, shopping cart integration, and daily cash out to USD.
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/faq/terminal Coinkite] Full-reserve banking, payment buttons, invoice pages, hardware POS terminals, and Debit-Cards.
* [https://mtgox.com/merchant MTGOX] Bitcoin payment processing
* [https://www.okpay.com/en/services/accept-payments/index.html OKPAY] Bitcoin payment processing for merchants
* [http://fasterco.in Fasterco.in] Bitcoin payment processing for merchants and day-traders
* [http://snowcron.com Snowcron] Bitcoin Store Engine: Handles payments, sends your customers information they ordered (reg. codes, passwords...) No web programming required.

== Help this article ==

This article is a stub, please add to it!

==See Also==

* [[Merchant Howto]]
* [[In-store Transactions]]
* [[Tax compliance]]
* [[Securing online services]]
* [[BitCoins Mobile]] provides accurate up to date pricing from multiple exchanges from your Apple iPad, iPhone, or iPod Touch.
* [[Bitcoin PayFlow]] automates the process for accepting bitcoins
* [[Lazy API]] The lazy (and possibly easiest?) way to accept bitcoin payments on your website

[[Category:ECommerce]]
[[Category:Local]]

[[de:Bitcoin_als_Geschäft_akzeptieren]]

How to accept Bitcoin, for small businesses

2013-11-28T15:08:55Z

Btcto:

{{merge|Merchant Howto}}

This guide is intended for small business owners who wish to help promote Bitcoin by accepting it as payment for goods and services. It's written with the assumption that you operate a regular business that sells goods or services for regular national currency such as dollars, and that you wish to accept Bitcoin as another legal way to pay, and that you intend to pay taxes on your Bitcoin income just like any other income.

With Bitcoin being touted as a way to conduct anonymous transactions and as way to compete with government currency, many small business owners wonder what's the right way to accept and account Bitcoin, or if it's legal or ethical, or whether and how they should pay taxes on income received through Bitcoin.

As far as we know, Bitcoin isn't yet formally recognized by governments and authorities as a "currency". But in practice, Bitcoin is likely no different than accepting payment in other forms, such as cash, or gold, or scrip, or gift cards or foreign currency. We think that it is pretty much the same as the local businesses of Great Barrington, Massachusetts choosing to accept their locally-printed [http://www.reuters.com/article/2007/06/19/us-usa-economy-berkshares-idUSN0530157720070619 "Berkshire Bucks"] to support their local economy.

====Starting to accept Bitcoin for transactions====
Accepting Bitcoin at a small business is best started in whichever manner keeps the accounting simple for you. This will vary by the type of business you are operating.

===Start with a sign===
[[{{ns:file}}:WeAcceptBitcoin.png‎]]

If you expect that the number of people interested in using Bitcoin is small, you might simply start by posting a sign or a note: "We Accept Bitcoin", and ask people to contact you directly in order to make a payment. Even if hardly anybody uses Bitcoin as a payment method, you're helping Bitcoin in two ways: one, by increasing awareness, and two, by making your customers more willing to accept Bitcoin as payment from others in the future, because now they know somewhere they can spend it.

===Utilize a merchant solution===
If you sell things on your website (goods or services), you'll want to use a [[#Merchant Services|Bitcoin merchant solution]] to accept the Bitcoins (you can usually opt to have them converted to USD or other currencies automatically with some services).

If you sell things in a brick and mortar shop, customers can pay using hardware terminals, touch screen apps or simple wallet addresses through QR Codes.

[[File:Bitcoin-pos-terminal.png|200 px|alt=Bitcoin POs Terminal|Coinkite terminal]] [[File:Mobile_Web_App_Bitcoin_Register.jpeg|100 px|alt=Bitcoin POs Terminal|Coinkite terminal]]

===Smart Phone or Tablet===
You can use a wallet address with this services:

* [[File:BitcoinRegister.gif|20px|link=http://phicorp.ca/Bitregister]][http://phicorp.ca/bitregister Bitcoin Register]
* [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS]
* [http://www.blockchain.info/wallet Blockchain.info]
* [https://coinbase.com/docs/merchant_tools/point_of_sale Coinbase]
* [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite]

For that it's best if you can place a QR code near your register to which the customers can scan with their phone and pay (use http://ma.eatgold.com/accept to make a QR code sign).

===Point-of-Sale hardware terminal===
With custom hardware you can integrate with existing registers and point-of-sales solutions.

* [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite]

===Accounting===
When a customer makes a payment, you might simply issue a credit to their account. Ideally, you want to enter it in a way that suggests you received a payment. You could consider entering it as a "discount", but you may want to consider whether this inappropriately disguises the nature of the transaction. If on the other hand, you're giving "discounts" for Bitcoins, but then you are selling the Bitcoins for currency and then counting that as income, then chances are good that your calculation of income is making up for it. Ask your accountant.

===Businesses that offer gift cards===
If your business sells gift cards or gift certificates, you may find that the easiest way to accept Bitcoin is to accept it only for the purchase of gift cards, and then require the gift cards to be used for actual purchases of goods or services. This way, the accounting practices you already have in place for processing gift cards can be put to use. The accounting for Bitcoins would then be minimized to tracking sales of a single SKU.

This method is also ideal for retail food establishments and convenience stores, where the payment of Bitcoins through a mobile phone for a small daily food purchase might be cumbersome or disruptive, especially in front of a line of other customers. Bitcoins in this case would be best used to reload prepaid cards that can then be swiped at point-of-sale.

If you don't accept gift cards, but you already accept credit cards through a swipe terminal, consider the possibility that you could add a retail gift card system through the swipe terminal you already own. Many point-of-sale terminals, including ones from VeriFone®, are designed around the ability to support multiple applications on the same terminal. Gift cards are also highly profitable because of "breakage", or in other words, the fact that a significant percentage of them never get redeemed.

You could consider adding a private label gift card program from a provider who specializes in this, not just as a jumpstart to accepting Bitcoins, but as an extra boost to income. A private label gift card service provider necessarily have to handle your funds - they can simply provide a solution that keeps track of the balance on the cards on your behalf, including features that allow users to check their balances by phone or by web. Such a solution, of course, is also what makes the cards swipeable through the card reader.

===Businesses that mail invoices===
Does your business send out invoices to customers? Adding one line may make a huge impact for the Bitcoin economy. Perhaps you list it as a payment option just after Visa, MasterCard, and American Express, even if that means your customer must call or e-mail to make a payment.

If you have access to the programming expertise such that you can generate Bitcoin addresses programmatically, consider generating a brand new Bitcoin address for each invoice, and print it on the invoice. When a Bitcoin payment arrives, you'll automatically know where it should arrive.

Customers might wonder how much BTC they should pay in order to satisfy an invoice in full. Your invoice might suggest an amount. For example, if your invoice is for $100 and BTC's are currently worth $1.24 each, your invoice might suggest that it can be paid in full ''"with a payment of 80.65 BTC if paid by (date)"''.

You might be able to anticipate the possibility that even though a Bitcoin address can be printed on an invoice or payment stub, that they are very cumbersome for most people to type, especially being a mix of uppercase and lowercase letters. However, you should probably still do it anyway. The customer is probably going to want some paper trail for his payment. Giving him a pre-printed payment stub with a pre-printed address will satisfy that, because the customer can independently and publicly prove through [[Block Explorer]] that the payment took place.

Does your business have a website? On your invoice, consider allowing them to go to a special URL to get the address to make a Bitcoin payment just by typing in their invoice number. For example, ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc'' with a form they can enter their invoice number, or just ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc/60365'' for paying invoice #60365. This way, they can see the Bitcoin address, copy and paste it directly into their Bitcoin client.

Use a brand new address for each invoice whenever possible, and use it only once. This benefits the customer as it removes any ambiguity as to which customer is making which payment and for which invoice.

Known payment systems supporting invoicing, and recurring invoice setup, [[File:BIPS.gif|20px|link=https://bips.me/checkout/invoice/cb/bb]] [https://bips.me/checkout/invoice/cb/bb BIPS]

===Avoiding fraud===

You should also consider the possible risk that fraudsters could send counterfeit invoices to your customers, and entice them to make a payment to a Bitcoin address they control, instead of you. While that isn't likely in general - it depends on how well a fraudster could find out who your customers are in the first place - it would certainly be an unpleasant situation if it ever happened. One way you could control that is, whenever possible, never let people try to type Bitcoin addresses off payment stubs - instead, force people to get the full Bitcoin address from your website via secure SSL. But, still print ''most'' of the address on the payment stub (perhaps with four or five characters starred out), so that the customer's need for a paper trail can be satisfied, so they can prove they paid if there is ever a dispute.

==Setting Prices==

When a business accepts bitcoins for payment, there generally is the need to convert them to the currencies used for paying suppliers, employees and shareholders. Some merchants set prices based on the current market rate at the time the price quote is presented to the customer (merchant services like [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS], [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase] or [http://paysius.com Paysius] do this automatically).

[[Bitcoin Prices]] lists the exchange rate for many currencies on multiple exchanges.

When prices are determined using an automated process, the current market rate can be based on either a current price or on a weighted average basis. [[Bitcoin Charts]] provides a [http://bitcoincharts.com/about/markets-api data feed that provides weighted prices].

When bitcoin funds for purchases are received, some merchants instantly exchange those proceeds into the preferred currency used (again done automatically by [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS], [http://www.bit-pay.com Bit-pay] or [https://coinbase.com Coinbase]. Hedging for each transaction can nearly entirely eliminate exchange rate risk that the business is exposed to when accepting bitcoins for payment.

==Contract==

A sales contract might be used to ensure that specific terms are met to lessen the chances of a misunderstanding. For instance, the party sending payment is responsible for paying any [[transaction fee]] that might be necessary. A contract might specify that a transaction fee must be paid and what amount, so as to prevent the situation where the transaction is considered a low priority transaction and thus isn't confirmed quickly.

Other items that might be addressed in a contract:

* Requirement and handling of escrow through an [[:Category:Escrow_services|escrow service]].
* Jurisdiction for disputes.
* Refund policy (particularly with the exchange rate being volatile)

==Paying taxes on Bitcoin income==
[[Tax compliance]] is a topic of concern for small businesses. We aren't accountants or lawyers, and can't give legal or accounting advice.

But in many respects, Bitcoin transactions work very much like cash. Just like Bitcoin, cash is anonymous and doesn't leave a paper trail, yet is widely used in commerce every day.

Ask yourself how you would handle a cash transaction. Do you accept cash transactions? Do you normally pay taxes on cash transactions? The answer for Bitcoin should probably be the same.

As for how to decide what a Bitcoin transaction is worth... the IRS, as far as we know, has never issued a guide mentioning how to value Bitcoin transactions. But they probably have rules and guidelines on how to value transactions made in foreign currency or "cash equivalents". We imagine the accounting would be similar.

With Bitcoins, there's likely to be some difference between the value of BTC when you received them as payment, versus when you go to exchange them for another currency like USD, should you decide to do so. This scenario, likewise, would be no different if you accepted foreign currency or gold as payment. Under some scenarios, it might make sense to book the dollar value of BTC income as it is received, and then to book any difference incurred when it is exchanged for fiat currency. Under others, it might make sense to book the whole thing at the time of exchange.

Perhaps you might talk to your accountant. You don't need to get into a discussion with your accountant about block chains and private keys or the philosophy behind a decentralized currency. By comparing the fundamentals of Bitcoins to accounting concepts already well understood by the public, you can probably get all the answers you need. What would you ask your accountant if you decided that you wanted to accept ''Berkshire Bucks'' or 1-ounce gold coins as payment?

== Merchant Services ==
* [http://blockchain.info/api/api_receive Blockchain.info] Free APIs to process bitcoin payments. No sign up or account needed.
* [[File:BitcoinRegister.gif|20px|link=http://phicorp.ca/bitregister]] [http://phicorp.ca/bitregister Bitcoin Register] Bitcoin Point of Sales application for Android, with integration into various exchanges. Similar to Square.
* [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS] Bitcoin Internet Payment System. A Bitcoin payment processor with mobile checkout, point of sale solutions.
* [https://www.bitpay.com BitPay] Bitcoin payment processor with mobile checkout solution
* [https://www.bitpagos.net BitPagos] Bitcoin and Credit Card payment processor
* [https://www.btcmerch.com BTCMerch] Payment processor for bitcoins and other cryptocurrencies. 0.5% transaction fee. Sandbox is available.
* [https://bitmerch.com BitMerch] Provides HTML buttons to start accepting bitcoins instantly. No server side setup required.
* [https://coinbase.com/docs/merchant_tools/payment_buttons Coinbase] Offers payment buttons, checkout pages, shopping cart integration, and daily cash out to USD.
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/faq/terminal Coinkite] Full-reserve banking, payment buttons, invoice pages, hardware POS terminals, and Debit-Cards.
* [https://mtgox.com/merchant MTGOX] Bitcoin payment processing
* [https://www.okpay.com/en/services/accept-payments/index.html OKPAY] Bitcoin payment processing for merchants
* [http://fasterco.in Fasterco.in] Bitcoin payment processing for merchants and day-traders
* [http://snowcron.com Snowcron] Bitcoin Store Engine: Handles payments, sends your customers information they ordered (reg. codes, passwords...) No web programming required.

== Help this article ==

This article is a stub, please add to it!

==See Also==

* [[Merchant Howto]]
* [[In-store Transactions]]
* [[Tax compliance]]
* [[Securing online services]]
* [[BitCoins Mobile]] provides accurate up to date pricing from multiple exchanges from your Apple iPad, iPhone, or iPod Touch.
* [[Bitcoin PayFlow]] automates the process for accepting bitcoins
* [[Lazy API]] The lazy (and possibly easiest?) way to accept bitcoin payments on your website

[[Category:ECommerce]]
[[Category:Local]]

[[de:Bitcoin_als_Geschäft_akzeptieren]]

How to accept Bitcoin, for small businesses

2013-11-28T15:07:31Z

Btcto: /* Utilize a merchant solution */ Re-organized, still needs to be improved.

{{merge|Merchant Howto}}

This guide is intended for small business owners who wish to help promote Bitcoin by accepting it as payment for goods and services. It's written with the assumption that you operate a regular business that sells goods or services for regular national currency such as dollars, and that you wish to accept Bitcoin as another legal way to pay, and that you intend to pay taxes on your Bitcoin income just like any other income.

With Bitcoin being touted as a way to conduct anonymous transactions and as way to compete with government currency, many small business owners wonder what's the right way to accept and account Bitcoin, or if it's legal or ethical, or whether and how they should pay taxes on income received through Bitcoin.

As far as we know, Bitcoin isn't yet formally recognized by governments and authorities as a "currency". But in practice, Bitcoin is likely no different than accepting payment in other forms, such as cash, or gold, or scrip, or gift cards or foreign currency. We think that it is pretty much the same as the local businesses of Great Barrington, Massachusetts choosing to accept their locally-printed [http://www.reuters.com/article/2007/06/19/us-usa-economy-berkshares-idUSN0530157720070619 "Berkshire Bucks"] to support their local economy.

==Starting to accept Bitcoin for transactions==
Accepting Bitcoin at a small business is best started in whichever manner keeps the accounting simple for you. This will vary by the type of business you are operating.

===Start with a sign===
[[{{ns:file}}:WeAcceptBitcoin.png‎]]

If you expect that the number of people interested in using Bitcoin is small, you might simply start by posting a sign or a note: "We Accept Bitcoin", and ask people to contact you directly in order to make a payment. Even if hardly anybody uses Bitcoin as a payment method, you're helping Bitcoin in two ways: one, by increasing awareness, and two, by making your customers more willing to accept Bitcoin as payment from others in the future, because now they know somewhere they can spend it.

==Utilize a merchant solution==
If you sell things on your website (goods or services), you'll want to use a [[#Merchant Services|Bitcoin merchant solution]] to accept the Bitcoins (you can usually opt to have them converted to USD or other currencies automatically with some services).

If you sell things in a brick and mortar shop, customers can pay using hardware terminals, touch screen apps or simple wallet addresses through QR Codes.

[[File:Bitcoin-pos-terminal.png|200 px|alt=Bitcoin POs Terminal|Coinkite terminal]] [[File:Mobile_Web_App_Bitcoin_Register.jpeg|100 px|alt=Bitcoin POs Terminal|Coinkite terminal]]

==Smart Phone or Tablet==
You can use a wallet address with this services:

* [[File:BitcoinRegister.gif|20px|link=http://phicorp.ca/Bitregister]][http://phicorp.ca/bitregister Bitcoin Register]
* [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS]
* [http://www.blockchain.info/wallet Blockchain.info]
* [https://coinbase.com/docs/merchant_tools/point_of_sale Coinbase]
* [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite]

For that it's best if you can place a QR code near your register to which the customers can scan with their phone and pay (use http://ma.eatgold.com/accept to make a QR code sign).

==Point-of-Sale hardware terminal==
With custom hardware you can integrate with existing registers and point-of-sales solutions.

* [[File:Coinkite.gif|20px|link=https://coinkite.com/promo/wikibiz]] [https://coinkite.com/promo/wikibiz Coinkite]

===Accounting===
When a customer makes a payment, you might simply issue a credit to their account. Ideally, you want to enter it in a way that suggests you received a payment. You could consider entering it as a "discount", but you may want to consider whether this inappropriately disguises the nature of the transaction. If on the other hand, you're giving "discounts" for Bitcoins, but then you are selling the Bitcoins for currency and then counting that as income, then chances are good that your calculation of income is making up for it. Ask your accountant.

===Businesses that offer gift cards===
If your business sells gift cards or gift certificates, you may find that the easiest way to accept Bitcoin is to accept it only for the purchase of gift cards, and then require the gift cards to be used for actual purchases of goods or services. This way, the accounting practices you already have in place for processing gift cards can be put to use. The accounting for Bitcoins would then be minimized to tracking sales of a single SKU.

This method is also ideal for retail food establishments and convenience stores, where the payment of Bitcoins through a mobile phone for a small daily food purchase might be cumbersome or disruptive, especially in front of a line of other customers. Bitcoins in this case would be best used to reload prepaid cards that can then be swiped at point-of-sale.

If you don't accept gift cards, but you already accept credit cards through a swipe terminal, consider the possibility that you could add a retail gift card system through the swipe terminal you already own. Many point-of-sale terminals, including ones from VeriFone®, are designed around the ability to support multiple applications on the same terminal. Gift cards are also highly profitable because of "breakage", or in other words, the fact that a significant percentage of them never get redeemed.

You could consider adding a private label gift card program from a provider who specializes in this, not just as a jumpstart to accepting Bitcoins, but as an extra boost to income. A private label gift card service provider necessarily have to handle your funds - they can simply provide a solution that keeps track of the balance on the cards on your behalf, including features that allow users to check their balances by phone or by web. Such a solution, of course, is also what makes the cards swipeable through the card reader.

===Businesses that mail invoices===
Does your business send out invoices to customers? Adding one line may make a huge impact for the Bitcoin economy. Perhaps you list it as a payment option just after Visa, MasterCard, and American Express, even if that means your customer must call or e-mail to make a payment.

If you have access to the programming expertise such that you can generate Bitcoin addresses programmatically, consider generating a brand new Bitcoin address for each invoice, and print it on the invoice. When a Bitcoin payment arrives, you'll automatically know where it should arrive.

Customers might wonder how much BTC they should pay in order to satisfy an invoice in full. Your invoice might suggest an amount. For example, if your invoice is for $100 and BTC's are currently worth $1.24 each, your invoice might suggest that it can be paid in full ''"with a payment of 80.65 BTC if paid by (date)"''.

You might be able to anticipate the possibility that even though a Bitcoin address can be printed on an invoice or payment stub, that they are very cumbersome for most people to type, especially being a mix of uppercase and lowercase letters. However, you should probably still do it anyway. The customer is probably going to want some paper trail for his payment. Giving him a pre-printed payment stub with a pre-printed address will satisfy that, because the customer can independently and publicly prove through [[Block Explorer]] that the payment took place.

Does your business have a website? On your invoice, consider allowing them to go to a special URL to get the address to make a Bitcoin payment just by typing in their invoice number. For example, ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc'' with a form they can enter their invoice number, or just ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc/60365'' for paying invoice #60365. This way, they can see the Bitcoin address, copy and paste it directly into their Bitcoin client.

Use a brand new address for each invoice whenever possible, and use it only once. This benefits the customer as it removes any ambiguity as to which customer is making which payment and for which invoice.

Known payment systems supporting invoicing, and recurring invoice setup, [[File:BIPS.gif|20px|link=https://bips.me/checkout/invoice/cb/bb]] [https://bips.me/checkout/invoice/cb/bb BIPS]

===Avoiding fraud===

You should also consider the possible risk that fraudsters could send counterfeit invoices to your customers, and entice them to make a payment to a Bitcoin address they control, instead of you. While that isn't likely in general - it depends on how well a fraudster could find out who your customers are in the first place - it would certainly be an unpleasant situation if it ever happened. One way you could control that is, whenever possible, never let people try to type Bitcoin addresses off payment stubs - instead, force people to get the full Bitcoin address from your website via secure SSL. But, still print ''most'' of the address on the payment stub (perhaps with four or five characters starred out), so that the customer's need for a paper trail can be satisfied, so they can prove they paid if there is ever a dispute.

==Setting Prices==

When a business accepts bitcoins for payment, there generally is the need to convert them to the currencies used for paying suppliers, employees and shareholders. Some merchants set prices based on the current market rate at the time the price quote is presented to the customer (merchant services like [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS], [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase] or [http://paysius.com Paysius] do this automatically).

[[Bitcoin Prices]] lists the exchange rate for many currencies on multiple exchanges.

When prices are determined using an automated process, the current market rate can be based on either a current price or on a weighted average basis. [[Bitcoin Charts]] provides a [http://bitcoincharts.com/about/markets-api data feed that provides weighted prices].

When bitcoin funds for purchases are received, some merchants instantly exchange those proceeds into the preferred currency used (again done automatically by [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS], [http://www.bit-pay.com Bit-pay] or [https://coinbase.com Coinbase]. Hedging for each transaction can nearly entirely eliminate exchange rate risk that the business is exposed to when accepting bitcoins for payment.

==Contract==

A sales contract might be used to ensure that specific terms are met to lessen the chances of a misunderstanding. For instance, the party sending payment is responsible for paying any [[transaction fee]] that might be necessary. A contract might specify that a transaction fee must be paid and what amount, so as to prevent the situation where the transaction is considered a low priority transaction and thus isn't confirmed quickly.

Other items that might be addressed in a contract:

* Requirement and handling of escrow through an [[:Category:Escrow_services|escrow service]].
* Jurisdiction for disputes.
* Refund policy (particularly with the exchange rate being volatile)

==Paying taxes on Bitcoin income==
[[Tax compliance]] is a topic of concern for small businesses. We aren't accountants or lawyers, and can't give legal or accounting advice.

But in many respects, Bitcoin transactions work very much like cash. Just like Bitcoin, cash is anonymous and doesn't leave a paper trail, yet is widely used in commerce every day.

Ask yourself how you would handle a cash transaction. Do you accept cash transactions? Do you normally pay taxes on cash transactions? The answer for Bitcoin should probably be the same.

As for how to decide what a Bitcoin transaction is worth... the IRS, as far as we know, has never issued a guide mentioning how to value Bitcoin transactions. But they probably have rules and guidelines on how to value transactions made in foreign currency or "cash equivalents". We imagine the accounting would be similar.

With Bitcoins, there's likely to be some difference between the value of BTC when you received them as payment, versus when you go to exchange them for another currency like USD, should you decide to do so. This scenario, likewise, would be no different if you accepted foreign currency or gold as payment. Under some scenarios, it might make sense to book the dollar value of BTC income as it is received, and then to book any difference incurred when it is exchanged for fiat currency. Under others, it might make sense to book the whole thing at the time of exchange.

Perhaps you might talk to your accountant. You don't need to get into a discussion with your accountant about block chains and private keys or the philosophy behind a decentralized currency. By comparing the fundamentals of Bitcoins to accounting concepts already well understood by the public, you can probably get all the answers you need. What would you ask your accountant if you decided that you wanted to accept ''Berkshire Bucks'' or 1-ounce gold coins as payment?

== Merchant Services ==
* [http://blockchain.info/api/api_receive Blockchain.info] Free APIs to process bitcoin payments. No sign up or account needed.
* [[File:BitcoinRegister.gif|20px|link=http://phicorp.ca/bitregister]] [http://phicorp.ca/bitregister Bitcoin Register] Bitcoin Point of Sales application for Android, with integration into various exchanges. Similar to Square.
* [[File:BIPS.gif|20px|link=https://bips.me]] [https://bips.me BIPS] Bitcoin Internet Payment System. A Bitcoin payment processor with mobile checkout, point of sale solutions.
* [https://www.bitpay.com BitPay] Bitcoin payment processor with mobile checkout solution
* [https://www.bitpagos.net BitPagos] Bitcoin and Credit Card payment processor
* [https://www.btcmerch.com BTCMerch] Payment processor for bitcoins and other cryptocurrencies. 0.5% transaction fee. Sandbox is available.
* [https://bitmerch.com BitMerch] Provides HTML buttons to start accepting bitcoins instantly. No server side setup required.
* [https://coinbase.com/docs/merchant_tools/payment_buttons Coinbase] Offers payment buttons, checkout pages, shopping cart integration, and daily cash out to USD.
* [[File:Coinkite.gif|20px|link=https://coinkite.com]] [https://coinkite.com/faq/terminal Coinkite] Full-reserve banking, payment buttons, invoice pages, hardware POS terminals, and Debit-Cards.
* [https://mtgox.com/merchant MTGOX] Bitcoin payment processing
* [https://www.okpay.com/en/services/accept-payments/index.html OKPAY] Bitcoin payment processing for merchants
* [http://fasterco.in Fasterco.in] Bitcoin payment processing for merchants and day-traders
* [http://snowcron.com Snowcron] Bitcoin Store Engine: Handles payments, sends your customers information they ordered (reg. codes, passwords...) No web programming required.

== Help this article ==

This article is a stub, please add to it!

==See Also==

* [[Merchant Howto]]
* [[In-store Transactions]]
* [[Tax compliance]]
* [[Securing online services]]
* [[BitCoins Mobile]] provides accurate up to date pricing from multiple exchanges from your Apple iPad, iPhone, or iPod Touch.
* [[Bitcoin PayFlow]] automates the process for accepting bitcoins
* [[Lazy API]] The lazy (and possibly easiest?) way to accept bitcoin payments on your website

[[Category:ECommerce]]
[[Category:Local]]

[[de:Bitcoin_als_Geschäft_akzeptieren]]

File:Mobile Web App Bitcoin Register.jpeg

2013-11-28T15:03:30Z

Btcto: Mobile Web App Bitcoin Register

== Summary ==
Mobile Web App Bitcoin Register
== Licensing ==
{{subst:nld}}

File:Rodolfo Novak.jpg

2013-11-28T15:01:49Z

Btcto: Btcto uploaded a new version of "File:Rodolfo Novak.jpg": Reverted to version as of 15:01, 28 November 2013