#blinkdaffer

1 messages · Page 1 of 1 (latest)

high hingeBOT
pine ridge
#

Once the payment method is attached to a customer, it can't be attached and copied to another customer

#

So no, it's not possible to re-use the saved payment method onto different customers

manic dew
#

let me explain my scenario better

#

so we want to accept payments first, and then onboard users to our platform.
for this approch, we are creating temp user in stripe in the begining to accept payments,
once the user in onboarded to our platform, we cancel the temp users subscription and create a new subsctiption with a new customer id

#

however a user may have a customer id with stripe already.

#

so we cant figure out how to attach the payment method to the new customer id

#

is there any way to handle this

#

scenarios

#

what would be the right way to intergate a solution like this

pine ridge
#

Why do you want to create the new customer in Stripe? You can simply just update the customer information on the existing one instead of creating the new one, so that they payment method will remain

manic dew
#

but not all customer will have customer id on stripe

#

hmm i am gonna try and update old customer id

#

thank i think i will use this approach

#

thank you

pine ridge
#

If you create the subscription on the temp customer, the customer have already be created. It's not possible to create a subscription without a customer

manic dew
#

just out of curoisity river, is there a better way to handle anon purchases and then onboard to our platform

pine ridge
#

Can you explain the flow of what you intend to achieve?

manic dew
#

so we want to accept payments before a user is onboarded into our platform

#

when the user onboards we have a user object that gets created

#

we want to accept payments before we have a user object

#

then when the user login into our app, we want to register this subscription

pine ridge
#

You can have one-time payment without customer object. However, a payment method can only be saved and used in a subscription after the customer object is created.

I'd recommend creating the customer object first and save the payment methods onto it. After the customer is onboarded to your system, then you update the customer information in the existing customer object instead of creating new one

manic dew
#

yeah that what i was thinking would be a viable solution.

#

thanks for all the help man