Error 10408 Express Checkout token is missing.

Hi all,

I am using 1.3.7 version.

And on the PayPal Express, now we received the e-mail of that error

" 10408 Express Checkout token is missing. - Express Checkout token is missing."

Anyone know why and what is it?

Thank you very much and wish you have a nice day.

Best Regards,
Jimmy

The token is given to your site from PayPal whenever someone clicks to start an Express Checkout process.

If that's not working, you've got something broken on your site.

Also, v1.3.7 is quite old, and there were many patch updates issued for PayPal Express Checkout on it, bundled (with several other fixes too) into 1.3.7.1. And v1.3.8 added more features and a year's worth of other fixes.
At the very least, you should make sure you've got the Paypal patch for 1.3.7 installed ... although there was never any report of the error message you're getting, so none of the patch updates deals with that directly: http://www.zen-cart.com/forum/showthread.php?t=56216

The only mention I've seen of token problems is as a result of installing Google Checkout ... which has its own problems.

I've installed Paypal express as a payment option. Everything seems to work fine, except that once the customer completes the process on the PayPal end, they're returned to the checkout page with an error message:

Error 10408 Express Checkout token is missing

What's causing this?

Thanks,

John

Read this thread please.. > Error 10408 Express Checkout token is missing

http://www.zen-cart.com/forum/showthread.php?t=114708

I'm getting the same error, but with version 1.3.9a. Any idea about what might be broken? Is there a Paypal patch for 1.3.9a?

John

First upgrade to v1.3.9h.
Then enable debug-log-to-file, and collect the log files, zip them, and put the zip file on your server and PM me with a link to the zip for analysis.
http://www.zen-cart.com/forum/showthread.php?t=61199

Thank you.

I upgraded the PayPal module files (only) to 1.3.9h. I also noticed I had failed to turn on the IPN and set the return link URL in my PayPal settings.

Since making those two changes, it seems to be working. But if I start getting errors again, I'll do as you suggested.

Thanks again,

John

jgold723:

I upgraded the PayPal module files (only) to 1.3.9h.
You REALLY should update ALL the rest of the stuff too.
Applying partial updates willy-nilly is risky.

I don't disagree with you at all.

However, the upgrade process for the cart seems to be terribly complicated. From what I understand, I need to get the upgraded cart files, then compare each one of them, line by line, with my current files in order to move over any customized code (and unfortunately, there's a lot in our cart).

And there appear to be hundreds of files.

I know this is the wrong thread for this and maybe I just don't understand the process correctly. If so, please point me in the right direction.

Thanks,

John

You just blindly replaced the paypal files, right?
And you did that because you knew you'd not altered those files, right?
So, what about the other files that have changed? Chances are the majority of the files that have been updated were not customized. So, you really only need to pay attention to merging customizations for files that have been updated. That's where automated tools like WinMerge make it really easy by identifying which files you've customized, and then you can use that list to determine which short-list of files require your personal attention.

True and your message raises a question that I had not considered: I'm guessing that the most highly customized files are the template files. Can those be moved directly into the upgraded cart without concern, or do I need to compare them against a default template?

John

Template changes between versions are kept to a minimum where possible, to minimize the pain of upgrades. Sometimes it's necessary to change them though, but usually the changes are minor, so very easy to adapt.

Should still compare YOURS against the ORIGINALs for your OLD version, to identify the changes you made. And then simply recreate those changes in the new template.