Web-hook API Issues about paypal-node-sdk HOT 44 CLOSED

Is this happening on both sandbox and the live environment?

from paypal-node-sdk.

These errors are in the live environment. I have not been able to test web-hooks properly on the sandbox environment as there's not a way to send eCheck payments. Refunding a sent payment also seems to not trigger a web-hook on sandbox either.

from paypal-node-sdk.

Hey @night there is active work going on to fix the intranet URL issue and we will keep you updated here. We will try to get you more feedback on the remaining issues as well.

from paypal-node-sdk.

@night The resend issue should be fixed now and the intranet URL issue fix is going to go out soon.

from paypal-node-sdk.

@night Intranet issue should be resolved now.

from paypal-node-sdk.

Now that just leaves the last issue I listed: (most) cleared eChecks do not trigger a webhook event.

Example PAY-IDs (from production) that completed, and had no webhook: PAY-39388053R70580154KTZWKFA, PAY-6DJ55021Y38754147KT2GIYA, PAY-5P340398M05892613KT3VHIQ

from paypal-node-sdk.

@night we will take a look at those ids and get back to you.

from paypal-node-sdk.

@avidas Any updates on those PAY-IDs?

from paypal-node-sdk.

Hey @night apologies for the delay, any chance you have some more recent PAY-IDs?

from paypal-node-sdk.

The most recent I have is PAY-7CY03637G9904192TKUEIVAY, which cleared March 20 and sent no webhook call.

from paypal-node-sdk.

