Zaprite primary sources — 2026-04-30

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is the main site, developers page, public API docs, llms.txt, and help-center taxonomy.

Primary-source snapshots

1) Main site

• URL: https://zaprite.com/
• Key excerpt:
  • Zaprite says it helps businesses “migrate to a bitcoin standard.”
  • The homepage highlights support for “any wallet,” “global, borderless payments,” “integrated checkout,” and “simple onboarding.”
  • The homepage also says: “Zaprite is not a payment processor-we never touch your money. Payments flow directly into your wallet of choice.”
• Notes:
  • The homepage is enough to recover the non-custodial merchant-payments framing, but not enough by itself to show the full operator and developer surface.

2) Developers page

• URL: https://zaprite.com/developers
• Key excerpt:
  • The page says Zaprite’s “public API and webhook service” is intended for developers building custom bitcoin, lightning, and card-payment flows.
  • It explicitly directs builders to an “API Reference.”
• Notes:
  • This page is the bridge from marketing copy to the operational API surface.

3) API landing page

• URL: https://api.zaprite.com/
• Key excerpt:
  • The API landing page links first-party resources for LLM Docs, OpenAPI JSON, the official JS SDK, sandbox guidance, and support.
• Notes:
  • This confirms that the API is a maintained first-class product surface, not an incidental internal endpoint.

4) API llms.txt

• URL: https://api.zaprite.com/llms.txt
• Key excerpt:
  • The docs describe Zaprite as “a single API for Orders, Contacts, and Webhooks.”
  • They say the API is “designed for hosted checkout flows: create an order, send your customer to checkoutUrl, and use webhook events to keep your own product in sync.”
  • The docs specify bearer-token auth, versioned /v1 paths such as /v1/orders and /v1/webhooks, sandbox testing, metadata support, and paginated list responses.
• Notes:
  • This was the highest-signal source for recovering Zaprite’s true product shape in this pass.

5) OpenAPI-described order model

• URL: https://api.zaprite.com/openapi.json
• Key excerpt:
  • The order schema includes hosted-checkout fields such as redirectUrl, redirectIfPending, customerData, customerFields, metadata, tags, and optional invoice payloads with line items.
  • The exposed currency list includes fiat currencies plus BTC, USDC, USDT, and LBTC.
• Notes:
  • This is strong evidence that Zaprite is packaging a full merchant payment workflow rather than only static QR acceptance.

6) Help-center home

• URL: https://help.zaprite.com/
• Key excerpt:
  • The first-party help taxonomy spans Accounts, Organizations, Contacts, Connections, Payment Links, Event Tickets, Invoices, Recurring Invoices, Point of Sale, Payment Requests, Checkouts, Orders, Transactions, API, and product updates.
• Notes:
  • The help-center structure is useful because it shows the operational breadth of the platform even when individual marketing pages stay concise.

7) API help collection

• URL: https://help.zaprite.com/en/collections/10412605-api
• Key excerpt:
  • The visible article in the API collection is “How to test payments for an API integration.”
• Notes:
  • Even this sparse collection page confirms that Zaprite maintains explicit API-integration support and testing guidance.

8) Point-of-sale help collection

• URL: https://help.zaprite.com/en/collections/10334945-point-of-sale-pos
• Key excerpt:
  • The collection is described as “Learn more about Zaprite’s Point of Sale (POS) feature.”
• Notes:
  • This is additional evidence that Zaprite is not only an API or invoice tool; it also maintains an in-person merchant workflow.

Working conclusion

Zaprite is best cataloged as non-custodial Bitcoin-first merchant payments infrastructure with a broader checkout, invoice, API, and webhook control plane. In this pass, the docs and support surfaces were more revealing than any single marketing page.