- This topic has 6 replies, 3 voices, and was last updated 12 years, 4 months ago by
.
-
Posts
-
I thought I’d already asked this question, but I searched and can’t find the question or an answer in other posts. It came up because I had a case of an invalid IPN being sent on, but it was not invalid from PayPal but rather because of a difference between the product prices because of a price change.
Anyway, what I need to know in specific is does the 3rd Party plugin have to separately validate the IPN forwarded from eStore against PayPal or does eStore filter out invalid IPNs before forwarding.
I have come to the realization that I do need to separately validate the payment, as that was sent on even though the eStore refused to record the sale, but I can see reasons for that, not for sending on an invalid IPN though.
Thanks.
We used to only forward the IPN for successful sales via eStore. Few users wanted to receive IPN for all transactions so now eStore forwards the IPN after the initial verification (for example: check if the IPN truly came from the PayPal site).
That sounds like something I’d ask for
. So to clarify, we do know that it’s a valid PayPal IPN if it comes from the eStore, but not necessarily a valid purchase.Perfect.
A valid purchase is one that the eStore accepts and inserts into its database, as opposed to a valid IPN that contains an invalid purchase price (for whatever reason) and so is not entered in the eStore database but is passed on to 3rd Party applications.
Ideally, the above case of invalid purchase should send the admin a flag for the problem. Honestly, it would be grand if you could add a status flag into the IPN that you pass, preferably with the reason if something is declared INVALID. I wouldn’t use the IPN valid/invalid tag because it could generate errors if the 3rd Party was expecting a PayPal response there, but a new tag that we could look at would be a great enhancement.
@Marfisk, Yes you are correct.
- You must be logged in to reply to this topic.