#Pickle_Rick - Payment Confirmations
paper zodiac
Hello! What exactly do you mean by "no confirmation was sent back?" That could be various things, so specific details would be very helpful. 🙂
Can you give me the Payment Intent ID so I can take a look?
oblique stream
Hi there,
Sure so stripe confirms that a payment intent either succeeds or fails - our system was waiting for that
pi_3JuQSWDV2WR4Y5rU2jTFhZ5P
Thank you for your reply 🙂
paper zodiac
Your system was waiting for it how? By listening for an event with a webhook endpoint?
It looks like you don't have any webhook endpoints set up to listen for events... are you relying on your client-side code to trigger fulfillment?
oblique stream
Sorry checking this now
paper zodiac
If that's the case you should not be relying on client-side code to trigger fulfillment, as the client-side code cannot be trusted to run. You can read more about this here: https://stripe.com/docs/payments/payment-intents/verifying-status#webhooks
oblique stream
Hi there, thank you for your patience and sorry for the delay
We are using the Stripe service on Angular- we call "confirmCardPayment" with the client secret and payment method and wait for a response
The response either succeeds or fails - this did not happen in this case. The system was left hanging.
So the user tried to process the card a second time with the same payment intent.
paper zodiac
That can happen if the client experiences a network issue, meaning the request to confirm the Payment Intent made it to Stripe, the Payment Intent was confirmed successfully, but the response going back to the client didn't make it for some reason.
You should do two things:
- Read the link I provided above about webhooks and fulfillment and update your integration to not rely on client-side code
- Update your client-side code to better handle the case where the same Payment Intent is confirmed two or more times and display a "payment successful" message to your customer if that error is encountered (since the payment already succeeded)