| 原通道ID | 通道名称 | 通道状态 | 投诉监控 | 商户号 | 证书序列号 | 私钥路径 | 同步时间 |
|---|---|---|---|---|---|---|---|
| 21 | 湖北鹏豪建筑劳务-1-1-1745352686 | 启用 | 1745352686 | 39F29910420B9EAFA6A78FF4AE42EC069F0F9DFB | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1745352686/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 20 | 东莞市贞琳文化-1-1-1112493371 | 启用 | 1112493371 | 4BA79F88C6C29D113824EF44CB5FDB0AC99F7B97 | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112493371/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 19 | 广州硕娅劳务有限公司-1-1-1112481447 | 启用 | 1112481447 | 72F518A1693791DC191E8D0D7BD2447B99EDA7C1 | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112481447/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 18 | 江西众瞬鹤科技-1-1-1112443560 | 启用 | 1112443560 | 55F59057C579FD79BE97B9A7569FB4F43521B23D | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112443560/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 17 | 武汉市炫岩烽网络科技-1-1-1112441007 | 启用 | 1112441007 | 70CD6E6CC6C0A46D49EC4F1897AA5EB0E1A6BD6F | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112441007/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 16 | 常德勤毓人力资源有限公司-1-1-1112374839 | 启用 | 1112374839 | 76321867D1081A886FB0CD7C59857DDC8D59599C | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112374839/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 15 | 广州延围商贸有限公司-1-1-1112327128 | 启用 | 1112327128 | 64B96E43929C20A078ED115EEF78EADCBB1690F6 | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112327128/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 14 | 天津麇韬电子商务有限公司-1-1-1112301197 | 启用 | 1112301197 | 1738AC1A3A8B163E62FAA3E9D68CF3CD0417A753 | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112301197/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 13 | 南京墨案科技有限公司-1-1-1112312909 | 启用 | 1112312909 | 6037D09339A5597D1C7221DA30E5C89604E5F24F | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112312909/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 12 | 荆州市畅万商贸有限公司-1-1-1745233922 | 启用 | 1745233922 | 61318EF385C154E51397FDDAB40E263CE9D0E10D | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1745233922/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 11 | 杭州扦足秀点客健康-1-1-1745239469 | 启用 | 1745239469 | 20E506BF8BBC7DA70268D7F3355F0A64BE517DF8 | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1745239469/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 10 | 广西清源市政工程有限公司-1-1-1745295276 | 启用 | 1745295276 | 76714F011CA7D703999B82ECC4DEE3F7751095BB | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1745295276/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 9 | 广州基系贸易有限公司-1-1-1745303431 | 启用 | 1745303431 | 59BA53008987479575D5F71B130B4CA01CF894E1 | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1745303431/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 8 | 深圳市麦馨达物业-3-3-1744925540 | 启用 | 1744925540 | 1C252FFBE30702FC7BE05B8759A9737D58EFA3D7 | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1744925540/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 6 | 重庆羽迅畅建筑工程有限公司-1-1-1745236321 | 启用 | 1745236321 | 61EC84BC87547E236D2BBD7A31EEAC5EC7598421 | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1745236321/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 5 | 东莞市鸿徊建材有限公司-1-1-1112337742 | 启用 | 1112337742 | 115AD99A22E80221B3A8F8A69B4609559FE5E344 | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112337742/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 4 | 琼海市覆仿欣商贸-3-3-1112320897 | 启用 | 1112320897 | 3DEB10B75654B90D59C838E13ABD2EC81D67F64D | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112320897/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 3 | 琼海市覆仿欣商贸-2-2-1112316038 | 启用 | 1112316038 | 3B27ECC6CB4468893CE622D1C4F93439BC272938 | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112316038/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 2 | 琼海市覆仿欣商贸-1-1-1112261461 | 启用 | 1112261461 | 728CAACAB32A185D16F2E0CF7DB20A641F4F060E | /www/wwwroot/ppay1.flytray.com/plugins/wxpayn/cert/1112261461/apiclient_key.pem | 2026-08-01 04:57:11 | |
| 1 | 快速复制 | 关闭/停用 |
商户号/证书序列号/私钥路径不完整时,投诉接口会自动跳过,不会报错。
|
空 | 空 | 空 | 2026-08-01 04:57:11 |
| 分账ID | 通道ID | 商户号 | 接收方 | 比例 | 触发价格 | 状态 | addtime | 是否已提醒 |
|---|---|---|---|---|---|---|---|---|
| 暂无符合价格规则且超过配置时间的待分账记录。 | ||||||||
| 时间 | 类型 | 业务键 | 标题 | 状态 | 返回 |
|---|---|---|---|---|---|
| 2026-06-02 09:50:30 | psreceiver_timeout | psreceiver_timeout_76 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:30 | psreceiver_timeout | psreceiver_timeout_75 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:30 | psreceiver_timeout | psreceiver_timeout_74 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:30 | psreceiver_timeout | psreceiver_timeout_69 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:30 | psreceiver_timeout | psreceiver_timeout_68 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:29 | psreceiver_timeout | psreceiver_timeout_66 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:29 | psreceiver_timeout | psreceiver_timeout_65 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:29 | psreceiver_timeout | psreceiver_timeout_64 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:29 | psreceiver_timeout | psreceiver_timeout_63 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:29 | psreceiver_timeout | psreceiver_timeout_61 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:29 | psreceiver_timeout | psreceiver_timeout_60 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:29 | psreceiver_timeout | psreceiver_timeout_59 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:28 | psreceiver_timeout | psreceiver_timeout_58 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:28 | psreceiver_timeout | psreceiver_timeout_57 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:28 | psreceiver_timeout | psreceiver_timeout_56 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:28 | psreceiver_timeout | psreceiver_timeout_55 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:28 | psreceiver_timeout | psreceiver_timeout_54 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:28 | psreceiver_timeout | psreceiver_timeout_53 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:27 | psreceiver_timeout | psreceiver_timeout_52 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 2026-06-02 09:50:27 | psreceiver_timeout | psreceiver_timeout_51 | 分账超时提醒 | 失败 | {"errcode":660026,"errmsg":"sending too many messages per minute"} |
| 时间 | 类型 | 状态 | 说明 |
|---|---|---|---|
| 2026-06-01 22:09:11 | cron | success | 监控执行成功 |
| 2026-06-01 22:08:43 | cron | success | 监控执行成功 |
| 2026-06-01 22:08:15 | cron | success | 监控执行成功 |
| 2026-06-01 22:07:47 | cron | success | 监控执行成功 |
| 2026-06-01 22:07:19 | cron | success | 监控执行成功 |
| 2026-06-01 22:06:51 | cron | success | 监控执行成功 |
| 2026-06-01 22:06:23 | cron | success | 监控执行成功 |
| 2026-06-01 22:05:55 | cron | success | 监控执行成功 |
| 2026-06-01 22:05:27 | cron | success | 监控执行成功 |
| 2026-06-01 22:04:59 | cron | success | 监控执行成功 |
| 2026-06-01 22:04:31 | cron | success | 监控执行成功 |
| 2026-06-01 22:04:03 | cron | success | 监控执行成功 |
| 2026-06-01 22:03:35 | cron | success | 监控执行成功 |
| 2026-06-01 22:03:07 | cron | success | 监控执行成功 |
| 2026-06-01 22:02:39 | cron | success | 监控执行成功 |
| 2026-06-01 22:02:11 | cron | success | 监控执行成功 |
| 2026-06-01 22:01:43 | cron | success | 监控执行成功 |
| 2026-06-01 22:01:15 | cron | success | 监控执行成功 |
| 2026-06-01 22:00:47 | cron | success | 监控执行成功 |
| 2026-06-01 22:00:19 | cron | success | 监控执行成功 |