SHKeeper

• Name: SHKeeper
• URL: https://shkeeper.io/
• Category: self-hosted merchant stack / multichain checkout and payout appliance
• Tags: bitcoin-ecosystem ethereum-ecosystem solana-ecosystem
• Summary: SHKeeper is a self-hosted merchant processor with a broad chain menu, invoice-state handling, callbacks, and payout tooling. The point is not supports many coins. The point is that the operator becomes the processor: unique deposit addresses, partial and overpaid invoice handling, payouts, auto-withdrawal, and the node burden that comes with it. Real merchant plumbing, still a secondary stack.
• What it does:
  • Lets merchants self-host a non-custodial crypto payment processor that routes funds to operator-controlled wallets rather than SHKeeper custody
  • Generates invoice-linked deposit addresses, tracks invoice states such as unpaid, partial, paid, and overpaid, and sends callbacks to merchant systems
  • Exposes invoice APIs plus payout and multipayout workflows for operator disbursement and treasury handling
  • Supports a broad multi-asset stack spanning Bitcoin, Litecoin, Dogecoin, Monero, XRP, Tron, Ethereum-family assets, Solana, and token variants such as USDT and USDC
  • Offers auto-withdrawal to cold wallets, adjustable rates and commissions, overpayment crediting, and configurable payment-success thresholds
  • Provides plugins for systems such as WooCommerce / WordPress and WHMCS while also supporting custom integrations through the API
• Key claims:
  • The official site says SHKeeper is a self-hosted, open-source cryptocurrency payment processor that combines gateway and merchant roles so businesses can accept multiple cryptocurrencies without intermediaries
  • The knowledge-base intro says the software is free, open-source, deployable on the user’s own servers, and meant for direct crypto acceptance without processor commissions
  • The README stresses the non-custodial model and positions SHKeeper as a way to “become a payment processor yourself,” which is the clearest taxonomy signal in the source set
  • The payment-flow docs say each invoice gets a unique cryptocurrency address tied to the merchant’s external_id, with explicit status handling for UNPAID, PARTIAL, PAID, and OVERPAID outcomes
  • The live API docs show SHKeeper is more than a checkout form: it exposes separate auth modes, invoice creation and lookup, payout tasks, multipayout tasks, and task-status retrieval
  • The site and README both describe auto-withdrawal, exchange-rate and commission controls, and operational resource requirements that vary materially with the chains and nodes an operator chooses to support
• 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.
• Sources:
  • https://shkeeper.io/
  • https://shkeeper.io/kb/launch/what-is-shkeeper
  • https://shkeeper.io/api/
  • https://shkeeper.io/kb/use-cases/wallet-management-and-payment-transfer-guide
  • https://raw.githubusercontent.com/vsys-host/shkeeper.io/master/README.md
  • https://vsys.host/shkeeper

Internal linkages

• Best upward reads: btcpay-server and bitcart.

Control surface

• Power sits in wallet and node coverage, invoice-state policy, callback truth, payout permissions, auto-withdraw defaults, exchange-rate handling, and how much operational burden the merchant is willing to own.

• The broad asset menu matters less than the choice to run a processor-shaped stack yourself.

• Last reviewed: 2026-06-15 UTC