TOPIC: [SOLVED] Paypal attempting to charge shipping at checkout

Does anyone know how I can get Paypal to stop trying to charge for shipping when I checkout after registering for an event? I need to fix this before I go live.

Scott

Hello. This has nothing to do with DT Register, but a setting in your PayPal account. Go to your PayPal profile, then under the column "Selling Preferences" click on "Shipping Calculations". You'll see shipping options that you or someone has setup. By default, there would be nothing there. To not have any shipping calculations provided in your checkout, you'll need to remove these. Click the checkbox on the left of each calculation. Then click the DELETE button.

With these shipping calculations removed, they will not be offered in your payment process. Thanks.

Thank you for the reply. I understand how to alter the shipping calculations in Paypal, but removing shipping fees assumes that we don't sell anything else with that account. However, we sell books, which do require shipping fees.

It appears that the registration fees through DT register are being sent to paypal as merchandise, this triggering the need for a shipping address and shipping charges. Is there a way that they can be sent to Paypal as a service fee or something other than goods?

I've fixed it so that we don't charge shipping for the registrations for now, but when we next sell a book, the customer won't be charged for that, which won't be cool.

-Tonight, we sold a book, shipping was not charged, and we lost our profit margin.

There has to be a better way than this, right? I find it hard to believe that all of the other DT Register users only use Paypal for DT register and sell nothing else on their site, but I could be wrong.

Scott

Scott, it is true that this has never come up before. We are looking into and working to resolve the issue in the next release, which is just around the corner... probably about a week out.

Any word on this fix? I've had to shut down DT Register so that we can sell our books.

I'm having the same problem . . . it's now April 14th, and still no fix or workaround like was suggested months ago.