Tencent CloudBase WeChat Integration

The problem

When integrating WeChat Pay, official-account OAuth, JSAPI, or Native QR-code checkout into CloudBase, the hard part is not a single API call. It is keeping the moving pieces separate: wx.requestPayment vs WeixinJSBridge.invoke, Mini Program openid injection, callback verification and decryption, order persistence, idempotency, and amount validation. Hand-rolled code often guesses generated function names, treats frontend success as payment success, or puts merchant secrets into source, READMEs, or chat.

How the skill works

This skill scopes the work to CloudBase Integration Center generated functions and official documentation. It first classifies the scenario, then points to the matching reference: mini-program-pay.md, native-qr-pay.md, official-account-jsapi-pay.md, or official-account-oauth.md. It enforces a conservative workflow:

• Console-first setup: use official index.md docs and the CloudBase console forms for Integration Center creation and credentials.
• No fixed function names: pay-common and offiaccount-common are examples only; confirm the actual generated function name before writing calls.
• Server-side payment state: rely on callbacks or query results, not UI success.
• Preserve security logic: keep credential environment variables and callback verification/decryption intact, then add order checks, persistence, idempotency, and fulfillment.

Boundaries

Use it for Mini Program Pay, Official Account JSAPI, Native QR-code Pay, Official Account OAuth, generated-function extensions, and troubleshooting. Do not use it for generic CloudBase Web Auth, unrelated cloud function development, or for inventing Manager SDK/Cloud API calls to manage Integration Center. Keep AppSecret, APIv3 keys, and certificates out of source code, README files, commits, and prompts.