Shop Pay payment handler specification
The dev.shopify.shop_pay handler enables merchants to offer Shop Pay as an accelerated checkout option through UCP-compatible agents. Shop Pay is Shopify's native payment solution that provides a streamlined checkout experience by securely storing buyer payment and shipping information.
This handler enables a delegated payment flow where agents can securely generate a Shop Token for a buyer's selected payment instrument in Shop Pay. Merchants can then process these tokens, and agents can leverage the same Shop Pay integration across all participating merchants.
Checkout MCP tools are coming soon.
Checkout MCP tools are coming soon.
Anchor to Key benefitsKey benefits
- Accelerated checkout: Buyers with Shop Pay accounts can complete purchases faster using their saved payment and shipping details.
- Delegated payments: Agents can orchestrate Shop Pay payments without directly handling sensitive payment credentials.
- Standardized integration: A single Shop Pay integration works across all UCP-compatible merchants.
Anchor to Merchant integrationMerchant integration
Merchants enable Shop Pay through UCP by advertising the handler in their payment configuration and processing Shop Pay tokens when buyers complete checkout.
Anchor to RequirementsRequirements
Requirements depend on whether you're a Shopify merchant or integrating as an external merchant:
If you're a Shopify merchant, Shopify automatically advertises all UCP payment handlers on your behalf, including Shop Pay.
If you're an external merchant, you must register for Shop Pay to obtain your shop_id before advertising Shop Pay through UCP.
Anchor to Handler configurationHandler configuration
Merchants advertise Shop Pay support by including the handler in their payment handlers array. The handler uses a minimal configuration containing only the merchant's Shop Pay identifier today.
Anchor to Configuration schemaConfiguration schema
| Field | Type | Description |
|---|---|---|
shop_idrequired | String | The merchant's unique Shop Pay identifier. |
The following example shows how merchants declare the Shop Pay handler in their payment configuration:
Anchor to Payment instrument supportPayment instrument support
By advertising the Shop Pay handler, merchants indicate they can accept and process Shop Pay payment instruments. Merchants must be able to handle payment objects conforming to the Shop Pay instrument schema.
Anchor to Instrument schemaInstrument schema
Shop Pay instruments extend the base UCP payment instrument with Shop Pay-specific fields and credential types.
| Field | Type | Description |
|---|---|---|
id required | String | Unique identifier for this payment instrument. |
handler_id required | String | Must match the handler's id (for example, shop_pay). |
type required | String | Must be shop_pay. |
credential required | Object | The Shop Pay credential containing the token. |
credential.type required | String | Must be shop_token. |
credential.token required | String | The Shop Token from the delegated payment flow. |
billing_address required | Object | The billing address associated with the Shop Pay account. |
display | Object | Display information for this Shop Pay instrument. |
display.email | String | The buyer's email address associated with the Shop Pay account. |
Merchants receive a payment object structured as follows when an agent submits a Shop Pay payment:
{} Response
Anchor to Agent integrationAgent integration
Agents orchestrate Shop Pay payments on behalf of merchants through a delegated flow that collects payment authorization from buyers and returns a token for processing.
Anchor to RequirementsRequirements
Before handling delegated Shop Pay payments, agents must register with Shop Pay to obtain a client_id that supports delegated experiences.
Anchor to Handler configurationHandler configuration
Agents advertise Shop Pay support by including the handler in their payment handlers array. The handler uses a minimal configuration containing only the agent's Shop Pay identifier.
Anchor to Configuration schemaConfiguration schema
| Field | Type | Description |
|---|---|---|
client_idrequired | String | The agent's unique Shop Pay identifier. |
The following example shows how agents declare the Shop Pay handler in their payment configuration:
Anchor to Delegated payment protocolDelegated payment protocol
Agents must follow this flow to process a dev.shopify.shop_pay handler:
Anchor to Step 1: Discover handlerStep 1: Discover handler
Identify dev.shopify.shop_pay in the merchant's payment_handlers map from the checkout response or merchant profile.
Anchor to Step 2: Build payment requestStep 2: Build payment request
Build a Shop Pay payment request by:
-
Initializing the delegated payment context:
- Provide the merchant's
shop_idfrom the handler configuration. - Provide your agent's
client_idobtained during registration. - This establishes that you're orchestrating a Shop Pay payment on behalf of the merchant.
- Provide the merchant's
-
Constructing the payment request with standardized UCP checkout data:
- Totals: Subtotal, shipping, tax, and grand total amounts.
- Fulfillment options: Available shipping methods or pickup locations.
- Line items: Product details, quantities, and pricing.
- Currency and locale: For proper formatting and display.
Present this payment request to the buyer through the Shop Pay interface, where they can authenticate and select their preferred payment method.
Anchor to Step 3: Complete checkoutStep 3: Complete checkout
After the buyer confirms, Shop Pay returns a Shop Token. Wrap this token in a UCP payment instrument conforming to the Shop Pay instrument schema and submit the complete checkout request to the merchant:
Upon successful processing, the merchant returns the completed checkout state with an order_id confirming the purchase.
Anchor to Merchant processingMerchant processing
Upon receiving a shop_pay payment instrument, merchants must:
-
Validate handler: Confirm
handler_idmatches a configured Shop Pay handler. -
Extract token: Retrieve the
tokenfromcredential.token. -
Process payment: Use the Shop Token to complete the payment through Shop Pay's payment processing API.
-
Return response: Respond with the finalized checkout state including order confirmation details.
Anchor to Security considerationsSecurity considerations
The Shop Pay handler implements multiple security measures to protect payment data and ensure proper authorization throughout the delegated payment flow.
Anchor to Token securityToken security
- Single-use tokens: Shop Tokens are designed to be single-use and can't be reused across transactions.
- Time-limited: Tokens have a limited validity period and should be used promptly after generation.
- Checkout-scoped: Tokens have context about the checkout and merchant, preventing usage outside of the verified checkout.
- Secure transmission: All token exchanges must occur over TLS 1.2+.
- Agents must register with Shop Pay to obtain a valid
client_idbefore processing delegated payments. - The
client_ididentifies the agent to Shop Pay and enables proper authorization tracking.
Anchor to Schema referenceSchema reference
The following JSON schemas define the structure and validation rules for Shop Pay handler configuration and payment data:
- Handler schema: The root schema defining all Shop Pay handler components, from configs to instruments to credentials.
- Merchant config: Defines the required
shop_idconfiguration field that merchants include when advertising the Shop Pay handler. - Agent config: Defines the required
client_idconfiguration field that agents include when advertising the Shop Pay handler. - Shop Pay Instrument schema: Specifies the structure of Shop Pay payment instruments that agents submit and merchants process, including credential and billing address requirements.
- Shop Token Credential schema: Details the Shop Token credential format used to authorize payments through the delegated flow.