Summary
UX improvements for the banking section (on-ramp + off-ramp) to be worked after the off-ramp PR (#2289) is merged.
Scope
1. Address autocomplete
The beneficiary address form in the off-ramp payout account dialog (and potentially the compliance step) currently uses free-text fields for street address, city, state, postal code.
Typical UX pattern:
- User selects country first (already implemented)
- User starts typing street address
- Autocomplete (e.g. Google Places API) suggests full verified addresses
- User selects a suggestion → all fields (street, city, state/subdivision, postal code) are populated at once
Why: prevents format errors (PO Box addresses, invalid postal codes, non-standard street formats), reduces friction, improves Bridge API success rate.
To analyze:
- Which autocomplete provider to use (Google Places, Mapbox, etc.)
- Where in the form flow to trigger it (after country selection, on street address field focus)
- Whether to populate all sub-fields or just the address string
- Cost / API key requirements
2. List pagination
Currently the banking section lists are hard-capped at the first page of Bridge results:
As spaces (and now individual members) accumulate more accounts and transfers over time, users will only see the first page with no way to load more.
To implement:
3. Easier use of provisioned payout addresses in proposals
Spaces that have registered payout bank accounts through the Banking tab should have a more friction-free way to reference those addresses when creating proposals. The exact solution is TBD — could be surfaced via existing proposal types, a new proposal type, or another integration point.
To analyze:
- How the current proposal flow handles payout destinations
- What integration approach best fits the existing UX (adapt existing proposals vs. introduce a new type vs. other)
Depends on
Summary
UX improvements for the banking section (on-ramp + off-ramp) to be worked after the off-ramp PR (#2289) is merged.
Scope
1. Address autocomplete
The beneficiary address form in the off-ramp payout account dialog (and potentially the compliance step) currently uses free-text fields for street address, city, state, postal code.
Typical UX pattern:
Why: prevents format errors (PO Box addresses, invalid postal codes, non-standard street formats), reduces friction, improves Bridge API success rate.
To analyze:
2. List pagination
Currently the banking section lists are hard-capped at the first page of Bridge results:
spaces/[spaceSlug]/banking/accounts) and personal (people/[personSlug]/banking/accounts, added in feat(banking): personal wallet — on-ramp/off-ramp (deposit & payout) for individual bank accounts #2381)spaces/[spaceSlug]/banking/transfers) and personal (people/[personSlug]/banking/transfers, added in feat(banking): personal wallet — on-ramp/off-ramp (deposit & payout) for individual bank accounts #2381)As spaces (and now individual members) accumulate more accounts and transfers over time, users will only see the first page with no way to load more.
To implement:
PaginationParams/PaginatedResponse<T>contract already used elsewhere in the banking routes — flagged again in feat(banking): personal wallet — on-ramp/off-ramp (deposit & payout) for individual bank accounts #2381's review (CodeRabbit) on the new personal accounts/transfers routes; deferred here rather than fixed one-off so the space and personal routes land on the same contract together3. Easier use of provisioned payout addresses in proposals
Spaces that have registered payout bank accounts through the Banking tab should have a more friction-free way to reference those addresses when creating proposals. The exact solution is TBD — could be surfaced via existing proposal types, a new proposal type, or another integration point.
To analyze:
Depends on