#mark.simpson
1 messages ยท Page 1 of 1 (latest)
relevant links are of the form: ```
payment on dashboard: https://dashboard.stripe.com/acct_<acct-id>/payments/ch_<charge-id>
log of posted charge: https://dashboard.stripe.com/acct_<acct-id>/logs/req_<req-id>
Can you share that chargeID please ?
ch_3MoC4wCkhSJ9MBxk0SexHtl8
Thanks for sharing, checking...
How are you accepting the payment in your platform ?
I believe when we create the charge (via the stripe api) we are auto-accepting it
Hi there ๐ jumping in as my teammate needs to step away soon. I'm not sure offhand why the dashboard doesn't seem to be showing the same details as the rest of the process. Just making sure I'm understanding correctly, you're saying when looking at the Charge via the API you do see that the zip check was completed, but you don't see that same detail when viewing the charge via the dashboard?
Not quite. When I access the charge via the Stripe APi or via the payment screen on the dashboard i see 'Unavailable' (screen) or 'unchecked'/null (api). But looking at the posted charge log page i see 'pass'. Also i belive that near to the time when the charge was creaed (21 March 2023) my application ran a report and saw that the verifications were both 'pass' via the API.
Can you help me understand how you're retrieving the Charge from the API that is showing the checks weren't completed? Do you have a request ID for that?
I am using the ruby stripe library function: Stripe::Charge.retrieve giving it the charge id and the connected account id. I'm not sure what you mean by request id.
Apologies, by request ID I was referring to the ID that is generated for each request made to the Stripe API:
https://stripe.com/docs/api/request_ids
https://support.stripe.com/questions/finding-the-id-for-an-api-request
It will likely take me some time to do as the server is a bit busy, but could you provide me with full steps to reproduce the behavior that you're seeing so I can try to replicate on my end?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
So looking at hte Dashboard alone this URL https://dashboard.stripe.com/acct_1MON3ACkhSJ9MBxk/payments/ch_3MoC4wCkhSJ9MBxk0SexHtl8 shows 'Unavaiable' for Address / Zip verification but this URL https://dashboard.stripe.com/acct_1MON3ACkhSJ9MBxk/logs/req_OvNyocliaV6o4r shows pass in the response body shown.
(The call to the stripe api shows the same data as the first URL).
Why are these two dashboard screens showing different data?
I don't know offhand, my team focuses on helping developers work with our API which is why I'm trying to understand whether the API is showing you consistent and correct information. If the concern is purely with how the dashboard is showing this information, I would encourage you to report that behavior to our Support team for review:
https://support.stripe.com/?contact=true
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Ah, sorry. I'll ask there. thanks.