#carrot_support

1 messages · Page 1 of 1 (latest)

undone shellBOT
short kite
#

Good question. Checking in to this and will get back to you. I don't think Stripe would impose that limit

keen lake
#

Thank you!

short kite
#

Still having trouble finding an answer here. Will consult my colleagues and get back to you

#

I found this article which says to reach out to Stripe support after they have failed setup three times, that sounds like it is a Stripe imposed limit, though I am still unclear if simply setting up another source would also be a way to address it. https://support.stripe.com/questions/verify-a-new-ach-direct-debit-customer-using-micro-deposits

keen lake
#

Ty ty - yes this is the documentation I initially found that led me here since it's not super clear whether or not manually reaching out to Stripe Support is the only way to bypass. I'll wait to hear back on what you find but definitely appreciate you digging this up!

rose swan
#

👋 no you should not be locked out of future attempts if you create a new Source, but the microdeposits for the new Source will be different.

keen lake
#

Ah okay - thanks so much. That's super helpful. One final on the micro-deposits, if I may:We've seen a few occurrences lately where the customer reports only seeing a single microdeposit amount (rather than the usual two)

#

Would there be any known reason for this? We don't set them up as PaymentIntents so I don't believe there should only be a single one

rose swan
#

Hmm I'm not 100% sure but I think we have switched over to the single descriptor code microdeposit as much as possible, regardless of which version of ACH. But really this will be a better question to confirm with our Support team since it isn't really about the API and we don't know that much about it here

keen lake
#

Ah okay gotcha. I have a support request out to them now so hopefully will hear back soon. Very much appreciate your help here!