What the documents look like
For after-sales questions in Refund-only disputes, this page examines FastGPT HTTP integrations. Separate accessory concerns, refund subjects and proposed remedies without treating willingness to wait as platform cancellation. The examples are hypothetical.
Constraints at the HTTP integrations step
This page invents support material: a buyer reports a missing accessory, the refund form does not identify whether it concerns the main item or accessory, and a later message expresses willingness to wait. The merchant proposes sending instructions only. No platform cancellation or dispatch evidence is supplied. Preserve item rows, speakers and actions in HTTP returns instead of merging objects within one parcel. Willingness is a current position, and instructions differ from physical parts. No real order, amount or liability finding is supplied.
Configuration and implementation checks
| Refund-matter HTTP | Invented subject/state | Inspection |
|---|---|---|
| Buyer account | Accessory missing | No main-item expansion |
| Application subject | Item row unclear | Keep row-level gap |
| Later message | Willing to wait | Not platform cancellation |
| Merchant proposal | Instructions only | Not physical-part replacement |
| Handling | Separate cancellation/refund/dispatch | Query executes none |
Documented conditions
| Documented item / implementation check | Condition |
|---|---|
Request address and method | The request address and method follow the external contract. |
Params and Headers | Inspect parameters, headers and authentication separately. |
| Body | Where a JSON body is used, validate its structure against the external contract. |
Variable references | Variables can come from global, system or upstream outputs. |
Debug identity fields | Test mode lacks chatId and responseChatItemId. |
Three common errors
- If an accessory concern becomes accepted refunds for all main items, compare application subject, product rows and explicit handling positions. A shared order expands no scope.
- If willingness to wait becomes platform cancellation, inspect the buyer wording and actual ticket state. A conversational position performs no platform action.
- If proposed instructions become completed replacement of missing parts, compare proposed object, required item and actual handoff. Sending information is no physical repair.
How to verify the setup
Check application matter, order rows and message scope under the real contract, separating authentication from business access without guessed parameters. Retain raw returns and answer sources. If only an order-level state returns, leave the specific application subject unresolved instead of pretending row evidence arrived. Added mapping changes scope alone; cancellation and replacement execution each need records. Refunds, cancellation, dispatch and order writes require authorized procedures and receipts. Querying organizes support evidence without accepting a remedy for either party or sending messages.
| Material context | Scope |
|---|---|
| Document types | Refund-Only Application, Proof of Shipment, Proof of Receipt and Appeal Materials |
| Candidate sources | Platform After-Sales Backend, Carrier Tracking, Customer Service Chat and Warehouse Outbound Records |
| Technical baseline | FastGPT v4.17.2 |