#devangbhuva97-subscription

1 messages · Page 1 of 1 (latest)

opal lily
vital frost
#

yes @opal lily this one

opal lily
#

Can I have the Invoice Id?

vital frost
#

subscription id: sub_1LVs4tCScnf89tZo1IsMFlwU
last invoice id: in_1LVs7KCScnf89tZoKg5pBYEz

#

I created this subscription under acct_1Ihw53CScnf89tZo which is connected with our main platform account

opal lily
#

I think your account has a warning/error that it's not eligible to Stripe yet

#

Maybe that's the reason automatic advancement is not disabled

vital frost
#

Ok.. let me try another test account

#

Thanks @opal lily it's working in another test account acct_1JMYI1AjORjIkyJ0

#

but not getting webhook events from that account. Can you help me to debug that?

shy ridge
#

sure, can you say more. Like what's the ID of your main account, or the context of the webhook endpoint where you expected to see the event(like we_xxxx URL of the endpoint when looking at it in https://dashboard.stripe.com/test/webhooks would help for example)

vital frost
#

account: acct_1Cbrx8FpU9DlKp7R
webhook url: https://webhook.site/0076dfae-6184-4e7d-9309-929e68d2f531

shy ridge
#

that account acct_1JMYI1AjORjIkyJ0 is only connected to you in live mode so you don't get test mode events from it

vital frost
#

but how it's possible?

#

if it's not connected for test mode, then how can I perform any actions in test mode from our main account?

#

How to fix that issue?

shy ridge
shy ridge
vital frost
#

But we are giving both mode options to our end customers

#

And we saw that if we will connect our end customer using live mode oauth, indirectly we are getting access for test mode as well

#

and this is working in almost for all accounts except couple of like this

shy ridge
#

you must have manually done the test mode OAuth connection with those accounts then, as well as live

#

like I looked at acct_1Ihw53CScnf89tZo and it was connected in livemode on May 20 and testmode in May 30, so you probably did OAuth twice. Maybe someone at your company already asked about this quirk and learned that a testmode connection is needed and did that OAuth process again?

vital frost
#

Yes.. that possible - acct_1Ihw53CScnf89tZo account is connected twice. Because that I'm using as testing.

let me give you real customer account details who are using both mode

shy ridge
#

I don't really need any more details, I think I've given you the answer

#

but happy to look if you want

vital frost
#

Thanks @shy ridge but if you can help more - that would be great for us to clear some confusion

#

acct_19d70eAiXTXiSTir - this is real customer account

#

And I don't think - we are giving test mode oauth connection option to direct end customer...

So can you just confirm that - is this account connected for which mode?

#

Because this customer is able to doing transactions in both mode in our system

#

Test subscription: sub_1LFjfEAiXTXiSTirAwMlYCYA

#

Live subscription: sub_1LVIAbAiXTXiSTirbWBKx4my

shy ridge
shy ridge
vital frost
#

So my doubt here is - we can perform any actions in both mode but won't get test mode webhook events if account is connected only for live mode

#

Right?

shy ridge
#

that's my understanding yes

vital frost
#

Even now I understand.... even all actions won't able to perform...

shy ridge
#

here's a diagram my team mate made internally for this :p

unknown.png
vital frost
shy ridge
#

it does contradict me though I suppose so I might have misunderstood

vital frost
shy ridge
#

we don't really intend for you to do things this way, you're supposed to only do livemode things with live accounts, and do test mode things with test mode accounts. I do agree it's a bug that the Invoice there is broken, it should work but there are multiple teams at Stripe (Invoicing and Connect) and they might not be aligned

#

what it comes down to is you're supposed to connect to an account in live mode and do livemode API request on it, and if you need to test, you either use test mode on your own account, or create test mode accounts or test mode connections to accounts explicitly for testing Connect use cases. Providing both live and test mode access to your end-users is poorly supported right now since it's not a use case we really think about.

#

like I do agree with you from my perspective this should all just work, but it's just not seen that way internally and we are moving away from OAuth and these concepts overall so this unfortunately falls into the scope of 'things we'd like to improve but can't prioritise'

vital frost
#

Thanks @shy ridge for understanding our use-case & I really appreciate your time & efforts!

JFYI: Around 2-3 months ago, I reported this link broken issue only for test mode here & your team suggested us to contact support team for this. They were not able to help more due to some limitations. So we contacted stripe support team & after multiple conversions, we got final answer that it's resolved now!

image.png
#

Now I'm not able to understand - who will help in this?

#

Because now we have 2 issues

shy ridge
#

yep I mean there are bugs and that's how you report them. That screenshot talks about PaymentLinks though, not Invoices right?

vital frost
#

I think.. both same

shy ridge
#

I mean I don't know, I have zero context on what interactions you had

vital frost
#

We reported this issue

shy ridge
#

we have two products, PaymentLinks and the Hosted Invoice Page, which are separate and owned by separate teams and can have separate bugss

shy ridge
vital frost
#

yess

shy ridge
#

just whatever support agent replied to you called it "payment links" to be confusing

#

when PaymentLinks is an actual product. oh well

#

cool, then you should just reply back really and tell them it broke again as something might have regressed!

vital frost
#

sure.. we will reply back for this invoice broken link

#

& what about webhook events for test mode?

shy ridge
#

what about them? I explained the situation

#

it's not going to change, it's always been this way for years and we're unlikely to change anything

vital frost
#

but as per your diagram, we should receive both.. right?

shy ridge
#

yep, so maybe I misunderstood

#

let's re-center. Please post an exact evt_xxx that happened on a connected account and you expected to see but didn't

#

please make sure it's a recent one(ideally, today). No other information, please, just get me the Event ID evt_xxx and I'll take it from there.

vital frost
#

evt_1LVt48AjORjIkyJ0lk5aN7PX

shy ridge
#

you were using 20.120.0 recently

#

oops, wrong person

#

you only updated you webhook endpoint settings at 09 Aug 09:28 UTC to listen to invoice.paid

#

that event happened at 2022-08-12 08:17:59 UTC, so you weren't listening to that event type at the time.

So nothing to do with Connect or live/test mode quirks in that case.

#

ah no wait I can't read timestamps

#

ok, then I don't know!
ok ignore all that ^^

vital frost
#

sorry I didn't get 😄

shy ridge
#

oh no wait

#

ok you did that get that event

#

it went you to your livemode endpoin

#

as said in the image I posted

#

you recieve test mode events from accounts you're connected to in livemode

#

but they go to your livemode endpoints, not your testmode ones, that's your confusion

#

it's covered in the image I posted above and also on https://stripe.com/docs/connect/webhooks

For Connect webhooks, it’s important to note that while only test webhooks will be sent to your development webhook URLs**, both live and test webhooks will be sent to your production webhook URLs. **This is due to the fact that you can perform both live and test transactions under a production application. For this reason, we recommend you check the livemode value when receiving an event webhook to know what action, if any, should be taken.

vital frost
#

So you mean that - I will get test mode events in live mode webhook url

#

Right?

shy ridge
#

right

vital frost
#

I think.. that image is also represent same!

#

Thanks @shy ridge for helping me to understand!

#

Let me try!

#

Works @shy ridge

#

I really appreciate your continues help 👏