Today's Internet Runs on Permissions.
The Next Internet Runs on Settlement.
Today, access is granted by accounts, API keys, and platforms.
As AI agents become economic actors, that model breaks.
The next internet will run on settlement — where payment is authorization, and action follows automatically.
Hypawave is built for that shift.
Payments Should Do More Than Move Money
Most systems stop at "payment sent."
But payment alone doesn't complete an exchange. Files are sent separately. Access is granted manually. Execution depends on trust.
That gap creates friction — for people and for machines.
Hypawave removes it.
Payment Is the Trigger
Hypawave links settlement and action into a single deterministic flow.
When a payment completes:
- •Funds arrive directly in the recipient's Bitcoin wallet
- •Settlement is instant and final
- •Files, links, or permissions unlock automatically
No coordination.
No screenshots.
No manual approval.
Payment becomes the execution gate.
Execution, Not Authorization
Most payment systems are built around authorization first — risk management, disputes, and reversals are handled after the fact. That model works for human commerce.
Hypawave is built differently. Payment is not a signal of intent — it is the trigger for action. Execution happens only after settlement is verified. This removes ambiguity and eliminates reversal logic entirely.
Other protocols focus on authorization, checkout, or wallet infrastructure — they serve different layers of the stack and can be complementary. Hypawave focuses on what happens after settlement, where value delivery must be automatic and deterministic.
Direct. Final. Non-Custodial.
Hypawave never touches your funds.
There are no chargebacks.
There are no reversals.
Money moves peer-to-peer.
Rules are enforced automatically.
More Than Payments
Hypawave is:
- •A settlement-gated execution system
- •An automatic fulfillment gate
- •Infrastructure for humans and AI agents
It is not a wallet.
It is not a traditional processor.
It is the missing layer between payment and action.
Built for the Internet Economy
The internet runs on instant exchange — code, content, data, access.
Legacy payment rails weren't designed for this.
Hypawave turns payment into a deterministic state change.
When paid, action happens.
That's it.
In the bigger picture, Hypawave makes value move. It turns settlement into motion — economic potential into real-world execution. No waiting, no approvals, no intermediaries.
Economic motion for the machine age.
Humans had banks. Machines need something different — a protocol where value flows as fast as data, and every payment is a trigger, not a transaction.
Protocol Overview
Every Hypawave payment runs through Hypawave Protocol — a settlement-gated execution protocol. Terms are locked at creation, payment is verified via cryptographic preimage proof, and execution fires deterministically. The entire flow is API-driven — no persistent connections required.
Lightning
The money moving — instant, peer-to-peer, final.
Hypawave Protocol
The authorization layer — terms integrity, preimage verification, and deterministic settlement-gated execution.
Step by Step
Creator makes a payment request
The creator calls the Agent API (SDK) or Offers API to create a payment request. Hypawave converts the price to Bitcoin (sats), locks the terms, and generates a unique session ID.
Payer fetches bolt11
The payer (agent or developer) calls the API to fetch the creator-issued Lightning bolt11. A terms_hash is returned — a SHA-256 snapshot of the locked terms — along with the bolt11 for payment.
Payer pays via Lightning
The payer's Lightning node pays the creator-issued bolt11. The money moves directly to the creator's wallet. Hypawave never holds or touches the funds. The payer's node returns the preimage instantly.
Settlement confirmed
The payer submits the preimage and terms_hash to the confirm endpoint. Hypawave verifies SHA256(preimage) == payment_hash, checks terms haven't changed, and marks the transaction paid. A service fee is recorded (see GET /api/public-settings for fee_percent).
Verification + receipt
Hypawave records settlement proof (payment hash + preimage) exactly once. Receipts are available via the API for both creator and payer. If an execution webhook is configured, the creator is notified immediately.
Access unlocks
Unlock is triggered unconditionally by settlement confirmation — it is never gated on fee payment or creator balance. Attached files, links, or permissions unlock automatically. Decryption keys are released exactly once. The exchange is complete.
Nobody has to trust anybody. Settlement proof is cryptographic. Execution follows deterministically. Hypawave verifies proofs and gates access — it never holds funds or decrypts content.
Two rails, never mixed: buyer → creator principal payments are direct-pay (Hypawave never touches them). Only fees and topups flow through Hypawave's managed-receive infrastructure.