#Rachel Bingham - Stripe Connect
1 messages · Page 1 of 1 (latest)
Thanks for the info. Checking in to this
Do you have a request ID for the second error?
For the first, it looks like the syntax for passing in the stripe_account parameter is different than for the other parameters
Trying to figure out the exact syntax for that for ruby
Thanks for the quick response.
The second error came from req_oisXu4EPpoAs8P
Thank you. Checking in to that as well
So for similar calls in ruby I am seeing this format
{INVOICE_ID},
{application_fee_amount: 100},
stripe_account: '{{CONNECTED_STRIPE_ACCOUNT_ID}}',
)```
Can you try passing empty curly braces for your ruby call? Something like
```Stripe::SetupIntent.confirm(
'seti_1KLqp6AZ75xSk2okhnvTocJG',
{},
stripe_account: 'acct_1Jji7zAZ75xSk2ok',
)```
Can't currently test myself but can come back to that in a moment
Checking it out now.
It worked for confirming the first issue 🙌
trying for moto error now...
Good to hear! Moto looks to be a different issue, just getting back to that one
Can you send me the snipped of code where you are confirming the payment intent and specifying moto?
I think I can tell how it is being set but that may be helpful
It looks like your account is not enabled for moto, otherwise the syntax that you had when you made req_oisXu4EPpoAs8P looks correct
You can reach out to our support to ask to be enabled for moto payments on your account https://support.stripe.com/?contact=true
Sorry for the delay. I have reproduced the error. The moto payment intent would be being confirmed from FE js with the connect context. Here's the error again https://dashboard.stripe.com/test/logs?object=acct_1Jji7zAZ75xSk2ok&success=false
But, yes, we can reach out to support to get it enabled. Thanks again for your quick response.
you can't confirm client-side that's impossible
MOTO requires a server-side confirmation, it's a custom flow for your own admins/support teams and you have to use a different integration
And the problem is that you have the MOTO functionality enabled on part of your account (your own API requests) but not for your platform (API requests you make on behalf of other accounts) which the support team can help fix!
Oh, yes, we do confirm MOTO on server side. It was the setup intent that is being confirmed client-side (sorry for the mixup).
Will get MOTO enabled on the connected accounts too, Thanks!