#nebojsa-plaid-save
1 messages · Page 1 of 1 (latest)
nebojsa-plaid-save
Hey @vast shuttle. If you use our legacy integration then you want https://stripe.com/docs/ach-deprecated#manually-collecting-and-verifying-bank-accounts
The goal is to have the capability of autopayments, just wanted to note
though we recommend using our own implementation/product instead really instead of Plaid
Your product features processing times of 2-4 days which is why Plaid is necessary in our case
I've been following that guide, but there is no mention of saving the payment method for future use
the link I gave you is literally about saving the bank account, that's exactly what you need
I don't understand what you call the 2-4 days delay or processing time
Ah, so let me elaborate. I understand that Stripe's PaymentIntents API when using the in-house ACH system can authorize payments instantly. However, the status of the payment intent after a customer makes a payment goes to payment_intent.processing for 2-4 days, no?
yes, which is exactly the same with Plaid
Do you have a reference for this handy?
a reference for what?
I'm trying to convince my employer to go Stripe only
But for some reason they believe that Plaid provides instant charge feedback
The main setback is providing users with a "successful payment" feedback, even with ACH payments
Which I'm still trying to wrap my brain around.
I mean I don't know what Plaid offers. But through Stripe they don't provide "instant feedback for a payment" it always is pending for a few days.
In Stripe's ACH implementation, after a user authenticates with their bank account and makes a payment, would this be an option? I'm not worried about the actual funds transfer taking days, just that they have instant feedback that their payment "went through"
Or is that 2-4 days processing time also the time it takes to receive feedback that the user has enough funds in their account etc.
yeah I worry there's a completely misunderstanding
what is instant is the bank account verification. That's unrelated to their payment at all.
Plaid offers instant verification, like you log into your bank account with your bank and prove you own it. We (Stripe) offer the same thing. Both products let you verify instantly, save bank account details for later, etc.
Yep, I'm clear on that
The reason for going with Plaid is their ability to verify the funds in a users' bank account instantly as well, we can provide instant feedback on payment success (or other status)
So just to be clear, with the bank account token I receive from Plaid and send over to Stripe, I have the ability to store it as a payment method tied to a customer object?
yes, with the link I shared earlier
also we support the same thing: you can look at the balance on a bank account too
that's exactly what the API your linked does
Okay, just final confirmation on this
When using bank accounts through Stripe:
- User gets instantly verified
- They make their payment
- The payment intent's status goes from "created" to "processing"
- After 2-4 days, the payment intent goes to "succeeded" or some other status
Is that correct?
yes
Okay, so the bank account token I receive from Stripe via Plaid can be used with the above linked endpoint to tie it to a customer
yes
yes
Okay, thank you so much