Nexus and UCP: Complementary Layers for Agentic Commerce
Published: 2026-03 | Based on public documentation, Google Developer Blog, and Nexus RFCs
Overview
Google's Universal Commerce Protocol (UCP) and Nexus are not competing standards — they operate at different layers of the agentic commerce stack. UCP defines how agents talk to merchants (discovery, checkout, fulfillment). Nexus defines how payments settle (escrow, release, dispute). Together they form a complete pipeline from product discovery to settlement assurance.
Nexus is compatible with UCP and encourages User Agents and Merchant Agents to adopt UCP as their commerce communication protocol.
At a Glance
| Dimension | UCP | Nexus |
|---|---|---|
| Originator | Google + 20 retail partners (2026) | Nexus Team |
| Layer | Commerce protocol (discovery → checkout) | Settlement protocol (escrow → release) |
| Scope | Product search, cart, checkout, fulfillment | Payment locking, release, dispute, refund |
| Transport | REST API, A2A, MCP | MCP, REST API, HTTP 402 |
| Payment Model | Payment handlers (tokenized, delegated) | On-chain escrow (EIP-3009 + escrow contract) |
| Merchant Integration | /.well-known/ucp manifest | skill.md + MCP tools |
| Privacy | Tokenized credentials | Confidential Token (ZK proofs) |
| Open Source | Yes | Yes |
How They Fit Together
┌─────────────────────────────────────────────────────────┐
│ User Agent (Gemini, Claude, custom) │
│ │
│ 1. Discover merchant via UCP /.well-known/ucp │
│ 2. Browse products, build cart (UCP Checkout) │
│ 3. Select payment handler → Nexus │
│ │
├─────────────────────────────────────────────────────────┤
│ UCP Commerce Layer │
│ • Product discovery, cart, discount, fulfillment │
│ • Standardized JSON schemas & capability manifests │
│ • Transport: REST / A2A / MCP │
├─────────────────────────────────────────────────────────┤
│ Nexus Settlement Layer │
│ • Quote → Orchestrate → Sign → Escrow Lock │
│ • 13-state payment machine │
│ • Auto-refund on timeout, on-chain arbitration │
│ • Confidential Token for enterprise privacy │
└─────────────────────────────────────────────────────────┘UCP gets the Agent to the checkout button. Nexus handles everything after the Agent clicks it.
Why UCP Needs a Settlement Layer
UCP deliberately decouples payment instruments from payment handlers. This is by design — UCP is commerce-first, not payment-first. The protocol defines how to create checkout sessions, apply discounts, and manage fulfillment, but delegates actual fund movement to pluggable "payment handlers."
This creates a natural integration point for Nexus:
| UCP Concept | Nexus Role |
|---|---|
| Payment Handler | Nexus registers as a UCP payment handler |
| Tokenized consent | Maps to EIP-712 group signature (cryptographic proof of user consent) |
| Checkout session | Triggers Nexus quote + orchestration flow |
| Fulfillment status | Drives escrow release (merchant confirms → funds unlock) |
| Post-purchase | Dispute window, auto-refund, arbitration |
UCP provides the commerce semantics. Nexus provides the settlement guarantees that UCP intentionally leaves open.
What Nexus Adds to UCP Merchants
1. Escrow-Based Buyer Protection
UCP relies on payment handlers for buyer safety. Nexus's escrow model ensures funds are locked before service delivery and released only after merchant fulfillment — with automatic timeout refunds as a backstop.
2. On-chain Dispute Resolution
When something goes wrong, UCP defers to the payment handler's dispute process. Nexus provides deterministic, transparent dispute resolution:
- 72-hour dispute window after escrow
- Optional third-party arbitrator for split resolutions
- Auto-refund after arbitration timeout (no human intervention needed)
3. Privacy for Enterprise Commerce
UCP uses tokenization for credential privacy. Nexus goes further with PlatON's Confidential Token — encrypting transaction amounts and balances on-chain via zero-knowledge proofs. For B2B commerce where transaction visibility is a competitive risk, this matters.
4. Multi-Protocol Routing
UCP is one of several emerging agent commerce protocols. Nexus's protocol router supports:
- UCP — Google's commerce standard
- x402 — Coinbase's HTTP payment pipe
- AP2 — Agent Payment Protocol (Google/industry)
- HTTP 402 — Native web payment status
Merchants integrating Nexus as their settlement layer get payment coverage across all these protocols, not just UCP.
Integration Architecture
A merchant supporting both UCP and Nexus exposes two complementary interfaces:
UCP Surface (/.well-known/ucp):
{
"capabilities": ["checkout", "discount", "fulfillment"],
"payment_handlers": [{
"type": "nexuspay",
"config": { "merchant_did": "did:platon:lat1..." }
}]
}Nexus Surface (skill.md / MCP):
- nexus_get_quote: Get price quote for items
- nexus_orchestrate_payment: Create escrow-backed checkout
- nexus_confirm_fulfillment: Release funds after deliveryThe User Agent discovers the merchant via UCP, negotiates the cart and checkout via UCP primitives, then settles payment through Nexus's escrow flow. The Merchant Agent receives UCP commerce events and Nexus settlement webhooks — both through standard interfaces.
Key Takeaways
Different layers, shared goal. UCP standardizes commerce communication between agents and merchants. Nexus standardizes settlement assurance. They are complementary, not competing.
UCP's payment handler model is the natural integration point. Nexus plugs into UCP as a payment handler that provides escrow, dispute resolution, and privacy — capabilities that UCP deliberately leaves to downstream providers.
Multi-protocol matters. The agentic commerce landscape is fragmenting across UCP, x402, AP2, and others. Nexus's protocol router ensures merchants can settle payments regardless of which protocol the User Agent speaks.
Nexus encourages UCP adoption. For agent-to-merchant commerce communication, UCP is a well-designed, industry-backed standard. Nexus focuses on what happens after the commerce layer hands off to settlement — and supports UCP as the recommended commerce layer.