Benjamin Nickolls

re-adding this to prioritisation as we evidently need it to control the number of projects that we're accepting...

@aminakazi can you drop the design that we got to for this?

W3 notes - finalising data collection - updating form

- review pr for wrap-up of final mods - announcement of change to eligibility criteria

+1 this is a good issue, I wonder whether we should spend a quarter working on 'risk, compliance and security' to prioritise work like this.

> Is Wise a possibility? Stripe has a nice flow for thishttps://stripe.com/docs/payments/bank-transfers And (related) for recurring ACH/Wire and Sepa https://stripe.com/docs/payments/ach-debit and https://stripe.com/docs/payments/sepa-debit (for EU)

- [x] kick off - [x] decide on technical approach (and document it here) - [x] decide on MVP to deliver for the sprint (and document it here)

I mainly created this issue to gather some ideas for improvements myself, but I noticed Alanna provided some in https://github.com/opencollective/opencollective/issues/4261

## Features for collectives - [x] include assignee, monthly limit and name in request - [x] allow collectives to freeze/unfreeze cards - [ ] allow collectives to delete virtual cards...

one teething problem that we have with the process: privacy is currnetly blocking card creation because we have a number of cards that are still unused. So we may need...