#.stevenp

1 messages · Page 1 of 1 (latest)

short archBOT
#

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.

serene knoll
#

Hello! Can you give me some more context - are you referring to an Invoice that has multiple payment attempts?

untold valve
#

Not exactly, I'm referring to someone who signs up for a monthly subscription. Does the paymentIntent.created event fire for each billing attempt?

serene knoll
#

A payment_intent.created event would be fired for each Invoice that is generated. For a monthly subscription you'd typically get an Invoie every month when it' time to renew

untold valve
#

got it - and its fire before the invoice is actually generated and charge object is made right?

serene knoll
#

It's actually typially fired after the Invoice is created (because the Payment Intent isn't created until after the Invoice is finalized)

untold valve
#

got it, and its where we would set the billing descriptor if we want to change it right?

#

this makes it seem like the payment intent is crated after the customer is charged

serene knoll
#

And yes, if you want to set the descriptor you'd listen for the payment_intent.created event

untold valve
#

so on a 30 day subscription, the payment_intent.created event is going to fire on day 0 or day 29 right before the charge?

serene knoll
#

It's going to fire when you create the Subscription and it's going to fire 30 days later when it's time to renew