That sounds like you may be testing with Buy Now buttons, rather than cart buttons. Since Buy Now buttons bypass our cart and take buyers directly to instant checkout with a specific payment processor for just one item at a time, they cannot work for products priced at 0.00, because the processor cannot process a checkout "payment" of nothing.



You can either test your Buy Now buttons with an actual price and payment of at least 0.01 (you can always refund the test payment later), or you can use cart buttons, which will offer a Free Checkout in the cart when the order total is 0.00. This help page gives some other tips for testing your setup:

7http://www.e-junkie.com/ej/help.test.htm7

Our trial period is fully-functional, so that's not a relevant issue here. Could you provide the URL of the page where you're testing our cart buttons, along with any other details you're using for test orders?



Also, make sure you're using our standard E-junkie Shopping Cart button codes. The optional "PayPal Cart" buttons currently available in Seller Admin don't work as they're supposed to anymore, due to changes at PayPal's end that we have been unable to work around, so we'll be removing that version of button codes from the next version of Seller Admin. The standard E-junkie cart will offer buyers a PayPal checkout button in the cart, which will also allow you to test 0.00 order totals using our Free Checkout method.

This shouldn't have anything to do with the button code in your page, so there's no need to concern yourself with that. The button code in the test page you linked looks fine. However, we were unable to reproduce any error from your test page.



Just to confirm, is "Invalid Processor" the exact, entire error message you're seeing? If not, please copy the complete error message you get and paste it into a reply here. I'm going to ask Development to look into this, since the last time an "Invalid Processor" error started appearing, it did turn out to be a glitch we needed to fix on our end.



The & thing is actually fine, as well. That happens because the "&" character has a special significance in HTML, used to indicate when you're inserting a symbol (e.g. &© inserts a copyright symbol). Technically if you have an "&" in the raw HTML code that should be treated as a literal "&", you're supposed to use "&&" (meaning "insert an ampersand symbol here), so many page-editor programs will do that automatically, but all major web browsers are sophisticated and lenient enough to recognize the difference anyway. We leave it as a plain "&" in our button-code URLs just to keep the code we provide tidy and compact, but it works fine either way.