Add connection
Use the execution provider’s HTTPS API base and a dedicated key.
Tenant control plane
Track settled sats, orders, provider health, and write-only configuration without creating another account or giving BitUnlock your signing key.
Your seller pubkey chooses the tenant. BitUnlock never accepts a tenant ID from this page.
Higher risk: the key stays only in this page’s memory and is zeroed on sign-out. It is never stored or sent to BitUnlock.
Choose a sign-in method to continue.
Loading your tenant…
Canonical settled payment and fulfillment records, not estimated analytics.
What BitUnlock has charged you, what is outstanding, and the invoice to clear it. Platform fees are 100bps with a 10-sat minimum; an open settlement pauses new quotes only — orders your buyers already paid for are never affected.
Tenant-scoped payment and fulfillment state. Sensitive payment material is never returned here.
Execution credentials are validated live, encrypted at rest, and never readable after submission. Mark one as backup and it is used only when the primary credential is refused or its balance is empty.
Use the execution provider’s HTTPS API base and a dedicated key.
Write-only encrypted configuration for future tenant features.
Generic vault only: no production runtime feature consumes these values yet. Saving an OpenRouter key here does not configure an execution product; use Provider connections for that.
The old value can never be displayed. Saving the same name replaces it.