Re: Payment_Kddi class

On Thu, Apr 11, 2002 at 01:32:55PM +0200, Stig S. Bakken wrote: > On Thu, 2002-04-11 at 05:36, Naoki Shima wrote: > > Hello all, > > > > I've been developing class which handles processing prepaid card using > > KDDI Payment Gateway Service(XS-3). KDDI is one of the leading > > Telecommunication/ISP here in Japan and they provide credit/prepaid card > > processing service described above. > > This class requires pear/SOAP/Client.php, XML/Parser.php and curl extension. > > You can view the script at > > > > http://www.avantexchange.com/php/repository/example/show.php?file=/php/repos > > itory/Payment_Kddi/Prepaid.php > > > > I'll add this to PEAR if you guys like it. > > Now that we're starting to get multiple payment interface classes, I > think it's important to try finding a common API for all of them. I > have no experience with any payment systems though. Now, there's abig difference between verisign/KDDI and clieop payments. KDDI/Versign are processing online transactions, while clieop is a more bankground process for larger companies. Versign/KDDI handle only one payment each time, where clieop uses batches. But that doesn't mean there can't be a generic interface to Verisign and KDDI. I will try to find some similarities between verisign and KDDI. I think both work with cardnumbers and expire dates. Both have to make a connection with a payment server and i think both protocols can poll the status of a payment. Later one this week i will add a payment class for the Bibit payment system. They already provide a light-weight php class for quick implementation. But there's no error trapping and validation so ever. Another project that i about to start is to create ISABEL data files. ISABEL is a belgium payment system for processing large batches. They have a similair way of building data files. Both have a file containing batches and each batch is containing transactions. Later more on this.. Dave Mertens