Order & delivery system status

This page reports the real state of the order, payment and file-delivery system. It is a status page, not a store: it takes no payment, creates no order and gives away no files. Prices shown anywhere on this site are indicative planning figures, not approved sale prices.

1 · What is built

2 · Products and shipped files

The catalogue below is compiled from the shipped manifest.json files. 4 products / 9 real files. Files are held inside the delivery Worker, not in the public static directory — they are released only after a valid download grant is checked.

Product IDVersionIndicative pricePrice statusFiles
fde-toolkit-2026 v1.0 $29 Indicative — not an approved sale price 3
rag-production-playbook v1.0 $19 Indicative — not an approved sale price 2
ai-landing-case-studies v1.0 $15 Indicative — not an approved sale price 2
prompt-pack-enterprise v1.1 $9 Indicative — not an approved sale price 2
Product IDFileBytesSHA-256 (prefix)
fde-toolkit-2026 toolkit.md 73,270 69d817d4cbb672ab…
fde-toolkit-2026 toolkit.html 98,597 362663863d7ef4a7…
fde-toolkit-2026 gpu-cost-model.csv 4,173 dabcbe06093a2f3f…
rag-production-playbook playbook.md 23,734 37373d1306ecdc50…
rag-production-playbook playbook.html 35,755 80ef88d0fd99c09f…
ai-landing-case-studies case-studies.md 30,859 d911066d22339e87…
ai-landing-case-studies case-studies.html 46,849 48c90b22b2d13569…
prompt-pack-enterprise prompt-pack.md 217,340 db67ea1163dc3134…
prompt-pack-enterprise prompt-pack.html 275,689 8171a6b1268162df…

3 · End-to-end test record (simulated payment)

84/84 checks passed (0 failed), generated 2026-11-10T16:00:56 UTC. Environment: local Node E2E against the real Worker modules (no payment provider contacted). Mode: test. Revenue recorded: 0. Every shipped file was downloaded through the authorised endpoint and compared byte-for-byte (SHA-256) against the source file on disk: 9/9 matched.

Covered: successful payment, payment failure, replayed callbacks, unknown product IDs, unauthorised downloads, expired links, repeat downloads, per-product file isolation, amount / product / currency checks, signature verification, refund revocation, and strict separation between test and live orders. All of this is simulated — no payment provider was contacted and no money changed hands.

Test groupPassedResult
A 商品目录与状态6/6PASS
B 未配置密钥时不得假装能买6/6PASS
C 错误商品 ID / 非法入参5/5PASS
D 正常支付 → 订单 → 授权 → 真实文件交付18/18PASS
E 重复下载可追溯3/3PASS
F 无权限 / 越权下载4/4PASS
G 不同商品 → 不同交付文件4/4PASS
H 支付失败3/3PASS
I 重复回调幂等4/4PASS
J 金额与商品一致性核对7/7PASS
K 退款撤销下载权限4/4PASS
L 过期下载链接2/2PASS
M test 与 live 不得串单3/3PASS
N 支付适配层可替换(本机模拟 Gumroad 回调,非真实收款)5/5PASS
O 全部交付文件逐个 sha256 验收10/10PASS

4 · What is not open yet, and why

Real checkout is deliberately disabled. The technical pipeline is finished and tested, but three items require the project owner personally:

  1. Complete the payment provider's identity verification (KYC) and bank-account binding in the owner's own name.
  2. Supply the real store product URLs and the webhook signing secret (a secret — never committed to a public repository).
  3. Approve the four final sale prices. The current figures are indicative only and have no approval record.

Until those three are done, order creation and payment callbacks return PROVIDER_NOT_CONFIGURED. That is the honest state, not a bug and not a teaser. We do not promise that opening payments will produce revenue.

5 · Live machine-readable status

The worker publishes a read-only status endpoint: https://fdenotes-contact.793527298.workers.dev/api/checkout/status. It lists the catalogue and whether each payment provider is configured. A provider showing configured: false means real payments are off — which is expected today. Test-mode order creation is disabled in production so that nobody can self-issue a grant and take the paid files for free.