Stealth-address Bitcoin payments

Crypto Payments That Leave No Trail Behind Them.

Stealth Pay generates a fresh on-chain address for every inbound payment. Senders send. Receivers control. Observers see nothing.

No address reuse — ever
Non-custodial by default
Enterprise custody rails
Live payment surface
Privacy orchestration
Scanner active
Derived payment routeECDH key agreement
Receiver stealth address
A + B public keys
Published once
ephemeral derivation
One-time address
P = H(r·A)·G + B
Unique per tx
Detection latency
30s

Near real-time scan cadence across all monitored outputs.

Privacy guarantee
1 → 1

One transaction. One address. Zero reuse.

1 tx
One address per payment
30s
Scan-to-detect latency
0
Shared address reuse events
100%
Non-custodial receiver control
What powers it

Cryptographic privacy with a product experience that doesn't feel like a research paper.

Zero address reuse

Every payment resolves to a unique on-chain destination. Observers see nothing linkable — ever.

Institutional infrastructure

Wallet execution runs on enterprise-grade custody rails, so the privacy layer never compromises security.

Private inbound detection

Receivers scan for incoming funds using isolated view keys — no exposure of spend authority required.

Always-on scanning

Continuous transaction monitoring detects ownership in near real-time, without revealing receiver identity.

ECDH privacy layer

Cryptographic key derivation severs the link between sender and receiver at the protocol level.

Built to ship fast

Clean typed APIs, enforced auth boundaries, and composable services let your team move without friction.

How it works

Simple for senders. Private for receivers. Invisible to everyone else.

01

Publish a stealth address

The receiver shares a reusable public key pair — view and spend — without ever reusing a static Bitcoin address.

02

Sender derives a one-time output

An ephemeral key is generated per payment. A unique on-chain destination is computed — invisible to outside observers.

03

Scanner detects, receiver controls

The scanner inspects outputs with the view key only. The receiver retains exclusive spend authority.

Architecture rationale

Privacy lives above the wallet layer — not inside it.

Stealth Pay doesn't replace your wallet stack. It wraps around it — adding cryptographic unlinkability as a clean protocol layer while keeping custody, key management, and execution exactly where they belong.

Read the architecture doc
System properties
Address sharing model
View + spend key pair
Auth boundary
Session-backed, isolated
Custody layer
Enterprise rails
Detection method
Ephemeral metadata scan
Receiver control
Non-custodial spend keys
Get started today

Your users deserve privacy.
Now you can give it to them.

Start with the free tier. No payment required. Upgrade when you're ready to go to production.

Pricing

Product tiers designed for stealth-payment teams at every stage.

Starter

$0

For demos and pilots

  • Stealth address generation
  • Scanner events
  • Single workspace

Scale

Popular
$99

Per month · team tier

  • Policy controls
  • Priority scanner queue
  • Ops observability

Enterprise

Custom

Security + compliance teams

  • Dedicated infra
  • Security onboarding
  • SLA-backed support

Quick compare

See what changes as your privacy operations scale.

Capability
Starter
Scale
Enterprise
Stealth Addressing
Core
Advanced
Advanced
Scanner Throughput
Standard
Priority
Dedicated
Policy Layer
Basic
Extended
Custom
Support
Community
Priority
Dedicated
Platform matrix

From cryptography to product clarity.

Distinct layers make the system easier to trust, explain, and ship.

1
Stealth layer

One-time derived outputs per payment with deterministic receiver recovery.

2
Execution rails

Wallet orchestration remains on proven institutional infrastructure.

3
Detection loop

View-key scanning keeps spend authority isolated from monitoring.

Use-case catalog

Treasury settlement

Protect high-value inflows from static receive-address correlation.

Partner payouts

Deliver merchant payouts while keeping payment graph exposure lower.

Global collections

Accept BTC globally with cleaner metadata boundaries.

Signal panel

Launch-ready UI
Minimal friction onboarding
Composable services
Fast engineering iteration
Operational signal
Readable state and flow
Scanner and dashboard remain operation-ready by default.
Testimonials

Teams trust the product because the experience feels as rigorous as the protocol.

Stealth addressing gave us real privacy differentiation without replacing wallet operations.

Head of Payments · Fintech Team

The scanner-first architecture made detection understandable for both ops and product.

Engineering Manager · Treasury Ops

Design quality made the protocol story immediately credible in stakeholder demos.

Product Lead · Crypto Infra

Blog

Insights for teams building private payment products.

Architecture

Stealth addressing as product UX, not just cryptography

6 min read

Read article
Engineering

Scanner-first operating model for inbound payment intelligence

8 min read

Read article
Product

How to position privacy features for enterprise trust decisions

5 min read

Read article
FAQ

Answers for product, engineering, and security teams.

Need deeper review?

Architecture walkthrough with your team.

We can walk through stealth derivation, scanner flows, and production rollout sequence.

Book a review