Skip to content
Five ways to sell

Start with the way you sell.

Select the audience that matches your offer. Each path uses the same visible terms and direct settlement model.

Request access See current plans
Four offer formats connect to one hosted checkout Products, services, subscriptions, and paid APIs use one hosted checkout before settlement reaches the merchant wallet. Four offer formats Product Service Subscription Paid API Hosted checkout Visible terms Wallet Receives Four offer formats connect to one hosted checkout Products, services, subscriptions, and paid APIs use one hosted checkout before settlement reaches the merchant wallet. Four offer formats Product Service Subscription Paid API Hosted checkout Visible terms Wallet Receives
Four offer formats connect to one hosted checkout Products, services, subscriptions, and paid APIs use one hosted checkout before settlement reaches the merchant wallet.

Products, services, subscriptions, and paid APIs share one visible settlement route.

Creators

Sell one release without building a store.

Publish a product page for a download, course, or membership. The buyer sees the offer and wallet destination before authorization.

  • Use one shareable payment link.
  • State the price and delivery terms.
  • Release access after confirmed payment.
Digital product Hosted product page
Field notes bundlePDF and source files
24 USDC
The buyer reviews the file, price, network, and recipient before payment.

Consultants

Turn a clear work package into a payment page.

Define the service, price, and delivery terms. Share one checkout instead of sending an unstructured payment request.

  • Publish the work scope beside the price.
  • Give the buyer a clear receiving wallet.
  • Keep the payment record tied to the offer.
Service package Merchant-defined terms
ScopeArchitecture review
DeliveryWritten findings
The merchant remains responsible for the scope, support, refund terms, and delivery.

Software teams

Connect payment state to product access.

Use hosted checkout for a software plan or subscription. Keep the offer terms visible before the buyer authorizes payment.

  • Present the billing terms in checkout.
  • Use settlement state for access decisions.
  • Keep billing records in the merchant console.
Software plan Recurring terms
Team workspaceMonthly access
49 USDC
Recurring behavior depends on the configured plan and the selected live payment rail.

API builders

Return payment terms from the resource itself.

Protect an endpoint with an x402 challenge. A compatible client can authorize the terms and retry the request.

  • Keep API credentials on the server.
  • Return machine-readable payment terms.
  • Fulfil only after the required payment state.
Paid API request A protected route answers with payment terms; the client authorizes them and retries the request to receive the paid response. PAID REQUEST SEQUENCE GET 01 Protected route 402 02 Payment terms SIGN 03 Payment proof 200 04 Paid response The client reads the terms, authorizes payment, and retries the request. Paid API request A protected route answers with payment terms; the client authorizes them and retries the request to receive the paid response. PAID REQUEST SEQUENCE GET Protected route 01 402 Payment terms 02 SIGN Payment proof 03 200 Paid response 04 The client reads the terms, authorizes payment, and retries.
Paid API request A protected route answers with payment terms; the client authorizes them and retries the request to receive the paid response.

On-chain groups

Publish one clear route to a receiving wallet.

Offer member access or a published resource through a configured wallet. Keep the recipient and payment terms visible.

  • Use a verified receiving wallet.
  • Show the selected network before authorization.
  • Keep the offer record separate from fund custody.
Group access Visible receiving route
01Published offerTerms and access conditions remain visible.
02Verified walletThe payment surface names the receiving destination.
LinkSell records the offer and payment state without holding the group funds.

One settlement model

Different offers. The same visible money path.

Each surface presents merchant-defined terms. A compatible buyer authorizes payment, the selected facilitator and network settle, and LinkSell records the result.

One settlement model

Products, services, subscriptions, and paid routes use the same visible authorization and settlement boundary.

One settlement model Products, services, subscriptions, and paid routes use the same visible authorization and settlement boundary. MERCHANT OFFERS Product Service Subscription Paid API Hosted checkout Visible terms Merchant wallet Receives USDC One settlement model Products, services, subscriptions, and paid routes use the same visible authorization and settlement boundary. MERCHANT OFFERS Product Service Subscription Paid API Hosted checkout Visible terms Merchant wallet Receives USDC
One custody boundary. Each offer ends at the merchant wallet.
Availability, finality, wallet behavior, and possible external costs depend on the selected live network and facilitator.

Start getting paid

Start with a supported wallet.

Create your account, verify a receiving wallet, and configure a payment surface. Review the live networks, plan limits, and external costs before publishing.

Need help first? Contact [email protected].

Request access Read the docs