UCP Payment Handlers: Stripe, Adyen, Visa & More

How UCP Payment Works

Before diving into specific handlers, it helps to understand how payment flows through UCP. Unlike traditional e-commerce where the consumer enters card details on a checkout page, UCP uses a tokenized payment model:

1. Consumer pre-authorizes. The consumer links a payment method to their UCP identity through their identity provider (typically their AI agent platform). This happens once, not per transaction.
2. Agent requests a payment token. When the consumer confirms a purchase, the agent's platform generates a one-time payment token scoped to that specific transaction; merchant, amount, and currency are baked into the token.
3. Merchant resolves the token. The merchant passes the token to their payment handler, which contacts the issuing network to authorize and capture the payment.
4. Settlement flows normally. After authorization, settlement follows the same path as any card-not-present transaction. Merchants receive funds through their normal payment schedule.

The critical design decision here is that the agent never touches raw payment credentials. No card numbers, no CVVs, no bank account details flow through the agent or the UCP protocol itself. This is what makes UCP transactions secure despite involving a third party (the agent) in the purchase flow.

The Payment Handler Landscape

Several major payment handlers have announced support for UCP or are expected to participate based on their endorsement of the protocol. As of early 2026, specific integration details are still emerging; here's what we know based on announced support and the UCP specification's payment_handlers field.

Stripe

Stripe is expected to be one of the primary payment handlers in the UCP ecosystem, given their extensive developer tooling and existing payment infrastructure.

Integration approach. Based on Stripe's announced UCP support, merchants are expected to use Stripe's existing infrastructure to process UCP payment tokens. For merchants already using Stripe, adding UCP payment support is expected to require minimal additional configuration.

Expected features:

• Fraud detection adapted for agent-initiated transactions
• Support for 135+ currencies through Stripe's existing infrastructure
• Dispute handling that accounts for the agent-mediated purchase flow

Pricing. Details are still emerging, but Stripe's standard processing fees are expected to apply without a UCP-specific surcharge.

Integration complexity. Expected to be low for existing Stripe merchants.

Adyen

Adyen's UCP implementation leverages their unified commerce platform, making it a strong choice for merchants who sell across multiple channels (web, mobile, in-store, and now agent).

Integration approach. Based on Adyen's announced support, UCP is expected to be treated as another payment channel in their unified platform, with token exchange through Adyen's existing checkout API.

Expected features:

• Unified reporting across web, mobile, POS, and agent channels
• Strong in European markets with local acquiring across 30+ countries
• Advanced risk management capabilities
• Multi-acquirer routing for optimal authorization rates

Pricing. Adyen's standard processing-plus pricing is expected to apply.

Integration complexity. Moderate. Adyen's API is well-documented but has more configuration options than Stripe, which can be overwhelming for smaller merchants.

Visa Direct / Visa Token Service

Visa is a UCP endorser and is expected to provide payment infrastructure support. Visa Token Service (VTS) is the likely underlying tokenization infrastructure for Visa-based UCP transactions.

Integration approach. Visa's UCP support is expected to work at the network level. Most merchants would access Visa's UCP support indirectly through their existing payment handler (Stripe, Adyen, etc.), which uses Visa's token infrastructure behind the scenes.

Expected features:

• Network-level tokenization (tokens valid across Visa-accepting processors)
• High authorization rates from card-network-level token resolution
• Cross-border transaction optimization

Pricing. Standard Visa network fees are expected to apply.

Integration complexity. High for direct integration. Most merchants will access Visa's UCP support indirectly through Stripe, Adyen, or another handler.

Mastercard

Mastercard's UCP involvement is expected to mirror Visa's network-level approach, leveraging their Digital Enablement Service (MDES).

Expected features:

• MDES tokenization for Mastercard and Maestro cards
• Integration with Mastercard's fraud scoring capabilities
• Identity verification through Mastercard's ID service

Integration complexity. Similar to Visa; most merchants would access Mastercard UCP support through their existing payment handler.

American Express

Amex's potential UCP involvement could leverage their closed-loop network advantage, because Amex is both the network and the issuer for most Amex cards, they could offer faster authorization and richer transaction data.

Expected features:

• Closed-loop advantage: faster auth, richer data
• Strong in premium/luxury merchant segments

Integration complexity. Details are still emerging. Most merchants would likely access Amex support through their existing payment handler.

PayPal

PayPal's potential UCP support would bring their massive consumer base into the UCP ecosystem. Any consumer with a PayPal account could link it as a UCP payment method.

Expected features:

• Huge consumer reach: 400M+ accounts globally
• PayPal Buyer Protection potentially extended to UCP transactions
• Venmo integration for younger demographics

Pricing. Standard PayPal processing fees are expected to apply.

Integration complexity. Expected to be low, given PayPal's history of developer-friendly integrations.

Choosing a Payment Handler

For most merchants, the decision comes down to a few factors:

If you already have a payment handler: Start there. Adding UCP support to an existing Stripe or Adyen integration is significantly easier than onboarding a new payment handler just for UCP.

If you're starting fresh: Stripe is a strong default. Low integration complexity, transparent pricing, and excellent documentation.

If you're selling internationally: Adyen excels at local acquiring and multi-currency processing. Their authorization rates in European and Asian markets are typically higher than Stripe's.

If your customers prefer PayPal: Don't ignore PayPal. A large segment of consumers prefer PayPal for agent-mediated purchases because it adds a familiar trust layer between them and the merchant.

If you're a large enterprise: Consider supporting multiple handlers. Use Stripe for domestic transactions and Adyen for international, or let consumers choose between card payment and PayPal. UCP's payment_handlers manifest field supports listing multiple handlers per merchant.

Payment Handler Comparison Table

Security Considerations

Regardless of which handler you choose, UCP payment security rests on a few non-negotiable principles:

• Tokens are single-use. A UCP payment token can only be used once, for the specific transaction it was issued for. Intercepting a token is useless.
• Tokens are scoped. Each token is bound to a specific merchant, amount, and currency. A token issued for a $50 purchase at Store A cannot be used for a $500 purchase at Store B.
• PCI scope is reduced. Because merchants never handle raw card data (only opaque tokens), so UCP transactions reduce your PCI compliance burden.
• Consumer confirmation is required. The protocol mandates consumer confirmation before payment is processed. No silent charges, no surprise purchases.

The payment handler ecosystem is one of UCP's strengths. By staying payment-handler agnostic, UCP avoids the lock-in problem that plagues other agentic commerce approaches and gives merchants the flexibility to choose the best processor for their business.

Browse Payment Handlers in the Directory

The UCPList directory tracks 7 confirmed payment handlers with UCP support, including Stripe, Adyen, Visa, Mastercard, PayPal, and American Express. Each listing shows integration maturity, supported regions, and documentation links.