#k3davis
1 messages · Page 1 of 1 (latest)
Specific example(s) you can share? But yes, this can happen
I can show you what the response body in our log looks like, give you some other transaction context, but I haven't been able to correlate it with anything in Stripe's logs, which is puzzling.
what would be helpful to see?
A pi_xxx ID would be great
sorry should clarify, this integration uses the Charges API
All responses look like this when this occurs
{"Charge":null,"StripeError":{"charge":null,"code":"card_declined","decline_code":"generic_decline","doc_url":"https://stripe.com/docs/error-codes/card-declined","message":"Your card was declined.","param":"","payment_intent":null,"payment_method":null,"payment_method_type":null,"setup_intent":null,"source":null,"type":"card_error","error":null,"error_description":null},"Exception":null}
Ok, then an example of an API request that fails: req_xxx
I haven't been able to find any correlating entries, as I said, but let me double-check a recent one
yeah i'm not able to find any correlating request in the logs
i suppose that points to an issue in our integration?
What's your acct_xxx ID?
acct_1Js6nhFnSqw89al6
A few examples:
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
The most recent occurrence was 2022-04-21 17:38:20.890 (CST)
All which returned a ch_xxx
2022?
ha my mistake in sorting, 2023-05-02 19:35:51.517
those look different, they have charge IDs and don't have a generic_decline code
2023-05-03 00:35:50 UTC?
yes i believe so
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Check the timestamp
the charge amount is different, this one was $500 usd
and the response code was generic_decline
We've no logs of any other requests around that time
OK, that's what i was seeing also. I think there must be a logical flaw in the integration that is logging some kind of default error response on our end that isn't actually being generated by stripe's api
i'll have to look more deeply at it in the code. thanks for taking a look.
Hi! I'm taking over this thread. Let me know if you have any other question.
the only thing left to ask is regarding the statement that sometimes a decline can be returned without a charge id; can you elaborate on what circumstances might cause this, and is there any instance where the request itself would not show up in the log?
That was under the assumption you were integrating with Payment Intents
Where there may not be a Charge object that represents a failure/decline
I'm not aware of a scenario where that would happen in a direct Charges integration like yours
OK that makes sense. thank you again.