Cowrie Research

coinsnap-primary-sources-2026-05-02

3 min read

Coinsnap primary sources — 2026-05-02

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current source of truth is Coinsnap’s official site, developer docs, webhook docs, payment-link docs, plugin catalog, and public GitHub organization.
  • The materials consistently make Coinsnap look broader than a plugin bundle or simple checkout button.

Primary-source snapshots

1) Main site / merchant positioning

  • URL: https://www.coinsnap.io/
  • Key excerpt:
    • The homepage says merchants can accept Bitcoin on-chain and Lightning payments in online stores, websites, and on-site.
    • It says merchants can receive funds directly into their own Bitcoin wallet or bank account.
    • It describes Coinsnap as a self-custody Bitcoin provider and highlights a self-custodial wallet with integrated POS support.

2) Developer docs homepage

  • URL: https://docs.coinsnap.io/
  • Key excerpt:
    • Coinsnap says developers can create an invoice, show a QR code, and get a webhook when paid.
    • The docs describe hosted checkout, dual Lightning/Bitcoin support behind one integration surface, and webhook-first settlement.
    • The docs emphasize that the merchant does not need to build wallet UX, QR rendering, or exchange-rate logic directly.

3) Quickstart

  • URL: https://docs.coinsnap.io/docs/getting-started/quickstart/
  • Key excerpt:
    • The quickstart says a merchant can accept a first Bitcoin payment in 15 minutes.
    • The invoice response includes both lightningInvoice and onchainAddress, plus a hosted checkoutLink.
    • The guide instructs merchants to confirm payment via signed webhooks, not redirect-based client signals.

4) Webhooks overview

  • URL: https://docs.coinsnap.io/docs/webhooks/webhooks-overview/
  • Key excerpt:
    • Coinsnap says only the webhook is reliable because redirects can be blocked, early, or spoofed.
    • Webhooks are signed with X-Coinsnap-Sig and an HMAC-based secret.
    • Event states include Settled, Processing, Expired, Invalid, and settlement edge cases such as Overpaid, Underpaid, and PaidAfterExpiration.
  • URL: https://docs.coinsnap.io/docs/use-cases/payment-links/payment-links-overview/
  • Key excerpt:
    • Coinsnap distinguishes between a long-lived pay link and short-lived generated Bitcoin invoices.
    • The pay link stays valid for 30 days by default, while each generated Bitcoin invoice has a 15-minute expiry.
    • The docs explicitly position pay links for asynchronous order-confirmation, email, account-area, and invoice-PDF payment flows.

6) Plugins catalog

  • URL: https://docs.coinsnap.io/docs/integrations/plugins/
  • Key excerpt:
    • Coinsnap lists official plugins across WooCommerce, Easy Digital Downloads, GiveWP, Paid Memberships Pro, Shopify by request, Shopware, Magento, PrestaShop, OpenCart, Wix, Drupal, pretix, and more.
    • The docs say each plugin handles API integration and links directly to installation repositories.
    • This breadth makes Coinsnap look like a merchant integration platform, not only a single checkout widget.

7) GitHub organization

  • URL: https://github.com/Coinsnap
  • Key excerpt:
    • The org tagline describes Coinsnap as a Lightning payment provider.
    • The repo inventory is centered on platform integrations such as WooCommerce, Magento, Wix, forms, donations, and a coinsnap-core package.
    • The public repo shape reinforces the view that Coinsnap distributes merchant-operating infrastructure through many surfaces.

Working conclusion

Coinsnap is best cataloged as a Bitcoin merchant-payments control plane with hosted checkout, webhook-driven reconciliation, asynchronous payment-link support, and a large integration/plugin footprint. The decisive evidence in this pass was the combination of one API covering Lightning plus on-chain, signed settlement webhooks, long-lived pay links for offline or delayed billing, self-custodial/POS language on the main site, and a wide first-party integration catalog across commerce and CMS ecosystems.

Graph View