#david2_api

1 messages ¡ Page 1 of 1 (latest)

little siloBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1326598410605695081

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

surreal geyser
#

Hello! You can look at your API request logs to find the latest confirmation request.

latent pasture
#

is there an api for that? or that is only on dashboard?

surreal geyser
#

There's no API, you'd need to look in the Dashboard.

#

That said, why do you want to know? What's your goal? Maybe there's another way to accomplish whatever you're trying to do.

latent pasture
#

ultimately I was trying to record the "payment submission date" from within a "payment_intent_processing" webhook for ACH payments. I'm not sure what kind of delay I can expect between time-of-payment-confirmation-request-submitted to time-of-payment-intent-processing-event-received

surreal geyser
#

Can you give me the ID of one of those Events so I can take a look? It's the ID that starts with evt_.

latent pasture
#

(and if I error or etc. then webhooks will be handled potentially hours after the fact and I need the submission timestamp, not timeof webhook receipt timestamp)
evt_3Qf2WNAQbHn4ElzT2PuNmYQo

surreal geyser
#

You can look at the created property of the latest Charge associated with that Payment Intent.

latent pasture
#

is there a guarantee that that a charge is created exactly (or within a few hundred milliseconds...) at the timeof submission of the paymentIntent confirm request?

surreal geyser
#

The Charge is created as a result of the confirmation request. More specifically, that specific Charge represents that specific attempt to pay the Payment Intent.

#

So, in this scenario, yes.

latent pasture
#

cool, sounds good and proper. Now for the hard part: is there a document somewhere that states as such?

surreal geyser
latent pasture
#

Something to the effect of: "As a result of a single invocation to payment_intent.confirm returning a 200 status code, exactly 1 charge object will have been created" , I think the above docs lean in that direction, if they don't outright say it.

#

anyway, good info here, thanks for your time