By any chance are you the same Dave we've been emailing with about this issue?



If not, make sure you've configured your Common Notification URL and/or Payment Variable Information URL field(s) with a complete URL starting with "http://". Also, since those fields already have "http://" in them by default as a hint, make sure you haven't duplicated that part (e.g. by pasting your full URL after the existing "http://"). If your URL fails to respond at all, you should get an email notification of that sent to your E-junkie login email address; if you are not getting such notifications, then your URL is actually responding, so the question then becomes a matter of what your script is doing with the data we're POSTing to it.



If you are the same Dave we've been emailing about this issue, now we're a bit confused because your post here is from a different E-junkie account than the one we've been looking at based on your email correspondence, so which account is the one having the problems with our Integration feature? We should probably just continue communicating by email, since we're up to the point of exchanging sensitive information like affected Transaction IDs and your actual Integration URLs, which really shouldn't be posted publicly here.

bfjackMy Common Notification was working fine all through July and August and just this last week and a half has started acting up. We do get occasional notices that e-junkie cannot connect when the site is up and working - at least from the end users point of view. So why e-junkie cannot connect is a mystery - the url hasn't changed.

Is there any way to simulate the POSTing process for testing purposes? Is it safe to assume that if a free purchase goes through that a paid one would too?

We'd use exactly the same function to notify your script URL after a Free Checkout as we would after any paid checkout, so that would be a valid test. If you can get it to POST at all even once, that indicates things are fine at our end; moreover, if things weren't fine at our end, we'd be getting reports from everybody since ours is a centrally-managed service where all our functions are shared in common among all users. Any glitches or flakiness in submitting to your script would then be a matter of whether a connection across the Internet to your server can be established, and whether it can respond, on a consistent and reliable basis.

Just glad to hear you apparently got it sorted out. Let us know if you have any further problems or questions. :^)