#_api

1 messages ¡ Page 1 of 1 (latest)

dusk basinBOT
#

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

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

indigo badgerBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

  • _api, 21 hours ago, 42 messages
ashen temple
#

Hello, just so happens to be me here again! Can you send me the ID of the specific intent that you got that error with?

near torrent
#

oh Hello

#

setup intent?

ashen temple
#

Correct

near torrent
#

The id is seti_1Pg5s6GES5MQAgehibsijyld

#

Any insight?

ashen temple
#

Looking in to how you can address that error. So the situation is that the user saves a bank account to your platform and you want to charge payments to it while specifying your connected accounts as the merchant of record?

near torrent
#

yes

#

and the merchant account sometimes changes down the road

#

but the setup intent is still associated with the old merchant account

ashen temple
near torrent
#

ok im waiting

ashen temple
#

Okay, so going forward I think the easiest way to do this would be to have your initial setup intents not use on_behalf_of. If you don't use that, you can charge that PM on behalf of whichever connected account and we will automatically make the new mandate

#

For your existing saved payment methods you can make a new mandate with OBO set to different connected accounts. I am still figuring out the exact params to do that correctly.

near torrent
#

I rather not get rid of the mandate in order to not break existing processes

#

I basically transfer the money charged via payout to the account mentioned in the OBO

ashen temple
#

That isn't getting rid of the mandate

#

It would still be creating mandates automatically. The thing is that we can automatically use the mandate from your platform to make mandates for your connected accounts but we can't do that for two different connected accounts

near torrent
#

The setup intent is connected to the payment method and token, so creating a new setup intent is not an option, isn't it? Then a person will have to insert bank account details again manually (correct me if im wrong)

ashen temple
#

Okay so when you have a PM that has a mandate on behalf of one of your connected accounts, you can create offline mandates for the same account without the user inputting new details.

near torrent
#

the '{{ACCOUNT_HOLDER_NAME}}', '{{ROUTING_NUMBER}}' and '{{ACCOUNT_NUMBER}} details, where can I find them?

ashen temple
#

Sorry should have clarified. You wouldn't pass payment_method_data here, that param is for creating new payment methods. It is being used in that doc because no PM exists on the Stripe account at all yet. In your case you can just pass the existing pm_1234 ID of the payment method that you want to use:

  payment_method_types: ['us_bank_account'],
  customer: '{{CUSTOMER_ID}}',
  confirm: true,
  payment_method: 'pm_1234',
  mandate_data: {
    customer_acceptance: {
      type: 'offline',
      accepted_at: 1692821946,
    },
  },
});```
dusk basinBOT
near torrent
#

Do i need to stale the old setup intent?