#vadym-connect-payments
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.
- vadym-save-paymentmethod, 11 minutes ago, 7 messages
- vadym4646-checkout, 2 days ago, 26 messages
Hi ๐
The doc you linked in your other thread did not mention anything about Connect and neither did you so it was easy to miss.
First off, what Connect account types are you using? Standard, Express, Custom?
Okay so in that case you would want to use Destination Charges.
You would provide the ID of the payment method you saved and attached to the customer when creating the Payment Intents https://stripe.com/docs/connect/destination-charges#create-a-charge
https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method
but were is a Customer's checkout in this flow? What should we do on the Client side?
What are you trying to do? Saving a payment method is usually associated with merchant initiated transactions.
We have Service providers on our platform, they have Express accounts in stripe.
We do not know nothing about Customer's Stripe accounts.
The flow we are trying to implement is:
The Customer order a service -> We redirect Customer to Stripe's checkout, but not charge the User -> once Service will be completed we want to charge user
Once you use the Checkout Session to save the payment method, you will be able to charge the customer without further interaction from that customer. The payment method will be configured for off-session payments.
So, checkout will be proceed only once for the customer, and than we just charge the Customer from the server side right?
Correct.
Happy to help ๐