EasyInvoice - Payee destination management page

[MantisClone]

Problem

Payees need a frontend interface to connect their wallet and claim their destination preferences.

Proposed Solution

Create a "Claim Destination" flow as a standalone page:

User Flow:

1. Payee connects wallet
2. Payee selects chain and currency for receiving payments
3. System generates destination ID from connected wallet + selections
4. Payee signs EIP-712 message to claim destination
5. System calls POST /v2/destinations/claim
6. 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 ]               │
└─────────────────────────────────────────────┘

Implementation Notes

Build as a standalone page within this repository (decided Feb 2, 2026).

• Not integrated with main 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 for now)

Rationale: Request Commerce's future is uncertain, and a standalone app would require too much boilerplate. Easy Invoice is the pragmatic choice.

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

• RequestNetwork/request-api#439 (POST /v2/destinations/claim endpoint)
• RequestNetwork/request-api#440 (GET /v2/destinations/{id} endpoint)

---

Migrated from RequestNetwork/request-secure-payment#34

[coderabbitai]

⚠️ Possible Duplicate Issue

• Frontend - Connect wallet + claim destination flow #204

🔗 Related PRs

#23 - feat: add direct payment page. [merged]
#176 - feat: request faucet tokens from app [merged]
#187 - feat: add payout confirmation dialogue component that showcases fees [merged]
#188 - feat: add payout confirmation component to direct payout [merged]
#194 - feat: pass connected payer wallet to the API to avoid having to approve all the time [merged]

---

Enable issue planning

_{To enable issue planning, add the following to your .coderabbit.yaml:}

issue_enrichment:
  planning:
    enabled: true

_{You can then request a plan by commenting @coderabbitai plan on any issue.}

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[MantisClone]

Instead of "Claim" prefer "Setup"

[MantisClone]

Closing in favor of building this in a new app (Vite + React) per Feb 5 Tech Daily decision. See request-dashboard repo for replacement issues. Kerry's claim flow components from #204 can be copied directly.