Is d402 overengineered AI payment middleware?

d402 claims to make AI-agent actions, API calls, and general internet payments programmable. Instead of a simple transfer, it adds persistent payment state, retries, recovery, refunds, disputes, reusable access, and one-time fulfillment across multiple servers. Why would anyone use that instead of building a payment database and plugging into the webhooks that already exist? The project stupidly assumes future payments will need to recover from failed requests, dispute bad results, reuse payments, and survive duplicate or interrupted delivery. Looks an over-engineered blockchain replacement for a database, a queue, and some webhook handlers. Demo: d402.rakelabs.workers.dev