#naoki_ach-microdeposit

1 messages · Page 1 of 1 (latest)

autumn apexBOT
#

👋 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/1270790388956921988

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

crystal junco
#

Hi, can you share the request if where it worked as well?

To do this, provide an email in the payment_method_data.billing_details[email] field in the form of {any-prefix}+test_email@{any_domain} when you collect the payment method details.

I do not see payment_method_data.billing_details on this request, https://dashboard.stripe.com/test/logs/req_r4FgFRtpsBThb8. If you can share your other request, I'm happy to further look

prime dagger
#

not that request, as I wrote it in my first post, here is the request "Related Request ID(s)
req_jgYtEQ3wfmqkPv
"

#

interestingly, link_account_sessions API doesn't show up in logs

autumn apexBOT
prime dagger
#

the screenshot

Screenshot_2024-08-07_at_10.18.03_AM.png
#

I can see payment_method_data in payload in Chrome console

Screenshot_2024-08-07_at_10.19.06_AM.png
#

It was working on July 31st

#

I got this email

Screenshot_2024-08-07_at_10.22.38_AM.png
#

originally I thought something to do with email issue, but I believe I pass the email information correctly

crystal junco
#

I'm not aware of any changes on this. I assume you already activated the account and hence you saw that email

jade spear
#

naoki_ach-microdeposit

prime dagger
#

sorry what do you mean? I haven't verify the bank account yet, so that's why "verify deposit" link is there, right?

jade spear
#

that SetupIntent is verified though. Sorry I'm not really following what you're saying
Can you try again with just the confirmation and not doing anything else after and then sharing the exact SetupIntent?

prime dagger
#

req_EyKMIvOW6mlOMT

#

this setup_inetnts call

#

Also, I called req_j8ANOLjIUBi1uU but verification is pending

jade spear
#

perfect. So where exactly did you pass that exact email address you said you passed?

prime dagger
#

pm_1PlD71KJEVjDdF5f8qpWGWKF

jade spear
#

still looking, sorry there are a lot of other people in parallel

prime dagger
#

no problem, take your time

#

let me know if you need more information

jade spear
#

sorry still strugglign to follow what you're doing. I see you trying to detach that PAymentMethod that wasn't even attached yet

prime dagger
#

Please ignore that one

jade spear
#

Can you try and provide detailed information about your code and the steps you are following? I would expect to only ever see

  1. Create SetupIntent
  2. Confirm SetupIntent
    and nothing else.

Ah ok

prime dagger
#

it is not somedthing to do with my last SetupIntent

jade spear
#

hum but you gave me that pm_123 id right?

prime dagger
#

ah sorry, that is wrong one

jade spear
#

all good

#

Okay so first I tested on my own account and it works fine. Now let me compare with yours

prime dagger
#

sure

jade spear
#

Okay so can you share your code? How are you confirming that SetupIntent? Are you creating a PaymentMethod first? My requests look quite different from yours

prime dagger
#

just a sec

# 
        (await stripe?.collectBankAccountForSetup({
          clientSecret,
          params: {
            payment_method_type: 'us_bank_account',
            payment_method_data: {
              billing_details: {
                name: externalBrokerName,
                // The Stripe sends an email to the customer to verify the bank account.
                // We will use broker's email in legacy info passed in setupAutomatedDebit
                // but it is not implemented yet.
                // https://docs.stripe.com/payments/ach-debit/set-up-payment?platform=web&payment-ui=direct-api#send-transaction-emails-in-test-mode
                // https://docs.stripe.com/payments/ach-debit#mandate-and-microdeposit-emails
                email: legalEmail,
              },
            },
          },
          expand: ['payment_method'],
        })) || {};
#

legalEmail is ntakano+test_email@flexport.com

#

I follow the instruction as the doc is written

jade spear
#

ah you use that weird flow lol

#

is email: legalEmail, the test email?

prime dagger
#

yes

#

ummm but your doc says so 🤷‍♂️

jade spear
#

I follow the instruction as the doc is written
what is that doc? That's not what I recommend most people do, usually you just use PaymentElement + confirmSetup()

prime dagger
jade spear
#

