From 8f865c97a71fa71a70ea280b95f5fd5b26e260d6 Mon Sep 17 00:00:00 2001 From: moojttaba Date: Thu, 4 Jun 2026 12:54:04 +0330 Subject: [PATCH] =?UTF-8?q?docs:=20activity=20log=20=E2=80=94=20frontend?= =?UTF-8?q?=20v2.8.88=20(in-shell=20direct-transfer=20payment)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.8 (1M context) --- 09 - Audits/Activity Log.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/09 - Audits/Activity Log.md b/09 - Audits/Activity Log.md index 94f1e1d..fc35925 100644 --- a/09 - Audits/Activity Log.md +++ b/09 - Audits/Activity Log.md @@ -1239,4 +1239,23 @@ main list (+ no-results state). Unarchive already worked (archiveConversation --- +### 2026-06-04 — frontend v2.8.88 — in-shell direct-transfer payment (no wallet connection) + +Buyers can now pay a pending_payment request entirely inside the Mini App, with +NO web3 wallet connection — mirroring the web «انتقال مستقیم» rail. +TelegramPaymentView: resolves the selected offer (seller + amount) → +getPaymentOptions for chain/token → createDirectBalanceIntent (provider +amn.scanner, rail direct_balance, mode check) → shows a copyable derived deposit +address + exact amount + a strong "send only this token on this network" warning +→ «پرداخت کردم» calls checkDirectBalancePayment. +Edge cases (all surfaced): OVERPAYMENT accepted (backend delta>=expected → +paid); UNDERPAYMENT shows "received X of Y, send the rest" (paidDelta vs +expectedAmount); WRONG TOKEN — the check flow can't detect a foreign token, so a +prominent on-screen warning is shown (backend webhook rejects token/chain +mismatch). Wired from the request-detail pay CTA via a new openPaymentRequestId +shell overlay + BackButton. (Replaces the earlier "open web payment" hand-off.) +**Verification:** tsc + eslint clean. + +--- +