Cowrie Research

zaprite

3 min read

Zaprite

  • Name: Zaprite
  • URL: https://zaprite.com/
  • Category: Bitcoin payments infrastructure / hosted checkout and invoicing control plane / non-custodial merchant payment gateway
  • Tags: bitcoin-ecosystem
  • Summary: Zaprite is hosted merchant ops with a non-custodial wallet handoff. Orders, checkouts, payment links, invoices, event tickets, POS, and webhook reconciliation are the package. Useful operator tooling, not a new rail.
  • What it does:
    • Lets businesses accept bitcoin payments with Lightning and onchain rails, plus fiat payment options, through hosted checkouts and payment links
    • Exposes a public API for Orders, Contacts, and Webhooks so developers can create custom checkout and order flows
    • Supports invoices, recurring invoices, payment requests, event-ticket sales, and point-of-sale workflows for merchants and operators
    • Uses redirect-based checkout flows where merchants create an order, send a customer to checkoutUrl, and reconcile state through webhook events
    • Provides sandbox organizations, scoped API keys, and an official JavaScript SDK for testing and integration work
    • Lets businesses connect their own wallets and emphasizes that payments flow directly into the merchant wallet rather than Zaprite custody
  • Key claims:
    • The homepage says Zaprite helps businesses “migrate to a bitcoin standard,” supports “any wallet,” and offers “integrated checkout” for bitcoin and fiat while requiring “no server” for merchants using the hosted product
    • Zaprite explicitly says “Zaprite is not a payment processor-we never touch your money. Payments flow directly into your wallet of choice,” which is the clearest signal that it should be cataloged as non-custodial merchant infrastructure
    • The developers page frames Zaprite as a public API and webhook service for “custom bitcoin, lightning and card payment flows” and links directly to the API reference
    • The API llms.txt says the API is designed for hosted checkout flows and defines a concrete integration pattern: create an order, redirect the customer to checkoutUrl, and subscribe to webhook events to keep the merchant system synchronized
    • The API docs show versioned /v1 resources such as /v1/orders and /v1/webhooks, bearer-token authentication, paginated list responses, metadata fields, and sandbox testing guidance, which is much stronger evidence of a real merchant-integration platform than the marketing site alone
    • The help center taxonomy exposes a broad product surface including Accounts, Organizations, Contacts, Connections, Payment Links, Event Tickets, Invoices, Recurring Invoices, Point of Sale, Payment Requests, Checkouts, Orders, Transactions, and API support
    • The OpenAPI-derived docs enumerate supported settlement and pricing currencies well beyond BTC alone, including fiat currencies plus BTC, USDC, USDT, and LBTC, which reinforces that Zaprite is packaging a broader payment operations layer rather than a narrow Bitcoin-only QR tool
  • Whitepaper: No canonical standalone Zaprite whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site, developers page, API docs, llms.txt, and help-center corpus; see ../whitepapers/zaprite-primary-sources-2026-04-30.md.
  • Sources:

Internal linkages

Control surface

  • Power sits in order creation, checkout redirects, connected-wallet defaults, webhook truth, organization and API-key policy, and which merchant workflows Zaprite keeps inside its own hosted surface.

  • The useful read is hosted merchant operations. The bitcoin standard story is branding over that.

  • Last reviewed: 2026-06-04 UTC

Graph View