Paypal Javascript Button data-notify-url Instant Payment Notification - paypal

Can we use data-notify-url attribute to received IPN?
script(src='paypal-button.min.js?merchant=username#email.com', data-button='buynow', data-name='My product', data-amount='1.00', data-env='sandbox', data-notify_url='http://example.com/ipn')
The payment was successful but it seems specified notify_url wasn't called.
I also used Instant Payment Notification (IPN) simulator and enter my notify_url but encountered the error below:
IPN Delivery Failed:503 Service Unavailable
But looking at the logs of my application, I can see the notify_url was called.
I used web accept as transaction type.

This just looks like your Backend-Script (may it be PHP or anything else) is currently not available.
It can happen due to a server overload.
The 503 is a HTTP-ErrorCode so it has nothing to do with PayPal. PayPal tries to send the IPN to you and your web-server responds with a 503 error.

Related

What happens to paypal IPNs if no message sent back to PayPal

For a while I have been running a site which logs paypal transactions by sending a notify_url to the paypal site, and listens in on that notify_url. My listening page parses the IPN info sent from paypal, and returns an http 200 response, but it doesn't then "send the complete message back to PayPal using HTTPS POST" to https://ipnpb.paypal.com/cgi-bin/webscr (point 3 at https://developer.paypal.com/docs/classic/ipn/integration-guide/IPNImplementation/). The payments seems to have been going through OK. I want to know what problems I have been storing up for myself by not doing this response part of the IPN request-response flow?
You have laid yourself open to accepting IPN messages that may not be from PayPal. The purpose of the message you're omitting is to ensure that the IPN you are processing came from PayPal.

PayPal Instant Payment Notification Warning

We always get this message from paypal. The payments are going in and the url in the message is correct.
Is there a way to stop these messages?
>Please check your server that handles PayPal Instant Payment
>Notifications (IPN). IPNs sent to the following URL(s) are failing:
>
>http://sitename.com/payment/postbackPaypalSignUp/
>
>If you do not recognize this URL, you may be using a service provider
>that is using IPN on your behalf. Please contact your service provider
>with the above information. If this problem continues, IPNs may be
>disabled for your account.
>
>Thank you for your prompt attention to this issue.
>
>
>Thanks,
>
>PayPal
IPNs to that URL are failing. You can see the log somewhere at PayPal. You must fix your IPN handler. Check its logs too.

Is there an IPN sent after DoExpressCheckoutPayment?

After we do DoExpressCheckoutPayment - resulting in payment status Completed or failing with some other status - is there any IPN sent from PayPal?
Yes, DECP sends IPN notifications. If you're not getting them make sure you have IPN enabled either through your profile or by the NOTIFYURL parameter in your request. Then check the IPN History in your PayPal account and your web server logs for details on whether or not the script is getting hit or not, and if there might be an error keeping it from running correctly.

PayPal IPN Failing

I got an email from paypal saying:
>Hello <>,
>Please check your server that handles PayPal Instant Payment
>Notifications (IPN). IPNs sent to the following URL(s) are failing:
>
>url--
>
>If you do not recognize this URL, you may be using a service provider
>that is using IPN on your behalf. Please contact your service provider
>with the above information. If this problem continues, IPNs may be
>disabled for your account.
>
>Thank you for your prompt attention to this issue.
>
>
>Thanks,
>
>PayPal
Is anyone familiar with this? We got 1 payment that made through today, it updated the database and all but still I am concern if this email will be a threat to our website.
I tested the IPN url using the IPN stimulator and it worked fine. Should I need to change my IPN setting? Some forums are saying to turn off the IPN notifications. Should I assume that this is coming from the server refusing to accept the Paypal IPN? I'm so confused on what to do with this problem, let alone my client also knows.
I checked my site error logs but I couldn't find any new errors related to the my paypal IPN listener.
thanks,
If the warning message you are receiving is showing "url--", you may want to double check:
- the value set up in your PayPal Profile > Instant Payment Notification
- or the value you have inserted in your integration in the variable "notify_url" (if you are using Website Payment Standard or "PAYMENTREQUEST_n_NOTIFYURL" (if you are using API).
When you receive an IPN warning message, I'd recommend to check your IPN history (in your PayPal account) to check what is the HTTP response that your server is returning to PayPal.
You can test your IPN listener here
Find IPN overview here

PayPal Instant Payment Notification (IPN) Issue: PayPal sends VERIFIED response but has FAILED status in IPN History. 404 Error

PayPal is sending the VERIFIED message to my IPN listener but my IPN History shows a FAILED status. The IPN History also shows a 404 error. The code I am using for my listener can be found here: https://cms.paypal.com/cms_content/US/en_US/files/developer/IPN_PHP_41.txt. I am testing this with sandbox. How can I be receiving a VERIFIED response from Paypal but yet the IPN History shows a failed STATUS with a 404 error? Shouldn't PayPal be sending an INVALID response since the IPN History status is failed?
VERIFIED has nothing to do with how the transactions appear in your ipn history. How you respond to the original ipn post is what determines what shows in your ipn history.
If your ipn history says it's receiving a 404 response, then you need to check your ipn script and stop sending a 404 response.
If it were any other error, since you are using PayPal's script, I would bet you didn't change the environment variable/the URLs to match your environments. With a 404 though, you're telling the client (paypal in this case) that the page they want doesn't exist, even if you're still reading the data