#Reuben
sleek agate
Hello! Let's keep everything in this thread:
- Is there a way to track what emails have been sent from Stripe to a customer? Specifically, I'd like to find logs related to emails sent for failed charge attempts.
- Is there a way to receive information about the issuer or bank related to a charge attempt either via the API or from an emitted webhook event?
- How can I trigger an invoice.upcoming event when using a test clock? I've tried a couple of ways but have been unsuccessful so far.
a. Attempted to set the test clock to the date exactly equal to the day on which the invoice.upcoming event would have been sent in a real scenario (example would be 3 days before the billing period ends.)
b. Attempted to set the test clock to the date of the next billing period.
sly walrus
sounds good!
sleek agate
For #1, I don't think we have logs for that in the Dashboard... there might be something on the Customer detail view, but I'm not certain (we're not Dashboard experts here).
For #2, what information are you looking for specifically?
sly walrus
For #2, specifically just want access to the issuer/bank for a charge
sleek agate
For #3, those approaches should have worked. Are you using Subscription Schedules by chance? Can you provide more details about the exact steps you're taking?
sly walrus
we can see it in the UI but have been unsuccessful seeing it programatically on an event or API call
sleek agate
Not sure I understand? You see the Event in the UI? Can you give me the ID of one of them (starts with evt_)?
For #2 you would need to contact Stripe support and ask them if it's possible for you to get access to that information: https://support.stripe.com/contact/email
sly walrus
Hi @sleek agate , my apologies for the delay. For #2 -- to clarify, the UI that displays a payment shows the issuer but we can't see that in the event data. An example id (taken from a test account) is: pi_3N44RNLfPKSAcX8W3MJHPZNM
For #3, we are not using subscription schedules. The exact steps we're using are: (a) setup a test clock and test customer. (b) create a subscription for the test customer. (c) advance the test clock forward (either to 3 days before the end of billing period or to the end of the billing period). Note that no invoice.upcoming event is emitted
sleek agate
Yeah, in order to get that info in the API you need to ask support if you can get access.
sly walrus
we are making sure that the billing period is greater than the minimum required for emitting the invoice.upcoming event
Got it. Thank you for the tip on asking support and I"ll do that
sleek agate
That process should work to emit that Event. Do you have a Subscription ID I can take a look at?
sly walrus
Sure thing. A subscription ID we are using is: sub_1N3n4GLfPKSAcX8WxRxSmCqc
(again in test mode)_
clever cradleBOT
sleek agate
Looking...
robust jacinth
Still looking in to this. As far as I can see that event really should get sent here. I will try to reproduce this myself. Sometimes there can be things that don't get simulated properly with test clocks. It should support this event as far as I know but it could be an edge case with something else that I need to file a bug report for. Will get back to you with what I can find.
sly walrus
Thank you
robust jacinth
It is working for me with my own subscription and test clocks. Have you run this multiple times and it hasn't worked for any of them? I can look for differences between our setups if so. It is also possible that the test environment had a one time fluke here though usually we do send these events afterwards if they were temporarily held up
clever cradleBOT