Allinpay SYB Acquiring Integration Assistant

Problem

When integrating Allinpay SYB, engineers often need to switch between choosing request classes, generating Java examples, checking response fields, and landing a Maven project. If an entry-level assistant directly generates code without routing, it can easily produce wrong Request construction patterns, miss client() initialization, blur signing and verification boundaries, or handle callbacks and idempotency inconsistently. This skill keeps the entry layer focused on scenario triage and routing, so field details and code generation are not mixed together.

How It Works

• Route by task stage: determine whether the request concerns order creation, query, refund, callback, file handling, or front-end redirect before choosing a submodule.
• Protocol and security capabilities: route signing, verification, asynchronous notification, idempotency, credential boundaries, and runtime constraints to allinpay-syb-pay-shared-base.
• API and code conventions: route request-class selection, Java example generation, and project scaffolding to allinpay-syb-sdk-unified.
• Required source checkpoints: before answering, read the §0 main flow in MODULE.md, then hit §0 end “Before Writing Java / Demo”, §2 initialization + client(), and §3 skeleton; when Maven tickets or project landing are involved, also hit §5.
• Delivery modes: default to show_code_only for Java examples only; switch to scaffold_java_maven_demo only when the user explicitly asks to generate into a directory, modify pom, or run mvn package.
• Local field lookup: for fields and required attributes, first search local req-route.md, req-matrix-*, and response-side resp-matrix; do not conclude “unsupported / not recorded” before local retrieval is complete.

Scope and Caveats

This skill is useful for integration debugging, example generation, and scaffolding routing for Allinpay SYB acquiring. It does not expand large field tables and does not replace the authoritative field sources in the submodules. If the task is unrelated to SYB acquiring, signing callbacks, or Java SDK usage, it should not be treated as a general payment integration entry point.