#gus_api

1 messages ยท Page 1 of 1 (latest)

wary helmBOT
#

๐Ÿ‘‹ 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/1369030581463027854

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

open steppe
#

hey there, as the error indicates, this is a payment intent that was created and is managed by a checkout session, you can't modify it directly like this

#

Do you have an example of a request you're doing in production today that matches this shape? I wasn't aware of this ever being allowed.

#

You can cancel payment intents that you created yourself, yes.

#

But not ones created for you via Checkout.

dim hemlock
#

Hey, I can try to replicate it in production, yes, let me check

wary helmBOT
dim hemlock
#

Here's the request ID of a payment intent that was canceled in production:

req_es7uF5wFRg1LRg

lyric swan
#

๐Ÿ‘‹ stepping in as synthrider needed to step away

#

Taking a look

dim hemlock
#

sure, no prob, thanks!

lyric swan
#

It looks like you were using the 2019-05-16 version in your test mode request. Can you try that same request in test mode with the 2020-08-27 version like you used in live mode?

#

Ah

#

Wait

#

I see

#

One sec

#

Okay I believe this was an internal configuration issue on your platform that was only applied for live mode and not test mode. I've aligned this configuration to apply to both live/test. Can you try again?

dim hemlock
#

sure

#

nop, get the same error, here's the request:

req_cihorySdzRy4Pc

lyric swan
#

That's a different platform

dim hemlock
#

oh I did the test in our testing environment yes

lyric swan
#

Ah ah sorry yeah I didn't clarify

dim hemlock
#

first you asked me in production which I did, then I did this in test mode

lyric swan
#

Yeah I didn't actually realize at first these were two separate platforms. Your production platform had only had the feature enabled in live mode so I had added it to test mode on that platform.

#

One sec, let me enable it just for test mode on your test account

#

I can't enable it for live mode there as you would need to get that reviewed/approved.

dim hemlock
#

Oh no worries, in test mode is just fine, thats all we use that platform account for

lyric swan
#

Sounds good, one sec

dim hemlock
#

sure

lyric swan
#

Okay now try again

dim hemlock
#

yup, it worked ๐Ÿ™‚

lyric swan
#

Great!

dim hemlock
#

was this something that someone on our side changed from the default or something internal to stripe? I'm just curious

lyric swan
#

Internal to Stripe

dim hemlock
#

gotcha!

lyric swan
#

The ability to cancel PaymentIntents generated by Checkout was deprecated but I believe you were grandfathered in as you were likely doing it before that deprecation.

#

Thus the internal config to allow your account to do that.

dim hemlock
#

ahhh, that makes sense! yeah cause we are doing it everyday in production

#

so now we won't, we are in the process of upgrading the API and adjusting our code

#

but as I was going back and forth with versions I noticed I wasn't able to cancel the PI on this test plaform which seemed weird (cause we could in production)

lyric swan
#

Gotcha, yep that all checks out.

dim hemlock
#

awesome, that fixes it, thank you so much Bismarck