#wafflcoptr_api

1 messages ¡ Page 1 of 1 (latest)

cyan nightBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1261156288352751647

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

lucid pike
#

Hi, looking into this

quasi bay
#

Might help to compare the confirm api call from
contactless_emv: req_5RLRFbWSnLJjfL
to
contact_emv: req_Q7tfsDjs6yrJQD

lucid pike
#

Hi could you clarify on each flow which reader you are using?

#

Are both WisePosE?

quasi bay
#

Yup same WisePosE terminal was used for both tansactions

cyan nightBOT
lucid pike
#

In the case of contact_emv, did you insert the card in, then only after 2 minutes you received the terminal.reader.action_succeeded webhook event or the payment_intent.succeeded webhook event?

quasi bay
#

Yes contact_emv was when I inserted the Stripe test card. Then on the dashboard I notcied that the payment_intent.succeeded only occurs after about 2 minutes.

chilly cairn
#

give us a while to take a closer look

#

hrm, does this long processing time happen fairly consistently?

quasi bay
#

we have noticed it in the past too
infact we have been avoiding insert and swipe payments because of it but we are trying to make it work due increased customer requests

#

our backend currently does not support payment intents going into a processing state which from my understanding should not happen for card payments?

chilly cairn
#

that guide you are looking at is more pertinent for online payments. card_present payments (i.e. Terminal) does have a processing as you've probably noticed from the events

#

can you write in via https://support.stripe.com/contact/email with a couple more PaymentIntent examples where you are seeing such a long processing time. Once you've done that, let me know and I'll put a note on the support ticket so that it can get routed to the right team. The processing time seems to be occurring on our (Stripe's) end and we'll want to investigate further.

quasi bay
#

ok just to summarise contact_emv payments going into a processing state is expected bahviour but processing times of ~2min is not?

#

do you have any guidelines on what Stripe aims the processing times for this types of payments to be?

chilly cairn
#

yes, contact_emv payments going into a processing state is expected behaviour. A processing time of ~2 mins is definitely very very long, and not expected. We don't have any guidelines of what the processing time should be

quasi bay
#

ok support request sent

chilly cairn
#

found it! We'll keep you updated via the support ticket