> For the complete documentation index, see [llms.txt](https://rwapact.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rwapact.gitbook.io/whitepaper/integrations-and-standards/eip-3009-and-x402.md). # EIP-3009 and x402 How EIP-3009 and x402 relate to payment authorization around the RWAPACT execution environment. ## EIP-3009 and x402 EIP-3009 and x402 are payment and authorization-related infrastructure referenced by the RWAPACT technology stack. They provide a conceptual basis for gasless payment authorization around autonomous execution. They are not Pact layers. RWAPACT's Pact consists of KRO, KSO, KPV, KGR, and KAR. ``` Agent -> Payment and authorization infrastructure -> RWAPACT risk decision -> Execution ``` ### Payment authorization and risk authorization Autonomous agents need mechanisms that can authorize or facilitate transactions without manual handling for every action. Payment authorization infrastructure addresses that surrounding execution need. Risk authorization answers a different question. RWAPACT decides whether the underlying RWA trade should execute after evaluating risk, Session, policy, and gas conditions. An Agent may be able to authorize a payment while the Pact still rejects the associated trade. For example, the Trade Intent can fail the KRO risk condition or KPV policy condition. Payment authorization does not bypass the Pact decision. ### Architectural position EIP-3009 and x402 can support payment authorization around the execution environment. They do not replace KRO's risk evaluation, KSO's Session validation, KPV's policy enforcement, KGR's gas decision, or KAR's Attestation record. RWAPACT does not require EIP-3009 or x402 for every transaction. The standards are external infrastructure references, while RWAPACT remains the decision layer between an Agent's Trade Intent and execution. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://rwapact.gitbook.io/whitepaper/integrations-and-standards/eip-3009-and-x402.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.