AI Agent Hub
Back to skills
WeChat Pay Merchant Risk Check icon

WeChat Pay Merchant Risk Check

Professional Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md and install @user_8509461a/wechatpay-risk-check.

About this skill

Problem

Before merchant onboarding for WeChat Pay, identity, bank account, license, and store verification often depends on manual checks. This can lead to inconsistent standards, missed risk signals, and repeated data entry. WeChat Pay Merchant Risk Check structures the official WeChat Pay risk, trade, and settlement interfaces into a workflow for pre-onboarding checks and payment operations.

How it works

The skill starts with the PreRisk module before transaction APIs:
- Risk checks: queryMchRisk, queryCertificateRisk, and querySettlementRisk cover ID names and numbers, bank account details, licenses, company names, store addresses, and coordinates.
- Payment flow: JSAPI, Native, and APP orders can be created, then queried, closed, refunded, or reversed using methods such as queryOrder, applyRefund, and reverseOrder.
- Settlement: getBalance, getBillDownloadUrl, and getDailySummary support balance checks, bill downloads, and daily summaries.
- Notifications: parseNotify, verifyNotifySign, and responseSuccess handle callback parsing, signature verification, and success responses.

It requires dual SSL certificates, RSA encryption for sensitive fields, and HMAC-SHA256 signatures. Amounts are in fen, production callbacks must be verified, and fund-related operations should remain idempotent. The skill is an integration reference, not a replacement for internal compliance approval or final risk decisions.

Use Cases

  • Payment product teams use identity, bank, and license checks before merchant onboarding approval.
  • Backend engineers integrate JSAPI, Native, or APP orders, refunds, and callback signature verification.
  • Finance operators check balance, download bills, and reconcile daily transaction summaries after payments.
  • Risk reviewers use UNKNOW, MEDIUM, or HIGH results to request documents or reject onboarding.

Best For

  • Payment product managers: include identity, bank, and license risk results in onboarding approval.
  • Backend engineers: integrate orders, refunds, callback verification, and certificate signing setup.
  • Risk reviewers: decide whether to request documents, manually review, or reject based on risk level.
  • Finance operators: check balance, download bills, and reconcile daily summaries after payments.