addition buttons buy codes confusion customer data database determines direct down explained feature generate generated generation help information integration ipn issue license licenses notice notification originate override page payment paypal post retry sales send server shared software storing unlike url

I am looking into using E-Junkie and have a question about the IPN.

Currently, I use IPN to generate software licenses. When a customer makes a payment via PayPal, I get the IPN notice on my server and issue the license and that works fine. However I now want to use E-Junkie instead of my direct Buy Now buttons.

The confusion is around the IPN. Does the IPN Post go to e-junkie instead of my server or in addition to my server? If it is instead of my server is there any way to get that notice to my server?

Bumping this up as it determines whether or not I use e-junkie.

If you use E-junkie buttons, then for those sales (which originate from our buttons) we override the IPN and IPN comes to us.

If you need IPN for license generation, then you can use our "generated codes" feature (see "codes" in help page.)

If you need the IPN for storing the information in database, then you can use our notification feature (see "integration" in help page)

However, unlike IPN, we only send data to your URL once. If your server is down or not reponsing, E-junkie does _not_ retry the IPN.

Is there any way to authenticate that post from e-junkie like the IPN?

There is a shared secrete paramters - hanshake. It's explained on the integration help page and also on the codes help page.