#CollDoug
supple cedar
fickle cape
Can you provide an example of that? What kind of issues are happening?
Payment Intents are our current API to use rather than Charges, but existing Charges integrations can continue to operate
What exactly are you looking for/ what do you need help with?
You can read about the API differences here, which was documented when we launched Payment Intents in 2019
https://stripe.com/docs/payments/payment-intents/migration/charges
empty seal
So it looks that every payment over $100 does not get through to the POS, they charge in Stripe/from the customer's account but stay stuck in Pending status, so the restaurant never receives the order
We've tried recreating the products and categories that are mapped with Order Ahead in case there was a glitch somewhere there, but now it appears the pattern is that all orders over $100 are not successful. Only the ones under $100 are, and it doesn't seem to make a difference from what customer they're doing the ordering.
fickle cape
Is Order Ahead your platform, or something else you use?
Can you provide any of the payment IDs from those examples?
eg pi_123 or ch_123?
empty seal
It's a Lightspeed product for online ordering - the customer orders via Order Ahead landing page - payment goes through Stripe - order comes from cloud to the iPad so restaurant receives the order
Let me check!
Doesn't appear I have visibility on the payment IDs from the back office, just the info in the screenshot I sent over
fickle cape
Ah, well if this is all via Light Speed's platform you'd need to speak to them. I'm not clear why the API changes would affect your use of the platform service, though.
empty seal
I asked the devs on our end if I can access web logs for more info but waiting on the product manager to give me final word
fickle cape
If this is something that involves an API integration on your side to Light SPeed, your dev team will want to work with LS on sorting out the required changes
empty seal
No me neither, and the part about an email being sent 3 weeks prior threw me off a bit. Does anyone from API know about that part?
I'm requesting a PID from the customer for one of the recent ones that's failed - could you possibly take a look at this from your end to see if there's more info on it at all? 🙂
this is the info customer sees on Stripe portal for a failed transaction (customer was charged successfully, however) - I don't see a PID on there
fickle cape
There should be an id on that page, either in the top right corner or the URL
empty seal
Asking customer to check there! BRB
Here is what they found: ch_3M7iDWBadFY9qSwR0nnV6fJT
fickle cape
Sorry just looping back here, this charge looks to have been successful so the issue might just be with the representation on the platform you use