ACCUZ® Brand Guard™ Customer Verification API SDK 1.3.3
HTTP API v1 server flow

1. Validate trusted configuration before accepting taps. Every exact entry path selects
   one encodingVersionId and one server secret binding. Reject duplicate, ambiguous or
   reserved paths. Never trial credentials or let a browser select the API origin.
2. Capture the complete original HTTPS NFC URL before redirecting or rewriting it.
3. Atomically retain the original key/body/API origin, selected encoding and secret
   binding name, creation time and a snapshot of the product routing catalog.
4. Call the assigned API with the selected server-only bgci_ credential. Network or
   response-body transport interruption, 202, 429 and 503 may resume the same operation.
   Honor Retry-After. Never change the key, body, origin or encoding to resolve uncertainty.
5. A complete 200 body with an invalid envelope, identity, seal, required timestamp or
   encoding binding is terminal unconfirmed. Never retry the same bad receipt. Keep a
   generated safe support reference, discard raw tap/visitor data and show no pass.
   Validate acceptedAt and decidedAt independently. Bad optional SKU/path goes neutral
   without discarding a trustworthy verification decision or verifying again.
6. 401, 403, conflict and invalid-token configuration are terminal diagnostics, separate
   from NFC decisions. Use httpStatus + diagnosticCode + correlationId; never log tokens,
   raw tap URLs, response bodies containing private data, visitor IPs or key material.
7. Eligible valid receipts can select a trusted Item-specific path first. In SKU mode,
   look up the complete exact SKU. A catalog entry may be a legacy path string or a set
   of localized paths with a defaultLanguage. Negotiate the first page from weighted
   Accept-Language. Freeze the complete selected product's page family with this receipt.
8. Only that frozen family can read/acknowledge the session-bound opaque reference.
   Language switching preserves __bg_receipt; another product cannot read the receipt.
   Path mode/Item overrides stay authoritative. UID associations are read-only here and
   are established by a separate controlled business process, never by a replay or visitor.
9. Send original decidedAt/acceptedAt/checkedAt with timeZone (UTC by default). The browser
   formats the same instant in its page language. Localize all five decisions and every
   seal state separately; no opening reported is not a lifetime guarantee of integrity.
10. A same-key recovered result may be its first actual display. After rendering, the
    component stores a browser seen marker and POSTs same-origin /bg/presented. Lost result
    JSON is not presentation. Lost ACK can be confirmed idempotently on the next refresh.
11. Preserve original receipts/counts on refresh. Current ineligibility shows historical
    status with no new pass or product redirect. Presentation endpoints never verify a tap.
12. Each operation expires at its own createdAt + five minutes. Remove raw data and pending
    indexes independently. An expired operation cannot be resurrected by in-flight writes.
13. Region is optional and off by default. Use trusted ingress only; show estimates with
    clickable DB-IP and CC BY 4.0 attribution when present.
14. Start with single-entry configuration; advanced multi-entry is optional. Read old configurations and saved receipts without backfill.
    Old pending invalid-200 failures become terminal; never revive their raw request.

中文要点
每个可信精确入口固定对应编码和服务器凭据，不按碰卡网址参数轮试。
完整但不合格的 200 回执是终态未确认；传输中断与可恢复 HTTP 状态继续用原键。
SKU 多语言页组在操作开始时冻结，按入口 Accept-Language 选首落页，切语言保留引用。
单件专属路径优先；时间原值和次数不变，由浏览器按页面语言及默认 UTC 格式化。
只有真正呈现后才确认；每笔操作分别到期并清理，旧状态不能恢复秘密资料。
