Overview

Naven Payment Intents let a product accept x402 payments without maintaining its own facilitator integration, receiver registry, or settlement database. Naven creates the payment requirement, verifies and settles it, and stores the authoritative result. Your application remains responsible for fulfilling the order after it confirms settlement.

Resource model

Naven user (implicit default workspace)
└── Project
    ├── Project API Keys
    ├── Wallets
    └── Merchants
        └── Payment Intents

• A Project represents one application or environment.
• A Project API Key is a server-only credential for that Project.
• A Merchant is an isolated payment receiver with one payTo address.
• A Payment Intent is one immutable payment obligation for one Merchant.

A Project may contain multiple Merchants. Use separate Merchants when payment receivers, products, environments, or revenue streams need separate payTo addresses.

Responsibility boundary

Naven owns:

• payTo, network, asset, facilitator, and token configuration.
• Exact x402 payment requirements.
• Verification and settlement.
• Intent state and transaction-hash deduplication.
• An immutable payment configuration snapshot.

Your application owns:

• Customer and order identity.
• Checkout UI and wallet connection.
• Credits, provisioning, or order fulfillment.
• Idempotently applying the result after querying Naven.

Authentication boundary

Never expose a Project API key to browser code. The browser only needs the public paymentUrl returned by your backend.

API documentation

The interactive OpenAPI explorer is available at api.naven.network/docs/ui. The raw OpenAPI document is available at api.naven.network/docs.