PayPal still has not addressed the third-party cookie blocking issue which compelled us to adopt the compromise approach we're still using now (as explained above). Furthermore, it appears they are no longer actively developing or promoting PayPal Payments Advanced, in favor of pushing PayPal Payments Pro, so it seems unlikely they will ever resolve this problem.



If you might consider upgrading to PayPal Payments Pro -- which uses a single, self-contained, secure page we manage for your card-based checkouts -- this help page explains how to integrate that with E-junkie:

2http://www.e-junkie.com/ej/paypal-partner.htm2



Unfortunately, checkouts can never occur on your own site/domain with E-junkie due to our inherent nature as a centrally-managed service which does not install any software on your server; this is one of the tradeoffs for our ease of use and site integration.

This is the page where I found PayPal Payments Advanced listed as a "Legacy product" which is "No longer actively marketed; now included with PayPal Payments Pro":

2https://developer.paypal.com/webapps/developer/docs/classic/products/payflow/2



Elsewhere in that documentation, they have indicated that "Legacy products remain available for pre-existing users", so it seems they will continue to support existing integrations using it into the foreseeable future.



We've already prepared the design for a more modern, mobile-responsive card checkout page, but Development still needs to actually implement that as a live checkout page, replacing our current card checkout page (which is not responsive, as you've seen). When that project is completed and goes live, we would post a notice to our System Status & Updates forum here:

http://www.e-junkie.com/bb/forum/6

There are ways to have us post the order details to more than one URL, and I've contacted EDD support to clarify something about their integration which would determine the best approach for that; however, EDD's E-junkie integration would only have us post the order details to EDD after we're done processing the buyer's order, so you'd still be using E-junkie's purchase buttons and checkout -- i.e., this wouldn't allow you to use some other checkout experience and then have E-junkie issue download links after the buyer has paid.

2Checkout's process begins with the basic form on our site but then redirects to a different payment form at their end. You can see that by filling out the demo checkout at http://www.e-junkie.com/ej/2checkout-shopping-cart.htm with any information and then clicking the "Proceed to payment form" link at the bottom.

EDD has not replied to my inquiry from over a month ago, so I've just sent them a followup reminder.

EDD SupportSo it actually looks like we'll have to make some decisions with this extension very soon (as we are about to do with all extensions we sell). The thing is, EDD hosts an extension marketplace. While there are several 3rd party extensions that we do nothing more than link to, there are also several that we sell for 3rd party developers. We simply take a small commission cut.



Some extensions, like this one, don't sell much at all. And we've recently made the decision to start getting rid of them. I did ask the extension developer about the things you mentioned, specifically the last paragraph of your original query [regarding why, or even if, it required both a Code Generator URL and Payment Variable Information URL, both identical]. His response was:



"Thanks for the update. It's been a while, so I'm not sure why I chose to use both."



Obviously, that's not very helpful. It was immediately followed by asking us, the EDD team, if we were interested in buying the extension from him. Because of its very low sales (2 in a year and a half), we aren't. So it's very possible that it will be taken off of the market extremely soon. And I can say with certainty that its codebase will not be receiving an update from us or its developer.

It may help to clarify whether you're upgrading to PayPal Payments Pro vs. PayPal Payflow Pro.



If you'll be using PayPal Payments Pro, then there are no credentials to enter at our end, aside from your PayPal Email; the API permissions in our setup instructions would take care of the rest:

http://www.e-junkie.com/ej/paypal-partner.htm



If you'll be using Payflow Pro, that uses the same PayPal Manager credentials as PayPal Payments Advanced:

http://www.e-junkie.com/ej/paypal-payflow-pro-shopping-cart.htm



In both cases, card-based checkouts would use a secure checkout page we manage for you, rather than anything at PayPal's end. To preview what this page looks like, you can test the demo cart buttons at either of the links above. It's mostly the same as the buyer name/address initial checkout page you saw with PayPal Advanced, except that it incorporates card account info fields in the same page, rather than using the separate, bare-bones PayPal-hosted card-info page you saw with Advanced. BTW, we're quite aware that checkout page looks rather dated and are planning to modernize it soon. :^)

This is the first we've heard of in-context checkout, so it must be pretty new, and we'll have to research that further; thanks for the tip!



I've already prepared the HTML/CSS for a new card checkout page, just waiting on Development to get to that item on their to-do list. :^)

This is the first we've heard of in-context checkout, so it must be pretty new, and we'll have to research that further; thanks for the tip!



I've already prepared the HTML/CSS for a new card checkout page, just waiting on Development to get to that item on their to-do list. :^)