docs: sync from backend 896f17f - persist webhook confirmations

04 - Flows/Payment Flow - Scanner.md

@@ -6,6 +6,8 @@ created: 2026-05-30
 
 # Payment Flow — AMN Pay Scanner (In-House)
 
+> **Last updated:** 2026-05-31 — documented backend `2.6.81` confirmation persistence for scanner `confirmed` webhooks.
+
 End-to-end payment flow using the in-house AMN Pay Scanner, replacing the Request Network integration. The scanner is a separate microservice; the backend talks to it over an internal HTTP API.
 
 See also: [Scanner Architecture](../01%20-%20Architecture/Scanner%20Architecture.md), [Scanner API](../03%20-%20API%20Reference/Scanner%20API.md)
@@ -57,7 +59,7 @@ Authorization: Bearer <SCANNER_API_KEY>
   "tokenAddress":   "0x55d398326f99059ff775485246999027b3197955",
   "destination":    "0xSellerWalletAddress",
   "amount":         "10000000000000000000",
-  "callbackUrl":    "https://api.amn.gg/api/payment/scanner-callback",
+  "callbackUrl":    "https://api.amn.gg/api/payment/amn-scanner/webhook",
   "callbackSecret": "<per-intent HMAC secret stored in payment doc>",
   "confirmations":  12
 }
@@ -116,13 +118,14 @@ The scanner POSTs to `callbackUrl` with:
   "amount": "10000000000000000000",
   "token": "0x55d...",
   "chainId": 56,
+  "confirmations": 12,
   "status": "confirmed"
 }
 ```
 
 Header `X-AMN-Signature` = `HMAC-SHA256(body, callbackSecret)`.
 
-The backend verifies the signature, matches the intentId to a Payment record, and marks it paid.
+The backend verifies the signature, matches the `intentId` to a Payment record, and marks it paid. Backend `2.6.81+` treats scanner `status: "confirmed"` as final enough to run Transaction Safety Provider checks and persist `blockchain.confirmations`. The stored confirmation count comes from verifier evidence first, then the webhook payload, then the configured per-chain threshold fallback when the scanner has already waited for enough blocks but did not send a raw count.
 
 ### Step 6 — Backend acknowledges