[TYPO3-paymentlib] Better Interface for processing payment datas

[Udo Gerhards, Softwareentwicklung und Webdesign]

Hello Tonni,

developing paymentlibs in the past confuses me sometimes because of 
setting the payment details on my paymentlibs. Many online payment 
provider give more ability to their payments as only sending the total 
amount . Thats why i think that the array which is used at the 
"transaction_setDetails"-method is not really a defined interface for 
providing data to the paymentlibs because each calling extension could 
have different keys for one and the same content (e.g. the delivery 
address or the basket). Als a paymentlib provider you are not able to 
develop your extensions to handle all different possibilities in the 
data array which may come from other extensions in the future.

Another problem is that a lot of extension don't use the paymentlib at 
the moment because of this problems. At the moment they could only give 
their payment data in the limited way the paymentlib provides or define 
keys by their own in the data array. But then the paymentlibs must know 
which keys are also defined and this means you have to program your 
paymentlib directly for the needs of this extension to provide further data.

I think that the paymentlib was developed to give a generalized 
interface to extensions with predefined parameters for the extensions 
data, so that underlaying paymentlibs can access these informations and 
use it in their individual way.

Therefore i would ask you if you are interested in extending the 
paymentlib with a further data-object which holds data like delivery 
address or basket data for exchanging informations between the calling 
extension and the underlaying paymentlib. This data object could be used 
in the "transaction_setDetails" instead of the array which is used at 
the moment. The benefit of this solution will be predefined methods and 
members which could be used by extensions and also underlaying 
payment-methods to exchange the payment data without the need of 
individual programmings in the paymentlibs  for different extensions.

If you think this is a usefull suggestion i could develop the class and 
extend the paymentlib with this object.

Awaiting your answer

Udo Gerhards