Thanks @night do you have the Sale ID of that particular transaction? The sale id is returned in the response after you call [execute on the approved payment](https://developer.paypal.com/docs/api/#execute-an-approved-paypal-payment . This enables us to look in the logs for the account and timestamp.

from paypal-node-sdk.

@avidas That ID would be 2NP27880VW3103247

from paypal-node-sdk.

@night We reached out to the API team responsible for web hooks. Will let you know when we get an update.

from paypal-node-sdk.

Two more (from today and yesterday), in case it helps:

3GN12750AG949493N
5M199116C4918124Y

I also don't have evidence yet, but I do not believe refunds nor reversals cause web-hooks to be called either. Refunds I know for sure do not trigger a web-hook on sandbox, at least when granted via the PayPal website.

from paypal-node-sdk.

I'm no longer receiving any web-hooks. I log all API payment calls and web-hooks, and the last web-hook I received was at 2015-04-06T09:08:31.281Z (1 week ago).

from paypal-node-sdk.

@night any Sale ID or paypal debug ids you could provide?

from paypal-node-sdk.

@avidas I was getting "completed" web-hooks for a lot of non-eCheck transactions (not all) after the payment was received, but those stopped completely (as my last reply dictated). It seems every transaction yields no web-hooks now.

Another pending transaction that completed without a web-hook (yesterday): 60555830Y71350233

At this point, it seems web-hooks are completely nonfunctional, which is an incredible nuisance. For a large payment provider, I would expect not to have this kind of issue when accepting payments (issues like this are okay in sandbox, but this is production).

Another bug: Here's the output of the web-hook event search API:

{"events":[],"count":0,"httpStatusCode":200}

It doesn't seem to show any web-hooks, at least at first. About 5-10 minutes after, calling the API again gives you web-hooks you seek, but the last web-hook listed as sent is not the last I received. The reason for this is obvious, the internal request is timing out, but subsequent requests complete because the data is cached. The last web-hook I can get the API to spit back is anything before April 5th (specifically, the last I see is from "2015-04-04T23:59:22Z"). Anything past that point is unretrievable. Interestingly, I can still retrieve the missing web-hooks (from after April 4) by their event ID (since I log all web-hooks I have these IDs available).

I'm also surprised I am the only one who has been encountering these issues. Perhaps I'm one of the few who are actually trying to use these web-hooks. I would prefer to use a REST interface with web-hooks than the Classic APIs with IPN, and it is sad that it is this unstable and unsuitable for production.

from paypal-node-sdk.

Hi, this is Alex from PayPal webhooks team, sorry this issue happened to you. We're actively looking at your issue now. All the transaction ids you have shared seems are from echeck payment, to help us narrow down your problem, can you please run an instant payment through REST API, in the response header, you can find debug_id, please forward that id to us, that will help us trace your problem.

from paypal-node-sdk.

Here is a debug_id from an INSTANT_TRANSFER payment: 01d152cc27f78

Unrelated: In the response from executing a sale, payer.payer_info.first_name is always "" (empty string). If you want, I can open another GitHub issue about that.

from paypal-node-sdk.

@night Please open another GitHub issue regarding the empty first_name and include the debug_id from the response header. I wasn't able to reproduce that behavior on sandbox, so I'm not sure if it's related to the live service or something else. Regardless, we'll notify the Payments API team of the issue. Thanks!

from paypal-node-sdk.

Any updates?

from paypal-node-sdk.

Your problem has been identified, our engineer team is working on fixing your problem, will keep you posted after it gets fixed.

from paypal-node-sdk.

I really hope this gets fixed soon, cause the amount of support emails I am getting because of this is annoying now, and over the past couple weeks this has got worse and worse.

from paypal-node-sdk.

Could we please have a update one this, its getting very annoying.

from paypal-node-sdk.

Any updates?

from paypal-node-sdk.

Hey guys, really sorry about the delay here. This happened to be a broader issue than initially anticipated and there are multiple teams working on the fix at present. Because of the multiple moving pieces it is harder to put an exact date down but last I have heard they were planning on releasing in a week or two.

from paypal-node-sdk.

Okay well any update is better than no update I suppose, thank you @avidas I am going to add my work around for the time being.

from paypal-node-sdk.

Anymore updates?

from paypal-node-sdk.

Can you try it now?

from paypal-node-sdk.

I am just making some changes to my code and once a payment comes through which wont take long ill response back with my findings.

from paypal-node-sdk.

@alexkshu So I'm getting web-hooks now, but it appears that the requests are now malformed? My server is rejecting them with a 400 Bad Request because they don't appear to verify properly against their signature. Any idea why that might be? I'm using PayPal.notification.webhookEvent.verify from this repo, along with headers PAYPAL-CERT-URL, PAYPAL-TRANSMISSION-ID, PAYPAL-TRANSMISSION-TIME, PAYPAL-TRANSMISSION-SIG and the web-hook ID and raw body of the request.

from paypal-node-sdk.

@night, signature validation test is passing on my side. Have you downloaded the latest certificate from CERT-URL? Can you use webhook-simulator to send an sample event to your url and see if it works?

from paypal-node-sdk.

@alexkshu https://github.com/paypal/PayPal-node-SDK/blob/master/lib/resources/Notification.js#L48 The repo appears to grab it fresh on every IPN, so I'm not sure. The CERT-URL header is providing me with "https://api.paypal.com/v1/notifications/certs/CERT-360caa42-fca2a594-df8cd2d5" currently. I tried the simulator, but it just tells me "successfully queued" and I haven't gotten a POST from the server yet.

from paypal-node-sdk.

Found the issue: https://github.com/paypal/PayPal-node-SDK/blob/master/lib/resources/Notification.js#L42

Auth-Alg is now SHA256withRSA

from paypal-node-sdk.

please always get the algorithm from header instead of hard coding it.

from paypal-node-sdk.

please always get the algorithm from header instead of hard coding it.

Might want to suggest that to @avidas since that would require a change of the verify API in the SDK.

from paypal-node-sdk.

@night we will update the SDK to start accepting the algorithm as a parameter, feel free to add to the PR #90

from paypal-node-sdk.

@alexkshu So instant transfer payments come through properly, but not all eChecks do? This morning an eCheck transaction cleared, but I searched the web-hook events for today and did not see a web-hook generated for it (but I have an email confirming its' completion). The debug_id of the initial payment is 921d7072750fc. The transaction id is 11D24003RS694704H.

from paypal-node-sdk.

@night, do you see this issue happening to all your echeck payment?

from paypal-node-sdk.

@alexkshu Not all, but most eChecks appear to not generate a web-hook event. Maybe like 1 in 5 will, from what I've been seeing anyways.

from paypal-node-sdk.

Any progress?

from paypal-node-sdk.

@night can you check now?

from paypal-node-sdk.

@usubhash Sorry for the late response.

I got web-hooks for all eChecks since your reply except 7LX37159S3120111F. For this transaction, I received an email confirming the clearing at 6 Jul 2015 06:12:58 -0700 (PDT), but not a web-hook. I do not have the debug ID of the initial transaction, however, since I removed my logging of that.

from paypal-node-sdk.

@night According to the API team this should be resolved now, please reopen if necessary.

from paypal-node-sdk.