#pdenyer123-connect-workflow
tropic magnet
Thank you very much! Happy to provide more detail too. Or show what we are trying to do through our Stripe account.
high dragon
This vendor will be added under our main Stripe account and we want to capture the payment directly on their account rather than the main Stripe account that is connected to the ecom platform
When you say vendor will be added under our main stripe account, did you mean as a connected account?
tropic magnet
Yes, sorry
high dragon
Okay. got it.
Still figuring it out
tropic magnet
Okay thanks can i attach a photo to help with context? It just seems like we cant directly charge the vendor (the connected account on Stripe) unless a customer has a payment method attached on Stripe. Which means we would have to require them to store a card on the ecom platform.
Which we don't want to require
However, if we dont require it, no payment method is attached to the customer. Only to the order.
high dragon
What type are the connected accounts? i.e. Standard, Express or Custom
tropic magnet
Let me check
I'm sorry - how do I identify that?
Right now we are just in test mode
It looks like it varies between Custom and Standard
@high dragon what does that mean for us?
high dragon
apologies for the delay
juggling between a few threads at the moment
tropic magnet
No worries - i understand
high dragon
You'd typically want to use Direct Charges with Standard Accounts only.
tropic magnet
Why is that? Can we easily switch a Custom account to Standard?
kind silo
That follows the recommended charge types based on the different Accounts. You can see the breakdown of the different charge types here: https://stripe.com/docs/connect/charges
tropic magnet
Okay yes. I see that. However, does this answer my initial question? If we go the Standard account route, will we be able to more easily capture the payment on the Standard connected account by not requiring a customer to have to store a card?
It appears the vendors we have connected to our prod mode on Stripe are all Standard. It was the one test vendor we had that was Custom. So thats an easy change on our end.
kind silo
So if your customer does not have a saved payment method, what is it you are going to charge?
tropic magnet
That's what I'm trying to get help with. When an order is placed on our ecom platform, we authorize that order via Stripe. We do get a unique Transaction ID on the order, which we see but we dont see one at the customer level. When the order is marked as Shipped, we want to then charge that order amount to a connected vendor. The only way we've seen a way to do that is to require a customer to store a credit card on their account (which is not an ideal workflow). We'd like it so customers can checkout without requiring a stored payment method.
kind silo
Wait so what is the payment flow? When does the customer's fund leave and where do they first land?
tropic magnet
- Order placed on Ecom Site 2. Order amount is authorized on Stripe 3. Order gets sent to a vendor to fulfill 4. Order is marked as Awaiting Fulfillment 5. Upon a trigger of "Awaiting Fulfillment", we capture payment on the order. 6. Payment is captured on the vendor who fulfilled the order (as they have a list of vendors).
kind silo
2: Order amount is authorized on Stripe
What is the method you are using to authorize the amount here?
kind silo
And when you attempt step 6 how is the payment method charged?
tropic magnet
Through a direct charge (but only way so far is by using the customer Payment Method to create the charge) and then we clone customer and their payment method to the connected account .
Im not sure if that is the right approach. Id like to find a way to charge without forcing the user to save a card on their account
kind silo
So you do not want to have a payment_method associated with the customer? What would you charge?
tropic magnet
I guess my question is how do we get a payment_method associated to the customer without requiring them to store it on our ecom platform? When we place an order with a customer who doesnt choose to store their card, no payment method gets attached to their profile on Stripe so we cant charge it. When we require them to save their payment method on our ecom platform, then it gets stored on Stripe which is the way we've been able to charge it
It's not typical to require a customer to save their card on a checkout flow. Thats my concern
kind silo
Alright, when do you expect them to enter their payment information? What is the desired flow?
tropic magnet
They enter it at checkout. Standard flow. Then they submit their order.
I just dont want to require them to check "save this card for future transactions" in order to be able to charge it on the connected Stripe account
radiant marten
@tropic magnet stepping in on behalf of snufkin, are you planning to use the Payment Element to collect card details?
tropic magnet
Thank you. Unfortunately not. We are using a native checkout from Bigcommerce
So we are unable to use that (from what I understood from previous conversations - i may be wrong!)
radiant marten
if you're planning to use Stripe Connect, you're going to need to implement one of Stripe's offerings e.g. Payment Element or Stripe Checkout to collect the card details to charge though
if i'm not mistaken, your current question is - how do you create a direct charge on a connected account without saving the card. Using the Payment Element as an example -
- you would create a PaymentIntent with the Stripe-Account header set to the connected account.
- you would initialize the Payment Element with the PaymentIntent client_secret
- collect the card details
- then confirm the charge.
tropic magnet
I see. That is helpful. I didn't realize you would have to use Payment Element or Stripe Checkout. Thank you.
I guess my question is which one is more simple of a route (less time consuming) if we are on Bigcommerce. Can you embed a Payment Element onto a native Bigcommerce / Shopify checkout?
Or is Stripe Checkout an easier redirect from an ecom platform?
radiant marten
i'm not familiar with BigCommerce and I think your question would be better answered by them. I do want to mentioned that using Connect is going to require you to know how to code. You would need to set up the creation/linkage of connected accounts, creating a server to generate the PaymentIntents, and also update your frontend to collect the card details.
tropic magnet
We know how to code
Thanks.
I just was curious from your experience which is an easier set up
or how do you determine which one is best for our scenario (Payment Element or Stripe Checkout)
radiant marten
It really depends on your needs, in general Stripe Checkout is a lot easier to set up because it's essentially a pre-built Checkout page. You can take a look here - https://checkout.stripe.dev/ The Payment Element would only collect the necessary payment method details, you can see how it looks like here : https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
radiant marten
yes, Stripe Checkout is PCI compliant
radiant marten
feel free to reach out if you have more questions!
tropic magnet
Thanks!
tropic magnet
if i'm not mistaken, your current question is - how do you create a direct charg...
Really quickly @radiant marten . Sorry to continue 🙂 But what would the layout look like here for Stripe Checkout instead of Payment Element if you wouldnt mind
radiant marten
as in, how does Stripe Checkout look like when a customer makes payment?
tropic magnet
Yes and what that process flow looks like (at a high level)
Do you create a PaymentIntent as well
radiant marten
you would create a Checkout Session instead with the Stripe-Account header set to the connected account as well - https://stripe.com/docs/api/checkout/sessions/create
the response would contain a URL which is the hosted Checkout page
you would redirect the customer to that URL to make payment
if you select your relevant use case in this page, you'll eventually be redirected to a Checkout page and you can see how it looks like : https://checkout.stripe.dev/
tropic magnet
Got it thanks very much!