#Avery246813579 - Terminal
neon spade
Server side Javascript
When I say the terminal payload I mean the pi payload from the webhook
spice hornet
What webhook event?
neon spade
payment_intent.succeeded
spice hornet
Do you have example event IDs for each behavior? These start with evt_
spice hornet
Or Payment Intent IDs pi_
neon spade
pi_3Lb4z0AcqRxm04BK0YTHyjYC - Returns 0 (Reader version - 2.3.3.0)
pi_3Lb4ulAcqRxm04BK14mMXIdN - Returns undefined (Reader version - 2.6.2.0)
Check the confirm response, they are different but with same code on our end. Seems the reader versions are different as well since the card removal animation is different but no updates are available.
This is kinda a sev 1 on our end. Totally just broke out checkout flow.
There is no other way during checkout to know if it was reader side tipping besides tip amount being set to something
spice hornet
That was the first thing I noticed. The /confirm call on the second PI is passing an amount_tip parameter while the first PI is not. So the shape of the response makes sense.
neon spade
That's done by Stripe. We don't handle that
That's all done by the reader
We just pass the payment intent to the reader and wait for the payment_intent.succeeded webhook
spice hornet
WHen you say reader version, are you referring to the firmware? For which reader?
neon spade
Wise POS E. Just the version that shows when opening the sidebar
spice hornet
Thanks.
Okay I reached out to the team behind this and it appears either you or someone else from your company reached out to our Support team for this issue.
neon spade
yeah I reached out with our internal contact but they usually say go to discord help so I wanted to hit it from both angles
should I just talk with my internal contacts?
spice hornet
The team that handles this is working on the issue through your internal contact presently. It's not something I can relay easily.
neon spade
All good! Thanks for the help!