#mahraamir
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. 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.
- mahraamir, 20 hours ago, 18 messages
hello! Can you share the corresponding PaymentIntent id?
Hi! I'm taking over this thread. Looking into this...
Ok
Sorry for the delay. You are doind a Destination Charges on behalf of a custom connected account. But the connected account doesn't have the CashApp capability. So it's expected to not work.
This is how you can request the cashapp capability on the connected account: https://stripe.com/docs/api/accounts/update?lang=node#update_account-capabilities-cashapp_payments
it can only be done via api?
You can do it from the platform's dashboard. But ideally you would request this capability when you create the account with the API.
ok we will do that but right now for testing, I should go to settings?
it's already have that Capability
Hey, stepping in here to assist
Apologies, you're right the CA does have the necessary capability. Seems however that this specific flow (saved PM on platform for usage with destination charges and on_behalf_of) is not currently supported for CashApp
I think the issue is the on_behalf_of parameter. I imagine if you remove that, it'll work. If that's a requirement for your business then I'd recommend writing in to support who can help: https://support.stripe.com/contact
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
let me try by removing transferring to connect account
Let me know how you get on
Checking
Yeah unfortunately I'm not sure what is going on here. I suspect it's because the PM was created via a Setup Intent where you pass on_behalf_of so the mandate exists on that account
As I said, if you need on_behalf_of (which it seems you do) you should write in to my team at the URL above and reference this thread
ok