ClawHub

Huifu DouGong Aggregation Query

v1.0.2

汇付支付聚合支付查询与关单的斗拱SDK Skill：覆盖聚合交易查询、聚合交易关单、关单查询、对账单查询。参数表和业务规则按协议字段组织，Java SDK 调用方式放在语言适配入口里。当开发者需要查询聚合支付订单状态或关闭未支付的聚合订单时使用。触发词：聚合交易查询、聚合订单查询、聚合关单、聚合交易关闭、对账单。

⭐ 3· 294·0 current·0 all-time
by青衫墨痕@codecodeing

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for codecodeing/huifu-dougong-aggregation-query.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Huifu DouGong Aggregation Query" (codecodeing/huifu-dougong-aggregation-query) from ClawHub.
Skill page: https://clawhub.ai/codecodeing/huifu-dougong-aggregation-query
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Config paths to check: HUIFU_PRODUCT_ID, HUIFU_SYS_ID, HUIFU_RSA_PRIVATE_KEY, HUIFU_RSA_PUBLIC_KEY
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install huifu-dougong-aggregation-query

ClawHub CLI

Package manager switcher

npx clawhub@latest install huifu-dougong-aggregation-query
Security Scan
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (Huifu aggregation query/close/reconciliation) match the artifacts and required config: product/sys IDs and an RSA keypair are reasonable for signing requests to Huifu's APIs. Declared dependency on a base aggregation SDK is expected.
✓
Instruction Scope
SKILL.md is documentation-style runtime instructions (how to build requests, sign with RSA, call Huifu endpoints, parse returned download_url). It does not instruct reading unrelated system files or exfiltrating data to third-party endpoints beyond Huifu. The code snippets explicitly sign requests and POST to Huifu endpoints, which is within scope.
✓
Install Mechanism
Instruction-only skill with no install spec and no bundled code — lowest-risk install model. All runtime behavior is described in docs rather than arbitrary downloaded code.
✓
Credentials
Required config items (HUIFU_PRODUCT_ID, HUIFU_SYS_ID, HUIFU_RSA_PRIVATE_KEY, HUIFU_RSA_PUBLIC_KEY) are expected for a payment SDK because requests must be signed and identify the merchant. These are sensitive (private key) but justified by the skill purpose; no unrelated secrets or broad credentials are requested.
ℹ
Persistence & Privilege
Skill is not forced always-on (always:false) and is user-invocable. Model invocation is allowed (normal). Note: granting an agent access to a merchant RSA private key increases blast radius if the agent is allowed to invoke the skill autonomously; this is a policy decision for the user, not an incoherence in the skill.
Assessment
This skill appears to be documentation-based glue for Huifu's aggregation query/close/reconciliation APIs and legitimately needs the merchant IDs and an RSA keypair to sign API requests. Before installing: (1) Verify the skill source/trustworthiness (source is listed as unknown; homepage points to Huifu). (2) Only provide test or scoped credentials (not your production private key) until you confirm behavior. Store keys in a secure vault and grant least privilege. (3) Review the upstream dependency huifu-dougong-aggregation-base (the skill references it) — ensure it is trustworthy. (4) If you do not want autonomous calls that could sign requests with your key, restrict agent/skill invocation or require explicit confirmation before network calls. If you want higher assurance, request the skill author or Huifu-signed source code or perform an internal code review of the base SDK.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

ConfigHUIFU_PRODUCT_ID, HUIFU_SYS_ID, HUIFU_RSA_PRIVATE_KEY, HUIFU_RSA_PUBLIC_KEY
latestvk970p99rmfhw35pp72bfyfrgps84twq3
294downloads
3stars
3versions
Updated 2w ago
v1.0.2
MIT-0
青衫墨痕@codecodeing
latest
Download

版权声明：本 Skill 内容来源于上海汇付支付有限公司官方开放平台文档，版权归属上海汇付支付有限公司。如有疑问可咨询汇付支付客服：400-820-2819 / cs@huifu.com

Source: Official Open Platform documentation of Shanghai Huifu Payment Co., Ltd.

Copyright: Shanghai Huifu Payment Co., Ltd.

聚合支付 - 查询、关单与对账

交易查询 + 交易关单 + 关单查询 + 对账单查询。

