wechatpay-deduction-service

Guide WeChat Pay entrusted deduction integration across V2 and V3 protocols.

323|23|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/wechatpay-apiv3/wechatpay-skills --skill wechatpay-deduction-service
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wechatpay-deduction-service
Source: https://github.com/wechatpay-apiv3/wechatpay-skills/tree/main/wechatpay-deduction-service
Command: npx skills add https://github.com/wechatpay-apiv3/wechatpay-skills --skill wechatpay-deduction-service

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers implement WeChat Pay entrusted deduction (委托代扣) safely end to end by covering contract setup, deduction requests, notifications/callback handling, refunds, reconciliation, and troubleshooting for both merchant and partner service-provider modes.

Core Features & Use Cases

  • Product selection & access mode alignment: Determine whether the business should use periodic deduction (24h delay or pre-notification) or “pay later” style (免密/先享后付), and choose the correct contract method by terminal type (public account H5, app, mini program, H5, or payment-in-contract for merchant mode).
  • Integration knowledge base (V2/V3 protocol aware): Provide V2 (XML + APIv2 key) guidance for contract/deduction/termination/query/refund/billing/callback, with a strict exception that only the “pre-deduction notification” callback uses V3 (JSON + APIv3 key + RSA). Includes callback routing, idempotency, and concurrency handling rules.
  • Official-doc-only reference + quality & issue resolution: Direct users to the correct interface index and reference materials, then apply a production-grade “go-live checklist” mindset and a dedicated problem troubleshooting manual for common errors (signature errors, V3 pre-notification verification failures, order closing/CONTRACT_NOT_EXIST, refund and reconciliation anomalies, etc.).

Quick Start

Ask the Skill to “help me choose the correct entrusted deduction mode and contract type for my scenario, then list the exact next integration steps and the required callbacks to implement.”

Frequently Asked Questions about wechatpay-deduction-service

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right WeChat Pay entrusted deduction contract type for my scenario?

WeChat Pay entrusted deduction contract types depend on your terminal, choosing public account H5, app, mini program, or contract-by-merchant mode for periodic or pay-later flows.

V2 vs V3 protocol: which signature method does WeChat Pay entrusted deduction use?

WeChat Pay entrusted deduction uses V2 protocol (XML + APIv2 key) for contract and deduction APIs, while pre-deduction notification callbacks exclusively use V3 protocol (JSON + APIv3 key + RSA).

Why does my WeChat Pay pre-deduction notification callback fail signature verification?

Pre-deduction notification callback verification fails when applying V2 APIv2 key logic instead of the required V3 protocol using JSON payloads, APIv3 key, and RSA signature verification for WeChat Pay entrusted deduction.

How do I handle WeChat Pay entrusted deduction callback routing and idempotency?

WeChat Pay entrusted deduction callback routing requires explicit idempotency and concurrency controls to prevent duplicate processing, separating V2 contract callbacks from V3 pre-deduction notifications correctly.

What is included in the WeChat Pay entrusted deduction go-live checklist?

The WeChat Pay entrusted deduction go-live checklist enforces mode confirmation, idempotency controls, callback routing verification, and troubleshooting for signature errors, refund anomalies, and contract termination issues.

How do I troubleshoot WeChat Pay entrusted deduction refund and reconciliation anomalies?

WeChat Pay entrusted deduction refund troubleshooting addresses signature errors, V3 pre-notification verification failures, CONTRACT_NOT_EXIST order closing errors, and reconciliation anomalies using official reference indexes.