At 02:24 PM 04/20/2002 -0400, you wrote: >What is their definition of third party processor. Would that include >Authorize.net and the like?
So far as I have been able to read into this, and this is only my take on it (mastercard isn't talking with anyone as lowly as a "little" web dev company), it's strictly companies that act as the payee on the card. Authorize.net and most processors simply act as the conduit. If you have a commerce site and the charges appear on the visitor's card under "YOURCOMPANY", Mastercard is fine with that. If, however, The site is "YOURCOMPANY", and the charges appear as "PAYPAL" who in turn pays "YOURCOMPANY", that's where the issue lies. It is about accountability. ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
