#kaeshk-subscription

1 messages · Page 1 of 1 (latest)

vernal patio
#

I think you have mixed up things here. PaymentIntent and SetupIntent has separate API, no way you can have a SetupIntent Id returned in a PaymentIntent creation

#

You choose either PaymentIntent flow or SetupIntent flow, that's it

#

When you create a Subscription, there 2 cases:

  1. It could require Payment immediately. In this case you take its Invoice's first PaymentIntent, plug into client side to confirm it
  2. It doesn't require PaymentIntent immediately, ie. on trial etc. In this case Stripe automatically create a SetupIntent. You also take this SetupIntent and plug into client side to confirm it
wicked jasper
#

referring to the first case, choosing the payment intent flow , where first installment is required immediately followed by MIT without customer intervention. Would the flow be:

  1. create payment intent with setup_future_usage (with customer and payment method info)
  2. customer authorizes payment
  3. confirm setup_intent (need clarity here)
  4. recurring payment (using payment_intent, would help if there is a sample curl)
vernal patio
#

No I don't think this is the flow if you want to create a Subscription. You would want to use our Subscription API instead

wicked jasper
#

how do i link subscription and payment intent entity

vernal patio
#

On Step 5, you will see that from the Subscription's latest_invoice.payment_intent, you will have the PaymentIntent secret

#

it's the same with if you create a standalone PaymentIntent and returns secret