CryptAPI

• Name: CryptAPI
• URL: https://cryptapi.io/
• Category: crypto payment gateway / wallet-forwarding checkout glue / webhook middleware
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: CryptAPI is wallet-forwarding checkout glue. Hand it a wallet address, get a payment endpoint, verify the callback, and mind the minimums. Small tool, not a processor anchor.
• What it does:
  • Creates payment addresses by taking a merchant wallet address and forwarding customer funds straight through to that destination
  • Supports custom checkout flows where the merchant owns the UI, amount display, QR generation, and payment-state handling
  • Exposes service-info, conversion, QR, and logs endpoints so merchants can quote amounts, validate minimums, and reconcile payment events
  • Sends signed pending and confirmed webhooks and documents signature verification against a public key endpoint
  • Ships libraries and ecommerce plugins for the usual merchant stack, plus a wide ticker-based asset menu
• Key claims:
  • The lightweight path is the whole point: merchant supplies a wallet address, CryptAPI returns a payment address, and settlement forwards automatically without the usual account-first processor posture
  • Minimum-deposit handling matters more than the marketing copy because sub-minimum deposits can be ignored and effectively lost
  • The real operator surface is the webhook and service-info layer: signed callbacks, public-key verification, fee tiers, asset support, and per-asset minimum thresholds are all explicit
  • The plugin and dashboard path broadens the shell a little, but it still does not turn this into a merchant-ops anchor
• Whitepaper: No canonical standalone CryptAPI whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the official docs corpus, llms.txt, raw docs export, and the main site; see ../whitepapers/cryptapi-primary-sources-2026-04-30.md.
• Sources:
  • https://cryptapi.io/
  • https://docs.cryptapi.io/
  • https://docs.cryptapi.io/llms.txt
  • https://docs.cryptapi.io/get-started/custom-payment-flow
  • https://docs.cryptapi.io/api/raw/get-started/custom-payment-flow
  • https://docs.cryptapi.io/api/info
  • https://docs.cryptapi.io/webhooks/verify-webhook-signature
  • https://docs.cryptapi.io/api/raw/webhooks/verify-webhook-signature
  • https://docs.cryptapi.io/get-started/ecommerce
  • https://github.com/cryptapi

Internal linkages

• Best upward reads: coingate and opennode.

Control surface

• Power sits in address issuance and forwarding defaults, webhook truth, minimum-deposit policy, fee tiers, and supported-asset menus.

• Treat it as small merchant checkout glue. The multi-asset menu is breadth, not a new payments primitive.

• Last reviewed: 2026-06-16 UTC