#divyashaliniics_microdeposits
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1243108966435651584
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Can you share the expected and actual behaviours in details, so that I can have a better understanding of the discrepancy that you're referring to?
Yeah sure
cus_PmBdnqUsQeH1Bn - This is the customer ID
Hey! Taking over for my colleague. Let me catch up.
Could you please share more details about the issue ?
Pending Verifications- pm_1PJHJiHdtz9jEBQSpF1DFhOM pm_1PJHBMHdtz9jEBQSY14qppdV pm_1PJH1XHdtz9jEBQS233dmCuA Success Verifications- pm_1PJHInHdtz9jEBQSexJQKsVk pm_1PJH91Hdtz9jEBQScRIo91ID pm_1PJH3xHdtz9jEBQSNnourH8T
These are few of payment methods added for ACH
Above 3 are the ones which are still in pending state
Below are the ones which got success
hi! I'm taking over this thread.
looking ath the first PM you shared, here's the related SetupIntent that is incomplete: https://dashboard.stripe.com/test/setup_intents/seti_1PJHJQHdtz9jEBQSdsSdVaDu
the status is status: "requires_action", so next step is to conform the SetupIntent on the frontend and let the user go though the actions needed
Ok, but I am creating the setup intent using same keys, just different values
So may I know why change in status for few of intents?
can you share an ID that succeeded so I can see the difference?
thanks! give me a few minutes to look into this.
Sure
one of the SetupIntent generated a microdeposit, and the other didn't. are you sur you used the exact same test values for the two requests?
yes I am sure
that's odd... looking into this.
Ok, let me know
generally you test microdeposits by pressing the "verify account manually" button in the FinancialConnections popup for it, so I'm guessing you clicked that button for some of the SetupIntent (which are now in requires_action) and for other's you didn't (the ones that succeeded)?
No no, I haven't clicked any button I am using setupIntents.create and passing the customerID and payment_method_types
Using this code from node
๐ taking over for my colleague. Let me catch up.
divyashaliniics_microdeposits
Are you there?
Sure
sorry for keeping you waiting
No problem
I'm honeslty unsure why this happened
the only difference I see is that the billing details don't match
that might be the reason why manual verification was needed on the second request
Yes, because as I attached a screenshot of my code of creating a setup intent
And using same code for every place
would you mind trying again but this time use the same billing information from the first one?
in all cases you should take into account all of the different scenarios
it is always possible to have a requires_action for manual microdeposit verifications and your code should handle it regardless
this is explained here https://docs.stripe.com/payments/ach-debit/set-up-payment?platform=web&payment-ui=direct-api&lang=node#web-verify-with-microdeposits
I have tried with same billing information but still getting the same
pm_1PJHBMHdtz9jEBQSY14qppdV - Pending
pm_1PJHInHdtz9jEBQSexJQKsVk - Success
yeah that's strange, not sure why this is happening. you can try asking Stripe support directly? they will have more time to investigate this issue: https://support.stripe.com/contact
Ok, sure