pbreit

Sid, that's a great suggestion and I will look into that immediately.

Can you try setting the path to "paypal_wpp/certs/cert_key_pem.txt". Yes, you need to download a certificate from PayPal. Log in to your PayPal account and go to "Profile > API Access > Obtain API Certificate". Download a certificate and upload it to your web server over-writing the "cert_key_pem.txt" that already exists at "paypal_wpp/certs/". You might rename the existing cert_key_pem.txt so it doesn't go away.

The contribution below implements the IPN notification service. It was developed by the OSCommerce core team. http://www.oscommerce.com/community/contributions,2679

A 10002 error indicates that the API Account Name, API Account Password and API Certificate aren't matching. Double check each of those. You might try re-downloading your API certificate. Make sure you are using your API password which is different from your regular PayPal account password. And make sure you are you are using the appropriate site, either the sandbox or the live site.

Setting the IPN there is optional. We will make that clear in the documentation. If you are a merchant and want IPN (see paypal.com/ipn) it's probably best to set up IPN in your PayPal Profile. We are still looking into the other issues users are seeing and hope to have information shortly.

Did you edit the path to the API Certificate File or is that what it defaulted to? Can you try setting it to: "paypal_wpp/certs/cert_key_pem.txt".

Is the mis-spelling of "category" just in your post or did you copy/paste that from your OSC admin?

When testing Direct Payment on the sandbox, use a credit card number other than 4111111111111111.

This is a support thread for the PayPal Website Payments Pro v0.1 contribution. Please log all bugs and feature requests here. The contribution is available at: http://www.oscommerce.com/community/contributions,3716

The double display of the "Total Amount" appears to be a bug. I've logged a bug on our side. Since it's a cosmetic bug, I don't think it will make it into an emergency fix so we may not see a fix for a week or two. I will work with the osC team to see if we can come up with a better way to handle addresses so that merchants can make sure they ship to an address they are comfortable with. Thanks for the feedback.

Vger, there shouldn't have been any change in which page is displayed first on paypal.com (except that our recent wite upgrade may have referesehd cookies). I can have a look if you provide a link to your store.

The new "sign up optional" flow will be used if your account has been activiated. You don't have to do anything to your osC integration to get it. If you are not seeing the new flow (check the upper right for "breadcrumbs" in the "not a PayPal user" branch), the best thing to do is contact customer service who will be able to turn it "on" for you.

IPN retries until it is successful. Our server looks for a "2xx" response from your web server (e.g., "200 OK"). Make sure you aren't catching errors and returning a page wth a 200 response. 500 errors should be returned if you want the IPN server to retry.

If the setting is On in your account, buyers should be going through the optional sign up flow. It's not a situation where the shopping cart could turn it on or off. You should see this: https://www.paypal.com/xclick/business=ruby...ld.com&amount=1

Regarding https and cURL: Since PayPal does not require IPN transmissions to be "https" (no credit card information is being sent), it is OK to go with "http" in which case fsockopen can be used. It might be preferable to default to this since it is nearly universally supported whereas cURL and https are much less broadly supported.