I think Payflow Pro or Payflow Link, both from Versign, are the standards for CC processing. PayflowLink just provides a link off your web site to do the processing while Payflow Pro allows you to do much of the processing from your web site. PayflowPro integrates thru a COM object, I believe. Both work well with VFp but I'd recommend starting with Payflow link, since it's so much easier, unless you require more...
>Hi Rick,
>
>I am a novice at web apps and processing credit card transactions but I have a pressing need to tackle both. If I purchase your Web Connection and you Web Store, will I be able to avoid other third party purchases such as the Developer Kit from Go Software?
>
>My immediate need (for a new retail client) is to provide CC processing integrated into our POS app. This client also wants us to develop his web site so that customers can review their purchase history and also make purchases. The onsite retail location also wants that web interface to be available at a "kiosk" in the store so that walk in customers can have the same access as customers using the internet.
>
>Thanks,
>
>Ken
>
>
>
>
>>>Hello everyone,
>>>My secure e-shop gets credit card information and saves it to the VFP table.
>>>Is there a class that executes electronic transaction.
>>
>>I would be very careful about spending any money on a third party solution for another third party solution for another third party solution to CC processing as each step of the way costs extra money.
>>
>>If you're looking for Internet based CC processing the best way these days is to sign up with one of the IP gateway providers like Authorize.NET or PayFlow Pro.
>>
>>These services are easy to use (PayFlow provides a COM object - Authorize.NET let's you use a plain HTTPS POST which is great).
>>In fact, I just switched my provider from AccessPoint (another option that uses HTTPS POST) to Authorize.Net and the whole process cost nothing in setup fees, the only charges are monthly for the gateway ($15/mth plus transaction charges) and I was up and running the next day although I did have to create the POST interface for the provider.
>>
>>There's more info on the services that I wrote up as part of my Web Store documentation. Although it's part of the store docs the info there is applicable generically:
>>
>>http://www.west-wind.com/westwindwebstore/docs/index.htm?page=_13U0XJX0K.htm
>>
>>You might find it useful as a starting point. Given that no matter what you'll have to right some sort of interface to whatever API/Provider/Software you use you might as well do the integration at a lower level which is cheaper and more efficient.