Jump to content

sponna

Members
  • Content count

    42
  • Joined

  • Last visited

Posts posted by sponna


  1. Ref. the reason for updating the module, the changes were made to incorporate 3D-Secure and Authenticate and Authorise. All options are switchable from admin i.e. no changes needed for the 3D-Secure options or payment type within the code itself.

     

    Thanks


  2. Hi,

     

    Good point but I would have to make it a condition of sale up to the point that I break even on the development. After this I will make it available. To date I have one potential taker but then Protx are not quite ready at their end yet :(


  3. I look forward to seeing something in the contributions section soon.

     

    Unfortunately I had to pay to have the development done and tested - once I've covered the cost, I'm more than happy to make it a contrib. However, as I'm currently a fair bit out of pocket, I'm keen to break even. Seems reasonable?


  4. Hi,

     

    The code will be tidied up to core oscommerce standards. I appreciate that the existing contribution does use the 2.22 protocol and (apparently) supports 3D-Secure - at least in part. I'm not sure that the international Maestro check is supported however.

     

    The update will support international Maestro plus all 3D-Secure and authenticate and authorise. The latter part is Protx's replacement for "preauth" which will be defunct in a couple of months time. Preauth is used by merchants who cannot guarantee to despatch and charge the card within a set number of days (I think 6?) which precludes the "deferred" payment option. You can read about this on the Protx news page.

     

    So in summary, the update will be cleanly coded, support all current 3D-Secure options and "authenticate and authorise" (plus the existing "deferred" etc options).

     

    Thanks

    Dave


  5. Hi,

     

    I'm just about to have the contribution updated to cover 3D-Secure and support "authenticate and authorise". The code will also be cleaned up. I'm just looking to cover costs on this - so if anyone wants it when its done, I'd say $50 (or £25) will help towards it.

     

    Please post or pm if you are interested.

     

    Thanks

    Dave


  6. Hi Dave,

    Well I have checked and at the time we installed it (August 2006) it was the latest version - protx form V1.0.9 cart details by Mike Jackson. I then added all the patches eg. success redirection, so it should be virtually the same as the current 1.09 version. It does indeed use the 2.22 protocol.

     

    Best of luck with the changes

    David

     

    Hi David,

     

    I've loaded the lastest module and all seems to be working except that the cart details are not passed to Protx i.e. it still shows "pay for My Store Name" at Protx. This is not critical but it would be nice to get it working correctly. Did you have any probs passing the cart details please? Looks like I may need to get my (dusty) coding hat on!

     

    cheers

    Dave


  7. Hi Dave,

    Well I have checked and at the time we installed it (August 2006) it was the latest version - protx form V1.0.9 cart details by Mike Jackson. I then added all the patches eg. success redirection, so it should be virtually the same as the current 1.09 version. It does indeed use the 2.22 protocol.

     

    Best of luck with the changes

    David

     

    Thanks David - I'm hoping it should be straightforward; copy over the old module, input the encryption code, vendor etc and that should be it :sweating:


  8. I have just upgraded to 3D-Secure without making any changes to the module. Touch wood all the orders are going through as normal. I don't use any pre-auth or repeat payments etc. just the standard transactions.

     

    Thanks for the update - presumably you are using the 2.22 protocol (or later?) - I will need to update the payment module for several clients :(

     

    Which contrib. do you use please - I'll go with that as it seems to be working well for you.

     

    Authenticate and Authorise - I have a couple of clients who can't use the "deferred" option so we'll need to look at "authenticate and authorise" as soon as Protx get their finger out with the test area - we've been unable to scope it so far due to delays at Protx - ho hum.

     

    Thanks

    Dave


  9. Hi,

     

    I've just received another email from Protx about the update, they say "The changes to your code are trivial" so hopefully any changes should be minimal.

     

    Dave, you mention that there would be a cost involved in making any change, how much would these costs be?

     

    Thanks

     

    Trevor

     

    Sorry for late reply - kinda busy. I will dimension this over the coming weeks and post back when I know more. Hopefully the changes are indeed "trivial".

     

    cheers

    Dave


  10. I see that PROTX are contacting all their customers to inform them that 3D-secure will be needed for processing international Maestro Cards later this year (June?).

     

    Would I be right in assuming that the PROTX Form module will need upgrading to allow this to happen? And does anyone know what changes will be needed?

     

    TIA

    David

     

    I'm also thinking that Protx Form will need to be modified - for 3D secure and possibly also because "pre-auth" transactions will not be supported. This is being replaced by something called "authenticate and authorise". A number of us will be affected no doubt. If necessary, I can have the module altered if people are willing to split costs - I'm still in contact with the author of the original contrib.

     

    Thanks

    Dave


  11. Hi,

     

    I just (a bit late) did the August security updates on a number of sites which seems to have caused a small problem with the call-back to site after the user "cancels" at Protx.

     

    Before the update, cancelling at Protx brought the user back to the appropriate place in the check-out from where they could try again. Now it just defaults to the index page. A completed order goes to the success page as expected. I've validated this across several stores (test and live protx servers).

     

    Anyone else seeing this please? Is it a session corruption issue? Not sure where to look at the moment.

     

    Thanks

    Dave


  12. Hi,

     

    We have a client running an MS1 store (very limited mods) and despite searching through the contrib. notes and thread, I am struggling to see which version is best for an MS1 install (tax included in prices).

     

    This is for a live and succesful store so I'm very keen to get it right first time and not screw it up!

     

    Grateful for any advice on which version I should use please.

     

    Thanks for what looks like a great contrib.

     

    Many thanks

    Dave

×