Speed

  • Name: Speed
  • URL: https://www.tryspeed.com/
  • Category: bitcoin-and-stablecoin payments control plane / Lightning and onchain checkout infrastructure / PSP-connectivity and global payout platform
  • Tags: bitcoin-ecosystem
  • Summary: Speed is hosted checkout-and-payout middleware with some connected-account routing on top. The useful part is one operator surface for payment links, payouts, API keys, and settlement defaults. Still packaging, not a rail.
  • What it does:
    • Lets businesses accept BTC, USDT, and USDC through payment links, hosted pages, QR flows, APIs, and ecommerce plugins
    • Supports Lightning and onchain payment methods plus browser-side checkout through Speed.js
    • Provides global payout tooling for bulk, manual, and scheduled disbursements in Bitcoin and stablecoins
    • Offers a Connect-style platform layer for PSPs and fintechs with whitelabel API integrations, compliance onboarding, reporting, commission splits, and platform monetization features
    • Exposes payment-address objects with custom domains and connected-account support so platforms can route receiving flows into linked accounts
    • Gives developers test/live environments, secret/publishable/restricted keys, webhook endpoints, and event objects for integration and automation
  • Key claims:
    • The main site says Speed is a unified platform to accept, send, and settle crypto, bundling payments, payouts, onramp/offramp, and platform connectivity under one rail rather than presenting only a checkout widget
    • The payments page says merchants can accept Bitcoin, USDT, and USDC through payment links, APIs, QR codes, hosted pages, and plugins, while the platform also claims mobile optimization and instant confirmation across payment surfaces
    • The payouts page says businesses can automate bulk payouts, use manual instant payouts, and schedule recurring or future-dated payouts, with Lightning Network transfers positioned as a faster and lower-fee alternative to traditional payout rails
    • The Connect page says platform operators can use whitelabel API integration, instant compliance checks, reporting, custom markups, automated commission splits, and payout splits, which is strong evidence that Speed is selling reusable infrastructure for other payment businesses
    • The API introduction says the platform is organized around a REST API, supports checkout links, payment links, and checkout sessions, and provides test and live modes for integration work
    • The API keys documentation says Speed offers publishable, secret, and restricted API keys across test and live environments, with resource-scoped permissions for microservices and server-side secret-key access for sensitive operations
    • The webhooks and events docs say Speed pushes structured event objects to registered HTTPS endpoints and retains event data in the web app for 30 days, reinforcing that the product is meant for operational integration rather than one-off payment links
    • The payment-address docs say platforms can create LNURL-backed payment addresses with custom domains and even create payment addresses inside connected accounts, which makes the system look like a routed receiving layer for broader payment operations
    • The Speed.js docs position the browser-side library as a lightweight way to embed checkout-session payment flows in web or mobile apps with only a few lines of code
    • The marketing pages repeatedly say Speed runs its own core ledger and settlement rails with “no middleware,” which is a notable first-party claim about infrastructure depth
  • Whitepaper: No canonical standalone Speed whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official product pages plus the public API reference covering authentication, webhooks, Speed.js, and payment-address objects; see ../whitepapers/speed-primary-sources-2026-05-02.md.
  • Sources:

Internal linkages

  • Best upward reads: btcpay-server for merchant-stack control and bridge-xyz for broader hosted stablecoin payment operations.

Control surface

  • Power sits in hosted checkout defaults, payout routing, connected-account policy, API-key scopes, webhook/event handling, settlement settings, and which currencies and counterparties Speed is willing to intermediate.

  • The pitch is breadth in one dashboard. The underlying work is ordinary processor orchestration, not a new payment rail.

  • Last reviewed: 2026-06-04 UTC