UCP Integration

This section is advisory.

UCP (Universal Commerce Protocol) is an open-source standard (Apache 2.0) co-developed by Google with Shopify, Etsy, Wayfair, Target, and Walmart. It covers the full commerce lifecycle: discovery, catalog, checkout, orders, fulfillment, and post-purchase adjustments. UCP uses a composable extension architecture and publishes its own well-known discovery file at /.well-known/ucp.

LCP as a UCP Extension

UCP requires formal allOf schema extensions using reverse-domain naming conventions. Legal context would be registered as:

{
  "extensions": {
    "com.integra.legal-context": {
      "type": "sha256",
      "value": "0x7f83b165...",
      "disputeResolution": {
        "method": "AAA Commercial Arbitration Rules",
        "jurisdiction": "New York, USA"
      }
    }
  }
}

Relationship to UCP's Existing links Array

UCP checkout responses require privacy_policy and terms_of_service URLs in the links array. These serve as the Level 1 (informational) integration — the terms are discoverable. The LCP extension adds Level 2+ capabilities (content hash, signed acceptance, dispute resolution hooks) without replacing the existing links requirement.

Relationship to UCP's Buyer Consent Extension

UCP provides a Buyer Consent extension (ucp.dev/specification/buyer-consent/) for declarative consent capture. LCP Level 3 (signed acceptance) provides cryptographic consent — a stronger, verifiable form. The two can coexist: Buyer Consent for UCP-level declarative consent, LCP Level 3 for cryptographic proof of acceptance.

Relationship to UCP's Adjustments

UCP logs post-purchase events including dispute as adjustment types, but provides no dispute resolution mechanism. LCP Level 4's disputeResolution field and api endpoint provide the mechanism that UCP's dispute adjustment logs feed into.

Integration Flow

1. Define the com.integra.legal-context extension using allOf schema composition
2. Checkout object includes legalContext via the extension, with optional disputeResolution
3. Agent reads the reference during the proposal phase
4. Agent verifies the terms (Level 2+)
5. Payment confirmation carries the same reference