Integrate the whole payment lifecycle.
Start with hosted checkout, then add the API, signed events, embeds, or x402 protection your product actually needs.
Illustrative imagery; the person shown is not a LinkSell customer.
Request
Present stated payment terms
Response
Act on a verified outcome
Event lifecycle
Keep product state tied to payment state.
Treat each stage as a distinct operational boundary. Verification is not settlement, and fulfilment belongs after the confirmed money-movement outcome.
-
01
Created
Your application or a hosted LinkSell surface defines the payment terms.
-
02
Initiated
A buyer opens checkout or an agent receives a payment challenge.
-
03
Confirmed
The submitted authorization is verified before settlement completes.
-
04
Settled
Your system receives the settlement outcome and can fulfil the purchase.
HTTP-native payment
Request → 402 → settle.
A protected route returns payment requirements. A compatible client authorizes those terms, retries with proof, and receives the paid response after settlement.
A paid request
A compatible client receives stated payment requirements, authorizes them, and retries with proof.
Integration tasks
Add only the surfaces your product needs.
Start with one complete path, then add events, embeds, agent payments, or the published Laravel SDK when the job requires them.
Create checkout
Return a hosted payment URL
Create checkout terms from your server, then send the buyer to the URL returned by the API. Lists use a bounded data, count, and limit envelope.
REST API referenceConfirm settlement
Process signed state assertions
Verify the raw delivery body, accept active rotation signatures, deduplicate retries, and fulfil on the settled event.
Webhook guideAdd checkout
Progressively enhance an existing page
The small embed script opens a payment-link checkout and falls back to full-page navigation when a popup is unavailable.
Embed guideProtect an API
Challenge compatible agents over HTTP
A protected route returns x402 terms. The client signs a single-use authorization, retries, and receives the upstream response after settlement.
Agent-payment recipeUnderstand the protocol
Separate orchestration from the money path
LinkSell presents terms and records outcomes while compatible settlement moves USDC from the paying wallet to the configured merchant wallet.
What is x402?Evidence first
The page still works before JavaScript.
REST, webhook, embed, and agent-payment doorways are server rendered. The optional integration examples enhance this path only when published and enabled.
Open the REST reference →- Keep API credentials on the server.Browser widgets use purpose-built, limited surfaces.
- Verify webhook signatures against the raw body.Handle retry and rotation candidates before processing.
- Fulfil on settlement, not verification.Treat events as state assertions because delivery order is not guaranteed.
Documentation
Open the reference for the job.
Move from protocol concepts to the exact API, event, embed, agent-payment, or published SDK surface you need.
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].