#manic-ach-instutions
tall nexus
hi there
lament forge
@tall nexus we don't have a list of such institutions today
I'd recommend raising that to our support team and they can help document this and share information we have available: https://support.stripe.com/contact
tall nexus
sounds good. do you have an idea of how it compares to the number of institutions plaid supports
lament forge
I do not sorry
tall nexus
also curious if you can use payment sources collected using plaid with the payments intents API or if it's only with payment methods collected with the stripe element
tall nexus
I do not sorry
no worries
lament forge
The Plaid ones work fine with PaymentIntents but you will need to create a Mandate for those
but we have a compatibility layer so that legacy BankAccount objects ba_123 just work via the PaymentMethod API too
tall nexus
would a customer need to authorize the mandate explicitly for those existing sources or can we just auto create one? it seemed like I was able to programmatically just create one without customer consent while testing but not sure if that applies to production
lament forge
well you can create one without the customer consent, but that defeats the goal of the mandate and you'd be breaking NACHA's rules basically
if you get disputes you can't say "well I have a mandate that proves this customer consented" if you didn't ask them 🙂
tall nexus
yeah i'm just wondering what the migration path is, because for the payment_sources we already have they will have authorized our usage of them just not with this particular "mandate" entity
so seems weird that we have to reauthorize to work with this new API
lament forge
gotcha for legacy accounts that's different
so yeah in that case you'd do this without asking based on when they agreed upon this mandate, such as their first payment and such and that should be fine
tall nexus
okay so the timestamp should be when they originally authorized the source?