Developer Office Hours #58 - x402 on Cardano

Developers Misc Dev Talk
1

dev
dev1200×630 101 KB

:rocket: x402 on Cardano

Join Fabian Bormann, Head of Ecosystem Engineering at the Cardano Foundation, for an open session explaining version 2 of the x402 standard, including progress toward integration with Cardano.

This interactive session will include an overview of the Cardano x402 specification document and its current status, followed by an open discussion with the community to answer questions and gather feedback from the ecosystem.

:date: Friday, 24 April

:eight_o_clock: 08:00 – 09:00 UTC

Stay updated with our events!

You can subscribe directly to the calendar here: AddEvent

Join the discussion below! We’ll update this thread with the recording link as soon as it’s live.

2 Likes
2

Summary: x402 on Cardano: Version 2 Standard & Integration

In this edition of the Developers Office Hour, host Darlisa Consoni from the Cardano Foundation speaks with Fabian Bormann, Head of Ecosystem Engineering, about the integration of the x402 standard on Cardano. They are also joined by Aggelos, a core engineer from Indigo, to discuss technical specifications and recent progress.

What is the x402 Standard?
The x402 standard is an extension of the existing HTTP 402 “Payment Required” status code. It allows web servers to restrict access to an endpoint (such as a weather API or a game download) until a specific cryptocurrency payment is made. Originally started by Coinbase, the standard has now been moved under the umbrella of the Linux Foundation (x402 Foundation) to become an open, cross-ecosystem standard.

The Cardano Workflow
The implementation of x402 on Cardano is distinct from EVM chains. On Ethereum, a server or smart contract typically requires an allowance to pull USDC from a user’s wallet. On Cardano, the process is safer and natively user-controlled: the client builds and signs the transaction upfront based on the server’s requirements, and the server (or a facilitator) simply submits it to the network. The server cannot alter the transaction or change the destination address.

Facilitators and Extensions
Web2 companies usually do not want to manage blockchain node infrastructure or handle transaction settlements themselves. Therefore, the standard includes optional “facilitators” that handle the submission and verify if the transaction is included in the mempool or fully settled.
Furthermore, the standard utilizes “extensions” to keep the core specification clean. For example, Mazumi—a popular protocol for agent-to-agent (agentic) payments on Cardano—was proposed by Aggelos as an extension. This prevents the core schema from turning into a bloated vendor registry while still fully supporting crucial ecosystem applications.

The Microtransaction Challenge
A major discussion point was the cost of microtransactions. While chains like Base or Solana have fees low enough to charge tiny amounts for single API calls, Cardano’s base layer fees are currently too high for efficient fractional payments. To solve this, developers are looking toward Layer 2 scaling solutions like Hydra or “Conduit” (the version 2 evolution of Cardano Lightning) to process high-volume, low-cost API payments.

Next Steps
The official Cardano schema pull request has been successfully merged into the main development branch of the standard. The ecosystem engineering team can now begin implementing the standard into official software packages for Java, Python, Go, and TypeScript. Developers wishing to join the discussion can participate via the Cardano Foundation Engineering Discord server or directly on GitHub.

Top Five Q&A (FAQ) about the x402 Standard on Cardano

Question 1: What is the x402 standard, and what does it enable?
Answer: x402 is an extension of the traditional HTTP 402 “Payment Required” protocol. It enables servers and APIs to automatically request cryptocurrency payments before granting access to digital resources, abstracting the complex payment logic away into simple code annotations.

Question 2: How does the x402 payment flow on Cardano differ from Ethereum?
Answer: On Ethereum, users often have to grant allowances, letting a smart contract or server pull funds from their wallet. On Cardano, the user remains in complete control: the client securely builds and signs the transaction, and the server is only responsible for submitting it, without any ability to alter the funds or destination address.

Question 3: What is the role of a “facilitator” in this setup?
Answer: A facilitator is an optional third-party service that handles the actual submission of the transaction to the blockchain and verifies its settlement. This is crucial for mass adoption, as traditional web companies (like Steam) do not want to build or manage their own blockchain nodes just to process API payments.

Question 4: Why is the Mazumi protocol integrated as an “extension” rather than being part of the core standard?
Answer: Mazumi is a popular application for agentic (AI-to-AI) payments on Cardano. However, keeping it as an extension ensures that the core x402 schema remains neutral and lightweight, rather than turning into a registry for every single vendor or protocol that emerges in the future.

Question 5: How will Cardano handle the network fees for very small API payments?
Answer: Because Cardano’s base layer transaction fees are higher than those of some competing chains, micro-payments for individual API calls are currently inefficient on the mainnet. The community plans to bridge this gap using Layer 2 solutions such as Hydra and Conduit (the second iteration of Cardano Lightning) to facilitate fast, cheap off-chain settlements.

1 Like