I am not sure if this is a fault of my settings or whether this is a bug or whether this is caused by the fact that I am testing PayPal in testing mode - i.e. PayPal Sandbox.
There are three issues I have:
1) When a user orders a packages and pays with "PayPal Payments Standard" in Test Mode, Blesta did not recognized the payment was made, the Invoice is put to "Past Due" and it is just not finished, the user keeps getting those "Invoice Due" emails.
2) When the payment was done, the user was not taken back to Blesta Client area, but remained on the PayPal page. This actually happened to me when I paid for Blesta's license, so I assume this is an issue even in production environment. I am not sure whether there PayPal API supports this (but I would be very surprised if it does not), but if yes, I think it should be implemented and if not then it might be a good idea to change the anchor's "target" attribute of that PayPal button to "_blank" so that Blesta page keeps existing in the user's browser and it then it would be great if Blesta detected the payment user just made and refreshed that page after that to something that makes sense in the particular context - "Thank you for your purchase" or something like this.
3) When the PayPal payment web page is loaded after clicking the payment button from the Blesta's order page, the user is allowed to enter the name of the item (This also happended to me when I paid for Blesta's licence). I would rather want to have the name of the item fixed by the package/product creator, not by the client.
Could any of these issues be mitigated using some kind of settings I have missed?
Question
dait
I am not sure if this is a fault of my settings or whether this is a bug or whether this is caused by the fact that I am testing PayPal in testing mode - i.e. PayPal Sandbox.
There are three issues I have:
1) When a user orders a packages and pays with "PayPal Payments Standard" in Test Mode, Blesta did not recognized the payment was made, the Invoice is put to "Past Due" and it is just not finished, the user keeps getting those "Invoice Due" emails.
2) When the payment was done, the user was not taken back to Blesta Client area, but remained on the PayPal page. This actually happened to me when I paid for Blesta's license, so I assume this is an issue even in production environment. I am not sure whether there PayPal API supports this (but I would be very surprised if it does not), but if yes, I think it should be implemented and if not then it might be a good idea to change the anchor's "target" attribute of that PayPal button to "_blank" so that Blesta page keeps existing in the user's browser and it then it would be great if Blesta detected the payment user just made and refreshed that page after that to something that makes sense in the particular context - "Thank you for your purchase" or something like this.
3) When the PayPal payment web page is loaded after clicking the payment button from the Blesta's order page, the user is allowed to enter the name of the item (This also happended to me when I paid for Blesta's licence). I would rather want to have the name of the item fixed by the package/product creator, not by the client.
Could any of these issues be mitigated using some kind of settings I have missed?
10 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.