#smokey0477

1 messages · Page 1 of 1 (latest)

tulip perchBOT
modern zenith
#

If the user is already a member on your app, do you already have a Customer object for them? If so it may make more sense to use their customer ID and attach the new PaymentMethod to that

#

That way you only have to look at once Customer when trying to get their payment history and whatnot

sand anvil
#

At this stage, no user has a customer object

modern zenith
#

Gotcha, so yes your flow totally makes sense here. Is there a specific part of this you are concerned about or are trying to figure out?

sand anvil
#

No I was just a little confused why it wouldn't create the customer account and payment method automatically, but then I realised this is all done on the front-end so that is why. Now I typed it out, it makes sense to me.