CryptAPI

• Name: CryptAPI
• URL: https://cryptapi.io/
• Category: crypto payment gateway / wallet-forwarding checkout glue / webhook tooling
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: CryptAPI is forwarding-and-webhook checkout glue. Point it at a merchant wallet, get a payment address back, verify the callback, and mind the minimum-deposit rules. Useful, but still a small merchant tool rather than a payment rail.
• What it does:
  • Lets merchants create payment addresses by passing their own wallet address into ticker-based API endpoints, with direct forwarding of customer payments to the merchant wallet
  • Supports custom checkout flows where the integrator controls the UI, amount display, QR code generation, and payment-state handling
  • Exposes service-information, conversion, QR-code, and logs endpoints so merchants can validate minimum amounts, quote prices, and monitor payment events
  • Publishes official libraries for Node.js, PHP, Python, and other languages plus official ecommerce plugins for platforms such as WooCommerce, Magento, PrestaShop, OpenCart, and Odoo
  • Sends signed webhooks for pending and confirmed transactions and documents RSA-SHA256 signature verification with a public key endpoint
  • Supports many cryptocurrencies and tokenized assets through a common ticker-based API pattern rather than per-chain bespoke integrations
• Key claims:
  • The homepage says CryptAPI is a “leading crypto payment gateway,” is trusted by “thousands of services worldwide,” charges fees “as low as 0.25%,” settles transactions automatically into the merchant wallet, and does not require registrations or API keys as a baseline path
  • The docs llms.txt says CryptAPI’s API paths do not use a v1 prefix, stresses that minimum transaction amounts are critical because sub-minimum deposits are ignored and funds are lost, and points AI/tooling users toward the custom-payment-flow guide as the core implementation reference
  • The custom-payment-flow guide says merchants only need to provide a wallet address, can receive pending and confirmed webhooks, and should always fetch and display per-asset minimum transaction thresholds before accepting payments
  • The service-information endpoint documents supported currencies, supported blockchains and tokens, minimum transaction amounts, fee tiers, and optional fiat price data
  • The webhook-signature guide says every webhook is signed with a 1024-bit RSA SHA256 signature in the x-ca-signature header and that integrators should verify signatures against the public key exposed at https://api.cryptapi.io/pubkey/
  • The ecommerce docs say plugins and integrations may involve account-style setup and API-key configuration, which suggests CryptAPI now supports both a lightweight wallet-address flow and a more managed plugin/dashboard workflow
• 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

• Stronger self-hosted merchant-stack anchor: btcpay-server

• Hosted Bitcoin processor contrast with more explicit settlement and payout machinery: opennode

• Last reviewed: 2026-06-02 UTC