#bwurtz999-terminal-expand

1 messages ยท Page 1 of 1 (latest)

mighty summit
#

Hey there ๐Ÿ‘‹ do you have the request ID associated with this request?

civic mango
#

yup!

#

req_FmGbUGVGcAM85N

mighty summit
#

Awesome! Bear with me a moment while I pull that up.

civic mango
#

You still there toby?

mighty summit
#

I am, consulting with colleagues.

civic mango
#

thanks!

mighty summit
#

Apologies for the delay, we're still looking into this!

civic mango
#

that can't be good haha

pliant tundra
#

It's fine, I'm pretty sure this is just a backwards compatibility thing but I'm trying to test on my own reader

civic mango
#

yeah it's the old P400 reader

#

but it was purchased this year

pliant tundra
#

Yea mine does this too, and has no use of legacy sources at all

#

so unless this is causing an issue for you for some reason, i'd say you can safely ignore it

civic mango
#

well based on what I can see in my logs it looks like this request was sent when it should have been a request to confirm the payment intent

#

pi_3JiIkTCXMuDrMdnf1t4d7qjr

#

the items had been added to it (total of 285)

#

and then this request came from the reader

#

this happens a few times per day for me

#

not a lot, but I'd like to figure out what is causing it

#

because then I get an error when I try to capture the payment intent because it doesn't have an attached payment method

pliant tundra
#

That's going to be unrelated, i would expect

#

is this payment intent an example of that?

civic mango
#

oh wait you're right

#

sorry

pliant tundra
#

np ๐Ÿ˜„

civic mango
#

thanks for looking into this

pliant tundra
#

absolutely ๐Ÿ™‚ let us know if you encounter any problems as you go forward

civic mango
#

I have a few years before I need to upgrade my readers, right?

#

you mentioned this was a backwards compatibility thing

#

I'm assuming for the new readers

pliant tundra
#

I haven't heard about any timeline for that, so i would expect it to be supported until you're notified about any future change