Due to the popularity of our web development contract template article, we're offering the contract, estimate, and invoice templates for $199.50 $49.50 if you order by March 13. Click here to learn more.
Use Site Build It! to get up and running with your own website, no technical knowledge required, and get ready to cash in on a slice of the giant online advertising industry. Check out Site Build It! to get started.
The error We were unable to decrypt the certificate id has become quite common recently. Most commonly it's a result of a WYSIWYG (What You See Is What You Get) editor such as FCKEditor or TinyMCE. Basically, you obtain the button code for your Paypal Buy It Now or Subscription or other similar button to place in your webpage. If you were copying and pasting this into raw HTML it would most likely work fine. The problem with the WYSIWYG editors is that they, by default, when the page is processed, insert certain code elements. For example, in the case of FCKEditor, a linebreak (<br />) element was inserted towards the end of the button code.
To resolve this, examine your button code by viewing the source code of your webpage, and compare it to the original code in Paypal. If you notice anything different, particularly if there's a linebreak (<br />) or newline ("\n") element inserted, this is most likely causing the we were unable to decrypt the certificate id error.
To get your Paypal button working again, try:
When you save the page and view its source compare the button code to the Paypal original button code again. If they're the same, you should not be getting the above error anymore.
All Content © 2005 - 2010 Contract Web Development, Inc. All Rights Reserved. Privacy Policy | Terms of Use | Powered by Drupal
Solution to Paypal button problem
I had to solve this problem to get a button working on my own site, which is powered by Drupal.
Compare Paypal button codes
When you save the page and view its source compare the button code to the Paypal original button code again. If they're the same, you should not be getting the above error anymore.