修复错误购买报错的问题,修复接口返回虚流量启动错误的问题
All checks were successful
构建并部署到测试环境(无 SSH) / build-and-deploy (push) Successful in 7m48s
All checks were successful
构建并部署到测试环境(无 SSH) / build-and-deploy (push) Successful in 7m48s
This commit is contained in:
@@ -184,10 +184,17 @@ account
|
||||
|
||||
响应 data MUST 包含:`batch_no`、`package_code`、`success_count`、`failed_count`、`orders`、`failed_cards`。`orders` 每项 MUST 包含 `card_no`、`order_no`。`failed_cards` 每项 MUST 包含 `card_no`、`code`、`message`。
|
||||
|
||||
当任一卡购买失败时,外层 `code`/`msg` MUST 返回首条失败卡的错误码和原因,`data` MUST 保留批次明细;调用方 MUST 以 `success_count`、`failed_count`、`orders`、`failed_cards` 判断每张卡的处理结果,避免整批重试导致重复下单。
|
||||
|
||||
#### Scenario: 多卡部分成功
|
||||
|
||||
- **WHEN** 代理提交 3 张卡购买同一个套餐编码,其中 2 张成功、1 张失败
|
||||
- **THEN** 系统返回 `success_count=2`、`failed_count=1`、2 条订单号和 1 条失败卡原因
|
||||
- **THEN** 系统外层 `code` 和 `msg` 返回首条失败卡的错误码和原因,`data` 返回 `success_count=2`、`failed_count=1`、2 条订单号和 1 条失败卡原因
|
||||
|
||||
#### Scenario: 全部购买失败
|
||||
|
||||
- **WHEN** 代理提交的卡全部购买失败
|
||||
- **THEN** 系统外层 `code` 和 `msg` 返回首条失败卡的错误码和原因,`data.failed_cards` 返回全部失败明细
|
||||
|
||||
#### Scenario: 单套餐编码限制
|
||||
|
||||
|
||||
Reference in New Issue
Block a user