Choosing the right Paypal system to process signups and subscriptions

Question

The payments we collect on our website are for online subscription and conference registration. In both cases, we want to collect absolutely all information other than payment information , and ideally transfer part of it to PayPal (so that users do not need to fill in a name, address, etc. twice).

I know that there are solutions in which information is collected by the server itself and then redirected to PayPal through a call to web services, but this is not an option, unfortunately. All information collected about payment payments must be performed outside the server due to network policy.

In addition, not every form must be processed using PayPal. Some people will pay by check, etc. Therefore, they should not be sent to the payment page at all. Most of the solutions that I looked at have a Pay with Paypal button, so I assume that the message with the form needs to be sent to the PayPal website, but ideally we want to get there through the 302 redirect. Is this possible? (I know that we could do something like a form that was automatically submitted by JavaScript, but I would prefer not to go this route).

Depending on which system was implemented, you will also have to process recurring (periodic) payments.

Answer 1

Paypal -, Payflow Pro. VeriSign .

paypal api. , PayPal. Paypal . , (, ) .

, Payflow Pro. api.

Answer 2

, , , . conf. ( PayPal... iTransact Plug'NPay), API ( PayPal). , html. , , html- , API ( PayPal, ), , (, cutomer_id ..) POST .

, , , , ( ), , PayPal, ( ), , URL-, var -, (, , script ), .

, , , API .

, !