PayPal Website Payments Pro 2 questions . . .

[jlr1001]

I'm using the PayPal Website Payments Pro contribution created by pbreit. This is the one that doesn't require you to download the Paypal SDK.

 

I'm testing it with sandbox and everything is working great except for two small things. 1) The payment status isn't updated. In the module parameters there's an input field for the ipn url. However, I'm not sure what to put here. In the past I've experimented with the paypal ipn contribution. Should I put the url for that module here? If not, what IPN url should I use?

 

2) I can't test products that are downloadable. Basically OSC skips verifying a delivery address with downloads, which it should. However when you try to confirm the order this contribute (or Paypal possibly...) freaks because the "shipping address is missing". How do I get around this? Is there a hack?

 

Again this is an awesome contribution, and once I fix these two issues I'll be ready to go live!

 

Thanks,

 

 

 

-JLR1001

919-641-0134

[dragontale]

Sorry that I don't have an answer for you. But I have a few questions:) I really appreciate if you can help:

 

1. In the module, they asked for "PayPal BN identification code" and default value is:"OSCommerce-2.2MS2". Should I change this ? it yes, what to chage it to?

 

2. When you say, you tested it in sandbox, is that mean that I have to have a "Paypal website payment pro 2 " to test it? If not, could you explain a little bit on how to test it?

 

Thank you in advance.

-Steven

 

I'm using the PayPal Website Payments Pro contribution created by pbreit. This is the one that doesn't require you to download the Paypal SDK.

 

I'm testing it with sandbox and everything is working great except for two small things. 1) The payment status isn't updated. In the module parameters there's an input field for the ipn url. However, I'm not sure what to put here. In the past I've experimented with the paypal ipn contribution. Should I put the url for that module here? If not, what IPN url should I use?

 

2) I can't test products that are downloadable. Basically OSC skips verifying a delivery address with downloads, which it should. However when you try to confirm the order this contribute (or Paypal possibly...) freaks because the "shipping address is missing". How do I get around this? Is there a hack?

 

Again this is an awesome contribution, and once I fix these two issues I'll be ready to go live!

 

Thanks,

-JLR1001

919-641-0134

[jlr1001]

Sorry it's taken me so long to reply...

 

1. I believe that is the setting you'd use to tell Paypal the software you're using to access the api. It's proobably an arbitrary parameter since you'd have to be able to put your own id in there if you developed your own shopping cart. (I imagine it's the same as the "browser type" information you'd see in your weblogs). That way the Paypal people can identify shopping carts that successfully (or even fail to) interact with their api.

 

I'd just leave it to its present setting.

 

2. Hmm. Not quite sure what you're asking here . . . Basically, paypal has a development area where you can test its features before making your shopping cart live. You can find it at developer.paypal.com. You should go there and create an account. You'll, then, create a fake paypal account and make it a business account. (Since this is a test account all of the verification stuff doesn't really happen, so you just apply to have it verified and it automatically becomes one). Finally, you "apply" for a web payments pro account for this fake paypal business account.

 

Once that's successful--I ran into problems because the system kept trying to verify my social security number. If you have that problem, put in a fake tax id number instead and the application should go thourgh--you create an api certificate. This is the exact process you'll have to go through when you apply for the real web payments pro account.

 

Now you upload the sandbox api certificate to the proper location in the WPP module and when you install the module in the backend you need to make sure it's status is "test" not "live" and that the api cert it's looking for is the sandbox one. Also, when you created the certificate you would have created an api password (the username it generated for you).

 

Enter that username and password into the module and save everything. Now when you make a payment through your shopping cart it show up in your sandbox account. That way you can make sure your shopping cart is functioning without having to use real money.

 

Once everything's to your liking you'll apply for a real web payments pro account. When you're approved (and this takes several business days) you'll go through the exact steps you did for the sandbox account: creating the api username and password, generating the api certificate, entering this info into the module, uploading the real api certificate, setting the module's status from "test" to "live".

 

And, then, you're up and running.

 

Hope that helps.

 

 

 

-jlr1001

 

p.s. Sorry for the long post.

 

 

Sorry that I don't have an answer for you. But I have a few questions:) I really appreciate if you can help:

 

1. In the module, they asked for "PayPal BN identification code" and default value is:"OSCommerce-2.2MS2". Should I change this ? it yes, what to chage it to?

 

2. When you say, you tested it in sandbox, is that mean that I have to have a "Paypal website payment pro 2 " to test it? If not, could you explain a little bit on how to test it?

 

Thank you in advance.

-Steven

[dragontale]

Thanks a lot!!

 

I got everything working. And I also learned how to use sandbox!! Thanks again.

[jbeales]

jlr1001 -

 

I'm having the same problems as you were - did you ever find a solution?

 

Thanks a lot,

 

John