-
Notifications
You must be signed in to change notification settings - Fork 7
Closed as duplicate of#205
Description
Problem
Payees need a frontend interface to connect their wallet and claim their destination preferences.
Proposed Solution
Create a "Claim Destination" flow in the frontend:
User Flow:
- Payee connects wallet
- Payee selects chain and currency for receiving payments
- System generates destination ID from connected wallet + selections
- Payee signs EIP-712 message to claim destination
- System calls POST /v2/destinations/claim
- Display success with shareable destination ID
UI Concept:
┌─────────────────────────────────────────────┐
│ Claim Your Payment Destination │
├─────────────────────────────────────────────┤
│ Connected: 0x742d35...35Cc │
│ │
│ Chain: [Polygon ▼] │
│ Currency: [USDC ▼] │
│ │
│ Your Destination ID: │
│ ┌───────────────────────────────────────┐ │
│ │ polygon:0x742d35...35Cc:USDC [📋] │ │
│ └───────────────────────────────────────┘ │
│ │
│ [ Sign & Claim Destination ] │
└─────────────────────────────────────────────┘
Frontend Placement
Decision (Feb 2, 2026): Build as a standalone page within the Easy Invoice repository.
- Not integrated with Easy Invoice navigation
- Simple, focused interface for wallet connection and payment preferences
- Wallet connection state will be shared with Easy Invoice if both are open (acceptable tradeoff)
Considerations
- Only show chains/currencies that are supported
- Validate destination ID format before signing
- Handle wallet connection errors gracefully
- Consider showing claim status for existing destinations
Dependencies
- #439 (POST /v2/destinations/claim endpoint)
- #440 (GET /v2/destinations/{id} endpoint)
Parent Issue
Sub-task of api#434 (Destination Preference Epic)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
✅ Done