Payment streaming is a mechanic where an active per-second transfer runs between two addresses. On Whop that transfer is denominated in USDT, the stream starts the moment consumption starts, and it stops the moment consumption stops. There is no billing cycle to align to and no cancellation flow to navigate; the live state of the stream is the live state of the relationship.
Every ongoing relationship on Whop that is actively consumed has a payment stream. A follower copying a signal caller pays per second. A Terminal subscriber watching a live feed pays per second. A reader scrolling continuously through a Feed article pays per second. A vault contributor receives pro-rata distributions from vault profits in real time.
This isn't a subscription with a shorter billing cycle. It's a structurally different primitive. Traditional subscriptions treat the payment as a commitment to a future relationship. Streaming payments treat the payment as the relationship itself, active stream means the relationship exists, no stream means it doesn't.
Why Per-Second Is the Right Primitive
Traditional subscription models misalign incentives in three ways:
- ›A monthly subscription charges the buyer whether or not they use the product.
- ›The seller is incentivized to lock in the subscription, not to deliver continuous value.
- ›Cancellation is friction. The buyer has to actively take an action to stop paying, and the longer they forget, the more the seller earns.
Per-second streaming inverts all three:
- ›The buyer pays only while actively using the product.
- ›Stop following → payment stops immediately. No cancellation flow. No billing cycle to wait out.
- ›The seller is incentivized to deliver value every second. The moment value stops, payment stops.
An active stream to max.whop means you're currently copying max.whop. No stream means you're not. No subscription management, no cancellation flows, no billing cycles. The system state is the payment state.
Why It's Only Viable Now
Streaming payments at per-second resolution require three things that weren't simultaneously available on any chain before Aptos hit its 2026 performance thresholds, with more improvements coming throughout the year (Archon, Zaptos, Shardines):
- 02Settlement fees small enough that a 1¢/second rate isn't eaten by gas (Aptos gas averages ~$0.0005/tx).
- 04Finality fast enough that "stop" means stop within a block (sub-second).
- 06Throughput high enough to support millions of concurrent streams without degrading (Zaptos + Shardines, 1M TPS headroom).
On other competing payments chains such as Plasma and Tempo, these types of payments are not possible, the complex logic drives gas fees up and the network treats high-frequency low-value transfers as spam, congesting the chain. Only possible on Aptos.
Streaming Across Every Product
Terminal Streams
Per-second payments to data providers, Shelby CDN operators, news sources, signal callers whose feed is included in a Terminal dashboard. A subscriber with three streams active pays three separate providers simultaneously. Remove a stream, that payment stops. Breaking-event urgency pricing is set by the stream owner.
Trading Vault Distributions
Trading vaults are the one place in the trading stack where payment streaming actually fits. A vault takes deposits from contributors, runs a strategy against them, and the realized PnL streams back out to contributors pro-rata by stake. Holding the vault stake keeps the distribution stream live; withdrawing the stake ends it. Contributors don't have to claim, rebalance, or trigger distributions manually, the stream settles continuously from realized PnL as it hits the vault's ledger. Copy trading, indicator subscriptions, and direct trade execution settle per event rather than per second, so they don't belong here.
Providing Passive Liquidity
Any yield product on Whop, lending markets, LP positions, staked stablecoin pools, structured yield vaults, auto-accrues interest as a continuous per-block stream to the depositor. A user deposits once and the yield compounds in real time rather than waiting on a weekly or monthly distribution cycle. There's no claim transaction to remember and no manual reinvestment step to capture compounding, which gives retail depositors the same always-on reinvestment that sophisticated LPs run with custom scripts today. The compounding rate is higher for the same underlying APY because no value sits idle between distributions.
Summary
| Product | Who pays | Who earns | Rate |
|---|---|---|---|
| Terminal Streams | Terminal subscribers | Data provider | Tiered, urgency-priced during breaking events |
| Trading Vault Distributions | Nobody (profits distributed) | Vault contributors (pro-rata) | Proportional to stake |
| Providing Passive Liquidity | Nobody (yield accrues) | Depositor / LP | Per block, proportional to deposit |
Private Streaming (Optional)
By default a stream is a public USDT or APT transfer. When the use case calls for it, the same stream primitive can run over a privacy layer.
- ›Confidential Assets (AIP-143) keeps the amount flowing through the stream private while the sender and recipient stay public. A vault where the distribution rate per contributor shouldn't be public, or a creator paying out to a team without exposing comp ratios, are natural fits.
- ›Invisible Assets (UTT) hides the full payment graph. A stream for adult-content, gambling, or any category where the existence of the relationship is itself sensitive can run as UTT notes refreshed on a schedule rather than a continuous CA stream.
These are opt-in overlays on the streaming mechanic, not prerequisites for it.
Related: Consumption-Based Pricing covers the buyer-side thesis in full, including the streaming-vs-consumption framing. Onchain Subscriptions covers the creator-focused recurring pattern for audiences that prefer predictable monthly billing. Privacy Zones covers Confidential Assets and UTT when a stream needs to be private.