sean-mandate-onbehalfof

[forest spire]

We are receiving this error when attempting a Patment

[dire pasture]

@forest spire unfortunately we don't surface the account a Mandate was set up for today and it's something you have to cache on your end, or look at the original SetupIntent to figure that out

[forest spire]

So we store the Connected account after setting up the Mandate

And then use it later when creating Payment Intents

Does this error mean we are storing the wrong connected account for the mandate?

[dire pasture]

yes I think so

Either you store the wrong id, or you didn't put the same on that PaymentIntent

[forest spire]

And there is no way to see what the correct connected account is?

[dire pasture]

Do you have the exact failed request id req_123?

sean-mandate-onbehalfof

[forest spire]

Yea one second

req_U62D9SIPmjP8F2

mandate_1N46JCJmyu3lEqhgnMceyNL6

pm_1N46JAJmyu3lEqhgSY9wzijM

Is there a way to chnage the connected acconut on a Mandate or does the Mandate need to be collected again?

[dire pasture]

you need to collect it again

but okay look at that request. It's a PaymentIntent creation request and you forgot to pass on_behalf_of

so it's telling you "hey mandate X is for on_behalf_of acct_123 but the PaymentIntent has no on_behalf_of this can't work"

[forest spire]

Hmmm.....OK I did not realize that from the request

Let me check one of the vlid ones for another account and compare

OK yea, that makes sense. One of our succesful requests has has the on_behalf_of

There must be something in our code not loading that for all requests

OK, thanks for the help!