#djordje_best-practices
austere furnaceBOT
👋 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/1488096302570143754
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
weary moat
hi there 👋 I'm not sure I fully understand your question - what is your current setup? do you save payment methods on both your platform and connected accounts?
what would be the scenario where you have two SetupIntents for one payment method?
hybrid musk
weary moat
yes sorry, it's possible to create a second mandate but my question is why, and in what scenario would you expect this to happen?
I'm guessing that your use case involves sharing payment methods across multiple connected accounts - is that correct?
if you could share more details about your use case I'll be better placed to help
hybrid musk
I'm guessing that your use case involves sharing payment methods across multiple connected accounts - is that correct? yes
If we have one pm which can work for multiple connected accounts then on UI we could use just one pm for multiple connected accounts , if we use 1 setupIntent -> 1 pm -> 1 mandate then we need to add additional fileds in db so that we can know with which pm we should do payment... but I'm not sure is that ok in context of changes that you plan to apply on 6 August this year (ACH v1 - ACH V2)
weary moat
I'd recommend following in the steps in the main guide for payment method sharing with Connect: https://docs.stripe.com/connect/direct-charges-multiple-accounts
in that approach, just one SetupIntent is used, on the platform when initially collecting the payment method
hybrid musk
one more question ... currently we have a lot of customers which having Bank accounts created by stripe BankService and Token (trough charge api) .. and my teammate was able to surround BankAccount with payment intent and do the payment ... will that be possible after 6 August ? ... my teammate says we don't use chargeApi now but paymentIntent ... but I still see bankAccount account on his picture .. and what I understtod from stripe email is that we need to replace ba_... acounts with pm_...
weary moat
when you say "surround BankAccount with payment intent", what does this mean specifically in your Stripe integration?
do you mean pass a legacy bank account ID (ba_123) to the payment_method parameter of the Create PaymentIntent API?
if so, then that will still be possible, but you'll need to collect mandate acknowldgement for the legacy objects
https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges?integration-path=payment-intent#mandate-acknowledgement
http://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges?integration-path=payment-intent#create-payment-intent
hybrid musk
when you say "surround BankAccount with payment intent", what does this mean specifically in your Stripe integration? yes ... He was able to make a payment now with a paymentIntent ..but I'm wondering will he be able to do that after 6 August ?
This is an email that we got from stripe:
weary moat
yes - it will still be possible to use legacy Bank Accounts to create payments using Payment Intents
but, there's a vital step, which the email you shared mentions:
"Backfill mandates and migrate previously collected bank account details using the Tokens API"
"Backfilling mandates" refers to this step: https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges?integration-path=payment-intent#mandate-acknowledgement
you'll have to ensure that there is a mandate for the bank account - but once there is a valida mandate, then you can continue charging them using the PaymentIntents API
hybrid musk
ChatGpt says .. that if we use my teammate approach .. so one payment method for multiple connected accounts ... then later we could have issues in these areas :
off_session payment
future usage
mandate validation
compliance
is that the true ?
weary moat
not once you complete the step that I referenced above, and ensure to create and complete a SetupIntent for the legacy bank accounts - that will allow you to set them up for future payments
hybrid musk
ok ... thanks