Hi all, I was able to build a jury-rigged payment module for CCBill on several of my SS websites. I was thinking of improving upon it and making it into a standalone module and releasing it for everyone. But before I expend the effort on that, I'd like to see if anybody else is interested in a CCBill payment module.

Comment if you're interested!

Comment!

I'm interested in the payments!

I've got my own payment manager for SagePay and Iridium - but sent out a message like this previous about integrating those and got no response. I'd like the payments module (http://www.silverstripe.org/payment-module/) to include as many systems as possible - so I'd be up for working with you - that would make paypal,DPSPayment ,ccbill,sagepay and iridium.

Anyone know the popular payment methods in Spain or the Netherlands?

Hi guys,

I'm wanting to help polish the Payments module....this includes defining a clear API / protocol for creating new payments.
Doing so will mean that people should be able to use the Payments module for whatever system they like, eg ecommerce, or anything else.

Jeremy

Hi Jeremy,

This sounds great... is there an eta with this? I have SagePay and Iridium payment gateways that I would love to add those to it and also get the benifit of other payment gateways. Right now I have a large amount of pressure to add new payment gateways and have been looking over the Payments module again. I've renamed my Payment class to Transaction and after that the main things that seem to tie it to the the eCommerce is the format of the cart and the use of member. I've moved my system to create members for orders - but the cart part is the one I still haven't worked out how to do.

I'd be very interested in the *interface* you'd be planning on. for example...

To get a payment:

$arrParams = array(
'PaymentSystem' => 'PayPal',
'InternalOrderRef' => 'ABC123',
'Product Description' => 'html description' / array('LineItem'=>33,'AnotherLineItem'=>44),
'ReturnSuccessURL' => 'successurl',
'ReturnFailURL' => 'failurl',
'Currency' =>'GBP',
'Amount' => 77,
);

To make a refund:

$arrParams = array(
'PaymentSystem' => 'PayPal',
'InternalOrderRef' => 'ABC123',
'Amount' => 77,
);

then both will pass back upon success/failure with...
$arrRetun = array(
'Code' => $iReturnCode, //this is from a *generic* list that we can hold.
'Detail' => $arrFromSpecficPaymentGateway,
);

Basically this would allow the site to run on Paypal today and then switch to WorldPay tomorrow, but still handle refunds from Paypal... also switch from different currencies on the fly instead of being locked to the one in your config file.

Barry

Hi Barry, I've posted my ideas so far here:
http://groups.google.com/group/silverstripe-dev/browse_thread/thread/109b1df6848fd740

Hi Swaiba

Did you get your SagePay Payment Class working for the Payment module? If not, how far did you get & what problems did you encounter? If you were successfull, can I download it, or can you send me a copy?

Many thanks,
Jules

No I didn't get it working for the module - but I very well might do for the new class jadateach is talking about on the group i think - the problem with the current class is that the interface is not generic enough to fit into my system. I am really hoping we can get something that just handles payments - nothing more - then I'll move over.

Instead I took the PayPal stuff and moved it into my structure instead - more info on the google group link posted previously.

There is quite a bit of interest on this so to keep it off the main devlist I created...
http://groups.google.com/group/silverstripe-payments-module