#vineet5769-invoices

1 messages ยท Page 1 of 1 (latest)

cedar otterBOT
fickle dock
#

Hi ๐Ÿ‘‹ can you share the ID of an Invoice where you're seeing an unexpected billing reason?

half vortex
#

Can there be any security issue by sharing live mode data? If you can just tell me when can I expect 'subscription_update' value, that will be great too.

fickle dock
#

You should expect subscription_update when the Invoice was generated by a Subscription being updated, unless you're using an API version before 2018-10-31 in which case you ill always see subscription_update:
https://stripe.com/docs/upgrades#2018-10-31

half vortex
#

yes, the api I'm using is 2015 version

#

So, in these cases, can we expect any renewals to have value as subscription_update?

fickle dock
fickle dock
#

An example of what?

half vortex
#

"You should expect subscription_update when the Invoice was generated by a Subscription being updated," This part to be exact

fickle dock
#

You should ignore that line since you're on an older API version before there was a difference between subscription_created and subscription_updated

half vortex
#

Okay

#

Another question I had:
We have enabled tax collection on stripe. As part of this, stripe is now collecting tax on our behalf. We want to confirm if the shown amount on dashboard (Section: "Your Overview" ; field: Net volume from sales) includes tax or excludes tax.

#

Say, my subscription fee is US $10 and tax collected is $2. Will I see $12 there or $10

fickle dock
#

We focus more on helping developers with the API in this forum, I'm not as familiar with how things are displayed in the dashboard. My understanding is tax rates can be inclusive or exclusive, so I'm not sure if you'll see a consistent behavior there or if it will fluctuate based on country/currency.

#

vineet5769-invoices

half vortex
#

How can I get the confirmation for this? It impacts how my organization does its revenue reporting and several other payouts

fickle dock
#

If you have an example Invoice you can share I can try to take a look at it and see if I can tell how the tax rate is structured. Otherwise I would recommend reaching out to our Support team about the tax rates being used by your flow and how they're represented in the dashboard UI:
https://support.stripe.com/?contact=true

half vortex
#

tax rate is exclusive, I just wanted to know about the specific field in Stripe Dashboard. I will contact Stripe Support for this, thank you

#

Thank you

fickle dock
#

Any time! Sorry I wasn't able to give you all the answers this time.

half vortex
#

No problem, you helped a lot.

#

Can I get any documentation on captcha that stripe recently introduced on clicking 'Subscribe' button in Stripe Checkout?

fickle dock
#

I believe that captcha is something that we (Stripe) control/decide to show to help mitigate card testing attempts, and that it is available for you to control. Trying to double check that though.

half vortex
#

And why do I always get webhook associated with the event invoice.payment_failed when captcha is displayed after clicking on Subscribe button?

#

Even before captcha verification, this payment failed event occurs

#

Example: sub_1NYS7BKBKFciBNc7Almpc0tH

#

I believe that captcha is something that we (Stripe) control/decide to show to help mitigate card testing attempts True, yesterday, while testing I saw it 3-4 times but can't reproduce it today.

fickle dock
#

My understanding is the Invoice payment techincally fails as part of the process to display the captcha. I'm not exactly sure if the captcha is displayed because the payment fails, or if the failure event is emitted as part of the flow whenever a captcha is deemed to be necessary.

half vortex
#

or if the failure event is emitted as part of the flow whenever a captcha is deemed to be necessary This is true, because I have been using the same test card ending with 4242, so all payment is deemed to be successful, but whenever captcha was displayed, payment failed event was triggered

#

Our system is breaking due to this particular webhook due to newly introduced captcha, so wanted to research everything about it.

fickle dock
#

Gotcha.

cedar otterBOT
meager dagger
#

Hello @half vortex ๐Ÿ‘‹
Jumping in here

Can you provide more information about what's breaking in your system exactly due to the captcha triggers?

half vortex
#

Whenever there is a payment failure webhook, we tend to cancel subscription in Stripe as well as our site.

#

Due to subscription cancellation in Stripe, users are displayed "checkout session expired" message and they are not able to subscribe.

meager dagger
half vortex
#

Yes, but then the billing_reason I see is 'subscription_update' and not 'subscription_create' due to use of an older api version. The developer who worked around the stripe code does not work here anymore and so I fear if any other feature might get affected if we do not cancel any subscriptions with billing_reason as 'subscription_update' .

meager dagger
#

I see. On your test account though, I am seeing that the API version is 2022-11-15

#

Is that not the account you're using for production?

half vortex
#

No, I'm a developer. I do not have access to production account owned by my organization.

#

The version they use is 2015-07-07

#

I can't even revert to the older version in my Stripe Dashboard, only can change version of webhooks via api.

#

Thus all this confusion

meager dagger
#

I see. Another alternative could be to set your own billing reason in checkout session metadata.

When you receive invoice.payment_failed , you can retrieve the checkout session for the subscription and look at the metadata to find the billing reason you're setting that way
https://stripe.com/docs/api/checkout/sessions/list

half vortex
#

I see, we already use metadata, so we can use this alternative.

#

Can you please tell me if captcha has been enabled for stripe pop-up as well?

#

or just stripe checkout?

meager dagger
#

Not sure what you mean by Stripe Pop-up

half vortex
meager dagger
#

That's most likely legacy checkout, not sure if we had CAPTCHA enabled for that. I'd highly recommend not using that flow if you're building a new integration as it is quite old (considered legacy)

half vortex
#

We are slowly migrating all the countries to Stripe Checkout, but still the legacy checkout is active for a few countries.

#

If captcha is not enabled there, I'm good

meager dagger
#

I see. I don't exactly know as legacy checkout predates me. My understanding is that legacy checkout does not have the same level of protections built in against card testing as the new checkout

half vortex
#

Got it, thanks for your help. The alternative you provided can be implemented quickly.

meager dagger
#

I understand you have a support ticket with us too that one of my colleague just responded to. Let us know if you have any further questions.

Good luck ๐Ÿ™‚

half vortex
#

Yes, this was kind of an urgent issue, so was looking for answers all over the place. Thank you

meager dagger
#

No worries!