WeChatPay Payment Integration Guide

Where WeChatPay integration usually gets stuck

Teams often do not lack API docs. They get stuck between product selection, merchant roles, field meanings, error codes, and pre-release checks. Payment issues span APIv3, callbacks, refunds, reconciliation, and security compliance, and writing code from memory can lead to wrong roles, failed order queries, refund anomalies, or production fund risk.

How the skill works

It focuses on domestic WeChatPay integration and requires resource sync and knowledge search before answering from official documentation. Core capabilities include:
- Product selection: match the payment product to the business scenario, role, and fund flow.
- Sample code: provide official request examples for curl, Java, and Go; for other languages, explicitly mark output as an AI reference implementation.
- Integration quality review: scan existing code with a quality checklist, product notes, and issue severity such as 🔴🟡🟠.
- Q&A and troubleshooting: act as the fallback path for field meanings, workflow questions, error codes, and order-status checks.

The workflow emphasizes search-before-answer: run knowledge search each turn, read the matching docs, and state when coverage is missing instead of inventing details.

Boundaries

It assumes domestic merchants and does not cover cross-border payments. Non-official language code must be reviewed by developers. It is useful for integration, debugging, and pre-release review, but it is not a substitute for business decisions, financial audit, or human security review.