Forums / PayPal Express Checkout support / no signature hash?

no signature hash?

Started by weirdorecords on 18 Jul 2011, 4:57 PM · Views: 977

Results 1 to 3 of 3
18 Jul 2011, 4:57 PM
#1
weirdorecords avatar

weirdorecords

New Zenner

Join Date:
May 2010
Posts:
72
Plugin Contributions:
0

no signature hash?

I'm looking to switch over from Paypal Website Payments Standard to Paypal Express, on the repeated good advice of Dr Byte on this forum. I'm trying to follow the instructions here:
http://www.zen-cart.com/index.php?main_page=page&id=15

I logged into paypal and have successfully retrieved my api username and api password. Unfortunately, I can't figure out how to view my signature hash. It doesn't seem to be written anywhere, there's no link to get to it, etc.

Is there a way for me to find out what it is?

Thanks for your time.

18 Jul 2011, 5:04 PM
#2
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,515
Plugin Contributions:
176

Re: no signature hash?

Sounds like you probably selected a Certificate instead of a Signature.

You can get quick support for your difficulties in using PayPal's website by contacting PayPal Support directly.

.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole

Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.

18 Jul 2011, 5:37 PM
#3
weirdorecords avatar

weirdorecords

New Zenner

Join Date:
May 2010
Posts:
72
Plugin Contributions:
0

Re: no signature hash?

Right you are. Paypal customer service actually did the trick- there were two api certificates on my account somehow & that's what caused the trouble. They were even quick & responsive! All fixed & switched over.