#nerder-paymentmethod-clone
1 messages · Page 1 of 1 (latest)
😞
i susupected it
Then maybe you can help me understand better this use case and how may I support it, because probably i'm approaching it wrong.
For context, we are building a platform for gyms. So all our connected accounts are gyms and the customer are practitioners of such gyms. We want to allow cross-gym purchases.
There are 3 scenarios we want to support:
Scenario 1
Customer NOT present in Connected Account (Without Payment Method in PLATFORM account)
Scenario 2
Customer NOT present in Connected Account (With Payment Method in PLATFORM account)
Scenario 3
Customer already present in Connected Account (Complete)
Really the only solution is to collect card details in the platform first, no other way around it
The problem is with Scenario 1
There is a way to attach a payment method all in the server? (i mean without using setup intents)
because one idea, was in the same call the first time a customer purchase anything:
- attach payment method in the platform
- clone the customer and the payment method in the connected account
- create a payment intent on behalf of the connected account
- return the client secret to the frontend and confirm the payment
Use SetupIntent, collect card details on the platform first. Then clone and use it
Okay I see, from the customer's prospetive the UX is a bit worse as they will need 2 steps instead of one to purchase their first membership
but if truly there are no way around it, than it will be it
yep
thank you so much @regal moss