Home/ Questions/Q 908743
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T16:45:53+00:00

Note: Our site is built in PHP and uses MySQL databases. I already manage

  • 0

Note: Our site is built in PHP and uses MySQL databases. I already manage another site with shopping cart in its entirety using Authorize.net so please dont respond with suggestions to use another provider. A new product/service we are releasing is classified as “High Risk” to the merchant providers and they want to charge us out the a**. In response, I figured setting up a Website Payments Standard account on Paypal.com was the best alternative for the following reasons:

1) no monthly charges, only pay for what is used

2) trust brand and people are comfortable with Paypal

The rates are quite a bit higher than we are used to but any High Risk Merchant account is so that is irrelevant. The issue I am running into is this:

1) throughout the registration process on our site, we collect quite a bit of user information and pass it from page to page using SESSION variables. When you use Website Payments Standard, you are forced to pass the consumer off to a Paypal owned webpage to submit their payment information. Upon successful completion, they are able to direct them back to a ‘confirmation’ page on our site but it is my understanding there is NO way to keep the old SESSION variables in tact. This is very important to us because the overall concept is to store the SESSION variables ONLY after successful payment has been made.

2) Using Website Payments Standard, I am unable to find a way to send a Pay-Amount variable (everything must be dictated up front, i.e. T-shirt is $2.99). Our site allows the consumer to enrollee multiple persons and have several ‘add-ons’ for each person so there are literally over 100 end check out amount possibilities. I am not sure if it is possible to override this.

Has ANYBODY had luck using Website Payments Standard on Paypal acknowledging the information above?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    1) Assuming the Session is cookie based, it should still be there when they come back to your site (as long as they havn’t closed the browser window in the mean time which is unlikely).

    If you really wan’t to be sure, store the session in the database in a temp table associated with the order_id you’re generating. I belive it’s possible that this (order_id) is passed back after the transaction is completed. Read the docs on PDT.

    2) I belive this is not the case. Check the docs page 250 onwards.

    • 0