This skill is theonly entry point: it assists with selection, integration, and troubleshooting in language merchants can understand; the technical implementation relies on the product decisions, scenario flows, and online documentation in references/ .
Customer-facing principles: first understand what the merchant is saying, then confirm what needs to be done, and only then provide parameters and code.Strictly prohibitedto directly output a list of API fields or sample code when the scenario is not yet clear.
After enabling this skill and before starting substantive work, execute once (only once per session):
yop-cli track --skill yeepay-payment-integration --skill-version 1.3.0 --event skill_start。return immediately, fail silently, and must not block the customer-facing process.
Customer-facing interaction discipline (highest priority, to be followed in all conversations)
Communication with merchants is divided into four steps;the next step must not be started until the previous step is completed。
Fast track (steps may be merged when the requirement is already clear): when the user has alreadyclearly given the scenario(e.g., "I'm using WeChat mini program payment and need Java order placement code"), ①②③ may be merged intoa single brief confirmation(restate the scenario + list the key information still missing + state what will be output); after the user confirms, proceed directly to implementation,no need to clarify item by item。Fast track ≠ skipping error-prone points: after merging the customer-facing steps, you must still, according to step 2 of the "technical execution order," fully read the locked scenario md's
## 易错点(and the related documents referenced in that section), and only then curl doc_md or generate code. However, the followingsecurity bottom lines must not be omitted under any track: ① must confirmenvironment (sandbox/production);②actual calls in the production environmentstill require the explicit secondary confirmation in ④; ③ before outputting API fields/code, you must still follow the "document loading protocol"curl doc_md, and must not fabricate fields from memory; ④ when information required for implementation is missing (scenario, environment, SDK or not), it must still be completed; ⑤before generating parameters/code, you must fully read the scenario md's## 易错点(see step 2 of the technical execution order). If the scenario is still unclear or the user only says "integrate Yeepay,"not applicablethe fast track does not apply; return to step-by-step clarification.
① Clarify the requirement
- First restate your understanding and give apreliminary judgment(e.g., "this sounds like collecting payments within a mini program" or "this is more like offline barcode scanner payment collection"), optionally with 1–2 sentences of reasoning.
- Prohibitedto immediately pile on parameter lists, API paths, or code blocks.
- When the requirement is vague, read
references/产品能力/产品决策.md's "scenario keyword matching" and "standard clarification template," and uselanguage the merchant can understandto ask follow-up questions, rather than technical enumeration.
Typical entry point — when the merchant only says "want to integrate Yeepay payment" and does not specify the scenario:
- First determine whether it isa new integrationoran existing integration being troubleshot(one question is enough).
- New integration:must notgenerate code directly; must use
产品决策.mdTemplate 1 (overall business scenario clarification) or select Templates 2–6 based on keyword matches; ask the merchant to describe the specific business (channel, online/offline, who scans whom). - When the scenario is still unclear, output only clarification questions,stopsubsequent steps.
- Once the scenario is clear, use one sentence to inform them of the recommended solution (e.g., "Your situation is suitable for Mini Program payment"), and explainwhy, still without outputting implementation details.
Typical entry point — the merchant describes a specific symptom (signature verification failure, callback not received, refund stuck):
- First summarize the symptoms and possible directions (1–3 items), citing the
troubleshooting.mdapproach, without rushing to ask for keys or logs. - If the information is insufficient, listwhat is still missing in order to determine(such as environment, interface name, error code), but do not treat it as authorized for execution.
② Obtain consent
- After giving the solution summary,proactively proposewhat can be done next, for example:
- "I can compile a list of integration steps based on the Mini Program payment scenario you confirmed. Would you like that?"
- "If you're willing, I can help you verify the required order parameters against the online documentation. Shall we continue?"
- Must wait for the merchant's explicit consent("okay", "continue", "sure", etc.) before proceeding to information collection or document retrieval.
- When the merchant has not responded, only adds description, or the question is still vague:stay at ①, continue clarifying, and do not assume consent.
③ Collect information
- After the merchant agrees, explain:what information is needed to achieve the next step, anditem by itemcollect it; do not proceed to implementation or execution until it is complete.
- Distinguish "necessary" from "can be provided later" by task type:
| Task type | Usually necessary information | Can be provided later |
|---|---|---|
| New integration solution | Payment channel, online/offline, whether they have their own Mini Program/APP | Merchant number, AppKey (may not be asked during the solution phase) |
| Generate integration code/parameter description | Confirmed scenario md, environment (sandbox/production), language/framework | Specific notifyUrl address |
| Joint debugging troubleshooting | Environment, interface name or catalog id, complete error code/original error text, whether callback was received | Order number (necessary when checking orders) |
| Script/tool execution | AppKey, private key path, merchant number, business order number, etc. (see scripts/README.md);must first pass python scripts/tools/check_python_env.py |
— |
- When collecting, use a table or numbered list,do not ask more than 5 at a time; remind them not to paste complete private keys/card numbers in the chat for sensitive information. When Hanglv Yida is involved, additionally do not request or receive passenger information, contact phone numbers, payment accounts, passwords, or airline B2B accounts (see
references/产品能力/航旅易达/航旅易达.md"Environment and Security Constraints").
④ Confirmation before execution
- The operations about to be executed include:curl to fetch documentation、Output complete code、Run scripts/、Provide production environment configuration recommendations etc., before execution state in one sentence what will be done.
- Run
scripts/Before runningpython scripts/tools/check_python_env.py, you must first executescripts/requirements.txt,must notcontinue executing other scripts. - Example: "I will fetch the unified order online documentation based on the mini-program payment scenario and organize the required parameter table, and continue after confirmation?"
- Involvingproduction environment、real fund operations(payment, refund, withdrawal, split settlement, settlement),additionally warn of risks: recommend sandbox first, write operations require idempotency and order query, production keys must not be leaked.Hanglv Yida has no sandbox, so "recommend sandbox first" does not apply, and you must directly follow production secondary confirmation.
- Execute only after the merchant confirms again; if only a plan is wanted and not code, the execution scope is limited to documentation and steps, and no runnable keys are generated nor production called.
Strong constraints for production environment calls (cannot be skipped): any pointing toproduction environmentactual interface call (including running
scripts/direct connection to the production gateway, write operations such as order placement/refund/withdrawal/split settlement/settlement initiated with production keys, and any request that will cause real funds or real data changes), on the basis of having completed the above ④ confirmation,must separately initiate one explicit secondary confirmation to the merchant, and clearly inform: target environment=production, operation type, affected fund/order scope, irreversible risks.Only when the merchant explicitly replies with agreement(e.g. "confirm execution in production") may it be initiated; if the merchant has not confirmed, the reply is ambiguous, or they ask to see it first, then in all caseshandle by default as sandbox/demo or only output the plan and commands, and must not call production without authorization.
Correspondence between dialogue stages and skill actions
商户开口
→ ① 明确需求(产品决策 / 关键词 / 澄清模板 / 排障初判)
→ ② 征得同意(提出下一步,等待确认)
→ ③ 收集信息(场景已锁定后的环境与参数)
→ ④ 执行前确认(拉文档 / 写代码 / 跑脚本)
→ 按下方「技术执行顺序」落地
→ 按「标准输出模板」回复
| Stage | Readable reference | Forbidden |
|---|---|---|
| ① | 产品决策.md Section 4 (scenario keyword matching), Section 5 (standard clarification template) |
Output code, curl business gateway, full parameter list |
| ② | Propose in natural language | Assume the user agrees and continue |
| ③ | "Integration steps" in the scenario md | If scenario is missing, ask for AppKey/private key |
| ④ | Documentation loading protocol,scripts/README.md |
Run scripts or call production without confirmation |
General technical discipline (to be followed during execution)
- Before write operations (payment, refund, split settlement, withdrawal, etc.), confirm: environment (sandbox/production), merchant number, AppKey, notifyUrl source.
- Before initiating any actual call to the production environment, explicit secondary confirmation by the merchant is required(see Customer Discipline ④ "Strong constraints for production environment calls"); if unconfirmed, you must not directly connect to production, and only output the plan/commands or handle as sandbox.
account(account),balance(payout/payment disbursement) grouped fund disbursement interfaces (such as withdrawal/rest/v1.0/account/withdraw/order, payout/rest/v1.0/balance/transfer_send)must use the CFCA certificatefor signing and configure an IP whitelist; calling directly without configuring the certificate will result in an error. When involving disbursement integration/troubleshooting, first readreferences/平台文档/接入准备/密钥管理/CFCA证书介绍.md。- Transaction final state = callback + order query dual-channel confirmation, not based on the frontend page.
- Write operations use a business unique order number; callback handling must be idempotent; for timeout/unknown, first query the status before deciding whether to retry.
- Error codes have two layers: first check the interface's own business code, then check the platform common code (see
references/平台文档/开始对接/平台错误码说明.md)。 - It is forbidden to output private keys, complete secret keys, or complete card numbers/ID numbers.
- Interface fields are subject to the online
doc_mdas authoritative;curlin the skillmainly refers to pulling documents, business gateway calls must use YOP signature, and cannot be successfully called with bare curl.
Code-writing task routing (whether to use the SDK)
Before writing integration code, first confirm whether the customeruses the official SDK; if not declared, list it as "to be confirmed" and ask,do not defaultto choosing a path.
Layer description (to avoid confusion with the step 4 table):
- L1 / L2 / L2': mutually exclusive paths, determining "how to send requests" — self-developed signature/encryption-decryption (L1) or official SDK (L2 Java / L2' other languages).
- L3:Shared by all code-writing tasks, not a mutually exclusive branch; refers to the online interface
doc_md(fields, error codes, example code skeleton), handled uniformly in steps 5–7 of "Technical Execution Order" and in the "Document Loading Protocol".
使用官方 SDK?
├─ 是:
│ Java → SDK使用说明.md(L2)+ doc_md 调用骨架(L3)
│ 其他语言 → 平台SDK.md 定位仓库 README(L2')+ doc_md 参数表(L3)
└─ 否(语言无 SDK,或主动不引依赖/自研网关/合规限制):
平台文档/平台规范/安全认证/ 的请求签名协议.md、回调解密协议.md(L1)
实现签名/加密/回调解密 + doc_md 参数表(L3)+ scripts/ 本地验证
Java SDK version (before L2 code writing): before generating dependency coordinates, the latest stable version of yop-java-sdk must be resolved in real time; hardcoding or relying on memory is prohibited. Prefer python scripts/tools/resolve_java_sdk_version.py, or according to SDK使用说明.mdthe "Version Resolution Protocol" in central.sonatype.com / Solr(must sort=v desc)。do not use search.maven.org(index lags);do not use Solr queries without sort=v desc (which may mistakenly return old versions such as 4.2.2-jdk6on). The soft algorithm package version must match the main package.
Java SDK configuration (L2): only configure AppKey + merchant private key;do nothave the merchant configure the YeePay platform public key / SM2 platform certificate (the SDK has it built in and updates automatically; manual misconfiguration instead causes signature verification failure). When generating configuration, do not write yop_public_keyby default; when reviewing existing yop_sdk_config*.json , if this item is found, firstask the user why it is configured(such as historical compatibility, mixing with non-official SDKs, etc.), thensuggest that the user remove it themselves, and do not directly delete or modify the other party's configuration. See SDK使用说明.md §3 for details.
Technical execution order (after the merchant has confirmed the scenario and agreed to continue)
- Verify prerequisites: against
references/产品能力/产品决策.md, verify the confirmed solution and collection entity (standard/platform/service provider); if verification fails (the scenario or entity is still ambiguous) → return to customer-facing discipline ①② to continue clarification,do not proceed to subsequent steps。 - [Mandatory] Read the scenario md and common pitfalls: first locate the business domain according to the "Business Domain Routing" below (merchant onboarding/acquiring/refund/split settlement/payout/reconciliation/finance/travel-easy-access); for acquiring, then lock the specific scenario file according to the "Acquiring Scenario Index"; for finance, then lock the product file according to the "Finance Scenario Index"; for travel-easy-access, then lock the channel according to the "Channel Decision" in the scenario md;read completely
references/产品能力/<业务域>/<场景>.mdthe full text, in which the## 易错点section is required reading(and related documents referenced in that section, such asprePayTn唤起方式速查.md)。Do not enter step 5 (curl doc_md) or step 7 (generate code/parameter table) before completing this step。If it cannot be mapped to any business domain/scenario(the requirement exceeds the coverage scope or still has ambiguity) → use产品决策.mdTemplate 7 (exceeds product capability scope) to reply or return to customer-facing discipline ①② for clarification,do not fabricate scenario paths。 - For code-writing tasks: confirm SDK usage intention according to "Code-writing task routing",lock in one of L1 / L2 / L2'(L3 is not selected at this step, see steps 5–7).
- Read platform documentation according to path and task type(use
references/平台文档/platform-doc-manifest.yamlto locate topics; the table below is required reading, the rest as needed):
| Task characteristics | Required reading |
|---|---|
| L1 (do not use SDK) | 平台规范/安全认证/请求签名协议.md、回调解密协议.md |
| L2(Java SDK) | 开始对接/SDK使用说明.md(when errors occur, add Java-SDK报错说明.md) |
| L2' (other language SDK) | 工具与支持/开发工具/平台SDK.md to locate the repository README |
| Involves disbursement (account/balance groups) | 接入准备/密钥管理/CFCA证书介绍.md、开始对接/配置IP白名单.md |
| Involves callbacks | 平台规范/结果通知机制说明.md |
| Troubleshooting | references/troubleshooting.md、开始对接/平台错误码说明.md |
L3 (interface doc_md): the table above only covers L1/L2local platform documentation; L3 is online interface documentation, handled in step 5 when locating
doc_md, step 6 when curling and pulling, and step 7 when generating code; for discipline see "Document Loading Protocol" and "Example Code Section Discipline (L3)".
- In
references/产品能力/api-index.yamllocate interfacedoc_md(L3 starting point;Prerequisite: step 2 pitfalls have been read)。 - Before generating or verifying interface fields/error codes, the document loading protocol (curl doc_md) must be executed(L3 pull;Prerequisite: step 2 pitfalls have been read)。
- Generate code/parameter table based on doc_md, step 2 pitfalls, and the selected L1/L2 path (follow "Example Code Section Discipline (L3)"; parameter values must be consistent with the pitfalls; in case of conflict, the doc_md field definitions shall prevail, and the pitfalls constrain business selection and combination).
- When local verification is needed, after confirmation via ④firstrun
python scripts/tools/check_python_env.py(Python ≥3.10 and dependencies ready); if it does not pass, guide the user to upgrade Python /pip install -r scripts/requirements.txt,must notcontinue executing other scripts. After it passes, then usescripts/(seescripts/README.md)。 - Reply according to "Standard Output Template".
Document Loading Protocol (API-type tasks)
Interface specifications are obtained in real time via curl from the open platform online markdown real-time curl :
1. 在 api-index.yaml 按域+场景定位目标接口,取其 doc_md。
2. 拉取接口文档:
curl -sS "https://open.yeepay.com/docs-v3/api/<slug>.md"
slug:<method小写>_<path去掉开头/,/ 换 _>(保留 . 与 -)
例外:yos 等接口优先用 api-index 已实测的 doc_md;404/403 再试 options_ 前缀。
3. 涉及回调(**以接口 doc_md 为准**):
a. 在上一步拉取的 doc_md 中查找「结果通知」节(含通知编码与 notify 文档链接)。
b. 取该节中的通知编码 / notify 文档 URL,curl 拉取 notify 文档后再实现回调解析。
c. api-index 的 notify_spi 仅为索引提示;与 doc_md 不一致或缺失时,**以 doc_md 为准**,不得臆造 SPI。
4. 参数解读(**以拉取到的反参为准,禁止凭字段名或同类接口推断**):
a. 各参数的支持方式(取值范围、枚举、格式、业务含义)以该 API 内
该参数的**描述(description)**为准。
b. `是否必填` = **条件必填** 时,openapi.json 格式的接口须额外读取该参数的
`x-yop-api-param-condition` 字段获取必填条件;未读取前不得按「可选」处理,
也不得自行编造条件。
5. 场景 md 只提供流程与易错点;禁止仅凭它拼接口参数。
6. curl 失败/超时:提示检查网络;不得编造字段;停止字段级实现。
7. 回复中注明 doc_md「基本信息」中的 API ID 与「最后更新时间」。
Example Code Section Discipline (L3)
The "Example Code" section of doc_md is anautomatically generated all-parameter template(containing dirty placeholder values); the agent only takes the call skeleton(Client construction, request method, Content-Type).
Parameters MUST be re-filtered according to the required/conditional logic in the "Request Parameters" table,copying is prohibitedall addParameter and placeholder values.
The parameter's support mode is based on that parameter's description , which shall prevail;条件必填 For parameters, in openapi.json one must read x-yop-api-param-condition to get the required condition before deciding whether to pass it (see Article 4 of "Document Loading Protocol").
The human-readable page
https://open.yeepay.com/docs/products/<product>/api/<uri>is an SPA,curl cannot retrieve fields. doc_md section structure:基本信息、请求参数、请求示例、响应参数、响应示例、错误码, (when there is a callback)结果通知、示例代码。references/平台文档/is the local authoritative content,do not use curl。Hanglv Yida exception: flight ticket APIs are organized by channel (solution),not applicable
docs-v3/api/<slug>.mdderivation rules; reading order is mandatory: first curl "Product Introduction"intro_md(applicable scenarios) → (if any)config_mdchannel configuration instructions and guide the merchant to complete/confirm → then curl "API Invocation Guide"doc_md(API invocation order matrix) → before field-level implementation, curl the target API openapi.json (list seereferences/产品能力/航旅易达/渠道API清单.md). When the product introduction scenario does not match, the channel's APIs must not be applied; API contracts must not be derived from other channels; when curl fails, content must not be fabricated. Channel configuration: configuration usually requires actions on the merchant backend, operations, account manager, or airline side, and the Agent cannot complete them on behalf of others. No sandbox: Hanglv Yida APIs are all called in the production environment, and must not be guided by "sandbox first"; actual calls require secondary production confirmation. Sensitive information: do not request or receive passenger information, contact phone numbers, payment accounts, passwords, or airline B2B accounts from the Agent; always use placeholders in examples. Invoicing: flight ticket reimbursement voucher/invoicing requests are usually directed to the electronic itinerary API; do not handle them as a general value-added tax invoice product (see scenario md "Additional Capability Description").
Business domain routing
| User intent (keywords) | Scenario catalog | catalog grouping |
|---|---|---|
| network access/application submission/onboarding/sub-merchant onboarding/merchant information change/unfreeze | references/产品能力/入网/入网.md |
merchant-netin |
| real-name verification/account opening intention confirmation/verification after merchant filing | references/产品能力/入网/实名认证.md |
merchant-netin |
| order placement/mini program/APP/H5/active scan/passive scan/order query | references/产品能力/收单/ |
acquiring |
| refund/refund query | references/产品能力/退款/退款.md |
refund |
| split settlement/split settlement query/fund return/payee | references/产品能力/分账/ |
profit-sharing |
| settlement/withdrawal/withdrawal card | references/产品能力/出款/ |
payout |
| reconciliation/bill download/discrepancy handling | references/产品能力/对账/ |
reconciliation |
| loan disbursement/corporate quick payment/joint loan/order payment/credit card repayment/cross-bank repayment/agreement payment/direct debit/sign-and-bind card/one-click card binding/legacy signing/batch payment | references/产品能力/金融/ |
financial |
| flight ticket/ticketing/refund/reschedule/cabin and price verification/NDC/Hanglv Yida/airline integration/electronic itinerary/flight ticket invoicing | references/产品能力/航旅易达/航旅易达.md |
airline |
| signature verification failure/callback not received/go-live check | references/troubleshooting.md + references/平台文档/ |
(local) |
When the requirement is not covered by the above table, use 产品决策.md Template 7 (beyond product capability scope) to reply, and do not fabricate a solution.
Acquiring scenario index
| Scenario | Scenario file |
|---|---|
| Browser H5 payment | references/产品能力/收单/浏览器H5支付.md |
| Mini program payment | references/产品能力/收单/小程序支付.md |
| APP payment (using YeePay mini program) | references/产品能力/收单/APP支付(使用易宝小程序).md |
| APP payment (using customer mini program) | references/产品能力/收单/APP支付(使用客户小程序).md |
| H5 + official account payment within WeChat | references/产品能力/收单/微信内H5+公众号支付.md |
| Passive scan payment | references/产品能力/收单/被扫支付.md |
| Active scan payment (standalone code - online PC) | references/产品能力/收单/主扫支付(独立码-线上PC).md |
| Active scan payment (aggregate code) | references/产品能力/收单/主扫支付(聚合码).md |
| prePayTn invocation method quick reference (cross-scenario) | references/产品能力/收单/prePayTn唤起方式速查.md |
Financial scenario index
Financial domain oriented tolicensed financial institutions(banks, consumer finance, auto finance, financial leasing, insurance, funds, trusts, microcredit, factoring, etc.). For selection, first follow references/产品能力/产品决策.md"II-II. Financial Industry Decision Tree" according tothe direction of funds, and when requirements are unclear useTemplate 8(withholding direction) orTemplate 9(lending model) to clarify.
| Scenario | Scenario File |
|---|---|
| Lending (order payment corporate quick payment / joint loan) | references/产品能力/金融/放款.md |
| Credit card interbank repayment (card center perspective) | references/产品能力/金融/信用卡还款.md |
| Agreement payment (contract signing and card binding / one-click card binding / existing contract signing / withholding / batch payment) | references/产品能力/金融/协议支付.md |
| NetsUnion one-click card binding supported banks quick reference (cross-scenario, load on demand) | references/产品能力/金融/网联一键绑卡支持银行.md |
Financial domain hard constraints (the "pitfalls" section of the corresponding scenario md must have been read before generating parameters/code):
- Agreement payment 1.0 and 2.0 are two separate sets of interfaces: order placement and query must be paired (1.0
cnppay-agreement-pay-request↔cnppay-query;2.0financial-order-pay-request↔financial-order-pay-query), cross-use will result in orders not being found. - Agreement payment ≠ acquiring: bank card withholding actively initiated by the merchant goes through the financial domain; active payment by the user present goes through the acquiring domain; they are not interchangeable.
- The lending payment card/collection card cannot be reversed:
remitCardInfo(payer = fund provider) under the order payment business, onlyCORPORATE;receiverCardInfo(payee = borrower) supportsDEBIT/CORPORATE。 - Products are enabled at the tertiary product level by bank: lending, agreement payment quick repayment, and credit card repayment all require clarifying the bank first; lending additionally requires completingcorporate account filing。
- Contract signing relationship consistency: when deducting with
bindIdifuserType/userNois submitted, it must match what was used at card binding; if no user identifier is submitted, it must be separately communicated and configured with YeePay.
Tool scripts (local, Python ≥3.10)
| Purpose | Script |
|---|---|
| Environment check (mandatory before running any script) | scripts/tools/check_python_env.py |
| RSA joint debugging (keys/order query/refund/callback/response signature verification) | scripts/rsa/; response signature verification scripts/common/response_verify.py |
| National cryptographic SM2 (keys/signature/callback/platform certificate/response signature verification) | scripts/sm/; cross-algorithm tools scripts/tools/(vector verification, offline response signature verification) |
Before running any script, customer-facing disciplines ②③④ must be completed, andfirstexecute
check_python_env.py; for joint debugging only, production uses the merchant's own system. Seescripts/README.md。
Standard Output Templates
The following templates arestructural references rather than mandatory forms: choose according to the stage of the conversation; empty sections may be trimmed and subsections merged. When requirements are already clear and the "fast track" is taken, A/B may be skipped and C (integration implementation) used directly; when the user explicitly says "only code/parameters", C may be simplified to "key pitfalls + interfaces + implementation steps + code + risks and items to be confirmed", but it must still retain
## 关键易错点(from the scenario md, cannot be omitted)、API ID/last update time(from the doc_md of curl) andenvironment/production secondary confirmationprompts.
A. First consultation / scenario not yet determined (corresponds to ①②)
## 我的理解
(用商户语言复述需求)
## 初步判断
(推荐方向 + 简短原因,不涉及接口参数)
## 需要您确认的场景
(引用产品决策澄清模板中的问题,或 2~4 个选择题)
## 确认后我可以帮您
(列出 1~2 项可选下一步,等待用户同意)
B. Solution confirmed, code not yet written (corresponds to ③)
## 为您匹配的方案
(场景名称 + 对应场景 md)
## 接入概览
(3~5 步业务流程,商户能看懂)
## 开通产品与前置条件
(若适用)
## 继续前需要您提供
(逐项列出,标注必填/选填)
## 您确认后我将
(拉文档 / 整理参数表 / 示例代码 — 须用户同意才做)
C. Integration implementation (after ④)
## 场景
## 关键易错点(已从场景 md 核对)
(逐条列出场景 md「## 易错点」中与本次实现相关的条目,可用勾选形式标注已落实)
## 必读规则(平台文档)
## 接口(含 API ID 与最后更新时间)
## 实现步骤
## 风险与约束(幂等/回调/查单/环境)
## 待确认(环境/是否使用SDK/支付方式/参数来源)
D. Troubleshooting Conclusion
## 现象
## 已排除
## 最可能原因(按优先级)
## 建议操作(先查后重试)
## 需补充的信息
## 如需我进一步查文档或脚本验证
(说明将做什么,等待同意)
Directory Description
Path of this skill package:skills/yeepay-payment-integration/(in the repository yeepay-skills ).
../../ 仓库根(yeepay-skills)
README.md / CHANGELOG.md / LICENSE.md
SKILL.md 本文件,唯一入口(面客纪律 + 技术执行)
scripts/ Python 联调工具(仅本地,详见 scripts/README.md)
validate_docs.py 发版守门(死链/版本一致/测试向量校验)
common/ 跨算法共用库
python_version.py Python 版本校验(≥3.10)
response_verify.py 应答验签(RSA/SM2)
url_encoding.py 签名一次编码 / HTTP 二次编码
yop_headers.py YOP 标准头
yop_content_type.py Content-Type 规范
yop_http.py HTTP 报文组装
yop_gateway.py 生产 yos / 沙箱 sandbox 网关
yop_multipart.py multipart 签名
yop_payload.py 请求体编解码
rsa/ sm/ RSA / 国密 SM2 密钥、客户端、查单/回调、测试向量
tools/ 跨算法 CLI:环境校验、向量校验、离线应答验签、Java SDK 版本查询
references/
troubleshooting.md 各业务域排障汇总
平台文档/ 本地权威(约 30 篇)
platform-doc-manifest.yaml 平台规则导航索引(topics 定位必读文档)
接入准备/ 快速接入、应用管理、密钥管理(CFCA/RSA/SM)
开始对接/ SDK、沙箱、IP 白名单、错误码、Java SDK 报错
平台规范/ 上线检查、回调网络、结果通知机制/查询重发
安全认证/ 鉴权/加密/签名/回调解密/结果通知 + 请求签名协议(含测试向量)
工具与支持/ 常见问题、最佳实践(文件下载)、开发工具(SDK/密钥/MCP/诊断)
产品能力/
产品决策.md 选型、关键词、澄清模板、超范围回复
api-index.yaml API curl 清单(doc_md / path / method / api_id)
入网/ 收单/ 退款/ 分账/ 出款/ 对账/ 场景文档(流程+易错点+前端示例+引用)
金融/ 放款、信用卡还款、协议支付 + 一键绑卡支持银行速查
航旅易达/ 机票场景文档(渠道决策+易错点)与渠道API清单(openapi.json 索引)