#jasonfish568
tribal narwhalBOT
tulip notch
👋 happy to help
dense aurora
This is continuing on the previous question, #dev-help message
tulip notch
what type of connected accounts are you using? what type of charges are you using (destination, direct)?
dense aurora
Standard account, direct charges
My design works fine with payments. The customers and merchants have a many to many relationship
tulip notch
yes I understand
in that case I think you would need n buttons for the n merchants portals
dense aurora
Is this a right implementation?
tulip notch
the only other way is not to use the Customer Billing Portal
and develop your own interface for that
dense aurora
By that way, if the customer changes the payment method for one merchant, I automatically change for other merchants too?
devout slate
Hi! I'm taking over this thread.
If you are using Direct Charges, then the payment method is stored on the connected account. So if a user change the payment method on one account, it will only change on that account and not the others.
dense aurora
Understood. So the customer indeed needs to manage the payment things separately for each merchant. Unless I don't use direct charges, and let the customers pay the platform first. Right?
devout slate
Yes that's correct. Note that there's another option:
- Save the payment method once on the platform account
- And then each time there's a payment to be made, clone the payment method on the connected account and do the payment there
You can learn more about this here: https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods
dense aurora
Thanks so much. I'll stay with the multiple client portals