#Jeyamari
1 messages · Page 1 of 1 (latest)
Can you share the errored request id? req_xxx
req_i6SyYj0RGe0x87
i'll try another payment and share a fresh request_id now. Please hold.
req_hyqjx1mgzn1yNB
Attached a screen recording of the failure here
Hey can you give me the Payment Intent Id? pi_xxx
nvm here it is pi_2NR9Jow0Fchmbo4g0L5coGES
Can you clarify which Doc and flow you are following?
sure. Just a min
If you can share that URL and how to navigate to that screen, we can look closer
We use financial connections to receive ACH payments.
the problem is probably that you are not passing stripeAccount on the frontend
since you created that PaymentIntent on a connected account, you need to make sure to correctly pass stripeAccount when initialising stripe.js on the frontend page that confirms it
- We create a paymentintent for the customer
- Load the Stripe JS (collectBankAccountForPayment) using the payment intent client secret
- customer will complete the payment and we te the payment intent id
- We retrieve the intent and save the payment information
But, we have this implemented for all our customers and we don't face any issues with other customers.
Is this anything specific to the particular account?
not that I know of
my guess is you do not use Connect properly on the frontend and you are using the API key of the account perhaps instead of the stripeAccount header?
That shouldn't be the case as we have the integration for a long time now. We use intent confirmations for card and other paymenet methods as well. The ACH pm was recently moved over financial connections, even then we are receiving successfull payments through this. This is the only case we face issue in.
add logging to your code and print the exact clientSecret you use on the frontend and share it here
this is happening in production. So we wont be able to add logger. However i tried a new payment and took the client secret from our server response which be used to load the JS.
The Client secret, intent and request Id are
pi_2NR9y8w0Fchmbo4g1fEFhgvr_secret_uPwCYToYHwJi8qMwsoNZVfTVz
pi_2NR9y8w0Fchmbo4g1fEFhgvr
req_cA4MN8zAUxvZOc - error request
yeah it's what I said already
"my guess is you do not use Connect properly on the frontend and you are using the API key of the account perhaps instead of the stripeAccount header?"
in your frontend, you are using a publishable key(pk_live_xxx) that you obtained from the connected account when you connected over OAuth, which is a deprecated way of authenticating in Connect
it will work if you use the pk_live_xxx of your platform(Zoho) account, and pass stripeAccount set to the ID of the connected account in question. https://stripe.com/docs/connect/authentication#adding-the-connected-account-id-to-a-client-side-application
Will check this with client team and get back. Thanks for your assistance.
it's because the client_secret value is scoped to the platform that creates the PaymentIntent