0060b16912
In-house Request Network checkout went fully end-to-end on dev today. A real 0.01 USDC payment flowed through wallet connect -> approve -> ERC20FeeProxy.transferFromWithReferenceAndFee -> RN webhook -> TransactionSafetyProvider -> Payment.status=completed -> page success state. Tx 0x494c77a29161b5100d8e0b1ac675f1822955d0bb3633ecdbfafb886f84f2f320. Docs: - New PRD: Wallet, Multichain, Confirmations, AML, Trezor (5 follow-ups, each sized for an independent contributor) - Updated PRD: Request Network In-House Checkout (phases 0..3 done, phase 4 partial, phases 5-6 not started) - Updated handoff: deployed versions, what is working end-to-end, follow-up tasks index Taskmaster: 5 new top-level tasks (#7..#11) covering ephemeral destination wallets, multichain proxy registry + USDC/USDT, runtime confirmation thresholds, optional seller-paid AML screening, and Trezor signing for admin actions. Tasks are scoped fine-grained so each is independent enough for kimi to pick up. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
36 lines
1006 B
Markdown
36 lines
1006 B
Markdown
---
|
|
taskmaster_id: "2.7"
|
|
status: "done"
|
|
priority: "medium"
|
|
depends_on: ["1", "2", "3", "4", "5", "6"]
|
|
parent_id: "2"
|
|
source: "taskmaster"
|
|
generated_at: "2026-05-28T11:49:27.076Z"
|
|
---
|
|
|
|
# 2.7 - Align documentation, API references, and runtime enums
|
|
|
|
- [x] 2.7 - Align documentation, API references, and runtime enums #taskmaster #priority/medium #status/done 🔼 🆔 tm-2-7 ⛔ tm-1 ⛔ tm-2 ⛔ tm-3 ⛔ tm-4 ⛔ tm-5 ⛔ tm-6
|
|
|
|
## Metadata
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Taskmaster ID | 2.7 |
|
|
| Status | done |
|
|
| Priority | medium |
|
|
| Dependencies | 1, 2, 3, 4, 5, 6 |
|
|
| Parent | 2 - Implement platform audit remediation plan |
|
|
|
|
## Description
|
|
|
|
Normalize disputed/payment/request status docs and implementation references after security behavior changes.
|
|
|
|
## Details
|
|
|
|
Resolve mismatch around absent dispute module, endpoint names, status enums, and action names across Data Models, API Reference, and Flows.
|
|
|
|
## Verification
|
|
|
|
Docs match implemented routes, models, enum values, and state transitions.
|