#Cédric Morelle
1 messages · Page 1 of 1 (latest)
Hello again soma sorry for bothering you again with Workflow issue
Yes you can use metadata to store information about the product (name, ID, whatever you need)
Ok let me rephrase my question
I have products in Stripe. Subscription product
each of them got their id sub_xxxxxxxx
I want to create a payment intent for those Subscription product
is it possible ?
Wait, if you use Subscriptions then the subscription will create the Invoices and PaymentIntent automatically for you.
So why do you want to create a PaymentIntent?
User may be not registered on our website. Still they will have the proposal to pay for a subscription.
So we can't create Customer object by advance
I'm sorry but I'm confused. So let's take a step back.
What is your end goal right now, is it to create a subscription for a user? What does your payment flow looks like?
Do you use Checkout Session to create the subscription, or directly use the subscription endpoint?
Ok let us start from the beginning.
W1: Right now our subscription flow, required our user to register/login, then we create a Stripe Customer, then create an Invoice, then we had a specific form in JS on our website. This workflow works perfectly but lacks of efficiency for sales conversion
W2: Then I discovered PaymentIntent and though it would be useful to let anonymous user makes their payment on Stripe, then grab the receipt_email to check if mails exists or not, if not I automatically create the account based on this mail. This workflow works perfectly as well
Now what I only need to do, is to change W2, so instead of making paid a single PaymentIntent, I wish I could make them pay their SubscriptionProduct even if I don't have a customer yet created as StripeCustomer because I don't know yet who is this customer
then we create a Stripe Customer, then create an Invoice,
I don't understand this part. Are you using Stripe Subscriptions objects or not? Because Stripe Subscriptions automatically create the invoices for you.