Alipay
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent, instruction-only Alipay integration guide with clear safety guardrails, but it touches payment operations, merchant account context, external payment endpoints, and persistent local notes.
This skill appears safe to use for an intended Alipay integration. Before using it on production payments, keep work in test mode until validation passes, avoid sharing private keys or PSP secrets, approve any live financial changes manually, and periodically review the persistent ~/alipay/ notes.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Changes made under this skill could affect checkout behavior, order state, captures, refunds, or payment closure logic.
These are high-impact payment operations. The behavior is purpose-aligned and surrounded by safety guidance, but live payment mutations should remain explicitly user-approved and scoped.
Require idempotency and reconciliation for all critical calls: Authorization request; Capture request; Refund or close operations
Use test mode first, require human approval for production payment mutations, and keep PSP or merchant-account permissions limited to the relevant project.
If the agent is given broad merchant or PSP access, mistakes could affect payment configuration or production operations.
Merchant console and PSP access are sensitive account authorities. They are expected for Alipay integration, and the artifact includes an explicit guardrail against collecting secrets in chat.
Access to Alipay merchant console and target PSP account ... Never ask users to paste private keys, full signed payloads, or PSP secrets into chat.
Use least-privilege test accounts where possible, do not paste private keys or PSP secrets into chat, and review any merchant-console or PSP configuration changes before applying them.
Future sessions may rely on stale or incorrect local payment notes, and local files may reveal integration status or operational details.
The skill persists project state, validation status, risks, and notes in a fixed local directory. The storage is disclosed and constrained, but persistent notes can influence later work or expose sensitive implementation context if not reviewed.
Create `~/alipay/memory.md` ... Keep persisted notes short and actionable. Store evidence links, not raw sensitive payloads.
Review ~/alipay/ periodically, keep permissions restrictive, avoid storing secrets or raw signed payloads, and clear the directory when switching projects.
Payment metadata and signed requests may leave the local environment or backend as part of the Alipay flow.
The skill discloses external provider data flows to Alipay and possibly a selected PSP. This is necessary for the stated purpose and is bounded by endpoint and data-minimization guidance.
https://openapi.alipay.com/gateway.do | Signed payment requests and metadata | Production Alipay gateway operations ... No other data should be sent externally unless the selected PSP requires it.
Verify endpoint configuration, keep sandbox and production separated, minimize metadata sent to providers, and keep callback signature verification mandatory.