├── .github └── funding.yml ├── CONTRIBUTING.md ├── LICENSE ├── README.md └── media ├── logo.svg └── social-preview.png /.github/funding.yml: -------------------------------------------------------------------------------- 1 | custom: https://mynode.alexkaul.com/gh-donate 2 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | Please ensure your pull request adheres to the following guidelines: 4 | 5 | - If you're adding a bitcoin payment processor, keep the table structure and fill all the columns with a correct data. 6 | - If you're adding a merchant story, use the following format: `- [Processor Name] [Story Title](link)` 7 | - Make an individual pull request for each suggestion. 8 | - New categories, comparison columns or improvements to the existing categorization are welcome. 9 | - Check your spelling and grammar. 10 | - The pull request should have a descriptive title in the format Add Name of Processor (Example: Add BTCPay Server), not Update readme.md or Add Processor. 11 | 12 | ## Adding something to the list 13 | 14 | If you have something awesome to contribute to the list, this is how you do it. 15 | 16 | You'll need a [GitHub account](https://github.com/join)! 17 | 18 | 1. Access the list's GitHub page: https://github.com/alexk111/awesome-bitcoin-payment-processors 19 | 2. Click on the `readme.md` file. 20 | 3. Now click on the `edit this file` button (pencil icon). 21 | 4. You can start editing the text of the file in the in-browser editor. You can use [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). 22 | 5. Say why you're proposing the changes, and then click on "Propose file change". 23 | 6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)! 24 | 25 | ## Updating your Pull Request 26 | 27 | Sometimes, a maintainer of the list will ask you to edit your Pull Request before it is included. This is normally due to spelling errors or because your PR didn't match the list guidelines. 28 | 29 | [Here](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) is a write up on how to change a Pull Request, and the different ways you can do that. 30 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 12 | HEREUNDER. 13 | 14 | Statement of Purpose 15 | 16 | The laws of most jurisdictions throughout the world automatically confer 17 | exclusive Copyright and Related Rights (defined below) upon the creator 18 | and subsequent owner(s) (each and all, an "owner") of an original work of 19 | authorship and/or a database (each, a "Work"). 20 | 21 | Certain owners wish to permanently relinquish those rights to a Work for 22 | the purpose of contributing to a commons of creative, cultural and 23 | scientific works ("Commons") that the public can reliably and without fear 24 | of later claims of infringement build upon, modify, incorporate in other 25 | works, reuse and redistribute as freely as possible in any form whatsoever 26 | and for any purposes, including without limitation commercial purposes. 27 | These owners may contribute to the Commons to promote the ideal of a free 28 | culture and the further production of creative, cultural and scientific 29 | works, or to gain reputation or greater distribution for their Work in 30 | part through the use and efforts of others. 31 | 32 | For these and/or other purposes and motivations, and without any 33 | expectation of additional consideration or compensation, the person 34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 35 | is an owner of Copyright and Related Rights in the Work, voluntarily 36 | elects to apply CC0 to the Work and publicly distribute the Work under its 37 | terms, with knowledge of his or her Copyright and Related Rights in the 38 | Work and the meaning and intended legal effect of CC0 on those rights. 39 | 40 | 1. Copyright and Related Rights. A Work made available under CC0 may be 41 | protected by copyright and related or neighboring rights ("Copyright and 42 | Related Rights"). Copyright and Related Rights include, but are not 43 | limited to, the following: 44 | 45 | i. the right to reproduce, adapt, distribute, perform, display, 46 | communicate, and translate a Work; 47 | ii. moral rights retained by the original author(s) and/or performer(s); 48 | iii. publicity and privacy rights pertaining to a person's image or 49 | likeness depicted in a Work; 50 | iv. rights protecting against unfair competition in regards to a Work, 51 | subject to the limitations in paragraph 4(a), below; 52 | v. rights protecting the extraction, dissemination, use and reuse of data 53 | in a Work; 54 | vi. database rights (such as those arising under Directive 96/9/EC of the 55 | European Parliament and of the Council of 11 March 1996 on the legal 56 | protection of databases, and under any national implementation 57 | thereof, including any amended or successor version of such 58 | directive); and 59 | vii. other similar, equivalent or corresponding rights throughout the 60 | world based on applicable law or treaty, and any national 61 | implementations thereof. 62 | 63 | 2. Waiver. To the greatest extent permitted by, but not in contravention 64 | of, applicable law, Affirmer hereby overtly, fully, permanently, 65 | irrevocably and unconditionally waives, abandons, and surrenders all of 66 | Affirmer's Copyright and Related Rights and associated claims and causes 67 | of action, whether now known or unknown (including existing as well as 68 | future claims and causes of action), in the Work (i) in all territories 69 | worldwide, (ii) for the maximum duration provided by applicable law or 70 | treaty (including future time extensions), (iii) in any current or future 71 | medium and for any number of copies, and (iv) for any purpose whatsoever, 72 | including without limitation commercial, advertising or promotional 73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 74 | member of the public at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be subject to 76 | revocation, rescission, cancellation, termination, or any other legal or 77 | equitable action to disrupt the quiet enjoyment of the Work by the public 78 | as contemplated by Affirmer's express Statement of Purpose. 79 | 80 | 3. Public License Fallback. Should any part of the Waiver for any reason 81 | be judged legally invalid or ineffective under applicable law, then the 82 | Waiver shall be preserved to the maximum extent permitted taking into 83 | account Affirmer's express Statement of Purpose. In addition, to the 84 | extent the Waiver is so judged Affirmer hereby grants to each affected 85 | person a royalty-free, non transferable, non sublicensable, non exclusive, 86 | irrevocable and unconditional license to exercise Affirmer's Copyright and 87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 88 | maximum duration provided by applicable law or treaty (including future 89 | time extensions), (iii) in any current or future medium and for any number 90 | of copies, and (iv) for any purpose whatsoever, including without 91 | limitation commercial, advertising or promotional purposes (the 92 | "License"). The License shall be deemed effective as of the date CC0 was 93 | applied by Affirmer to the Work. Should any part of the License for any 94 | reason be judged legally invalid or ineffective under applicable law, such 95 | partial invalidity or ineffectiveness shall not invalidate the remainder 96 | of the License, and in such case Affirmer hereby affirms that he or she 97 | will not (i) exercise any of his or her remaining Copyright and Related 98 | Rights in the Work or (ii) assert any associated claims and causes of 99 | action with respect to the Work, in either case contrary to Affirmer's 100 | express Statement of Purpose. 101 | 102 | 4. Limitations and Disclaimers. 103 | 104 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 105 | surrendered, licensed or otherwise affected by this document. 106 | b. Affirmer offers the Work as-is and makes no representations or 107 | warranties of any kind concerning the Work, express, implied, 108 | statutory or otherwise, including without limitation warranties of 109 | title, merchantability, fitness for a particular purpose, non 110 | infringement, or the absence of latent or other defects, accuracy, or 111 | the present or absence of errors, whether or not discoverable, all to 112 | the greatest extent permissible under applicable law. 113 | c. Affirmer disclaims responsibility for clearing rights of other persons 114 | that may apply to the Work or any use thereof, including without 115 | limitation any person's Copyright and Related Rights in the Work. 116 | Further, Affirmer disclaims responsibility for obtaining any necessary 117 | consents, permissions or other rights required for any use of the 118 | Work. 119 | d. Affirmer understands and acknowledges that Creative Commons is not a 120 | party to this document and has no duty or obligation with respect to 121 | this CC0 or use of the Work. 122 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 |
2 | Awesome Bitcoin Payment Processors 3 |
4 | 5 | # Awesome Bitcoin Payment Processors [![Awesome](https://awesome.re/badge-flat.svg)](https://awesome.re) 6 | 7 | A curated list of awesome Bitcoin payment processors enabling merchants, businesses and nonprofits to accept Bitcoin payments. 8 | 9 | ## Contents 10 | 11 | - [Self-Hosted Bitcoin Payment Processors](#self-hosted-bitcoin-payment-processors) 12 | - [Hosted Bitcoin Payment Processors](#hosted-bitcoin-payment-processors) 13 | - [Non-Custodial](#non-custodial) 14 | - [Custodial](#custodial) 15 | - [Backers 💝](#backers-) 16 | 17 | ## Self-Hosted Bitcoin Payment Processors 18 | 19 | Self-Hosted payment processors run on your server and provide you with a full control over the entire payment process and funds. There's no third-party involvement - that significantly increases the censorship-resistance, privacy, and security for you and your customers. 20 | 21 | | Processor | Fees | Lightning | Directly to Your Wallet | Conversion to Fiat | Requirements | 22 | | --------- |:----:|:---------:|:-----------------------:|:------------------:| ------------ | 23 | | [BTCPay Server](https://btcpayserver.org/) | No fees | Yes | Yes | Via [Strike plugin](https://github.com/Marfusios/strike-btcpayserver-plugin) or [Exchange Integration](https://redbtc.org/flows/integrations/kraken-exchange/) | 2 GB RAM, 80 GB Storage, Docker | 24 | | [One Time Address](https://github.com/alexk111/One-Time-Address) | No fees | No | Yes | No | NodeJS | 25 | | [CryptoWoo](https://www.cryptowoo.com/) | $34 - $99 per year | No | Yes | No | PHP 5.6+, Wordpress 4.3+, WooCommerce 3.0+ | 26 | | [BitcartCC](https://bitcartcc.com) | No fees | Yes | Yes | No | 1 GB RAM, 10 GB Storage, Docker | 27 | | [LnMe](https://github.com/bumi/lnme) | No fees | Yes | Yes | No | LND node | 28 | | [SatSale](https://github.com/SatSale/SatSale) | No fees | Yes | Yes | Weakhands: [swap to USDT on Liquid](https://github.com/SatSale/SatSale/blob/471c8c03bbc269df1f322f6484b6e7a7364e5b34/config.toml#L101), no-KYC | Python. Bitcoin node, Lightning node & WooCommerce optional. | 29 | | [Keagate](https://github.com/dilan-dio4/Keagate) | No fees | No | Yes | No | 1 GB RAM, Unix | 30 | | [LNURL Daemon](https://github.com/yanascz/lnurld) | No fees | Yes | Yes | No | LND node | 31 | 32 | ## Hosted Bitcoin Payment Processors 33 | 34 | Hosted payment processors run on someone else's server. This simplifies the initial setup process, but reduces the amount of control you have over the payment process. 35 | 36 | ### Non-Custodial 37 | 38 | These processors use your wallets for receiving payments. 39 | 40 | | Processor | Fees | Lightning | Directly to Your Wallet | Conversion to Fiat | Requirements | 41 | | --------- |:----:|:---------:|:-----------------------:|:------------------:| ------------ | 42 | | [Blockonomics](https://www.blockonomics.co/merchants) | 1% | No | Yes | Via [Payment Forwarding](https://www.blockonomics.co/views/payment_forwarding.html) | No | 43 | | [Payscrypt](https://payscrypt.com/) | No fees | No | Yes | No | No | 44 | | [Bitrequest](https://bitrequest.io/) | No fees | Yes | Yes | No | No | 45 | | [Zaprite](https://zaprite.com/) | $25 per month | Yes | Yes | No | No | 46 | | [Paymento](https://paymento.io/) | 0.5% | No | Yes | No | No | 47 | | [Flash](https://paywithflash.com/) | 1.5% | Yes | Yes | No | No | 48 | 49 | ### Custodial 50 | 51 | The following processors use their own wallets, not yours, for receiving payments. 52 | 53 | ⚠ They not only collect data about payments, they have full control over the funds. There are many risks associated with custodians, which might end up with lost/locked funds. 54 | 55 | ⚠ Most of them have KYB/KYC/AML requirements, which poses a serious threat to your and your customers' privacy. 56 | 57 | ⚠ They have country-based restrictions for merchants and merchants' customers. 58 | 59 | | Processor | Fees | Lightning | Directly to Your Wallet | Conversion to Fiat | Requirements | 60 | | --------- |:----:|:---------:|:-----------------------:|:------------------:| ------------ | 61 | | [Confirmo](https://confirmo.net/) | 1.3% (0.8% invoicing + 0.5% payouts) | Yes | No | Yes | Information about business / website. May require certain documents. | 62 | | [CoinGate](https://coingate.com/accept) | 1% (merchant) + some [variable service fee](https://support.coingate.com/en/109/why-does-coingate-charge-service-fee) (customer) | Yes | No | Yes | Requires [a lot of information and business documents](https://blog.coingate.com/2019/05/verify-merchant-account-faq), officially translated in english. | 63 | | [CoinPayments](https://www.coinpayments.net/) | 0.5% | Yes | No | No | On withdrawal may require a number of forms of identification and will require settlement of any outstanding amounts. | 64 | | [OpenNode](https://www.opennode.co/) | 1% | Yes | No | Yes | Requires [KYC/KYB documents](https://help.opennode.com/en/articles/3654899-kyc-and-kyb-requirements) | 65 | | [Strike](https://strike.me/business/) | 1% | Only | No | No | Requires [basic business info, documents, identity verifications of owners and operators](https://strike.me/faq/how-do-i-sign-up-for-a-strike-business-account/). | 66 | | [Coinremitter](https://coinremitter.com/) | 0.23% + 0.0001 | No | No | No | No | 67 | | [Utrust](https://utrust.com/) | 1% | No | No | Yes | Require certain documents. | 68 | | [NOWPayments](https://nowpayments.io/) | ≤0.5% | No | No | No | KYC/AML procedure applied to certain clients, wallet addresses and select assets. | 69 | | [ElenPAY](https://elenpay.tech) | ≤1% | Yes | Yes | No (Soon) | Low KYC | 70 | | [Speed](https://tryspeed.com/) | 1% | Yes | No | No | No | 71 | | [Sheepy](https://www.sheepy.com/) | 1% + $0.25 | No | No | Yes | Requires [KYB documents](https://www.sheepy.com/faq/what-documents-are-required-to-verify-my-merchant-account) | 72 | | [ALFAcoins](https://www.alfacoins.com/) | 0.99% | No | No | No | Requires KYB documents | 73 | | [Apirone](https://apirone.com/) | 1% | No | No | No | No | 74 | 75 | ## Backers 💝 76 | 77 | [![Backer](https://mynode.alexkaul.com/gh-backer/top/0/avatar/60)](https://mynode.alexkaul.com/gh-backer/top/0/profile) 78 | [![Backer](https://mynode.alexkaul.com/gh-backer/top/1/avatar/60)](https://mynode.alexkaul.com/gh-backer/top/1/profile) 79 | [![Backer](https://mynode.alexkaul.com/gh-backer/top/2/avatar/60)](https://mynode.alexkaul.com/gh-backer/top/2/profile) 80 | [![Backer](https://mynode.alexkaul.com/gh-backer/top/3/avatar/60)](https://mynode.alexkaul.com/gh-backer/top/3/profile) 81 | [![Backer](https://mynode.alexkaul.com/gh-backer/top/4/avatar/60)](https://mynode.alexkaul.com/gh-backer/top/4/profile) 82 | [![Backer](https://mynode.alexkaul.com/gh-backer/top/5/avatar/60)](https://mynode.alexkaul.com/gh-backer/top/5/profile) 83 | [![Backer](https://mynode.alexkaul.com/gh-backer/top/6/avatar/60)](https://mynode.alexkaul.com/gh-backer/top/6/profile) 84 | [![Backer](https://mynode.alexkaul.com/gh-backer/top/7/avatar/60)](https://mynode.alexkaul.com/gh-backer/top/7/profile) 85 | [![Backer](https://mynode.alexkaul.com/gh-backer/top/8/avatar/60)](https://mynode.alexkaul.com/gh-backer/top/8/profile) 86 | [![Backer](https://mynode.alexkaul.com/gh-backer/top/9/avatar/60)](https://mynode.alexkaul.com/gh-backer/top/9/profile) 87 | 88 | [[Donate](https://mynode.alexkaul.com/gh-donate)] Thank you for your support! 🙌 89 | -------------------------------------------------------------------------------- /media/logo.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /media/social-preview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alexk111/awesome-bitcoin-payment-processors/6c70ac4a1ff436d17b52dcd7c2eb2448ff45a79c/media/social-preview.png --------------------------------------------------------------------------------