Payments

Required configuration#

The deployment must configure the Solana cluster, RPC endpoint, approved USDC mint, payment recipient and any program ID actually used by the payment adapter. No token mint, recipient or program address is invented in this build.

The default preview cluster is devnet. Devnet assets have no mainnet settlement meaning. Network settings must match the quote, wallet transaction and server verifier.

Wallet approval#

The wallet connection only shares the public address. A live payment requires a separate transaction approval showing the service quote, USDC amount, token mint, recipient and cluster.

The current build never creates a real transaction from the demo quote. Without a configured server payment adapter, the live action remains disabled.

Server payment verification#

Before submitting the provider job, the server must verify a successful finalized transaction on the configured cluster. Check its signature, authorized source owner, token-account mint and recipient, the mint's token program, and exact amount in raw token units. Reject transfers through an unexpected token program.

Correlate the verified transfer to the persisted, unexpired quote using the adapter's specified reference or instruction rules. A signature pasted into the browser or a client-supplied quote ID is not sufficient. The same payment cannot fund several jobs; quote, signature and job idempotency must be persisted on the server.

Payment proof#

A confirmed Solana transaction can be linked from a real payment record. Demo receipts have payment: null and no explorer link. A transaction alone does not prove the provider ran the intended computation.

There is no investment balance, deposit pool, rent credit, NAV or redemption operation in the buyer flow.