Could you please provide the piece of code you're running on your checkout page. Do you call RequestPayment() ? That should take care of everything, including redirection to the gateway and back again.
Checkout should not be called on your checkout page. It is a bit confusing, however checkout() will run the checkout pipeline (which is the pipeline that should be run after you get back to the shop from the payment gateway). That should not be used in standard implementations of paymentproviders in uCommerce.
it would seem you've slightly mis-understood my question here.
Your last comment:
"Checkout should not be called on your checkout page. It is a bit confusing, however checkout() will run the checkout pipeline (which is the pipeline that should be run after you get back to the shop from the payment gateway). That should not be used in standard implementations of paymentproviders in uCommerce. "
Is exactly what im already doing, i call Request payment. the user is sent off to the payment method (in this case its paypal)....but they make their payment and close the browser down WITHOUT allowing or reading any comments or notices about needing to come back to the site via paypal to finish the process. I.e calling Checkout on return.
This means the method of checkout is never called because they dont allow the browser to come back.
If i follow the process and follow the insructions and allow paypal to return me, all is fine and the full sequence of events fun no issues. There must be a way to FORCE the user back rather than just relying on them to return and not close the browser when they get the paid message from paypal. Paypal DOES forward me back to the site...but it does that 5 second sort of thing. I believe its in this time the user is closing the browser.
Do you have a test site where i can test this ? With some test data.
I understand the question now. However if that's on paypals payment page i don't think you could do anything. But i haven't worked with paypal before so of course i can't tell for sure.
Sorry no we dont have external access for you to try.
I have tried ideas of putting the requestpayment within an iframe on he customers website to control the ability of closing the page. But that didnt go too well due to how umbraco loads the pages. If you can think of a simular theory that could work id love to hear it.
Or is there some kind of setting or param to send or set within the paypal account which on closing the tab/browser throws a warning the process is not complete and the user must follow through to the end back to the website etc etc.
Sorry no we dont have external access for you to try.
I have tried ideas of putting the requestpayment within an iframe on he customers website to control the ability of closing the page. But that didnt go too well due to how umbraco loads the pages. If you can think of a simular theory that could work id love to hear it.
Or is there some kind of setting or param to send or set within the paypal account which on closing the tab/browser throws a warning the process is not complete and the user must follow through to the end back to the website etc etc.
CommerceLibrary:Checkout() before user closes browsers during payment
How do you stop users from closing the browsers while in the paypal payment stages of the process.
It seems some customers are making their payment, thinking they have completed their order and closing the browser.
Anyone got any ideas??
Thanks
Hi Deano,
Could you please provide the piece of code you're running on your checkout page. Do you call RequestPayment() ? That should take care of everything, including redirection to the gateway and back again.
Checkout should not be called on your checkout page. It is a bit confusing, however checkout() will run the checkout pipeline (which is the pipeline that should be run after you get back to the shop from the payment gateway). That should not be used in standard implementations of paymentproviders in uCommerce.
Hope that helps.
Regards
Morten
it would seem you've slightly mis-understood my question here.
Your last comment:
"Checkout should not be called on your checkout page. It is a bit confusing, however checkout() will run the checkout pipeline (which is the pipeline that should be run after you get back to the shop from the payment gateway). That should not be used in standard implementations of paymentproviders in uCommerce. "
Is exactly what im already doing, i call Request payment. the user is sent off to the payment method (in this case its paypal)....but they make their payment and close the browser down WITHOUT allowing or reading any comments or notices about needing to come back to the site via paypal to finish the process. I.e calling Checkout on return.
This means the method of checkout is never called because they dont allow the browser to come back.
If i follow the process and follow the insructions and allow paypal to return me, all is fine and the full sequence of events fun no issues. There must be a way to FORCE the user back rather than just relying on them to return and not close the browser when they get the paid message from paypal. Paypal DOES forward me back to the site...but it does that 5 second sort of thing. I believe its in this time the user is closing the browser.
Hope this makes sense.
Surely someone has come across this before?
Thanks
Dean
Do you have a test site where i can test this ? With some test data.
I understand the question now. However if that's on paypals payment page i don't think you could do anything. But i haven't worked with paypal before so of course i can't tell for sure.
Regards
Morten
Sorry no we dont have external access for you to try.
I have tried ideas of putting the requestpayment within an iframe on he customers website to control the ability of closing the page. But that didnt go too well due to how umbraco loads the pages. If you can think of a simular theory that could work id love to hear it.
Or is there some kind of setting or param to send or set within the paypal account which on closing the tab/browser throws a warning the process is not complete and the user must follow through to the end back to the website etc etc.
Thanks for your response
Deano
Sorry no we dont have external access for you to try.
I have tried ideas of putting the requestpayment within an iframe on he customers website to control the ability of closing the page. But that didnt go too well due to how umbraco loads the pages. If you can think of a simular theory that could work id love to hear it.
Or is there some kind of setting or param to send or set within the paypal account which on closing the tab/browser throws a warning the process is not complete and the user must follow through to the end back to the website etc etc.
Thanks for your response
Deano
is working on a reply...