21 / 36
Aug 2012

Hi,



I just noticed that PayPal has a new Advanced account. I am currently selling through PayPal Pro. From what I can tell, it looks like the Advanced can accept credit cards but is only $5/month instead of $30/month for the service fee.



A couple of questions.



First, is there any difference between these services for the customer's view in the E-Junkie cart?



Second, the setup procedure looks different. Is there a way to make the switch seamless without any interruption to the credit card payment option working?



Thanks

We actually just added support for PayPal Payments Advanced a couple weeks ago; you can see a demo of the checkout process for Advanced payments here:

1http://www.e-junkie.com/ej/paypal-payments-advanced.htm1



We're still polishing off a few rough edges in the appearance of checkout screens for the card-based checkout option with PayPal Advanced, but it should function just fine. This help page explains how to set up PayPal Advanced for your E-junkie account:

1http://www.e-junkie.com/ej/paypal-payments-advanced-shopping-cart.htm1



Once you complete that integration procedure, the transition should be seamless with your existing E-junkie Cart buttons.

I'm having some trouble with this. I have the PayPal Advanced account approved, and I've created a new user for transactions, as per the instructions. However, I'm getting this error:



"We're sorry, but an error occurred while processing your payment to PayPal. This error has been logged. You might want to go back and try your transaction again.

Error 1: User authentication failed"



On https://www.e-junkie.com/ej/setupppa.php, I entered our PayPal email address, our partner (PayPal), our proper Merchant ID as shown on PayPal, and then the User and Password for the non-manager account on PayPal Advanced.



What confuses me is if, after submitting the info, I go to the Payment Preferences section of our eJunkie account, it's showing the Login ID as my Merchant Login (which is the same as our Login Name for the manager account on PayPal). However, the associated password that's shown is for the separate billing-only account I set up, per your instructions.



I've tried changing the user/pass shown there to match either my billing-only ID or (not recommended, I know) our master account. In both cases, I get the same error as shown above.



Help, please -- the credit card badge is now live on our cart, but we can't use it, and it won't be long before prospective customers start complaining.



thanks!

-rob.

I've bought this to Development's attention; if you could, please email Support to start a ticket about this issue, so we can exchange details privately about the parameters you're entering:

2https://www.e-junkie.com/ej/contact.php2



The fields we require on our PayPal Advanced setup screen should be as follows:



- PayPal Email: should be the email address you use to log into your PayPal account, or a secondary email linked to that account, where you will receive PayPal account-based checkout payments (rather than card-based payments) -- this field would be pre-filled and read-only if you'd already entered your PayPal Email in Seller Admin > Edit Profile;



- Partner: should be 'PayPal' unless you know that you use an Internet Merchant Account from a different provider;



- Merchant Login: This should be your main PayPal Manager login username (which is different from the login email for your regular PayPal account);



- User: This should be the username you want to use for transaction processing, such as a secondary account you may have added to your PayPal Manager for processing transactions (as we recommend for security), or otherwise this should be the same as your Merchant Login;



- Password: This should be the password for the account username you provided in the User field.

With some help from your engineering department, it appears we're now up and running. The setup instructions on e-Junkie need to be modified to reflect some additional changes required on the PayPal Manager account -- I don't remember what they all were, so I'm not going to try to enumerate them here. But I imagine the installation page will be modified with the new info in the near future...



-rob.

No problem, and generally, it's working well ... but I've got a new issue that's just come up: two customers in Canada are unable to use the system. They get this error message on the screen that comes up after entering their basic info (name and address), where they'd normally provide their info:



"Some required information is missing or incorrect. Please correct the fields below and try again.



• Error: An error has occurred. Please contact the system administrator."



Not the most helpful error message :).



I know it's not international in general, because I have orders from other countries in the system already. Any ideas?



thx;

-rob.

Correction: One user gets the above message. The other gets this one:



"There was a problem processing your request. Please press the Back button of your browser and then refresh the page. If you continue to have an issue, please contact us."



In the first case, the user can still see a credit card entry form below their error message; in this case, there's just the error message.



Is there a log somewhere (here or PayPal) that might show what the issues are?



regards,

-rob.

"Error: An error has occurred. Please contact the system administrator." is a PayPal internal error message (as will be anything that shows up above the card info entry form like that). PayPal seems to have had an unusual run of system problems lately; hopefully this was just a temporary problem.



You can see PayPal service problems, at least the ones they're bothering to report, related to the Payflow gateway (problems with which potentially impact both Payments Advanced and Payflow Pro users) here:

5https://www.x.com/developers/paypal/documentation-tools/site-status/pf-live5



The other message ("There was a problem...") sounded to me like one of our messages at first, but checking the verbiage exactly, is also a PayPal system error; one for which I can't speak as to what the problem is either >.>



