Alipay Payment Integration Assistant

Problem

When integrating Alipay payments, the early blocker is often not the API call itself, but whether the required business fields are complete. Values such as amount, currency, merchant order ID, payment channel, callback target, and extension parameters can be scattered across requirements, backend config, and frontend code. Missing fields or inconsistent naming make debugging, joint testing, and production troubleshooting harder. alipay-payment-integration is closer to a front-end structuring step: it breaks the fields needed for the payment flow into steps and writes them into structured JSON, reducing ad hoc parameter assembly and communication gaps.

How It Works

According to the SKILL.md, the core behavior is to request fields step by step and then write the confirmed content into JSON step by step. In practice, you can provide the target payment integration scenario, the fields you already have, and the gaps you need to fill. It can then walk through items such as:

• Basic info: business name, environment, transaction type, amount, and currency.
• Order info: merchant order ID, external order ID, paying entity, and remarks.
• Channel info: Alipay-specific scenario parameters, callback or notification-related fields.
• Structured output: package the confirmed fields into a reusable JSON snippet for code or configuration.

Boundaries

This skill fits pre-integration field cleanup and parameter review, especially when requirements are incomplete or frontend/backend field definitions do not align. It should not replace Alipay official API documentation or business validation. Signature, asynchronous notification, refund, reconciliation, merchant permissions, and API version details still depend on the actual Alipay integration and your system checks.