x402 FAQ

What makes x402 different from a normal payment gateway?

x402 uses HTTP 402 Payment Required as part of the product flow, so payment requirements and protected delivery are described in the same protocol interaction.

What makes x402 different from a simple wallet transfer?

A simple transfer only moves value. x402 adds delivery semantics, payment state, and settlement verification so an app or API can decide when to unlock the protected response.

Is HTTP 402 an error?

No. For order creation, HTTP 402 is the expected success path because the backend is returning payment requirements rather than the final protected content.

Which mode should I choose first?

Start with DIRECT unless you already know you need callback-enabled or delegated settlement behavior.

When should I use DELEGATE?

Use DELEGATE when payment must trigger on-chain logic or when the settlement flow requires delegated infrastructure rather than a simple direct payment path.

How does x402 relate to agents?

x402 is a natural fit for agents because it gives them a machine-readable way to charge for API calls, workflow execution, or premium endpoints.

How does x402 relate to ERC-8004?

ERC-8004 is a trust and discovery layer. x402 is a payment and monetization layer. They complement each other rather than replacing one another.

Does x402 replace Bitcoin-backed settlement?

No. x402 is the payment rail. GOAT Network still provides the settlement foundation beneath it.

What should I persist for audits?

Keep order identifiers, settlement proofs, and any internal delivery records required by your product or compliance model.

Where should I start if I am using AgentKit?

Start with AgentKit x402 Payments, then come back to the protocol pages if you need lower-level merchant or API detail.