#pedrosafontes
1 messages · Page 1 of 1 (latest)
You mean that you want to have a customer be able to pay for transactions related to multiple connected accounts?
What kind of payments are you creating? Direct charges or destination charges?
Direct charges.
It is an app for splitting and paying restaurant bills. If a user pays a bill in Restaurant A, I want to enable him to save his card details so that when he wants to pay a bill in Restaurant B he does not have to fill in card details again.
Gotcha, so you'd store that card on your platform first, then you would "clone" it to each connected account to create payments:
At the moment I don't have access to the card details to be able to create a payment method via the API. The users are inserting their card details in the form rendered by stripe elements.
Should I use setup_future_usage ?
Yes, but if you're doing direct charges that payment intent would be on the connected account already and wouldn't be usable on your paltform or other accounts then
You'd need to save the card on the platform first to accomplish this
If I pass a customer argument to the payment intent and that customer has an associated payment method would card details be pre filled in the payment elements form?
No, if you want to use a payment method already saved for a given customer, you don't need to present the payment element at all
I still want to render the payment element iframe as the user may want to pay with a different method. Would the best approach be offer a separate option with the saved payment method?
That's not something currently available, but we're working on it
So for now, you'd need to present your own UI representation of thse saved payment method, eg Visa ending in 4242
then the customer can select it and you complete the payment using the existing pm_123 id
So your code would have two paths based on if they used one of the saved PMs or enter new details, thats fine!