payment Template

Recommended baseline: agreements/payment/<version>/agreement.json.

Typical merchant-side capability groups:

• payment method discovery
• payment order creation
• payment order status query
• payment order closing
• refund request creation
• refund request status query

Recommended modeling rules:

• keep the agreement provider-neutral
• let the merchant service expose supported methods through provider and actionType
• keep provider-specific execution outside the agreement layer
• use payment actions such as cashier_url, payment_required, redirect_url, qr_code, deeplink, or form_post

Recommended split:

• the merchant service implements the payment agreement
• the user-side agent decides whether it already has a matching provider plugin or skill
• for example, if a payment action returns provider = alipay, the agent may use an installed Alipay plugin or skill to complete the provider-specific execution step