Re: RFC: Credit card processing
| From: | Ian Eure | Date: | Sat, 13 Dec 2003 00:34:20 +0000 |
| Subject: | Re: RFC: Credit card processing | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-24366@lists.php.net to get a copy of this message | ||
On Friday 12 December 2003 04:11 pm, Joe Stump wrote:
> This should probably go in the Payment group:
>
> http://pear.php.net/packages.php?catpid=18&catname=Payment
>
Huh, I missed that one.
> Also, about your dataset - why not create an all encompassing dataset and
> then allow factories to gracefully handle them (ie. transaction support
> for the mysql DB driver).
>
Well, I've only had experience with two processors at this point (Card Service
International, aka CSI or LinkPoint, and DPILink), but they've been very
different. I don't know how feasible coming up with an all-encompassing
dataset would be.
I suppose that I can use DPILink as a starting point, and add more fields as
more processors get written.
I wonder if having a class for the response would help at all... The data that
each processor sends back is pretty different, and it might help to have a
class just for handling mapping those results back to a standard. On the
other hand, it might just be bloat.
That's why I posted a RFC first. :^)
> Ie.
>
> function isCvvValid()
> {
> return true; // my processing gateway ignores this so don't barf
> }
>
Yeah, each processor has it's own validate() function already. And we'd have
to map from whatever the front-end fieldset is to the back-end anyways, with
a _prepare() or similar.