UCP Checker

Payment handlers

Which ways to pay a UCP agent will find at checkout, from what stores declare in their UCP profile.

Payment handlers are a core building block of the Universal Commerce Protocol. They use a trust triangle between the store, the platform and the credential provider, so payments go through without exposing raw card data. Each handler is declared in the profile with a reverse-domain namespace and works with capabilities such as checkout and with transports.

Three handlers cover almost every store

Google Pay, Shopify card and Shop Pay. Everything else is declared by a handful of stores each.

Declared by more than a couple of stores

One id per store

Some platforms give each store its own handler name. We count them together here.

Boutir custom payment methodsdev.boutir.payment.customized.*0.9% of valid profiles

Also seen

Declared by one or two stores. Listed by the name in the UCP profile.

Test and sample handlers 8

Mock, example and demo handlers some stores declare, our own test stores included.

dev.mock.payment_handlercom.ucpsandbox.pay_at_propertycom.example.processordev.ucp.mock_paymentcom.vibeshop.mockcom.example.processor_tokenizercom.demo.cardcom.ucpplayground.test_card

Questions

What are UCP payment handlers?
Payment handlers are specifications in the UCP profile that define how payment instruments are processed. They declare which payment methods a store accepts (e.g., Google Pay, Shopify card payments) along with configuration like accepted card networks and gateway details.
How do payments work in UCP?
UCP uses a trust triangle between the store, the platform and the credential provider. The platform obtains a payment token from the provider, then submits the opaque credential to the store. This keeps platforms out of PCI-DSS scope. The AP2 mandate capability (dev.ucp.common.payment.ap2_mandate) adds cryptographic authorization for autonomous agent purchases.
Can a store accept multiple payment methods?
Yes. Stores declare multiple payment handlers in their profile and can dynamically filter available handlers based on cart context. Each handler has a unique handler_id to prevent key confusion when multiple providers are available.

Explore protocol data