Skip to content

CONCEPT Cited by 1 source

Agent identity resolution gap

Definition

The agent identity resolution gap is the agentic-commerce-specific integration problem that the buyer's identity is not materialised until the buy moment because the agent is acting as a guest-checkout proxy on the buyer's behalf.

Per Stripe's 2026-03-12 retrospective: "Most agentic commerce still behaves like a guest checkout: the agent acts as proxy, and the customer's identity isn't revealed until the moment they hit 'buy.' Identity signals exist, but sellers have to do a lot of manual work to capture what's available and map it into existing customer and order management systems."

The logged-in state — which on browser / app channels is the seller's source of truth for loyalty, saved preferences, personalisation, and conversion attribution — is absent on third-party agent surfaces until transaction-close.

Concrete consequences

Sellers' existing customer / order-management infrastructure expects identity at session start. On agentic surfaces, identity arrives in the final API payload. As a result:

  • Loyalty benefits (points, tier perks, member discounts) are hard to apply at the point of agent-surfaced pricing because the buyer isn't recognised yet.
  • Targeted discounts depending on customer segment can't be surfaced through the agent without manual mapping.
  • Attribution (which marketing spend drove the buy, abandoned-cart diagnostics) breaks because the before-buy session is anonymous to the seller.
  • Faster agent decisions compound the cost of closing friction. "As agents get better at making timely, relevant recommendations, the decision to buy can happen faster. If checkout then forces extra steps (whether that's a click-out to a business's site or additional confirmation and form-fills), sellers risk losing that intent." — every extra identity-resolution step is a cart-abandonment risk.

Architectural responses

Stripe positions two complementary responses:

  1. Link as a returning-customer fast path. For Link users, shipping and payment details are already saved in Stripe; the agent can complete the purchase "without exposing a shopper's personal or payment details" and the buyer skips most of the close-friction that would otherwise defeat the agent-decision cadence.
  2. SPTs scoped to buyer intent. The SPT carries enough metadata to authorise the payment without materialising the buyer's identity to the agent — the seller can resolve identity post-authorisation if their systems need it.

Longer term, Stripe flags "loyalty programs plug in, more complex fulfillment options supported, and upgrades to post-purchase engagement" as the agentic-ecosystem maturation axis — i.e. the gap is expected to close progressively as more identity-primitive standards emerge.

First-party vs third-party asymmetry

  • First-party agents (e.g. NikeAI, Magic Apron from Home Depot) don't have this gap — the agent is an extension of the seller's own logged-in-state.
  • Third-party agents (e.g. OpenAI's shopping surface) carry the gap fully — the agent knows the buyer's OpenAI identity, not the seller's.

Seen in

Last updated · 476 distilled / 1,218 read