cloudbase-wechat-integration
CloudBase WeChat integration guide for Mini Program WeChat Pay, Mini Program virtual payment (虚拟支付, wx.requestVirtualPayment), Official Account JSAPI Pay, Native QR-code Pay, Official Account OAuth, openid handling, payment callbacks, and CloudBase Integration Center generated functions. This skill should be used when users ask to add, debug, or extend WeChat payment, virtual payment, or official-account flows on CloudBase.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 447
- Forks
- 138
01 前言 Front Matter
- name
- cloudbase-wechat-integration
- license
- MIT
- version
- 2.36.2
- alwaysApply
- false
- description
- CloudBase WeChat integration guide for Mini Program WeChat Pay, Mini Program virtual payment (虚拟支付, wx.requestVirtualPayment), Official Account JSAPI Pay, Native QR-code Pay, Official Account OAuth, openid handling, payment callbacks, and CloudBase Integration Center generated functions. This skill should be used when users ask to add, debug, or extend WeChat payment, virtual payment, or official-account flows on CloudBase.
02 资源文件 7
- 参考文档references/mini-program-pay.md3.2 KB
- 参考文档references/native-qr-pay.md2.3 KB
- 参考文档references/official-account-jsapi-pay.md2.5 KB
- 参考文档references/official-account-oauth.md2.4 KB
- 参考文档references/overview.md2.6 KB
- 参考文档references/troubleshooting.md3.6 KB
- 参考文档references/virtual-payment.md18.6 KB
03 SKILL.md 正文
CloudBase WeChat Integration
This skill routes WeChat payment and official-account work through CloudBase Integration Center. It gives the agent the stable execution contract and points to the official Markdown docs for console details that may change.
Sibling skills (local only)
Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../auth-tool-cloudbase/SKILL.md.
If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do not HTTP-fetch remote skill or protocol markdown into the agent context.
Official CloudBase Integration Center docs (human reference — do not treat as skill markdown to fetch into agent context as a sibling skill substitute):
- CloudBase Integration Center overview:
https://docs.cloudbase.net/integration/introduce.md - CloudBase Integration Center usage:
https://docs.cloudbase.net/integration/usage.md - When cloud function deployment or log operations are needed and no sibling skill is available, use the current platform's CloudBase MCP tools or CloudBase console instead of guessing unsupported APIs.
Activation Contract
Use this first when
- The user asks about WeChat Pay, 小程序支付, 微信支付, JSAPI 支付, 公众号支付, Native 扫码支付, 二维码支付, refund callbacks, payment callbacks,
wx.requestPayment,WeixinJSBridge,openid, or Official Account OAuth in a CloudBase app. - The user asks about 虚拟支付 (virtual payment) for virtual goods: 道具直购, 代币充值,
wx.requestVirtualPayment, OfferID, AppKey 签名,xpay_*callbacks (发货推送/查单/退款), or MP 后台虚拟支付开通与配置. - The task mentions CloudBase Integration Center, 集成中心, generated payment functions,
pay-common,offiaccount-common, or callback routing for WeChat payment. - The user needs to extend a CloudBase Integration Center generated function with order persistence, idempotency, fulfillment, or payment-status sync.
Then also read
- Mini Program structure and preview work ->
../miniprogram-development/SKILL.md(if unavailable, use the current mini program platform docs and the mini-program payment reference in this skill) - Web frontend work ->
../web-development/SKILL.md(if unavailable, use the JSAPI or Native references in this skill) - Cloud function runtime, logs, deployment, or gateway work ->
../cloud-functions/SKILL.md(if unavailable, use CloudBase console/MCP function tools and the generated-function guidance in this skill)
Do NOT use for
- Generic CloudBase Web Auth or Mini Program native identity work that does not involve WeChat payment or official-account OAuth.
- General CloudBase cloud function development unrelated to Integration Center generated functions.
- Creating or managing Integration Center instances through guessed MCP tools, guessed Manager SDK methods, or undocumented Cloud API actions.
- Storing merchant secrets, private keys, APIv3 keys, AppSecret values, or certificates in app source code, generated examples, README files, commits, or prompts.
Operating Rules
- Treat Integration Center creation as a console-first workflow unless a public Manager SDK or Cloud API contract is confirmed in official docs.
- Use official
index.mddocs for console UI steps and credential fields; do not copy stale console screenshots or invent field names. - Never ask the user to paste secrets into chat. Tell them to configure merchant and official-account credentials in the CloudBase console Integration Center form.
- Do not assume generated function names are fixed.
pay-commonandoffiaccount-commonare examples; ask for or inspect the actual function name before writing calls. - Treat frontend payment success as UI feedback only. The authoritative payment state must come from server-side query results or payment callbacks.
- When extending generated functions, preserve credential environment variables and generated callback verification/decryption logic. Add business logic around order checks, persistence, idempotency, and fulfillment.
- Before changing payment or callback code, identify the target scenario and load only the matching reference file.
- For 虚拟支付 inbound callbacks, do not reuse outbound
pay_sigas the notify authenticator. Cloud function and Integration Center deliveries are already verified. A self-hosted HTTP receiver follows mini program message-push verification inreferences/virtual-payment.md. Match the ack to the configured XML or JSON push format.refund_ordersuccess only means the refund task was accepted. A refund notify counts as success only when itsRetCodeis0and the refund id matches; do not invent unpublished idempotency or query-parameter mappings.
Routing
| Task | Read | Why |
|---|---|---|
| Capability selection, console-first boundaries, independent distribution | references/overview.md |
Establishes the Integration Center model and safety rules |
Mini Program WeChat Pay, wx.cloud.callHTTPFunction, wx.requestPayment |
references/mini-program-pay.md |
Covers Mini Program openid injection, order creation, and callback expectations |
Mini Program 虚拟支付, virtual goods, wx.requestVirtualPayment, xpay_* callbacks |
references/virtual-payment.md |
Covers OfferID/AppKey signing, sandbox vs 现网, delivery callbacks, query_order status, refund acceptance vs completion, and self-hosted message-push verification versus gateway-verified callbacks |
Official Account JSAPI pay, H5 inside WeChat, WeixinJSBridge.invoke |
references/official-account-jsapi-pay.md |
Covers official-account openid and JSAPI invocation |
| Native QR-code pay for PC/Web checkout | references/native-qr-pay.md |
Covers code_url, QR rendering, and polling/query flow |
| Official Account OAuth, openid/userinfo retrieval | references/official-account-oauth.md |
Covers OAuth routes generated by the official-account integration |
| 404, missing credentials, openid mismatch, callback failures, logs | references/troubleshooting.md |
Provides diagnosis steps before changing code |
Quick Workflow
- Classify the scenario: Mini Program Pay, Virtual Payment (虚拟支付), JSAPI Pay, Native Pay, Official Account OAuth, generated-function extension, or troubleshooting.
- Load the matching reference and the official
index.mddocs linked there. - Confirm the actual CloudBase environment ID and generated function name.
- Generate or modify only the required client/backend code; keep merchant credentials in Integration Center configuration.
- Add order-status query, callback idempotency, and amount/order validation when payment state affects business data.
- Verify through function logs, callback logs, and an end-to-end payment sandbox or low-value production test as appropriate.
Minimum Self-Check
- Did I avoid guessing undocumented Integration Center management APIs?
- Did I use the actual generated function name instead of assuming
pay-common? - Did I keep all merchant secrets and certificates out of source code and chat?
- Did the payment flow rely on callback/query state rather than only frontend success?
- Did I load only the scenario reference needed for the user's task?
Reference index
All packaged reference files (required for skill lint reachability):
04 同仓库更多 Skills
yingmi-skill
当用户需要查询基金、策略、公告、财经资讯,做资产配置、组合诊断、风险回测、现金流分析,或生成图表、PDF 时,优先使用本 Skill 获取真实数据与可执行能力。
web-access
所有联网操作必须通过此 skill 处理,包括:搜索、网页抓取、登录后操作、网络交互等。
tencentmap-map-assistant
腾讯位置服务·地图助手 Skill,一句自然语言调用腾讯地图全套能力,无需开发者账号、开箱即用。提供 AI 旅游攻略、地点搜索(含评分/人均/营业时间)、关键词提示、路线规划(驾车/步行/公交/骑行)、地址解析与逆解析、行政区划、IP 定位、距离计算、天气查询,并可将行程或多 POI 渲染成网页地图。涉及找地点、规划路线、旅游行程、查天气、坐标转换等出行场景时使用。
skill-scanner
Scan any agent skill for security risks before you install or use it. Powered by Tencent Zhuque Lab A.I.G (AI-Infra-Guard). 100% local static analysis — no file contents or credentials leave your device. Compatible with CodeBuddy, Cursor, Windsurf, Claude Code, OpenClaw and more. Triggers on: 这个 skill 安全吗, skill 安全扫描, 检查 skill 安全, audit skill, scan skill, check skill safety, analyze skill, inspect skill, verify skill, skill security, skill supply chain. Do NOT trigger for general agent usage, full system health checks, project debugging, or normal development.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends agent capabilities with specialized knowledge, workflows, or tool integrations.
shader-dev
Comprehensive GLSL shader techniques for creating stunning visual effects — ray marching, SDF modeling, fluid simulation, particle systems, procedural generation, lighting, post-processing, and more.