Ack thanks. Sorry there are just so many docs, at some point I just know what the right way and am always baffled when our docs are so confusing 😅
It should be as simple as

  1. Create SetupIntent
  2. Render PaymentElement client-side with the client_secret
  3. Call confirmSetup()
prime dagger
#

yes

#

that what I'm doing basically, collectBankAccountForSetup is #2, #1 is done in servier, #3 is done by client

#

this is the only way we can do for ACH debit, right?

#

and it was working on July 31st

jade spear
#

What does "it was working" mean? What was working? Sending the email in Test mode? Sorry you lost me now.

Your code works fine, just it's not what I recommend that's all. But now I'm trying to figure out what's different between your calls and mine

prime dagger
#

" What was working? Sending the email in Test mode? " yes

#

So I should be able to get this email when I do microdeposit verification, but I cannot receive now

Screenshot_2024-08-07_at_11.06.07_AM.png
#

It may work on productin, but I want to make sure if it is working on test-mode too

jade spear
#

Gotcha, I didn't realize it was working fine a week or two ago. In that case I'd recommend contacting our support team so they can dig into why those emails aren't being sent

prime dagger
#

so you cannot identify the issue now?

jade spear
#

no I can not sorry

prime dagger
#

cool, thanks

jade spear
#

I thought you were asking how to make it work for the first time. Not to debug why you suddenly stopped getting emails which is likely due to some other internal reasons, sorry

prime dagger
#

ah that makes sence, yeah it was working a couple of weeks ago...

#

so discord is not the right palce to ask this type of bugs?

jade spear
#

It's fine to ask here, just you might be redirected if we don't know. I did confirm it works fine for me so it's specific to your account or email at least

prime dagger
#

k, thanks!

#

one more thing, did you try microdepoit verification?

jade spear
#

what do you mean by "try"?

prime dagger
#

you said " I did confirm it works fine" right? if so, did you follow micodeposit verification?

#

I'm talking about very specific flow only

#

I can receive other emails, but microdeposit flow's emails are not delivered to my test email address, that is the issue

#

but you follow the instruction, right?

jade spear
#

what does "I can receive other email" mean? I'm sorry we are talking way past each other. Sorry I know our products inside out so I mostly skim things. I feel like you're stuck with a real different question but we're been ping-pong-ing on something unrelated.

#

we don't really send emails in Test mode in 99% of cases

prime dagger
#

Again, did you follow microdeposit verification with APIs? Yes or no?

jade spear
#

no I didn't look at that, that was not your question

prime dagger
#

that is my question

#

because I shared the doc, right?

#

so you didn't read the doc link?

jade spear
#

I'm really sorry, you've lost me entirely. What do you need me to test? Just that I can pass 32/45 to verify micro-deposits? That emails land on my inbox? That you receive emails?

prime dagger
#

I cannot receive this email from your system in Test mode

#

that is the issue

#

Does it make sense to you?

#

first, do you know what microdepoit is?

jade spear
#

Hum sorry we're talking a bit past each other right now

#

Let's recenter: I am an experienced developer, I know our products inside out. I just don;'t follow your asks.

Are you asking: did I click on the link to test micro-deposits? If so no I did not. I never do those things, I know exatly how the product works and in the next_action there's the hosted_verification_url property https://docs.stripe.com/api/payment_intents/object#payment_intent_object-next_action-verify_with_microdeposits-hosted_verification_url which I then load to do the next step.

#

Early on you seemed to solely ask why you didn't get the email, so that's all I focused on

prime dagger
#

cool, then can you understand what this means?

Screenshot_2024-08-07_at_11.27.16_AM.png
jade spear
#

yes I know what that means

prime dagger
#

great, then I should be able to get this email when I follow microverification deposit flow in test-mode. But I cannot receive the email anymore today. I was able to receive the email on July 31st, but it is no longer. In that case, do you think this specific microdeposit flow on test-mode behavior is changed? (or regression bug?) that is my question.

jade spear
#

Gotcha, then I don't know, that's what I was saying earlier. The next step is to contact our support team to help you debug this directly

prime dagger
#

awesome, yeah, that makes sense

jade spear
#

👍

#

okay I also was asking internally in parallel and it does seem to be a recent bug we're investigating. So make sure to talk to support!

prime dagger
#

awesome! that helps what going on, yeah i will reach out support thanks!