#anrighi.wr

1 messages · Page 1 of 1 (latest)

lone gyroBOT
cold helm
#

hi! I'm not really understanding why that would be an issue? can you give more details?

ruby star
#

sure: we have a customer with an active subscription

#

on the 21 July, it should be renewed, but the payment failed

#

on Stripe, we found 3 different payment intents, which have been created on different days:

  • 21 lug 2023, 15:39
  • 22 lug 2023, 10:50
  • 22 lug 2023, 10:51

which resulted in 3 different payments for the customer

#

we are trying to understand why the 3 different payments have been issued, since only one was required

cold helm
#

do you have the IDs of those payments?

ruby star
#

pi_3NWJYpK1xWAYzvtr0roTdSvr

#

pi_3NWbWwK1xWAYzvtr0BIzOzf0

#

pi_3NWbWgK1xWAYzvtr1OquOlMf

cold helm
#

ok. well you have three Invoices.
pi_3NWJYpK1xWAYzvtr0roTdSvr is associated with the recurring subscription invoice so it's the regular one

pi_3NWbWwK1xWAYzvtr0BIzOzf0 is associated with an invoice that was created because you called the API to reset the billing cycle of the subscription from your PHP backend; that forces a new Invoice for the new period. https://dashboard.stripe.com/logs/req_B2X1oVcAie9LyR

pi_3NWbWgK1xWAYzvtr1OquOlMf is associated with an invoice that was created because you called the API to reset the billing cycle of the subscription from your PHP backend; that forces a new Invoice for the new period. https://dashboard.stripe.com/logs/req_YDxsKkK33Jha0s

ruby star
#

therefore are we creating the two additional payments from our backend?

cold helm
#

yep