We do have logs, but a quick look through them turned up zero standard error responses. My feeling is these both the messages your buyers have seen are related to the payflow gateway flakiness over the last couple of days. However, if you want to file a ticket and send us some specific data on users so that we can look up what we have in the logs on those attempts, we'd be happy to do so.

Thanks for looking into it; seems it's on PayPal's side. I'll have my customers try again and see what happens. If it still fails, I'll bring it up with PayPal.



-rob.

8 days later

Unfortunately, the same users -- and others now -- are reporting the same problem with their purchase attempts; nothing has changed in the last week. The only common thread is that they're all non-US buyers.



Who do I go to to help resolve this issue?



thanks;

-rob.

None of the issues we've seen have been due to our backend integration for PayPal Payments Advanced; any problems have been a matter of either misconfiguration in the seller's settings at our end or in their PayPal Manager (which granted may have been due to omissions in our help page which we've now corrected), or sporadic glitches at PayPal's end for which we have no insight or control.



If you're still seeing any checkout problems using PayPal Advanced, first double-check that you've completed every step of our integration procedure for that service correctly (1http://www.e-junkie.com/ej/paypal-payments-advanced-shopping-cart.htm1), then if you've verified that's all good, contact PayPal support to bring the matter to their attention.

I've confirmed we're configured exactly as shown in the documents, so I guess it's off to PayPal to see what they have to say.



thanks;

-rob.

I also currently use PayPal Payments Pro and would like to change to PayPal Advanced since they seem identical per your demo listed at the beginning of this chain. But I don't want to make the change until the PayPal Advanced integration with eJunkie is fully vetted It's much too risky for my business. Is there any way to provide updates via this thread on the status of the integration? I'd love to save $25 a month but not at the risk of losing sales.



Cynthia

Our integration with PayPal Payments Advanced is complete, correct, and fully functional at our end, and this has been verified multiple times investigating the issues reported here, so any glitches at this point can only be coming from PayPal's end. Unfortunately, we don't have any special access to "insider information" about internal issues at PayPal's end, so we wouldn't have any news about that we could post here.



You can check PayPal's Site Status Updates page to keep informed of acknowledged issues at their end:

https://www.x.com/developers/paypal/documentation-tools/site-status



E.g., it appears there was an issue at their end with Advanced checkout on Aug. 8-9th:

https://www.x.com/content/resolved-paypal-payments-advanced-merchants-receiving-result-code-5-aug-08



Issues posted there which affect the Payflow gateway might also affect Advanced checkout, which is related to Payflow.



Merchants using PayPal Payments Advanced who encounter any issues with that, once you have double-checked every step of our integration procedure for that, should open a trouble ticket with PayPal Merchant Technical Support (MTS):

1https://ppmts.custhelp.com/1

I now have an open ticket with PayPal, and they claim there's no evidence of troubles on their part.



They even told me that one of the reported errors ("Error: There was a problem processing your request. Please press the Back button of your browser and then refresh the page. If you continue to have an issue, please contact us.") isn't anything in their system at all -- so if it's not theirs, then whose error is it?



They did ask for some specific user examples, and I've provided five names, email addresses, and failed transaction dates/times for them to look into. But if they come back from that and say there's nothing in their system about those users, doesn't that imply there's something going on between eJunkie and PayPal that's causing a problem?



Note that most transactions are going through, but we're seeing a much higher failure rate (as recently as yesteday) than I would expect. We sell to technically savvy users, too, so I seriously doubt these are user error issues.



I'll let you know what PayPal tells me when they investigate these names.



-rob.

Hi Rob,



That message does indeed come from PayPal; don't let them tell you otherwise. However, I think it's being generated somewhere in their web frontend, before anything gets far enough for them to have a record of it.



Tyson (the Guru) did a little research and came across a mention of something I hadn't considered; after a little testing to confirm, we think that that message is caused by having 3rd-party cookies disabled in the browser; the PayPal iframe in the page apparently needs that functionality to work. This is unfortunate, as it's privacy-hostile and some browsers have those disabled by default.



Do the problem reports you reference specifically list that exact message? We need to know how many of the errors your buyers are experiencing are due to this, vs. potentially some other problem (of which there have been no shortage so far--I've personally had an open ticket with PayPal MTS about my PPA test account being broken for at least the last week, with still no resolution...)



The page as it is currently, including the use of that embedded "template C" iframe for the payment collection, is how we planned out the integration with PayPal's team. We're not sure if switching to just redirecting to template A or B is an option; those both lack the order detail that we're providing, and allow the user to change the address (with no shipping recalculation callback that I'm aware of).



We will be doing some thinking on what, if anything, to do about this. Please keep us updated on how it continues to perform for you.

Unfortunately, only one user reported that exact error message. The rest were just along the lines of "it didn't accept my credit card."



I'll ask these folks to try with third-party cookies enabled to see what happens; thanks for finding that tidbit. I'll post back with any results.



-rob.

OK, the third-party cookies issue definitely helped a couple of our users ... but it's a major flaw in the system, for at least a huge percentage of our prospective customers.



We sell software to Mac users, and Safari is the dominant browser on the Mac -- very dominant. And unfortunately for us in this case, it defaults to disabling third-party cookies. That means that a very high percentage of our credit card purchase attempts will fail; probably much higher than those on other browsers.



*** EDIT: Chrome also blocks third-party cookies by default, and it seems IE 10 will do so, too -- not sure about IE 9. That means only Firefox ships with them enabled, and I would guess that will be changing soon, given the others' defaults. ***



Given that this issue is on the fatfreecartpro page, can you at least put up a big obvious warning box, explaining that users will have to allow third-party cookies, in order for the transaction to work? Ideally, this warning would contain a link that led to an explanation on how to do that in the major browsers, too.



But this is just a short-term fix suggestion; long term, using third-party cookies isn't acceptable, due to the security issues. If e-Junkie can't improve this process, we're going to have to figure out another way to accept credit cards (does this same issue exist with PayPal Pro?) ... and that would probably mean we'd need to start looking for a different cart solution, as we can't mix two systems together on our checkout page.



We've been very happy with e-Junkie thus far, and would hate to have to leave ... but we can't have a credit card system (where users are sometimes rightfully cautious to begin with) that requires a user to change a default browser setting



-rob.

I just heard back from PayPal on my open ticket there, and here's what they had to say:



"That makes sense, but there would not be any way around that. The iFrame is going to be using PayPal's domain not yours or eJunkie's. That means the particular method that eJunkies is using is not going to work by default for a lot of browsers going forward. They will either have to not use the iFrame and direct customers to PayPal for the checkout with Layout A or B in the Hosted Checkout. "



So is there a way for us to not rely on third-party cookies, given that most major browsers are now disabling them by default?



-rob.

Any update on this issue? I'm still getting multiple daily emails from customers unable to purchase our apps; I have a stock reply I now send, explaining how to enable third party cookies ... but this is horrid from a customer perspective.



thanks;

-rob.

Hi Rob,



After poking at what we could do about this (and me being out sick for a week), we've switched to just redirecting to PayPal's payment form, rather than including it as an iframe in out own detail page. This solves the 3rd-party cookie issue for now, at the expense of not being able to show order summary detail on the payment page. It's not the user experience we had planned when we developed the integration with PayPal, but at least it's not turning away customers because of browser issues.

Sorry to hear you were sick, but glad the non-response here wasn't a sign of ignoring the problem :).



I realize this isn't an ideal solution for you guys, but for me, it appears to be much better -- they'll still see the details after they pay, and will no longer get kicked out for (what to them are) mysterious reasons.



thanks!

-rob.

An unfortunate follow-up: our troubles persist. I just had a customer report a failed transaction, when everything looks good. He even has third party cookies allowed. I have the screenshots, and can email them if you'd like.



Basically, he's got:



* A valid name and address

* A valid credit card (used just this morning, he tells me) and CCV

* Third party cookies enabled, just to be safe



When he clicks Pay Now, he gets the mysterious "whose error is this?" message:



"Some required information is missing or incorrect. Please correct the fields below and try again.



• Error: An error has occurred. Please contact the system administrator"



Do I have to do anything in my PayPal Manager to reflect the change you made? That is, I still have it set to using Layout C; should I change that to A or B?



-rob.

You shouldn't need to change anything in your PayPal Manager settings; we're still using Layout C, but now we're just displaying the PayPal Payments Advanced payment screen as-is, rather than embedding it in an IFRAME which was causing the third-party cookie issue. Any errors that screen is producing could only come from PayPal's end, as that page is hosted on PayPal's servers, and the buyer is only redirected there after we've transmitted their order details to PayPal.



The fact that any PayPal Payments Advanced checkouts are working at all indicates the integration at our end is correct, as any mistake in our integration would cause all such checkouts to fail, so it seems either PayPal is sporadically dropping the ball, or perhaps affected buyers are entering their payment information in some weird way that PayPal cannot handle properly. Googling the error you reported, I found one mention on PayPal's developer forum stating that card numbers must be entered as a continuous 16-digit number, without any spaces, dashes, or other divisions in the full card number.



If you have screenshots of actual error messages, feel free to email those to support, so Development can try to research the matter further:

https://www.e-junkie.com/ej/contact.php

I went back to the customer, and he assured me he wasn't using any spaces. However, he also included this tidbit:



"The only other thing I had done is I was viewing the ManyTricks.com from Firefox. Since I like to keep my browser activity for banks and CC/PayPal separate from occasional browsing, I right-clicked and copied the "Buy Now - $10" link and opened it in Safari.



https://www.e-junkie.com/ecom/gb.php?c=cart&i=646650&cl=109807&ejc=2"



I had him try directly in Safari, and it worked ... so why would it fail when he copied our Buy Now link to another browser? Is there something you can verify on your end if a user does this, so they won't run into the same problem? (i.e. is it a cookie problem, or something else?)



regards,

-rob.

We tested that link in Safari on both Mac and Windows, where we had no trouble at least getting to the final payment page, though of course we didn't try entering card info to complete an actual payment. As you can see by the browser URL on the final checkout screen where the buyer would enter their card info, that page is served up by PayPal, so we have no influence nor insight over things by that point.



There's absolutely no difference in the checkout process by using a purchase button on your site vs. copying the button's link URL to visit directly, so that along with the fact the buyer was eventually able to complete checkout in Safari suggests they most likely just tripped over some transient glitch at PayPal's end the first time they tried submitting their card details at checkout, or maybe they just made a typo or stray keypress they didn't notice on their first attempt.



If you get more reports with details indicating a consistent, reproducible pattern, such as problems only happening in Safari, we'd suggest opening a ticket about that with PayPal MTS (and of course, the more details and specific, actual error messages you can provide, the better):

https://ppmts.custhelp.com/

18 days later
E-junkieGuruI've just updated our PayPal Payments Advanced integration help page with those extra details you mentioned:

http://www.e-junkie.com/ej/paypal-payments-advanced-shopping-cart.htm



Thanks for working with us to iron out these last few wrinkles in our setup procedure and documentation for this new checkout method. :^)





Hi there,

I just setup the Paypal Advanced according to the new instructions but cannot get a credit card payment through. The Paypal guy said that I need to have e-junkie be set to the Paypal Advanced Gateway and that's why it's failing. I looked under Payment Preferences, and there is no place to put Paypal Advanced, in fact Paypal Standard is checked, which is a different gateway. The only other option is Paypal Pro. I have entered the info at https://www.e-junkie.com/ej/setupppa.php#status. Right now I have tried a different user, and that crashes outright, and I have also tried to have the merchant login and user be the same, and that gives me an general error on the screen where I enter my cc info.



Please help, as I'm getting ready to launch my new teleseminar on Wednesday.

Thanks

-Karen

Right now there is no setting in Payment Preferences for the new PayPal Payments Advanced service; we're adding the relevant settings for that in the new Seller Admin we're building, and meanwhile we're just using that separate setup_ppa.php page you referenced. As long as you follow the setup instructions we provide for PayPal Advanced, and don't change any settings in your Payment Preferences afterwards -- and presuming everything is fine with your PayPal account setup at their end -- it should work fine:

http://www.e-junkie.com/ej/paypal-payments-advanced-shopping-cart.htm



It appears you have the relevant settings entered properly at our end, though of course we cannot tell whether the settings you entered are a correct match for the actual username(s) and password in your PayPal Manager account, so you may want to double-check those credentials in your PayPal Manager account and re-enter them in our setup page. We recommend using your computer's copy-paste functions to make sure what you enter in our setup page exactly matches what's in your PayPal Manager.



If you're still having troubles after that, please copy any actual error messages you're seeing and paste those into a reply here, or email them to our support team:

https://www.e-junkie.com/ej/contact.php

Hi,

Okay, after a full day and a half on this issue and speaking to almost everyone at Paypal, I think I am going to have to go back to Paypal Standard. Can you get me back there, please? I cannot simply take out the fields that I entered on the setup screen (merchant login etc). I am running out of time, and it's just easier at this point.

Thanks so much, and thanks for your quick response :-)

-K

It appears Development has now reverted your E-junkie account back to using PayPal Standard checkout, just wanted to followup to your post about that here as well.

29 days later

Hmm, going to paypal advanced seems a bit more risky now. Any new developments on this? You mentioned a new seller admin, when do you suppose that will be released?



Will there be any difference from the checkout standpoint between Pro and advanced. I'm assuming there will be the same credit card and paypal buttons. After clicking the credit card button, are the customers taken to the same checkout screen? After checkout, do they see the same confirmation page? If so, it would be worth switching to advanced because the only other functionality with pro is the virtual terminal which I don't use that often. Also, both options are capable of the Paypal Here which is the swipe device.

There was a bug with parameter parsing at PayPal's end that we'd been working on with them as of a few weeks ago. Last I heard, PayPal hadn't fixed the bug yet, but they'd suggested a workaround which we implemented, and in our testing that seemed to keep the problem from happening. We haven't received any further reports of trouble with PayPal Advanced since then.



You can test our PayPal Advanced demo page to see how the checkout process for card-based direct payments would look and work with that service:

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



After payment is completed, the buyer would be directed to the same thank-you page as with any other payment method we support.