AFAIK the different responses the diferent payment gateways return all
point back to either:
- card data invalid
- card not chargeable
- charging deferred
- card charged with transaction id
Problem with processor might also be nice, although I suppose it goes along with "Card not chargable". Maybe two cases like this:
- card not chargable (card or bank problem)
- card not chargable (gateway problem) (like connection issues, protocol problems, etc.)
I agree - I also think other things can be added in case gateways
eventually add features (ie. insert id is a part of PEAR::DB, but only
supported by a few DB's that have auto_incrememnt IIRC).
Well, only a few have auto_increment, but with DB I think you can always get it back. Some drivers just emulate it (actually, you're supposed to use "sequences" when the driver doesn't support it...or actually all the time, I think).
--
paperCrane <Justin Patrin>