Direct receiver
Each verified site can report the wallet address or payment destination it uses for unlocks.
Payments
Wallet-native unlocks for creator-owned routes.
Nibgate helps creators price protected content while payments flow from the buyer to the receiver configured in the creator's own site package.
x402 and Arc testnet
Receipts can point to gateway-style x402 events or Arc testnet transaction links as the payment rail matures.
Metrics, not custody
The hub tracks unlocks, receipts, and revenue signals. It does not become the withdrawal layer.
How earnings work
Your package protects routes and receives payment on your own site. Nibgate records signed unlock events so the dashboard can show revenue, volume, and payment history.
Why this matters
Creators can operate multiple sites with different receivers while keeping analytics centralized under their Nibgate profile.