#divyashaliniics_microdeposits

1 messages ยท Page 1 of 1 (latest)

abstract pewterBOT
#

๐Ÿ‘‹ 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.

nova acorn
#

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?

merry bane
#

Yeah sure

abstract pewterBOT
merry bane
#

cus_PmBdnqUsQeH1Bn - This is the customer ID

narrow cove
#

Hey! Taking over for my colleague. Let me catch up.

narrow cove
merry bane
#

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

dusky pasture
#

hi! I'm taking over this thread.

#

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

merry bane
#

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?

dusky pasture
#

can you share an ID that succeeded so I can see the difference?

merry bane
#

Sure

#

pm_1PJHInHdtz9jEBQSexJQKsVk

#

This is one of the payment method

dusky pasture
#

thanks! give me a few minutes to look into this.

merry bane
#

Sure

dusky pasture
#

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?

merry bane
#

yes I am sure

dusky pasture
#

that's odd... looking into this.

merry bane
#

Ok, let me know

dusky pasture
#

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)?

abstract pewterBOT
merry bane
#

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

white gyro
#

๐Ÿ‘‹ taking over for my colleague. Let me catch up.

abstract pewterBOT
#

divyashaliniics_microdeposits

merry bane
#

Are you there?

white gyro
#

sorry I'm still catching up

#

please give me a moment

merry bane
#

Sure

white gyro
#

sorry for keeping you waiting

merry bane
#

No problem

white gyro
#

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

merry bane
#

Yes, because as I attached a screenshot of my code of creating a setup intent

#

And using same code for every place

white gyro
#

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

abstract pewterBOT
merry bane
dusky pasture
#

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

merry bane
#

Ok, sure