Welcome aboard, mccool. I haven't heard of this one, unfortunately... hopefully you can use one of the existing CC modules as a starting point for the integration.

For documentation, you might check out hook_payment_gateway(). If Protx is just a service that you can submit data to remotely for processing a credit card, then maybe start w/ something like uc_authorizenet.module. If it's a hosted solution where you actually have to be redirected from Ubercart to complete payment, you'll need to mimic something like 2Checkout or PayPal Website Payments Standard. Then you'd need to check out the payment method docs.

Hi browman.

I'm just getting started - but I don't have the Protx account details from the client yet and I'm not sure how far I can get without them. I will hopefully have the required details by the end of the week.

Meanwhile I am investigating the Protx documentation and other Ubercart payment modules to get an idea of what I need to do.

My client is going for the VSP Direct package and wants it live for early January.

What's your plan and time scale? I'd be happy to collaborate!

Ok - displaying my full noob colours here!

I'm trying to create the Protx payment module, based on the uc_authorizenet.module, and I am fairly sure I know what I need to do.
I have my new Protx module installed, and in use, but at the 'Review Order' page, submitting the order just returns me to the same page.
If I manually force a success in the module, it processes the order.
So I need to debug my function uc_protxvspdirect_charge($order_id, $amount, $data).
I have installed the devel.module but I can't seem to get the function to display any of it's variables on the page. I need to view what the response is from the POST request.
So how can I display variables and arrays on the page.
I have tried using dsm() dvr() dpr() but to no avail.
Am I missing something obvious or do I just not understand how to use the devel module?

Any help or pointers greatly appreciated.

Cheers!

Hi Ryan.
Thanks ever so much for your swift reply.
I have the debug info displaying now - the problem was that I didn't have the $messages block set to display in my theme.
Doh!
A simple mistake which meant I was missing loads of information after every request.
Thanks again!
I'll crack on.

Hey robserious.
After much messing around I do have it working now - I will tidy up the code, read up on submittig contributions, and post it up.
It is for the Protx VSP Direct service, not VSP Form or VSP Server - just to be clear.
Cheers.

Hi Guys,

I've just uploaded an UC module which does the job of connecting to the Protx VPS Forms service.

It's here: http://www.ubercart.org/contrib/2773

Seems to work pretty well, but I would advise testing before production use. Please report any bugs and fixes on the comments thread..

( formerly 'browman' )

I'm hoping to have one finished this weekend, and will post it here when I'm done. It'd be useful to have some guinea pigs.

I have a working version, but unfortunately there are a couple of issues for core that need addressing before I can release it:
1) Reliable page referers. This is addressed somewhere in this thread.
2) Card Start Date & issue number. This is being discussed here.

The first seems halfway to being settled, and for the second it's been suggested that this could be an "enhancement module", but I think it's basic functionality that's required for Amex and Maestro, so it makes sense to standardise it and not make unnecessary dependencies for payment gateways.

A quick follow-up...

The issues I mention above are, I'm hoping, close to being committed into core. I'm hoping, therefore, to be able to release this module over the coming week or two; but there's still a niggling issue with the Protx Test Server integration that I have to fix.

@solarian: Nice I just got here, I am also into the task of developing this, actually I have already started lying out the main functions and i will certainly look at yours.. would you accept collaboration on this module, either in form of commits or patches? Anyway, will look at your module and let you know my thoughts.

a.=

I will soon start testing it and getting back to you if necessary, so far I can think of two improvements:

1. Support for AUTHENTICATE and DEFERRRED transaction types.
2. Store information that got back from the protx server in some internal table so more information can be available to the site owner and linked to the actual order.

Looking forward to your CVS account on drupal.org. In my case, I never got an answer from drupal.org but I found a CVS access tab on my user's profile and I was able to set me up a password there and then I was able to access it.

a.=

Just for information, Lemonbiscuit has just updated the VSP forms module and it works a treat!

Thanks for taking in my comments.

I noticed where you were storing the information from protx a little while after I posted my previous comment. That's perfect for now, but I still need to see how that data is available in case I work out somehow the AUTHENTICATE/AUTHORIZE part. I posted some ideas about implementing that in another post without any response yet. The post is http://www.ubercart.org/forum/development/5922/authenticateon_checkoutau...

I am probably adding a configuration entry to the gateway settings function so you can select between PAYMENT or AUTHENTICATE as a first step to handling AUTHENTICATE in your module.

I reviewed your new module code and so far I have one more comment.

I noticed you added base_path() to all of your drupal_goto() calls. drupal_goto() takes a drupal path as an argument, or a full URL, and a drupal path is just the path without anything else as you have it before or a full 'http://www.example.com' URL.

So for instance:

Should be set back to:

As you had before.

I don't mind at all Once your project got submitted I will probably start posting patches/suggestion in drupal.org. If at sometime you feel comfortable wiht my suggestion or you want to co-maintain that module I would be happy to commit things directly.

Anyway, just a few more comments in the line of the last fixes with url(), base_path() and stuff.

• Line 533:
<?php
    $redirect = base_path() . 'cart/checkout/complete';
?>

to

<?php
    $redirect = 'cart/checkout/complete';
?>

 

• Line 537:
<?php
    $redirect = base_path() . 'cart/checkout';
?>

to

<?php
    $redirect = 'cart/checkout';
?>

 

• Line 462 and line 541:
<?php
             <iframe name="Secure3D" id="Secure3D" src="'.base_path().'uc_protx_vsp_direct/3DSecure_waitingPage">
?>


<?php
    $output = '<html><head><title></title></head><body onload="document.forms[0].submit();"><form name="uc_protx_vsp_direct_3dsecure" method="post" action="'.url($redirect, null, null, true).'" target="_top"></body></html>
?>

I do think that using url() as you did in this last version for line 541 is the way to go and the same thing should be done to line 462. Just one question, why did you pass the absolute value to TRUE? Does it need to be an absolute URL? Anyway, I am almost sure that using a plain url() would work.

<?php
             <iframe name="Secure3D" id="Secure3D" src="'.url('uc_protx_vsp_direct/3DSecure_waitingPage').'">
?>


<?php
    $output = '<html><head><title></title></head><body onload="document.forms[0].submit();"><form name="uc_protx_vsp_direct_3dsecure" method="post" action="'.url($redirect).'" target="_top"></body></html>
?>

There is now an official release at http://drupal.org/project/uc_protx_vsp_direct

hanoii -- you have CVS access. Enjoy!

There's a reference to the project here too, at http://www.ubercart.org/contrib/5990, but please submit bug reports via the d.o project page.