Profile: wize1
I can't the problem happens in rare cases, but when it happens customers are very unhappy and claiming that we trying steal they money, because money taken and order not created.
Support wrote:
No, your issue is in another place.
Nopcommerce can't create the nop order.
You use the native onepage checkout, it means that customer addresses were validated in the one of checkout steps.
Do you see any error message in the nopcommerce log?
Nope :(
Support wrote:
Stripe changed the logic and sends webhook at once after payment but nopcommerce didn't create the nop order yet.
I added the timeout in the webhook handler.
Can you upgrade the plugin and check this issue again?
Where do i find fixed version? i only see 3.07 which im using now
Support wrote:
I'm using native nopcommerce one page checkout.
Hi again,
I'm glad to see you fixed some of bugs since we last spoke.
But I have one more for you to squeeze.
So here is scenario:
1. POST /v1/payment_intents 200 OK
- PaymentIntent status: requires_confirmation
2. WEBHOOK payment_intent.created - NOT SENT AS PER CONFIG
3. POST /v1/payment_intents/pi_1IkAv.../confirm 200 OK
- PaymentIntent status: requires_action
4. WEBHOOK payment_intent.requires_action - NOT SENT AS PER CONFIG
5. POST /v1/payment_intents/pi_1IkA.../confirm 200 OK
- PaymentIntent status: succeeded
- 3D Secure succeeded
6. WEBHOOK charge.succeeded - NOT SENT AS PER CONFIG
7. WEBHOOK payment_intent.succeeded - SENT, BUT FAILS
So payment_intent.succeeded webhook fails, because it nopcommerce does not have order by order guid specified in webhook. So the there is no order, but money is charged.
Im not sure what workflow you have in your plugin setup, at which point do you create order? Because in my case order is not created, but money is charged.
Regards, Dmitri
Customer
Sorry for later reply, it is all sorted now. Thank you.
Support wrote:
You will see the new parameter on plugin configure page.
Write me about result.
Sorted ... thank you...
But I have another request/idea which will make this plugin stand out from competitors. Is to add functinality for saving cards, I had that on my old plugin (you will need to save and list source and customer) in order to achieve that.
Finally found time to test it...
So the main issue is solved, well done!
Two things i noticed though:
1. I think error message from payment shoud only show message part to customer instead of this:
Error. Stripe error: Card Error. code:expired_card, message=Your card has expired.
2. It ether needs to be focused on error message, or what would be better solution is on error it should step back to payment details, show error below credit card details and focus on credit card textbox. Because our experienced show customer click on confirm dont see error message, so they click again and again thinking button does do anything they just close browser and we loose order and customer.
- 1
- 2