[bop-devel] Is this list live?

[cpan at heckman.net]

Hey,

Is development on this module still ongoing?  Is there some kind of archive for this list?

While I'm a newbie to the OnlinePayment module history a few things jump out at me regarding v2 and v3.

It seems like there should be a standard for field names with each module adapting the field name to their processor's idiom.

Is there a reason we don't have standardized data validation?  I know that some processors charge by request so a user putting in invalid data can cost you $.20 - $.30 per attempt.  By having the data validation routines in the core OnlinePayment module we can catch and reject requests before we even make an outside connection.

Is there a reason we don't have authorize, capture and refund methods in addition to the commit method?  Leaving each module author to define the value you send to determine if you're doing an authorize or a capture makes it difficult to change from one module to another.

Personally, it also seems like creating a 'merchant' object which contains the merchant information and is an object factory for transactions would better seperate the merchant specific information from the client information.

Sorry for the rambling email - I've been thinking about this quite a bit lately.

-Mike