Hi everyone!
I just wanted to draw your attention to this issue which I created. It is about a feature in the Oisy Wallet that would be very much useful (I believe!). If you agree, I would appreciate it if we could push for implementation.
Kind regards,
Jose
opened 06:19PM - 05 Mar 26 UTC
### Is your feature request related to a problem?
The Send dialog currently onl… y has a "To" address field and amount. There is no way to specify:
1. A **memo** — needed for many dApps and services that use memos to identify deposits (e.g. exchanges, payment processors, canister-based services)
2. A **subaccount** — neither a source subaccount (for users who want to organize funds) nor a destination subaccount (for sending to ICRC-1 accounts with subaccounts)
This limits Oisy's usefulness for anything beyond simple peer-to-peer transfers.
### Describe the solution you'd like
Add optional fields to the Send UI:
- **Memo field** (bytes or numeric) — passed through to the ledger transfer call
- **Destination subaccount** — the ICRC-1 textual representation already encodes subaccounts (principal + checksum + subaccount), but an explicit field would improve UX for users who receive a subaccount separately
These fields could be collapsed under an "Advanced" section to keep the default experience clean.
### Additional context
- The ICRC-1 standard supports both `memo` and `subaccount` in transfers — this is about exposing them in the wallet UI
- Related: #2474 (multiple accounts / subaccount management)
- The NNS dapp already supports both memo and subaccount in its send flow
1 Like