Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed Payment Email #1

Open
paulsusnet opened this issue Nov 30, 2017 · 5 comments
Open

Failed Payment Email #1

paulsusnet opened this issue Nov 30, 2017 · 5 comments
Assignees

Comments

@paulsusnet
Copy link

paulsusnet commented Nov 30, 2017

Hey, firstly I would like to say thank you, I've been searching for the answer to this for a long time. I've been testing it tonight with PayPal Sandbox mode on my Magento and I'm delighted to say it does indeed redirect the customer back to PayPal, gives them the reason why and let's them pick an alternative payment type. Awesome!

What I'm about to ask is maybe more a feature request rather than an issue.

Is it possible for Magento to still send me the failed payment notification email when a customer gets to that point?

This way I will see a failed payment notification email, then hopefully shortly after I will see the confirmation email for the order after the customer has updated their PayPal.

I will know it's working with this included, I also still like to know how many customers have this problem.

@LukeLeber
Copy link
Contributor

Hi @paulsusnet,

I'm going to update the code to dispatch an event when a user falls into this condition. This will let things be handled in a very flexible way that can be custom tailored to fit the needs of many different store owners, while still keeping the logic in the extension simple and easy to understand.

As a concrete test case, I'll also create an extension that will act as an observer that will send emails and throw that into a repository on this Github account as well. When I get things finished up, I'll close this issue so you'll get a notification.

Thanks,
Luke

@LukeLeber LukeLeber self-assigned this Dec 4, 2017
@paulsusnet
Copy link
Author

Sounds great Luke :)

I've now been running your solution for 5 days, randomly last night I received 2 failed notification emails for 2 different people. At first I was in a panic thinking that something was wrong but after looking through the logs I noticed that the emails related to different error codes.

Case 1 - The buyer got the usual 10486 error and was transferred back to PayPal as expected. At this point I'm not exactly sure what they did but they tried again and got this error code: 10004

[L_SHORTMESSAGE0] => Internal Error
[L_LONGMESSAGE0] => Transaction refused because of an invalid argument. See additional error messages for details.

The customer then completely changed the Payment type to SagePay and completed the order by manually entering their card details.

So a little confusing with the second error but overall I guess this was a success, the customer at least realised that the issue was at their end and was able to pick an alternative way to pay.

Case 2 - The buyer got the following PayPal error: 10606

[L_SHORTMESSAGE0] => Buyer cannot pay.
[L_LONGMESSAGE0] => Transaction rejected, please contact the buyer.

According to PayPal the cause is:
The credit card being used can't be used on the PayPal system.

The buyer left and no order was completed.

So I'm still trying to learn what all these errors really mean, I've been getting the failed notification emails a long time but I've only recently turned on the PayPal Express debug logs to see the error codes and messages. I always assumed the failed notification emails was for the same reason, but looks like it can be for a range of reasons.

I think a great addition to your plugin would be if we could have a custom message and link for all other PayPal error codes. So in my case I would have it say there's is an issue with PayPal and that they should try checking out with SagePay and then a link back to the checkout page.

@paulsusnet
Copy link
Author

Weirdly I've had another failed payment notification tonight, this time Error code: 10485
[L_SHORTMESSAGE0] => Payment not authorized
[L_LONGMESSAGE0] => Payment has not been authorized by the user.

This happened for the lady twice, then about 30 minutes later she come back and completed the order with PayPal first time. I guess the logical reason is that there was something wrong with her PayPal, she went away and updated it and come back. But the thing that's worrying me is the PayPal cause for this error says:

"The payer wasn't redirected to PayPal, so the user didn't authorize the payment."

Could just be a coincidence but getting 3 failed orders in 2 days is more than normal, usually it was 1 or 2 a week.

@paulsusnet
Copy link
Author

Hey,

Thought I would follow this up. I've not heard any more from you, I'm sure you have more important things to do than update this module haha!

Things have been good recently, looking at the logs I've only had 1 failed order in a few weeks. The person must have been transferred back to PayPal and given the reason for the failure and then left.

Still would be nice to have a notification email, we could then chase up these customers and see if there's anything we can do to help them complete their order.

If you get a chance to have a look I would be grateful but I understand if you don't, I'm still very thankful for the work you did on this module.

Have a good Christmas.

Paul

@LukeLeber
Copy link
Contributor

Hi @paulsusnet ,

Sorry for the radio silence over the holiday season and beyond. I've put in quite a bit of my own personal time to get up to speed with the new Drupal 8 framework that is being used for a new project at work.

I'm working toward getting a proper Travis CI build system set up for this repository, since it's been about a year since I've last worked with Magento. In fact, this module was first built in November, 2016 and I need to make sure that it still works with the Magento versions that have been released since then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants