Category: self-hosted crypto payment processor / multichain merchant payments and payout control plane / open-source e-commerce integration infrastructure
Summary: SHKeeper is best understood as a self-hosted merchant-payments and payout control plane rather than as a simple wallet or lightweight checkout plugin. Its official site, knowledge base, main README, and live API docs consistently describe an open-source processor that generates invoice-linked deposit addresses, tracks invoice states such as unpaid/partial/paid/overpaid, pushes callbacks to merchant systems, supports payout and multipayout workflows, auto-withdraws to cold wallets, and exposes plugins or custom API integrations for e-commerce stacks. The crucial categorization clue is that SHKeeper is designed not only to let a merchant accept crypto directly, but to let operators effectively become their own processor on top of a broad multichain stack.
What it does:
Lets merchants self-host a crypto payment processor that receives funds directly into operator-controlled wallets rather than into SHKeeper custody
Supports invoice-based payment flows with unique addresses per order, callback notifications, and explicit invoice-state handling for unpaid, partial, paid, and overpaid outcomes
Exposes API-key-protected invoice APIs plus Basic-auth payout and multipayout APIs for operational disbursement workflows
Supports multichain acceptance across Bitcoin, Litecoin, Dogecoin, Monero, XRP, Tron, Ethereum-family assets, Solana, and other token/network variants
Offers auto-withdrawal, adjustable rates and commissions, overpayment crediting, and configurable payment-success thresholds for merchant operations
Provides ready-made integrations for systems such as WooCommerce / WordPress and WHMCS while also allowing custom integrations through the API
Key claims:
The main site says SHKeeper is a self-hosted and open-source cryptocurrency payment processor that combines gateway and merchant roles so businesses can accept multiple cryptocurrencies without intermediaries
The knowledge-base intro says SHKeeper is free-of-charge, open-source, deployable on a user’s own servers, and intended to let users accept crypto payments directly on their website without commission
The README says SHKeeper uniquely serves as both gateway and merchant, highlights non-custodial direct acceptance, and lists a broad multi-asset surface including BTC, ETH, LTC, DOGE, XMR, XRP, TRX, BNB, SOL, MATIC, AVAX, FIRO, USDT, and USDC variants
The README’s payment-flow section explains that each created invoice corresponds to a unique cryptocurrency address tied to the merchant’s external_id, with callback notifications and explicit states including UNPAID, PARTIAL, PAID, and OVERPAID
The live API docs document separate auth modes, invoice creation, invoice lookup, payout tasks, multipayout tasks, and task-status retrieval, which makes SHKeeper look like a full merchant-ops and treasury surface rather than a narrow checkout form
The site and README both describe auto-withdrawal to cold wallets, adjustable exchange rates and commissions, and the ability to become a processor yourself, which pushes SHKeeper toward payment-operations infrastructure rather than a one-store plugin
The hosting/provider materials stress that resource requirements vary significantly by supported chains and node choices, revealing a much thicker operational footprint than a simple hosted gateway brand would usually expose
Whitepaper: No canonical standalone SHKeeper whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, knowledge base, main README, and live API docs; see ../whitepapers/shkeeper-primary-sources-2026-05-02.md.