I posed this question to Alex and his response was that it was not possible at this time. I'm guessing that it is a feature that may not be necessary to anyone else - but I felt that I would share it -- just in case. SPECIFICALLY: IDEA ONE: I wanted to have multiple sign-up pages that tie directly to a processor. I wanted to be able to specify the processor that was used BASED on the signup page being chosen. For example, if it was signup1, then 2checkout was offered to the customer; if it was signup2, then paypal was offered. Depending on the site transaction volume, being able to spread the traffic among processors can be beneficial to the webmaster. IDEA TWO: *NOT* using paypal recurring -- having the ability to pass a different paypal account email (or IPN setup) for a particular site. Example: I use my amember to control access for fred's site which is on my server. I can't bill for him under my account though because that would violate my terms with the processor. If however, I could send his paypal-email address with the purchase, he gets the money and I can still provide his access services. Example from manual of another company: Always open for comments ...
1. You can call signup page as http://www.yoursite.com/amember/signup.php?hide_paysys=paypal_r and only PayPal will be selected on this signup page (in fact, even this fact will be hidden). 2. aMember Pro is designed to handle one site only. Fred could order a copy and use it for his site.