DEV Community

AgentWallex
AgentWallex

Posted on

The Agent Payments Stack is Forming — Here's How to Read It

#ai #payments #webdev #crypto

This week, $50M+ poured into agent payment infrastructure. Five major announcements. Multiple Fortune headlines. AI agents paying for things is no longer speculative — it's a funded thesis.

But something more interesting is happening beneath the funding numbers: the stack is stratifying.

Not consolidating. Not converging on one winner-take-all protocol. Stratifying into distinct layers, each with different technical constraints, different go-to-market motion, different defensibility.

If you're building agent infrastructure or deciding where to build, here's how to read the layers.

Layer 1: Banking & Custody

Catena Labs — $30M Series A

Catena isn't building a wallet. They're filing for a national trust bank charter.

This is the custody layer. The place where fiat enters and exits. Where regulatory compliance happens. Where funds sit when agents aren't actively spending them.

Key signal: Circle co-founder Sean Neville is leading it. Circle built the stablecoin. Catena is building the bank that holds the stablecoin.

This layer requires billions in capital, years of regulatory work, and deep relationships with traditional finance. It's not a developer API play. It's infrastructure in the literal sense — pipes, vaults, insurance.

What this validates: Agents need on/off ramps. They need custody partners that can interface with traditional banking rails. Someone has to hold the money.

What this doesn't solve: Real-time payment authorization. Agents don't call a bank API every time they need to pay 0.002 USDC for an API call.

Layer 2: Infrastructure Distribution

Cloudflare — Programmable Wallets

Cloudflare isn't a payments company. They're a CDN. They distribute compute to the edge.

Now they're distributing wallets.

"Programmable wallets for the agentic Internet" means: wallet logic that lives close to where agents execute. Low-latency access. Global distribution. No single-region chokepoint.

This is the infrastructure layer. Not custody. Not authorization logic. Just: make wallet access fast and globally available.

Key insight: Cloudflare has 300+ data centers. If you're an agent running on Cloudflare Workers, your wallet logic can live in the same data center. Sub-10ms access.

What this validates: Latency matters. Agents operate in milliseconds, not seconds. Payment infrastructure has to match that speed.

What this doesn't solve: Who signs the transaction? Cloudflare distributes access, but the authorization logic — MPC key shards, policy checks, signature generation — still has to live somewhere.

Layer 3: Trust Frameworks

Visa + Mastercard + Ant International

The card networks are building "AI agent trust frameworks."

This isn't about transaction rails. It's about identity, verification, and dispute resolution.

When an agent pays a merchant, how does the merchant know the agent is legitimate? How do you handle chargebacks when there's no human cardholder? What does KYC mean when the "customer" is a piece of code?

This is the trust layer. Visa and Mastercard have 60+ years of experience adjudicating disputes, managing merchant risk, defining liability. They're applying that expertise to agents.

What this validates: Agent payments need trust infrastructure. Merchants won't accept agent money without verification. Regulators won't allow it without compliance hooks.

What this doesn't solve: Speed. Trust frameworks add latency. Verification checks, merchant lookups, fraud scoring — all of this happens in seconds, not milliseconds. Great for high-value B2B payments. Wrong for pay-per-API-call microtransactions.

Layer 4: Payment Routing

Sapiom — $15M Series A

Sapiom is building routing logic for agent payments.

The problem: an agent wants to pay for an API call. That API accepts USDC on Base, USDT on Solana, and PYUSD on Ethereum. Which token should the agent use? Which chain has the lowest fees right now? Where's liquidity deepest?

This is the routing layer. Token selection, chain selection, liquidity aggregation.

Think: 1inch, but for agent-to-agent payments. Optimizing for cost, not just swapping tokens.

What this validates: Multi-chain is real. Agents will need to pay across dozens of chains and tokens. Routing logic has to be abstracted away from the agent developer.

What this doesn't solve: The actual signing of the transaction. Routing picks the path. Something else has to execute it.

The Missing Layer: Gateway

Custody, distribution, trust, routing — all funded, all necessary.

But no one is owning the gateway layer.

The execution point where an agent:

  1. Authorizes a payment (policy check: is this allowed?)
  2. Signs the transaction (MPC: no exposed private keys)
  3. Settles on-chain (sub-150ms end-to-end)

This is the layer AgentWallex occupies.

Not custody (Catena). Not infrastructure distribution (Cloudflare). Not trust frameworks (Visa/MC). Not routing (Sapiom).

Gateway. The agent says "pay," and the transaction executes. Immediately.

Why the Gateway Layer Matters

Because speed is the constraint.

An agent booking a flight calls 47 APIs in 2.3 seconds. If each API call requires payment authorization, and each authorization takes 800ms (typical smart contract AA flow), the agent is now spending 37 seconds just waiting for payment confirmations.

That's not viable.

The gateway layer has to authorize in <150ms. That means:

  • MPC threshold signing (2-of-3 key shards, no blockchain lookups)
  • Policy engine that runs in-memory (no database queries mid-transaction)
  • Direct settlement to L2s (Base, Optimism, Arbitrum — not Ethereum mainnet)

No other layer optimizes for this. Custody optimizes for security. Distribution optimizes for availability. Trust optimizes for compliance. Routing optimizes for cost.

Gateway optimizes for execution speed.

How to Position in This Stack

If you're building agent infrastructure, here's the map:

  • Custody layer: Partner, don't build. Catena-style players will own this.
  • Distribution layer: Use Cloudflare or similar. Commodity over time.
  • Trust layer: Plug into Visa/MC frameworks when they're ready. Compliance is not a differentiator.
  • Routing layer: Integrate Sapiom or build light routing logic. Important but not core.
  • Gateway layer: This is where agent developers feel the pain. <150ms authorize or agents don't use you.

AgentWallex is the gateway. MPC wallets (via Paratro). Sub-150ms authorization. x402 native. Policy engine with no manual approvals.

We're not competing with Catena, Cloudflare, Visa, or Sapiom. We're the layer above custody, below routing, adjacent to trust.

The place where the agent actually pays.

3,600+ teams on the waitlist. Sandbox live at app.agentwallex.com.

The stack is forming. The gateway layer is open.

Follow & Try AgentWallex

Top comments (0)