Obenan Briefings · Flagship
Networks are building the bridge. Merchants still own the truth.
Networks are building the bridge from agent intent to payment execution. Merchant truth still lives inside the merchant. The April 2026 evidence stack makes that boundary concrete for the first time.
Published April 21, 2026
Operator takeaway
Catalog normalization, eligibility attestation, and bounded commitment objects are merchant-controlled work that network-side bridges will expose rather than fill, so operators should not wait for a network to deliver those primitives on their behalf.
The problem
The external problem
Card networks and closed-loop issuers now expose the agent-to-payment path in public. Visa Intelligent Commerce Connect is a single on-ramp across protocols. Mastercard Agent Pay is live across Europe, Latin America, ASEAN, and Thailand. American Express has published ACE capability specs. The bridge from agent intent to payment execution is being built. None of these bridges carry merchant truth. Availability, eligibility, service inventory, and commitment semantics remain upstream of every public network specification.
The internal problem
Operators building for agentic commerce cannot wait for a card network to ship merchant catalog normalization or eligibility attestation. Those are merchant-controlled primitives. The longer a merchant depends on a network to fill them, the less defensible the merchant's position becomes when the bridge actually opens to production traffic. The work is being publicly externalized, but it is still the merchant's work.
The deeper question
There is a load-bearing line inside agentic commerce that the market has been blurring. Networks own execution. Merchants own truth. When a network exposes a committability contract, what it is really asking for is a bounded commitment object from the merchant. That object does not come from the network. It comes from the merchant system that knows what can actually be honored.
What changed
Four signals that made the boundary concrete in April 2026
Visa opened Intelligent Commerce Connect as a multi-protocol on-ramp
On April 8, 2026, Visa unveiled Intelligent Commerce Connect: a single integration on the Visa Acceptance Platform bundling payment initiation, tokenization, spend controls, merchant catalog discoverability, and acceptance of agent-initiated payments across TAP, MPP, ACP, and UCP. Pilots are live.
Mastercard moved Agent Pay from pilots to multi-region live execution
Across March and April 2026, Mastercard shipped live authenticated agentic transactions in Europe with Santander, across Latin America and the Caribbean, across multiple ASEAN markets, and on April 7, 2026 in Thailand with Krungthai Card, where an AI agent booked a ride through Elife. Mastercard has stated its intent to expand into travel, entertainment, and retail.
American Express published ACE specs and named the ecosystem
As of April 14, 2026, the Agentic Commerce Experiences product page lists Account Enablement, Intent Intelligence, and Payment Credentials as available specifications, with Agent Registration and Cart Context under development. Amex introduced Agent Purchase Protection and publicly named Google, Microsoft, OpenAI, PayPal, Stripe, Adyen, Delta, Expedia, Fiserv, Global Payments, and Hilton in the ACE ecosystem.
Universal Commerce Protocol released v2026-04-08 as versioned code
On April 9, 2026, the Universal Commerce Protocol GitHub repository published release v2026-04-08. The release adds cart capability, catalog search and lookup, request and response signing, error handling, authorization and abuse signals, eligibility claims and verification, and formal totals and disclosure contracts. Live specs at ucp.dev distinguish provisional catalog truth from authoritative checkout truth.
The missing layer
Where the bridge ends and where the truth begins
Each of the four signals in April 2026 strengthened one side of the same boundary. Network-side execution, authorization, protocol contracts, and closed-loop intent are getting concrete in public. Merchant-side truth, the catalog normalization, availability attestation, eligibility binding, and bounded commitment objects that the bridge needs to land, remains inside the merchant.
Discovery
Agent finds a merchant through search, feed, or recommendation. UCP catalog search and Visa ICC merchant discovery cover this side.
Merchant Truth
Identity, availability, eligibility, service inventory, and current state verified at the moment of commitment. No public network bridge fills this layer.
Bounded Commitment
Eligibility claims bind at checkout. UCP signed envelopes, Mastercard Verifiable Intent, and Amex Intent Intelligence define the contract shape, but the merchant provides the commitment object.
Payment Execution
Authenticated agentic transaction through tokenized rails with network-level controls. Visa ICC, Mastercard Agent Pay, and Amex Payment Credentials cover this side.
Our position
Merchant truth lives inside the merchant
The April 2026 evidence stack does not contradict the Obenan thesis. It confirms it. Networks and closed-loop issuers are building the bridge in public. Standards bodies are publishing versioned contracts. The part that remains merchant-controlled is sharper than it was three months ago: catalog normalization, eligibility attestation, and bounded commitment objects for local-service commerce. Merchants who treat this as network-side work will be surprised by how much is still theirs when the bridge opens fully.
Networks own execution. Merchants own truth. The boundary is now visible.
Eligibility can advertise at discovery. It must bind at checkout. The merchant is the binding party.
Bounded commitment objects are merchant output, not network input.
What we do not claim
Four boundaries we hold
The April 2026 evidence stack is real and dated. It also has limits. Four claims we explicitly are not making in this briefing.
- 01
Obenan is not the payment execution layer. Mastercard, American Express, Visa, and UCP retain that role.
- 02
No public network bridge is production-complete for local-service commerce. Reservation state, hold primitives, deposit handling, and policy acceptance remain unresolved across every public piece of evidence in this pack.
- 03
UCP is not yet the universal agentic-commerce standard. Closed-loop (American Express ACE) and card-network (Mastercard Agent Pay, Visa Intelligent Commerce Connect) surfaces continue to run in parallel.
- 04
No Obenan-onboarded merchant is certified or committable by any public network specification. Those specifications are still being released and do not yet cover service inventory or reservation semantics.
A simple plan
Three steps to hold the merchant side of the boundary
Normalize your catalog for the contract
UCP v2026-04-08 defines catalog search and lookup contracts with provisional-at-browse and authoritative-at-checkout semantics. Structure your catalog so it can participate in that shape, including service inventory for local-service verticals where UCP has not yet reached.
Make eligibility and availability attestable
Amex Intent Intelligence, Mastercard Verifiable Intent, and UCP eligibility claims all expect the merchant to attest that a given intent can bind. Keep the underlying availability, policy, and eligibility signals current and expressible in machine-readable form.
Publish bounded commitment objects
For local-service commerce, a successful bridge needs more than a product variant. Codify service-slot, reservation, and policy-acceptance semantics that a downstream bridge can consume. This is the work no network is going to do on the merchant's behalf.
What success looks like
The network bridge opens in your vertical and your catalog binds cleanly to signed checkout envelopes
Eligibility attestation is queryable so agents stop guessing and start committing to what you can honor
Service inventory, reservation, and policy-acceptance semantics are published before any public network specification requires them
What failure looks like
The bridge opens and your merchant systems cannot produce a bounded commitment object in the shape the contract expects
Eligibility is advertised at discovery but collapses at checkout because the merchant side has not been attested
A network specification arrives for service commerce and your catalog is not structured to bind to it
Keep reading
How this connects to the rest of the merchant-participation thesis
The bridge is being built. The truth is still yours.
If you run catalog, eligibility, or service-inventory systems for local-service merchants, the practical next step is making merchant truth queryable and committable before the bridge arrives at your vertical.
Sources
Five primary sources across April 2026 that move the boundary from announcement language to concrete artifact. UCP v2026-04-08 is the non-announcement anchor via standards-body verifiable primary sources at github.com and ucp.dev.
- 1.Visa Intelligent Commerce Connect announcementusa.visa.com · April 8, 2026 · Checked April 10, 2026
Primary source for the Visa Intelligent Commerce Connect network on-ramp across TAP, MPP, ACP, and UCP; anchors the Network side of the bridge pattern.
- 2.Mastercard Agent Pay multi-region expansionmastercard.com · April 6, 2026 · Checked April 10, 2026
Primary source for authenticated agentic transactions live across multiple ASEAN markets plus Verifiable Intent; the multi-region execution context that surrounds the Thailand proof point.
- 3.Mastercard and Krungthai Card live agentic ride-booking in Thailandmastercard.com · April 7, 2026 · Checked April 14, 2026
Primary source for the first authenticated agentic transaction in Thailand and the live local-service booking proof point behind the Execution tag.
- 4.American Express Agentic Commerce Experiencesamericanexpress.com · April 14, 2026 · Checked April 17, 2026
Primary source for ACE capability specifications, Agent Purchase Protection, and the named ACE ecosystem; the Closed-Loop side of the boundary.
- 5.UCP release v2026-04-08 on GitHubgithub.com · April 9, 2026 · Checked April 21, 2026
Non-announcement evidence anchor via standards-body verifiable primary source. The release ships concrete cart, catalog, signing, eligibility, authorization, abuse-signal, and totals contracts. Live specs at ucp.dev/draft/specification/catalog and ucp.dev/latest/specification/checkout-rest corroborate the release independently.