适配版本与复核信息

项目内容
Skill 版本1.1.0
当前适配 SDKdg-lightning-sdk 1.0.3
最后复核日期2026-04-08
官方文档来源汇付开放平台聚合支付查询/关单/对账接口文档、Java SDK 文档、异步消息说明

运行依赖与凭据边界

本 Skill 依赖 huifu-dougong-aggregation-base 提供公共运行时。凭据使用规则与存放边界见 credential-boundary.md。

前置依赖：首次接入请先阅读 huifu-dougong-aggregation-base 完成 SDK 初始化。

进入本 Skill 前先确认：上游下单侧已经保存 req_date、req_seq_id、hf_seq_id、party_order_id 等查询键；具体来源和客户准备项见 customer-preparation.md。

官方开发指引补充约束：微信 / 支付宝 / 银联多个渠道文档都明确要求，用户前端页面收到支付完成回调后，后端仍需调用查询订单 API 确认最终状态。

协议规则入口

语言适配入口

这份 Skill 的查询字段、关单限制和对账字段，都是语言无关的。
具体语言怎么初始化和发请求，先看这里：

触发词

  • "聚合交易查询"、"聚合订单查询"、"聚合订单状态"、"查询聚合支付结果"
  • "聚合关单"、"聚合交易关闭"、"关闭聚合订单"
  • "聚合关单查询"、"关单状态"
  • "对账单"、"对账"、"账单查询"、"结算对账"

场景路由

用户意图场景详细说明
查询订单支付状态聚合交易查询见 payment-query.md
关闭未支付订单聚合交易关单见 trade-close.md
查询关单结果关单查询见 close-query.md
查询对账单对账单查询见 reconciliation.md

使用场景说明

交易查询

  • 用户支付后未收到异步通知，需主动确认支付结果
  • 收到异步通知后做二次确认
  • 反扫支付返回处理中（用户需输入密码），轮询确认
  • 当 trans_stat=P 时，建议间隔 5 秒轮询，最多 30 次（150 秒）

交易关单

  • 用户长时间未支付，主动关闭订单释放资源
  • 仅支持微信和支付宝交易，银联/数字货币不支持
  • 原交易已是终态（成功/失败）的，关单会失败
  • 不允许关闭一分钟以内的订单

关单查询

  • 发起关单请求后未收到结果，查询关单状态

对账单查询

  • 查询交易/结算/分账/出金/用户结算等对账文件
  • 接口支持 1 年内账单下载；控台下载当前口径暂未限制时间范围
  • 对账文件按 T+1/D+1 规则生成；最新产品介绍口径建议交易/分账文件 12:00 后下载，出金对账单 10:30 跑批后一小时，结算对账单 17:00 跑批后一小时
  • 每天建议不超过 3 次查询
  • 请求字段名固定为 file_date 和 bill_type；不要按中文释义改写成 bill_date、generate_date 或 file_type

注意事项

  1. 查询需要传入 huifu_id，并使用 out_ord_id、hf_seq_id、req_seq_id 三选一作为查询键；req_date 为条件必填，建议在按 req_seq_id 查询时一并传入
  2. 关单需要传入 req_date、req_seq_id、huifu_id、org_req_date，并在 org_hf_seq_id、org_req_seq_id 中二选一定位原交易
  3. 关单查询需要传入 req_date、req_seq_id、huifu_id、org_req_date，并在 org_hf_seq_id、org_req_seq_id 中二选一；且只能通过原交易查询关单状态
  4. 关单后用户将无法再对该订单进行支付
  5. 已支付成功的订单无法关单，只能走退款流程
  6. 银联二维码交易不支持关单
  7. 建议收到异步通知后仍调用查询接口做二次确认
  8. 常规对账单下载结果通常是压缩文件，压缩包内多为 csv；SETTLE_FUND_BILL 模板为 .xlsx，不要把所有账单都按 csv 解析
  9. 对账单查询请求参数应直接使用 file_date 和 bill_type，不要额外设计 bill_date/generate_date -> file_date 或 file_type -> bill_type 映射层

快速接入代码示例见 quickstart.md。

版权声明与联系方式见 copyright-notice.md

Comments

Loading comments...