Speed primary sources — 2026-05-02

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is Speed’s own product pages plus its public API reference.
• The materials consistently make Speed look broader than a simple merchant checkout processor.

Primary-source snapshots

1) Main site overview

• URL: https://www.tryspeed.com/
• Key excerpt:
  • The homepage describes Speed as a unified platform to accept, send, and settle crypto.
  • It groups payments, payouts, onramp/offramp, and platform connectivity under one rail.
  • It also says the company runs its own core ledger and settlement rails with no middleware.

2) Payments product page

• URL: https://www.tryspeed.com/payments
• Key excerpt:
  • The payments page says businesses can accept Bitcoin, USDT, and USDC using payment links, APIs, static QR codes, hosted payment pages, and ecommerce plugins.
  • It repeatedly positions the system as developer-friendly, globally usable, and built for instant confirmation.
  • This is strong evidence that Speed is packaging several merchant payment surfaces, not just one hosted checkout flow.

3) Payouts product page

• URL: https://www.tryspeed.com/payouts
• Key excerpt:
  • Speed says businesses can automate bulk payouts, send manual instant payouts, and schedule recurring or future-dated payouts.
  • The page explicitly ties these capabilities to Bitcoin and stablecoins over Lightning and onchain networks.
  • That makes the product look like a programmable disbursement rail in addition to a checkout tool.

4) Connect / PSP platform page

• URL: https://www.tryspeed.com/connect
• Key excerpt:
  • Speed Connect describes whitelabel API-based integration, global payments and payouts, reporting, custom markups, automated commission splits, and payout splits.
  • The page also frames the product for fintechs and PSPs rather than only direct merchants.
  • This is one of the clearest signs that Speed should be cataloged as platform infrastructure.

5) API introduction

• URL: https://apidocs.tryspeed.com/reference/introduction
• Key excerpt:
  • The API intro says Speed is a bitcoin and stablecoin payment platform organized around a REST API.
  • It names checkout links, payment links, and checkout sessions as core resources.
  • It also highlights separate test and live modes for integration work.

6) API keys

• URL: https://apidocs.tryspeed.com/reference/keys
• Key excerpt:
  • The keys docs describe publishable, secret, and restricted API keys in both test and live environments.
  • Secret keys can create checkout links, checkout sessions, payments, and check account balances, while restricted keys can be scoped resource-by-resource for microservices.
  • That level of credential design is typical of a full integration platform, not a lightweight widget.

7) Webhooks and events

• URL: https://apidocs.tryspeed.com/reference/webhooks-and-events
• Key excerpt:
  • Speed says it pushes structured event objects to registered HTTPS endpoints whenever events happen in the system.
  • The docs explain webhook registration, enabled events, event objects, and 30-day event retention in the web app.
  • This reinforces that the system is meant to sit inside operational payment workflows.

8) Speed.js

• URL: https://apidocs.tryspeed.com/reference/speedjs
• Key excerpt:
  • Speed.js is described as the browser-side JavaScript library for accepting payments with checkout-session flows using only a few lines of code.
  • The docs emphasize client-side integration for web or mobile experiences.
  • This adds an app-embedded checkout surface on top of the broader REST API.

9) Payment address object

• URL: https://apidocs.tryspeed.com/reference/payment-address-object
• Key excerpt:
  • The payment-address docs describe LNURL-backed payment addresses with unique usernames, custom domains, and default Speed domains.
  • The same page says platform accounts can create payment addresses in connected accounts.
  • That feature makes Speed look more like a routed payments layer for platforms than a simple merchant wallet.

Working conclusion

Speed is best cataloged as a bitcoin-and-stablecoin payments control plane with checkout, payout, connected-platform, and developer-operations layers in one stack. The decisive evidence in this pass was the combination of multi-surface acceptance, bulk and scheduled payouts, PSP/fintech platform tooling, resource-scoped keys, webhook/event infrastructure, browser-side checkout, and LNURL-style payment-address primitives for connected accounts.