#nsotelo
split oak
cursive totem
Hello! Yep, for the marketplace model we have Stripe Connect: https://stripe.com/docs/connect
And for card payments and next actions, I'm not sure exactly what you mean by "statuses". Can you be more specific about what you're looking for?
glacial sapphire
I mean the possible actions we can be requested
cursive totem
I don't think we have a comprehensive list anywhere, but it's not something you need to worry about as the Stripe frontend libraries take care of it for you. For cards, the big two are going to be 3D Secure and, rarely, a captcha challenge if we detect high levels of abuse.
glacial sapphire
Ok, but the API integration would require us to take the action, right?
I mean, redirecting the user for instance
cursive totem
Meaning if you don't use our client libraries at all?
glacial sapphire
Yes, we are thinking of using Stripe Elements for tokenization, but not the full Stripe's checkout experience
We would tokenize with elements, and then process the payments directly via API. This means, we understand, that we can receive "next action... 3ds" (for example) and we would have to redirect the user, or whatever action
cursive totem
Meaning you want to confirm server-side?
If so you can still use Stripe Elements to handle the next action using handleNextAction in Stripe.js: https://stripe.com/docs/js/payment_intents/handle_card_action
glacial sapphire
Oh, cool! We gonna check that
many thanks
Last question, I was reviewing the Connect documentation
Just to confirm:
1- with standard accounts, the $ from the transaction goes directly to the connected child account, right?
2- does the "main" account have any extra transaction charge or fixed cost from Stripe? (this is to make sure that the fees are in charge of the connected accounts)
cursive totem
That depends on the type of charge, not the type of connected account. See here for details: https://stripe.com/docs/connect/charges