SHKeeper primary sources — 2026-05-02

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is SHKeeper’s official site, knowledge base, main GitHub README, and live API documentation.
• The materials consistently describe SHKeeper as self-hosted payments infrastructure rather than as a simple plugin or wallet front end.

Primary-source snapshots

1) Main site

• URL: https://shkeeper.io/
• Key excerpt:
  • The homepage says SHKeeper is a self-hosted and open-source cryptocurrency payment processor and emphasizes the “unique combination of gateway and merchant.”
  • It highlights direct crypto payments, self-set commissions, partial payments, overpayment crediting, auto-withdrawals, non-custodial control, no KYC, and customizable deployment.
  • The roadmap and announcements also show the product evolving into a wider multichain operating stack, including Lightning support and later additions such as Solana, Arbitrum, Optimism, and TON-related support.

2) Knowledge-base intro

• URL: https://shkeeper.io/kb/launch/what-is-shkeeper
• Key excerpt:
  • The KB says SHKeeper is a free-of-charge open-source cryptoprocessor aimed at e-commerce but not limited to it.
  • It explicitly says operators can deploy it on their own servers and accept crypto payments directly on their website.
  • This strengthens the self-hosted merchant-infrastructure framing.

3) Main README

• URL: https://raw.githubusercontent.com/vsys-host/shkeeper.io/master/README.md
• Key excerpt:
  • The README says SHKeeper is an open-source, self-hosted cryptocurrency payment processor that serves as both gateway and merchant.
  • It lists a wide supported-asset surface and features including non-custodial operation, direct payments, no transaction fees or third parties, adjustable exchange rates and fees, overpayment handling, partial payments, auto-payments to cold wallets, and multipayout.
  • The installation and architecture sections also show that SHKeeper is a real operational stack with Kubernetes/Helm deployment paths, optional LNURL support, and chain-specific infrastructure choices.

4) Payment-flow and invoice semantics from README

• URL: https://raw.githubusercontent.com/vsys-host/shkeeper.io/master/README.md
• Key excerpt:
  • The payment-flow section says each created invoice corresponds to a unique address for the selected cryptocurrency and is tied to a merchant external_id.
  • It explains that callbacks are used for payment notifications and that invoice states include UNPAID, PARTIAL, PAID, and OVERPAID.
  • This is decisive evidence that SHKeeper is packaging real merchant reconciliation and workflow semantics, not only wallet monitoring.

5) Live API docs

• URL: https://shkeeper.io/api/
• Key excerpt:
  • The API docs describe API-key auth for invoice and wallet operations and Basic auth for payout-related endpoints.
  • They document endpoints for available cryptocurrencies, invoice creation and lookup, payout and multipayout task creation, task-status checking, and metrics.
  • Example payloads show callback URLs, external_id-linked invoices, generated deposit addresses, fee policies, payout destinations, and result tracking.

6) Wallet management and payment-transfer guide

• URL: https://shkeeper.io/kb/use-cases/wallet-management-and-payment-transfer-guide
• Key excerpt:
  • The guide explains invoice-amount-plus-network-fee expectations, configurable lower and upper success thresholds, partial-payment handling, and overpayment crediting.
  • That page reinforces that SHKeeper exposes tunable merchant payment-operations logic, not just address generation.

7) Provider / integration page

• URL: https://vsys.host/shkeeper
• Key excerpt:
  • The hosting/provider page says SHKeeper can let the operator “become a processor yourself” and highlights open-source deployment, custom integrations, free WooCommerce/WordPress and WHMCS plugins, and optional support tiers.
  • It also surfaces resource requirements and chain-specific node burdens, confirming that the product has substantial operator-facing infrastructure depth.

Working conclusion

SHKeeper is best cataloged as self-hosted merchant payments and payout infrastructure: a multichain operational stack for invoice creation, callback-based reconciliation, cold-wallet withdrawal, and treasury-style payout workflows. The decisive evidence in this pass was the combination of self-hosted positioning, explicit invoice-state semantics, callback flows, payout/multipayout APIs, and the repeated claim that operators can effectively become their own processor.