dashCommerce

Hi

Can anybody explain how to get the PayPal Pro Payment Provider Configuration  functioning.

I tried to enable a PayPal testaccount (sandbox) but got stuck in the installationprocess, when I had to choose between a button, cart or donate.

so I don't get any API-Credentials.

Do I have to configure a PayPal Pro Payment Provider to get the add to cart functioning.

regards Berndt

Berndt

I did manage to get a Pro account set up in the paypal Sandbox (not a terribly intuitive process) and received my API credentials. When you create a sandbox account you are issued two test accounts - one for a seller and one for a buyer. You need to log in to Paypal Sandbox using the Seller account. Log on to developer.paypal.com then click on "Test Accounts" under the Sandbox heading. Select the account that begins with "seller" then click the "Enter Sandbox Test Site" button. Note that you will use the password associated with the test account, not the password associated with your developer account. Once logged in, go to My Account, click on "Profile" (took me an embarrassingly long time to find this - it's under the row of tabs on the right), then click on "API Access" under "Account Information". Fill out the info, jump through Paypal's hoops, and voila - you're in business. Note that you will also need to set the options in "Website Payment Preferences" under Account Settings. The only tricky bit in here is the "Return URL" which should be set to http://address-to-the-root-of-your-dashCommerce-site/paypal/pdthandler.aspx

Having said all this I just now noticed the last line of your post. The answer to that is "no". You can use the Paypal Standard provider as well. In fact, I have not yet been able to make the Pro provider work - Get a 404 when clicking on "Proceed to Checkout" with Pro set as the provider. I have, however, successfully processed payments using the Standard provider.

Hope this helps,

Matt

Thanks it helped a lot.

Do you have any suggestions what i should put in the return URL when running the site on my laptop http://localhost/default.aspx ?

regards Berndt

Berndt,

In order for it to work properly you will have to supply a "public" address, either a valid domain or an IP address. In addition you will have to open Port 80 on any firewall you might be running to allow Paypal to pass back to your server. I have a domain registered so I use my domain URL to point back to the return page. If you don't have a domain to point back to you should be able to use the public IP assigned to you by your ISP, i.e. http://123.456.789.000/paypal/pdthandler.aspx. If you don't have a static IP from your ISP you will have to change this whenever your assigned IP changes. I have no idea how you are connected to the internet - connected directly, through a router and/or firewall - , so it is difficult for me to tell you exactly how to find your IP address. Your best bet would be to go to a site like http://www.ipchicken.com/ or similar to discover your address.

 Good luck,
Matt

Hi Mat

Thanks for your help.

I have a DSL connection and a router with my own ip's. I'm running cassini web server with portnr 3414.
So, when I understand you the right way my return URL at PayPal should be

http://ip_from_ipchicken:3414/paypal/pdthandler.aspx.

By the way, can you tell me what the pdthandler.aspx does?
I have some more questions about this,but I will put them in a new post. "Returning from payPal and redirect to a predefined aspx page".

berndt:

Hi Mat

Thanks for your help.

I have a DSL connection and a router with my own ip's. I'm running cassini web server with portnr 3414.
So, when I understand you the right way my return URL at PayPal should be

http://ip_from_ipchicken:3414/paypal/pdthandler.aspx.

By the way, can you tell me what the pdthandler.aspx does?
I have some more questions about this,but I will put them in a new post. "Returning from payPal and redirect to a predefined aspx page".

I quite honestly haven't even looked at pdthandler yet. I'm still wrestling with trying to get Paypal pro to work. I've made leaps and bounds but have come up against a wall with the requests timing out. I think that may just be Paypal's painfully s-l-o-w server for the sandbox. BTW, if you have not done so already, make sure you apply the ThreadAbortException exception patch found here http://www.codeplex.com/dashCommerce/WorkItem/View.aspx?WorkItemId=15426

I'm not 100% sure how/if Paypal will deal with handing off to a non-standard port. It should work, but if it doesn't you should be able to (depending on your router) use NAT to map the incoming request from Paypal on port 80 to port 3414 on your webserver. At any rate remember to open a port on your router's firewall to allow that traffic if you have not done so already.

 Matt

I'm not sure if this is the "right" PayPal thread to post this info to, but I was digging around in the PayPal developer forums trying to get my head around the many options that I have when configuring an account on PayPal, and found this gem:  http://www.pdncommunity.com/pdn/board/message?board.id=basicpayments&message.id=368.  This post is called "Getting Payment Data from PayPal: Auto Return, PDT, IPN Demystified" and was extremely helpful for me to understand what I'll call the "three little pigs" PayPal configuration scenarios, or the "good, better, best" approaches for using PDT, AutoReturn, or IPN, or both PDT and IPN.  It explains what each setting in the PayPal Profile section does (related to IPN and PDT) and gives you some scenarios on why and when you would use each.

Anyway, like I said, I'm not sure if this is the correct place to post this, but I figured it might help someone else out there to understand the enigma that is PayPal configuration.  Hope this helps someone.

Tim