Tasmanian Cloud documentation
x402 payment admission
Machine-facing payment proof for enabled API operations
Tasmanian Cloud supports x402 for enabled machine-facing operations. A caller can present a payment proof as part of the request path, and the service can verify the proof before admitting the requested resource or operation.
What x402 does
x402 provides a payment-admission path for machine clients. The proof is checked against the requested resource, payee, amount, network, and replay rules before a settlement is recorded.
It does not replace identity, tenant authorisation, request limits, or normal API credentials. Payment answers whether the payment condition was satisfied. Authorisation answers whether the caller may use the resource.
Why it matters
This supports services that consume infrastructure or API capacity without a human checkout step. A machine can request a paid operation, receive the payment challenge, and retry with proof when the operation is enabled for that rail.
Accounting boundary
x402 settlements use the same ledger boundary as other payment sources. A settlement reference is idempotent. A replay, resource mismatch, wrong payee, or invalid amount must be rejected rather than credited twice.
Availability and supported assets depend on the operation. Contact the team before treating x402 as a general billing replacement.