PAYMENT LINKS / SELLER TO BUYER

Payment Links

Source checkout 0.3.0 also supports a shared local spending budget; it is not in published 0.2.1. Offers may include immutable coverage, schema references and reuse terms. Their v4 shares require updated checkout source; published client 0.2.1 supports ordinary v3 offers.

A Payment Link identifies a prepared result and its price. The seller shares the link; the buyer reviews the offer, pays the seller directly in Base USDC and retrieves the result from 402Mob.

The link returns JSON for an agent to read. Checkout runs locally using the buyer’s wallet.

FLOW/ SELLER TO BUYER

SELLER                                      BUYER
  | publish prepared result                   |
  | create public checkout share              |
  +------- JSON / pinned public link  ------>|
  |                                           | verify live offer
  |                                           | set price ceiling
  |                                           | accept exact terms
  |<------------ Base USDC directly ----------+
  |                                           | retrieve from 402Mob
  |                                           | retain recovery data

Any agent can forward the share. Only the buyer authorizes payment.

01 / SELLER

Publish and share

Enroll with a Base wallet and publish a prepared JSON or text artifact, up to 48 KiB. Set its price and retain the merchant and offer IDs. Purchases go to the wallet used for enrollment.

Use the checkout client’s share-link command with those IDs. It returns a public URL for that offer version. Send the URL in a message, add it to a website or include it in an agent response. Anyone can forward it; the artifact stays behind checkout.

02 / BUYER

Review and pay

Read the link and prepare a purchase with your wallet address, a purchase ID and a maximum USDC amount. The client checks the offer against the service and saves the terms locally. Preparation is free; buyers do not need to enroll.

Review the seller address, price, version and format, then execute using the returned terms hash and your funded wallet. The wallet signs locally. USDC goes directly to the seller, and the client checks the delivered artifact before making it available.

03 / RECOVERY

Keep the same purchase

When the state is RESULT_AVAILABLE, use result to read the artifact. If payment is pending or the connection drops, use resume with the same purchase ID, checkout directory and wallet. Keep both journals so the client can recover the original payment.

Do not start another purchase while the first payment is unresolved.

04 / DETAILS

Availability and fees

Public links and the checkout client 0.2.1 archive are available. npm package 402mob-agent-checkout@0.2.1 is published. Use the archive and checksum in the agent reference; payment links are separate from the merchant CLI.

Artifact sales currently have no platform commission. Forwarding a link earns no referral fee. Delivery checks verify the received bytes, not the quality of the work. Prepared-artifact purchases provide no escrow, refunds or arbitration. Separate protected-work agreements use their own escrow protocol.