2.1 KiB
One Pipe System
This context captures the business language used by the admin system for orders, assets, finance operations, and operational batch tasks.
Language
Voucher attachment: A user-provided proof file attached to an order, refund, recharge, or operational task. Voucher attachments may contain any file type and a business record may hold multiple voucher attachment keys. Avoid: Voucher image, comma-separated voucher string
Voucher key list: The canonical representation of voucher attachment object-storage keys at the frontend and API submission boundary. Legacy single-key strings or comma-separated strings may be read and normalized for display, but new submissions use key lists. Avoid: Comma-separated voucher string
Batch import file: The structured data file that drives an asynchronous operational batch task. Unlike voucher attachments, a batch import file is constrained by the task's required template format. Avoid: Voucher, attachment
Operational batch task: An asynchronous admin task created from an uploaded batch import file and tracked through task status, counts, operator identity, and failure details. Avoid: Inline order operation, synchronous import
Operational remark: A note captured when an admin creates a financial or operational record. Operational remarks are retained for later review and are not edited after creation. Avoid: Editable comment, processing note
Recharge order: A C-side asset recharge order created when a user recharges an IoT card or device asset wallet. It is identified by recharge_order_no, is associated with resource_type and resource_id, and may be rejected while pending payment. Avoid: Agent recharge order
Rejected recharge order: A recharge order that an admin has rejected before payment because the recharge request should not proceed. Rejection is an irreversible terminal state and does not involve refunds. Avoid: Refunded recharge, closed recharge
Agent recharge order: A financial recharge record for an agent/shop wallet in the admin finance module. It uses a different API contract and status model from C-side recharge orders. Avoid: Recharge order