Analysis updated 2026-05-18
Add Kaspa cryptocurrency as a checkout option in a WooCommerce store without paying transaction fees to a payment processor.
Accept crypto payments while keeping private keys off the server, using only a public key.
Automatically mark WooCommerce orders as paid once the required Kaspa amount is confirmed on the blockchain.
| hapince-code/kaspa-woocommerce-gateway | colin-johnston/hadron | crynobone/playground | |
|---|---|---|---|
| Stars | 5 | 6 | 4 |
| Language | PHP | PHP | PHP |
| Last pushed | — | 2016-03-27 | 2014-03-05 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 2/5 | 1/5 |
| Audience | pm founder | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires the PHP BCMath extension enabled and an account-level Kaspa public key (kpub), never a private key.
KaspaPay is a WooCommerce plugin that lets an online store built on WordPress accept payments in Kaspa, a cryptocurrency, directly from customers with no middleman. There are no subscription costs or processing fees taken by the plugin itself, and the payment goes straight from the customer's wallet to the merchant's wallet. The plugin only ever needs the store owner's extended public key, often called a kpub, which can generate new receive addresses but cannot spend any money. When a customer checks out, the plugin derives a fresh Kaspa address just for that order from the kpub using a standard hierarchical key derivation method. The customer sends the coins to that address, and the plugin repeatedly checks the public Kaspa blockchain through its REST API to see whether the required amount has arrived. Once the payment is confirmed on chain, WooCommerce automatically marks the order as paid. The README is explicit that a private key, seed phrase, or ordinary wallet address should never be entered, since the plugin is built to work only with the public key. To install it, the store owner uploads the plugin folder to the WordPress plugins directory, activates it, and configures it from the WooCommerce payment settings. The server needs the BCMath PHP extension enabled, and the owner pastes in their account level public key along with a starting address index. If the store's currency is not US dollars, they also need to enter a conversion rate. The plugin supports both the classic WooCommerce checkout and the newer checkout block, works with WooCommerce's custom order tables feature, and needs PHP 7.4 or newer plus WordPress 6.0 or newer. A few practical details are worth knowing. Customers can pay in more than one transaction, overpaying is not a problem since only the required amount is tracked, and database level protections stop two simultaneous checkouts from being assigned the same address. If an API call fails, the plugin retries and can fall back between different connection methods. Developers can hook into a few filters to point the plugin at a self hosted Kaspa API, change the QR code service, or customize the checkout icon. The project is open source and licensed under the GPL version 3 or later.
A WooCommerce plugin that lets a WordPress store accept Kaspa cryptocurrency payments directly, using only a public key so the plugin never touches customer funds.
Mainly PHP. The stack also includes PHP, WordPress, WooCommerce.
GPL v3 or later: free to use, modify, and distribute, but derivative works must also be released under the same license.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly pm founder.
This repo across BitVibe Labs
Verify against the repo before relying on details.