YOUR PAYMENTS. YOUR CONTROL.

Built around explicit control.

Direct payments, separated protection and a clear record of every step.

Payments go to your wallet

The payment page uses the receiving address configured by your organization. Clients pay directly to that address. PerpInvoice stores public wallet details, not merchant payment private keys. A separate venue account is used for protection.

Payment status is verified server-side

The backend checks the configured chain, exact asset, recipient, amount, transfer success and confirmations. A transaction hash, browser event or webhook is not enough to mark an invoice paid. Transfer identifiers are deduplicated and allocations are atomic.

Workspaces are isolated

Authenticated requests are scoped to organization membership and role. Live data is protected by database access policies. Public payment tokens expose a limited invoice view, and demo sessions are stored separately from live organizations.

Manual protection is an explicit action

Live execution requires dedicated configuration, a bound organization and venue account, restricted agent signing, and an explicit user request. Order intents are persisted before submission. Unknown outcomes require reconciliation rather than a second order. Closing uses reduce-only instructions to avoid creating a new long position.

Understand the risks

Perpetual futures introduce funding costs, liquidation risk, venue risk, smart-contract risk, execution risk, basis risk and liquidity risk. A short can lose money if the asset price rises. Client nonpayment or a partial payment can leave protection out of proportion to the remaining receivable.

Funding can change, liquidity can disappear, and infrastructure can fail. A coverage percentage describes the intended quantity hedge; it is not a guarantee. Margin and liquidation health must be monitored using actual venue data. Currency exposure can remain when the invoice and venue settle in different currencies.

Current validation

The application includes automated accounting, isolation, quote and execution-integrity tests. Simulation is suitable for exploring the workflow. Configuring an integration does not constitute an independent security audit or validation with real funds.