#energetic_swan_85077

1 messages · Page 1 of 1 (latest)

sudden ploverBOT
proven iron
#

Hi, could you list down some specific Id and timeline here? ie. Which Subscription Id, which Invoices Id has been paid twice?

wraith flower
#

For example, why is the subscription ID sub_1NKeUJK8qsUQ7MPjImgmpqbR and the invoice in_1NmZQ3K8qsUQ7MPjBaMhmPGp eventually paid? Because it is generated after the payment collection is suspended. According to the document, doesn’t it say that the invoice generated after the payment collection is suspended will eventually be void?

proven iron
#

I see, so you mean after https://dashboard.stripe.com/test/logs/req_84PG2KzTR6yfcU, this Invoice is generated should be voided immediately, but instead it is still finalized and paid later after you move back the Sub on https://dashboard.stripe.com/test/logs/req_Q9WJsbQ5yquc1B ?

wraith flower
#

yes

proven iron
#

Umm I see. Yeah that should be voided according to the Doc

wraith flower
#

Yeah, so what's the problem?

#

By the way, will it be affected if the webhook of the invoice of this draft fails?

proven iron
#

Hmm was it failed? (checking)

#

no it didn't

wraith flower
#

Hmm, then why is it?

proven iron
#

Hi, gimme some times and will get back to you when I figured it out in more details

wraith flower
#

Okay, sorry to trouble you.thank you

proven iron
#

np!

#

Hi @wraith flower is this blocking you from implement payment? If that's the case could you write into Support and mentioned you have asked in this thread? We would need more time to investigate and look into details

wraith flower
#

Then you can ask me, how can I go to the API request to make this draft subscription void, because our business process is like this, so this kind of double payment must be avoided

#

because after pause it may be unpause the subscription and set The billing_cycle_anchor is now and the payment is collected immediately. Then that the invoice for the previous draft was also paid, which resulted in repeated payments

proven iron
#

I see. Please write to Support and include all your use case above