Complexity: 150 points
Summary
Map backend and Soroban error codes into clear frontend messages with actionable recovery guidance for users and contributors.
Tasks
- Define copy and UI patterns for top contract/backend error codes.
- Add a reusable error surface component for contract flows.
- Include retry/help actions where relevant.
- Add tests for at least the most common contract error states.
Acceptance Criteria
- Users see actionable error messages instead of raw technical payloads.
- Error UX is consistent across pay, refund, and setup flows.
- Recovery actions are obvious and usable.
Complexity: 150 points
Summary
Map backend and Soroban error codes into clear frontend messages with actionable recovery guidance for users and contributors.
Tasks
Acceptance Criteria