#TheUchi-paymentintent-incomplete

1 messages · Page 1 of 1 (latest)

ruby fable
#

Hi there, you can leave PaymentIntents indefinitely if you so desire. The only negative effect really will be clutter in your Stripe Dashboard.

Subscriptions create Invoices which create PaymentIntents. So yes all cases will fire a payment_intent.succeeded but only when you are actually using a Subscription or one-off invoices will you see invoice.payment_succeeded... so the recommended route here is to listen for payment_intent.succeeded and customer.subscription.updated on Subscription renewals.

still otter
#

Hmmm I want to try to create a DRY option, because on both cases(subs and normal purchases) I want to add a "commission" that will be sent to a connect account. Based on what you said, is it safe to assume that payment_intent.succeeded will not be fired up if a sub is renewed?

ruby fable
#

payment_intent.succeeded will be fired on a Sub renewal.

still otter
#

Is there a way I can simulate a subscription renewing?

ruby fable
still otter
#

Awesome, thank you so much!

ruby fable
#

Sure!

still otter
#

Question

#

To use the clock, it says "Upgrade to Billing Starter to use test clocks"

#

Does that mean I need to pay for something to use it?

ruby fable
#

Hmmm I'm not too familiar with pricing stuff as I focus on the API. Do you have a very old account?

still otter
#

Yes

ruby fable
#

Gotcha. Then yes I think it may move your account to a different pricing plan but you would need to talk to our Support team to confirm that since I really don't know anything about pricing. You could just create a new account for testing purposes and shouldn't have any issue using test clocks.

still otter
#

Hmm ok, got it

#

The account I am using is mostly used for testing anyways, so I dont mind if it is based on sales(like a fee to pay per sub for example)

ruby fable
#

Yeah there won't be any cost unless you are actually active in production

still otter
#

Sweet, thanks for clarifying