#autiii43_connect-mcc-obo

1 messages · Page 1 of 1 (latest)

forest impBOT
#

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

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

gray fog
#

Yea using on behalf of should use the connected account context (including MCC) for set up, but you'll need to perform the payments that way too later

#

I assuming you're already doing on_behalf_of for the payments?

tight drift
#

yes we are

#

My question was what else will this affect? Since the customer is on my platform will it block that setup intent from being used for other accounts? Or will the on_behalf_of of the payment intent override it? The documentation for on_behalf_of on setup intents is pretty sparse – tried asking the AI but it also gave a slightly vague answer

tight stag
#

For cards, on_behalf_of doesn't make a difference, you should be able to use a saved card for any of your connected accounts as far as I am aware (I would recommend double checking this in test mode). OBO can effect this with bank debit payment methods where a specific "mandate" is created which gives permission for a specific account to charge the account, but cards don't have that.

forest impBOT
tight drift
#

Appreciate that heads up -- would have quite an impact if I did not know that. Will likely just retry the setup intent for cards then if we get transaction_not_allowed error codes which are almost always this use case for us

#

If there is anything else you can think of that would have an impact on our integration that might not be in generally available docs (or are that I cant find) it's all appreciated. Otherwise thank you!

raw sedge
#

Hi 👋

I'm stepping in as my colleagues have to go soon. Give me a sec to get caught up

#

Are you saying that the same request will work with the same card? My understanding of the transaction_not_allowed decline code (https://docs.stripe.com/declines/codes) is that the customer needs to contact their bank to understand what is not allowed.

For your integration I recommend you ask the Customer to retry with a different card.

tight drift
#

These are cards given by the government that are locked to an MCC code for childcare

#

The setup intent fails because our platforms MCC code is software, not childcare services

#

They can't use a different card because then the funds are still just locked to childcare on the MCC locked card.

raw sedge
#

Gotcha okay. But it sounds like specifying the Connected Account as the merchant of record will address this case. Have you attempted that?

tight drift
#

Yes that's what I was asking about was the on_behalf_of param of the setup intent and what implications that would have outside of just the mcc code on the setup intent

#

E.g i think i read that for ACH it changes the email that's sent from "ACH Debit authorized for <Platform>" to "ACH Debit authorized for <Connected Account>"

#

and the documentation is very sparse around on_behalf_of for setup intents, so was wondering if you guys had any tribal knowledge here that would be helpful

#

I think I got what I needed though, so thank you. If you have anything else, please let me know

raw sedge
tight drift
#

Thanks again!

raw sedge
#

Happy to shed what 💡 I can 🙂