SHKeeper

SHKeeper is a self-hosted, open-source cryptocurrency payment processor that combines gateway and merchant capabilities.

  • Business & Finance
  • Crypto Currency
SHKeeper is a self-hosted, open-source cryptocurrency payment processor that combines gateway and merchant capabilities. It integrates with CMS platforms, e-commerce stores, and custom applications via a REST API, letting you accept payments in multiple cryptocurrencies without fees or third-party intermediaries. Built for developers and small businesses that want full control over their crypto payment infrastructure without relying on external processors.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

63/100 Good

Maintained
83last commit 82 days ago
Popular
56649 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
71no serious findings, 4 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
649
Open issues
25
Last commit
2026-08-31
Latest release
v2.5.32
License
GPL-3.0
Activity
stale

Checked today - source: GitHub (vsys-host/shkeeper.io)

Resources & Compatibility

Requirements not published yet.

Checked today - source: Docker Hub image tags and published docs

First-install notes

  • Replace the example demo address The snippets show demo.shkeeper.io, but point your own tools at your SHKeeper server address. Using the demo address or a wrong path will send requests elsewhere and can make your install look broken. source
  • Use the right API credential Balance and invoice calls use an API key (a secret token) in the X-Shkeeper-Api-Key header, while the metrics endpoint uses Basic Authentication (a username and password). If you use the wrong one, the API will reject the request. source
  • Check which coins are enabled Call /api/v1/crypto to see which cryptocurrencies are online and enabled in the admin panel before checking balances or invoices. If a coin is not in that list, SHKeeper is not currently set up to use it. source

Fetched today - each note links to its source

Alternatives (6)

Checked today - source: AlternativeTo

Common questions

What API setup details commonly matter for invoices and balances?

Point your tools at your own server URL instead of the demo example, and use an API key in the X-Shkeeper-Api-Key header for balance/invoice calls while the metrics endpoint uses Basic Authentication. Call /api/v1/crypto to confirm which coins are enabled before checking balances or invoices.

How should SHKeeper webhook callbacks be validated?

Verify invoice and payout callback signatures using HMAC-SHA256. The documentation provides step-by-step examples for Python, Flask, and PHP.

Do incoming payment funds stay under the operator's control?

SHKeeper generates receiving addresses and tracks transactions, but the funds settle into wallets you control.

Answers sourced from github.com, shkeeper.io, zendot.org

Community

Collected today - public community threads