#nitesh_api
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/1368935513876205588
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hey there! We have complete guides showing the server side aspects on this for Node.js, but it sounds like you've already worked through that part.
yes
but i don't think that the right way
please share details how to implement ACH in right way
i follow this doc but didn't understand
As for the front-end, we don't have first-party support for Angular, so for that you'll need to either build your own adapter layer, or leverage a community-maintained package like ngx-stripe ( https://github.com/richnologies/ngx-stripe )
i don't able to decide what to do on backend and frontend
This would be the guide to follow if you don't want to use Payment Element in the front end
what is Payment Element??
If you do want to use Payment Element, then you want to look at the "advanced integration" guides here
https://docs.stripe.com/payments/ach-direct-debit/accept-a-payment?web-or-mobile=web&payments-ui-type=elements&lang=node#web-collect-payment-details
what is Payment Element??
Payment Element is the prebuilt front end component to collect payment details securely in your client application, provided by Stripe.js: https://docs.stripe.com/payments/payment-element
is ther need of backend ??
Let's take a step back: what part of this are you having trouble with?
Yes, you need a backend to handle parts of this sequence. That is true for pretty most integration patterns, to varying degrees.
Are you trying to not have a backend component?
Just reset
If you just want to include a re-usable link to a Stripe-hosted surface for collecting payments rather than implementing this yourself, you can evaluate whether Payment Links could meet your needs: https://docs.stripe.com/payment-links
let me explain what i've done in backend and frontend
step 1
create setup intent 'us_bank_account'
step 2 ( frontend )
frontend load the card based on setup intent data
step 3
create bank account token using this API ( stripe.tokens.create )
step 4
Attach bank account to custome using this
stripe.customers.createSource(customerId, { source: tokenId }, { stripeAccount: connectedAccountId });
step 5
verify bank account
stripe.customers.verifySource
step 6
payment intent to cut the ammount
You're right, that is not following our latest recommended pattern. That seems like something you must have found referring to a third party example somewhere.
Are you specifically trying to collect the bank account without payment to use later? That is, you're not collecting any payment up front?
I ask because you refer to both setup intents and payment intents, and you should generally not be using both of these at once.
Then what will be the right way ??
I'm trying to help you narrow that down