#zeez5658

1 messages · Page 1 of 1 (latest)

ember crystalBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

woven lava
#

hi! that guide seems like exactly what you want.

You never create a PaymentMethod on the backend, since that would imply you have the raw credit card numbers in your backend code, which would put you in PCI scope. You create the pm_xxx on the frontend and can send the ID/object to the backend to use in API calls there, like in that guide.

#

was there a specific element or order that doesn't work for your purposes that you could expand on?

rapid dove
#

So basically my flow is as follows:

  1. Register form is submited
  2. validate all fields (inc credit card)
  3. Create stripe subscription
  4. Create account in my db

So essentially I want to ensure the stripe subscription and info in my db is created atomically

#

i.e. one isnt created without the other

woven lava
#

I suppose you could only create the things in your database after the subscription is successfully set up.
but yes, there's no perfect solution here really, since you need to create a Customer cus_xxx object first, in all cases.

rapid dove
#

I can create the payment method before the customer though right?

#

Don't I have to link the pm to the customer for future payements

woven lava
rapid dove
#

The guide creates the customer first. But good to know you can do it the other way around. Thankyou

woven lava
#

yeah I see the guide now. You don't have to create the Customer first anyway, you could do it in step 8 in the create-confirm-subscription route.

rapid dove
#

great, thankyou, appreciate the help