On Mon, 12 Mar 2001 17:34:14 -0500, Russ Cobbe ([EMAIL PROTECTED])
wrote:
>> On Mon, 12 Mar 2001 17:04:13 -0500, Russ Cobbe ([EMAIL PROTECTED])
>> wrote:
>> >If you are worried about your payment processor going down (which
>>to
>> >me would be a very serious concern) you might want to look at
>> >www.opayc.com which is a standardized way to talk to about 30 or
>>so
>> >payment processors.
>>
>> what makes you think that this company is less likely to go under
>> than a company like cybercash? this isn't a flame, I'm looking for
>> info.
>
>It isn't a payment processor it is an API to payment processors such
>as CyberCash, Authorize.Net, Signio/Verisign, iBILL etc...
>Basically
>you make an SQL call to a driver instead of a database and that
>makes
>the call out to the payment processor. The eliminates the
>complexity
>in dealing with the payment processors. Sometimes the integration
>with them is easy and sometimes it is a royal pain. This makes the
>integration the same for all of them so you simply switch drivers to
>switch payment processors. You could build a failover system so if
>the one you mainly use goes down for some reason you could build in
>logic to switch to another one quite easily.
hmm, yes but you're still relying on them for the driver updates, I'm
sure all the payment processors change their system every once in a
while.
The failover system sounds like a good idea if you don't mind signing
on with 2 payment processors, but otherwise it seems like all you're
doing is adding an extra layer where things can go wrong.
I'm leaning towards verisign/payflow pro. has anyone had trouble with
these guys?
thanks
- Mark
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
