I've developed a SECPay payment module. Just wondering if anyone else has been working on one, maybe you have a private module not yet shared and would like to join forces. Just putting the feelers out for now as not yet gone live with the module (although that should be happening today).
Fri, 07/11/2008 - 06:43
Re: SECPay (PayPoint) Payment Module
Is there no-one that needs/wants a SECPay module?
Re: Re: SECPay (PayPoint) Payment Module
How far did you get with the PayPoint module? Are you at a point to make it available or do you need some help with coding / testing it?
Needs taking to the next level
At the moment I have implemented the SECPage payment method. It's like PayPal standard where the user is redirected to the SECPay site to enter payment details. When the user submits their payment on the SECPay site, a callback is made to the Ubercart site and the payment is processed based on the callback parameters.
I have it running on one site and it's working fine. We had to change the authentication of the hash to add a comment to the order (if it failed) as orders where being completed on SECPay but being rejected by the module.
I have implemented the basic structure of the module but it needs taking to the next level. Ideally I would like to post it on drupal.org and fine a co-maintainer willing to help improve the module. Any offers?
Re: Needs taking to the next level
Do you have a list of things to do in order to take this module "to the next level" ?
I'm willing to peel it open during the integration for a client, and amend anything you feel needs work.
Add to drupal.org cvs and grant 'budda' permission if you wish.
Cheers for the work done so far.
secpay payment module
Just found out a client wants to integrate secpay from the current paypal account so this would be very useful for us. The deadline is asap as well so could test.
Okay, here we go...
Okay, here we go...
I have attached the most recent version of the SECPay module. I renamed all the references to 'secpay' to 'paypoint' and made a couple of slight improvements that I have only half tested. I have this running on a client site so I know it works fine in that environment.
If someone could set this up and do some testing that would help get this in a good shape for release on drupal.org. Please post back here if you have problems or suggestions on how this can be improved.
Here's a short list of what I think needs doing:
- Make checkout messages editable in the admin settings
- Implement payment page templates
- Implement other available options provided by the service
- Add more security checks (e.g. IP address)
- Tighter authentication (this sometimes fails)
- Documentation for installation and usage
- Integrate other services (currently redirects user to SECPay site)
Re: Okay, here we go...
I have added this module to drupal.org. Please post all issues, bugs, suggestions to the issue queue over there.
Re: Re: Okay, here we go...
Just saw that come up in the new modules feed. Awesome work. 
Re: Re: Re: Okay, here we go...
Thanks Ryan. I'm going to try and make this module as flexible as possible so it works with all PayPoint.net's different payment services. Would be great if someone could take a peek at the code and make sure I'm not doing anything stupid 
Re: Re: Re: Re: Okay, here we go...
Totally... and I really need to document some recent work I just did on contract. Basically, UC 1.6 and UC 2.x extends the ability of the credit card payment system so you can specify and support multiple transaction types through your payment gateway module's charge function. It passes in the transaction type in that data array (finally found a use for it!) and lets you store authorization IDs for delayed capture and reference IDs for subsequent payments. You can process these now through the "Process card" form. Chapter Three, LLC sponsored the development for one of their clients.
It rocks. 
(The code is available in bzr for now... I'll document it as soon as I can.)
Re: Re: Re: Re: Re: Okay, here we go...
Oh wow, that sounds awesome. Thanks for letting me know if this change. Will do a checkout from bzr now.
Re: Re: Re: Re: Re: Re: Okay, here we go...
No problem. You can see in this attachment (an altered version of Souvent22's Payflow Pro module) a w.i.p. version of a payment gateway integrating the new API.
| Attachment | Size |
|---|---|
| uc_payflowpro.zip | 31.2 KB |
secpay module
removed this post as the problem detailed in it turned out to be a typo (yep I feel dumb now) and nothing to do with the module. 
Sorry and thanks for a great module which is now working fine.
Andy
Any chance of a Drupal 6 port
Hi,
Just had a client ask for this instead of worldpay in a system I've already built in Drupal 6 and UC 2. Do you have any plans to port it to version 6?
Thanks
Alex
------------------------------
http://zero-design.info
Re: Any chance of a Drupal 6 port
I would also like to know if or how I can port this module to Drupal 6 & UC 2.
Re: Re: Any chance of a Drupal 6 port
Check out http://drupal.org/node/418154
I think I've managed to change all of the relevant code to work with Drupal 6. Please can someone badger psynaptic to have a once over. I'm hoping that the 'Implementation of hook_menu()' has been converted correctly. If there are any problems with it, I'm assuming it's the 'if()' statement. This used to be 'if($may_cache)' beforehand, so I removed the '$may_cache' from the line and Coder was happy with it.
Onewayticket