#leah-customconnect-embeddedcomponents

1 messages · Page 1 of 1 (latest)

atomic flameBOT
#

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.

vague ermine
pseudo bough
#

Account type is Custom in my use case.

#

let me know if you were asking about something else

vague ermine
#

Okay so with Custom accounts we highly recommend using Destination charges.
https://stripe.com/docs/connect/destination-charges

With that charge type the payments occur on your platform account and the risk/compliance would still be something you would need to handle.

pseudo bough
#

Makes sense to me. I intend to use Destination charges.
My understanding is that my connected account won't have access to the Stripe Dashboard.

As a platform when I receive an alert from Stripe that one of my connected account need to take action. The documentation states that Stripe will reach out to my connected account directly unless I use Embedded Dashboards (beta).

What can I do to avoid Stripe reaching out to my connected accounts directly and handle any action required in my application.

Can you point my the API responsible for passing this information?

vague ermine
#

Custom accounts do not have access to the Stripe dashboard, that is correct. The design for those account types is that "Stripe" does not exist for them. They interface only through your integration.

Can you share a link to the documentation you are referring to?

pseudo bough
#

"Connected account risk ownership and loss liability
When Stripe owns risk and loss liability, we manage credit and fraud risk for your connected accounts, including applying interventions and remediating fraud. If your connected accounts don’t use the Stripe Dashboard, your application must embed components that let them see and respond to alerts from Stripe."

vague ermine
#

Ah you mean this beta feature. Unfortunately, I cannot provide much more guidance on products and features in Beta.

#

This is specifically a part of the unified_accounts_beta

#

For assistance with that I recommend writing in to Support here: https://support.stripe.com/contact

Specifically. mention your want to make use of this beta program unified_accounts_beta (and include the doc link). That will help ensure your question gets routed to the proper team.

pseudo bough
#

I understand. I am trying to figure out my options with what is currently in GA.

Since Embedded Onaboarding is in GA and my account type is cutsom (no Stripe Dashboard access), what are my options to ensure my connected accounts take required risk and compliance actions in my application?

vague ermine
#

Unfortunately I cannot really help with that either. AFAIK there isn't an API to hanlde these operations so I cannot provide advice on how to take these actions. I would still recommend writing in to Support with a clear and crisp description of your concern and the correct team should be able to help

pseudo bough
#

Thanks a lot! I really appreciate your help here. I'll take this to Support.

vague ermine
#

I'm happy to shed what 💡 I can 🙂

I hope your are able to quickly get answers to all your quesitons.