#dgsunesen
distant agate
Hi there!
Can you share the ID (req_xxx) of the failing API request?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
nimble cosmos
req_hY1shKhLtR5hDg
distant agate
Thanks for sharing, Did you activated mobilepay in the live mode payments settings of the connected Accoun acct_1M08LRIYoTCtg55m:
https://dashboard.stripe.com/settings/payment_methods
nimble cosmos
It says it's on
distant agate
Sorry I meant for the Connected Account settings:
https://dashboard.stripe.com/settings/payment_methods/connected_accounts
nimble cosmos
Not sure how to proceed here?
For you to compare, here is one that went through during test: req_SNitbExNAl6tEe
distant agate
Not sure how to proceed here?
When you click on off by default in order to activate it what happens ?
woeful breachBOT
distant agate
Try to request the mobilepay_payments capability for the custom connect account acct_1M08LRIYoTCtg55mfollowing this:
https://stripe.com/docs/connect/account-capabilities#payment-methods
nimble cosmos
But how come this works in test mode?
without doing that
and in the docs you sent me I don't see mobilepay_payments anywhere
distant agate
mobilepay is invite only payment method, check this instead:
https://stripe.com/docs/payments/mobilepay#request-mobilepay-capabilities-for-your-connected-accounts
shrewd laurel
In any case, this is a private beta which we don't publicly support here. I'd recommend reaching out to the team via the email that invited you to the beta, or support directly: https://support.stripe.com/contact
nimble cosmos
Does this mean that the connected account that I want to do a payment to (on_behalf_of) needs to request those capabailities before I can do a payment?
shrewd laurel
Yes, generally. You'd do that when you create the Account: https://stripe.com/docs/api/accounts/create#create_account-capabilities
nimble cosmos
And so for already created accounts (prior to us introducing MobilePay payments), we would then need to update all accounts with those capabilities?
shrewd laurel
Yes
nimble cosmos
Hm... Okay.. I just think it's strange why we were able to do a successfull payment during testing
never seen this issue until now on production
shrewd laurel
Yeah not sure. But with custom accounts you need to be dilligent in specifically requesting the capabilities you actually need
They all have specifric requirements, so if you're uopdating capabilities on existing account it may trigger verification requirements that your accounts will need to provide