We've made several unsuccessful attempts to send order notifications to your notification callback URL, https://www.e-junkie.com/ gc/XXXXXX/ResponseHandler.php As a result, you aren't receiving order status, risk, or other notifications.

These don't seem to affect every GC sale nor every GC merchant, just a scattered few checkouts seemingly at random.



If you are new to using Google Checkout with E-junkie and have received errors like that, the first thing you should do is double-check our required integration settings:

http://www.e-junkie.com/ej/google-checkout-shopping-cart.htm#help

(Note in particular the API Callback URL and Method, and open the Advanced Settings section to ensure you have nothing checked under there.)



That said, if those settings are correct or you have already been accepting Google Checkout payments successfully before you started receiving those error notices, there does seem to be some sort of issue at Google's end lately. Aside from the sporadic error reports from our own merchants, we've also checked with other e-commerce providers who report their merchants are also having similar problems with GC lately. At any rate, it appears to be something out of our hands, but our Lead Developer is bringing this up with some inside contacts on the Google Checkout team to make sure they're aware of the situation and see what can be done.

Google Checkout's notification-failed messages are completely automated; no actual person has investigated anything when those messages are sent, so nobody is pointing any fingers from their end. All that message means is that nothing happened when their server attempted to contact ours, but that doesn't indicate the actual reason or source of the fault. Think of it this way: if your phone line is cut, we obviously won't be able to pick up when you dial our number, even though there is no problem with our own phone line.



We have personally investigated the issue thoroughly and run tests from our end and found nothing amiss, and we have contacted other e-commerce/cart providers who also integrate with Google Checkout, and they are also experiencing the exact, same sporadic pattern of errors with their Google Checkout callbacks lately, so obviously this issue is not isolated to E-junkie alone, indicating a general problem at Google's end affecting most or all Google Checkout merchants.

bigfootsfor the record.. this has never effected my digital delivery of items. its just an annoying message that google sends over and over every time i manually send a google invoice (money request)

as best I can tell this is the only time I get the message.

Aha, well that's to be expected then. When you follow our Google Checkout integration, you're instructing GC to inform our system every time a payment has been completed. If a given transaction was never started by our purchase buttons in the first place, then our system would ignore that notification which would thus fail, hence the errors you're seeing. If there's any way to disable callback notification for manual payment-request invoices, that would be on GC's end, so you'd need to ask them if that's possible and how:

http://checkout.google.com/support/sell/bin/request.py



@7w: could you confirm that all your purchase buttons are E-junkie buttons and that you don't have any button codes in use that you might have obtained directly from Google?

Great, just trying to eliminate anything you or we would have any control over.



If you were using GC with E-junkie just fine up until recently, didn't change anything, and yet suddenly these errors started happening "out of the blue", then it's the same problem at GC's end that other cart providers we've talked to are also reporting lately among their own merchants.



If it were due to some problem at our end, it would only be affecting E-junkie merchants alone, but since merchants using other cart systems completely unrelated to E-junkie are also reporting similar, sporadic problems just recently, this indicates the source of the problem and responsibility for fixing it has to lie with Google.