#Brittany

1 messages · Page 1 of 1 (latest)

small crownBOT
quick ether
#

Can you share an example request ID?

#

eg, req_1234

real pawn
#

sure, let me check.

quick ether
#

Is the client using a very old API version?

#

Prior to this version change, charges would be paid instead of succeeded

#

Updates the status property on the Charge object to have a value of succeeded for successful charges. Previously, the status property would be paid for successful charges.

real pawn
#

I'm actually an integration product manager so I reached out to our developers to get the request ID. But is the API version set on the client level on their Stripe account? I thought the API version is just based on our how our system is sending that data and we are using the Charges API for all of our clients. But if I'm misunderstanding that, then that could be the problem.

#

We basically have a plug-in for the Stripe payment processor that just gets configured for the client's account. We ran some tests on other client accounts that are using Stripe without issue. We are only having an issue when configuring this new client's Stripe account.

#

And our developers said that the status response is why we aren't logging the transactions as completed on our side. But it's a little confusing why we would only be seeing that response for this particular client.

quick ether
#

Depends how things are initialized or what exactly you're looking at, but I suspect this is the explanation one way or another

#

Could be the API version of the request/response, or possibly the API verison of the webhook endpoint if you're looking at webhook notification data

real pawn
#

Ok, I'll have them dig into this some more. I appreciate your help!

quick ether
#

NP!

real pawn
#

they sent me a charge ID... is that helpful or do you need request ID?

#

sample charge Id returning "paid": ch_2NIGIQLTjkuIHFd70me7nk9T

quick ether
#

Yep, that charge was created using a very old API version

real pawn
#

Ok, well that is great to know

quick ether
#

So that's what's happening here (and we can dismiss the webhook theory)

real pawn
#

Excellent

quick ether
#

The solution as you say is to make the requests with a more recent API version, or handle the old status paid

real pawn
#

Ok, so back to a previous question, so I'm clear... can the client control their own API version somehow? What would I instruct them to do to update that since it's their account?

#

I don't have access to log into the client's stripe account unfortunately

quick ether
real pawn
#

👍