Joinpay Payment and Allocation Integration
Paste the following prompt into your AI chat to install this skill:
Please follow https://skillhub.cn/install/skillhub.md to install @user_2ebb4693/joinpay-payment-skill.
About this skill
Problem
When integrating Joinpay, the common blocker is not a single endpoint but mixing three protocols: aggregated payment on /tradeRt/*, secondary-merchant onboarding on /altFunds, and repeated allocation on /allocFunds. Each has different signing and parameter rules. Applying aggregated-payment p0_, q*, and hmac rules to secondary merchants, or applying secondary-merchant sign, sec_key, and data rules to aggregated payment, causes repeated integration failures. This skill groups the entry point, triage, and subdirectory navigation so the task is first classified by product line before following the relevant docs.
How It Works
- Bundled entry: read the root file, then enter
hj-payment-integration,hj-joinpay-aggregation-*,hj-joinpay-secondary-mch, orhj-joinpay-many-allocateby task. - Protocol boundary: aggregated payment uses
/tradeRt/*and concatenates values after sorting keys; secondary-merchant onboarding uses/altFundswithmethod,version,data,rand_str,sign, andsec_key; repeated allocation uses/allocFunds. - Key steps: use the capability matrix for a quick scope check, the error-handling matrix for callback failures, and the protocol/version matrix for endpoint confirmation. For a first Joinpay integration with an unclear path, start from
hj-payment-integration/SKILL.md. - Subskills: aggregated payment covers initialization, ordering, querying, closing, fund-query, and refund; secondary merchant covers onboarding, images, and agreement signing; repeated allocation covers allocation, completion, and allocation queries.
Boundary and Notes
The skill is for integration navigation and example code. It does not provide real merchant materials, key custody, or production configuration changes. If the target Agent only accepts a single Skill zip, the full zip containing this entry is usually required; if it supports multiple directories, subdirectories can be imported separately. When new subskills or shared rules appear, sync the full structure from the official repository Joinpay-Official/hj-payment-skills instead of copying isolated files, to avoid inconsistent directory indexes, dependencies, or shared rules.
Use Cases
- When debugging aggregated-payment orders, verify /tradeRt/* p0_, q*, and hmac concatenation instead of reusing secondary-merchant sign or sec_key.
- When onboarding secondary merchants, assemble /altFunds request fields such as method, version, data, rand_str, and sign correctly.
- When handling repeated allocation, keep /allocFunds signing separate from /tradeRt/* and confirm allocation, completion, and query entry points.
- When troubleshooting async notifications or idempotency, start from the protocol boundary matrix and locate shared signing, notification, or subskill docs.
Best For
- Backend engineers integrating a payment gateway who need to confirm the protocol boundary between aggregated payment and secondary-merchant onboarding before debugging.
- Engineers or product owners handling merchant onboarding who need to order agreement, image, and submission fields around /altFunds.
- Backend engineers working on allocation settlement who need to separate repeated allocation via /allocFunds from aggregated-payment refund flows.
- Engineers maintaining Agent skill bundles who need to import a full zip or subdirectories and keep shared signing and notification rules in sync.
Related Skills
A one-shot coding agent built on Claude Code CLI that runs non-interactively, supports a specified workdir, and can be monitored in the foreground or background.
Preview and confirm file sorting by extension, with recursive cleanup, ignore rules, and transactional rollback.
An engineering assistant for static HTML/CSS/JS pages, design-token extraction, IE8-compatible review, and structured delivery.
An engineering workflow for requirement analysis, scenario modeling, risk planning, quality gates, testing, and knowledge capture, with lightweight, standard, and full modes.