[ic] Protx Payment Module Authentication

Lyn St George lyn at zolotek.net
Wed Jan 7 20:37:07 EST 2004

On Wed, 07 Jan 2004 18:01:44 +0000, Sandy Thomson wrote:

>Lyn St George wrote:
>>  It depends on just how much stuff you want to log - the expiry is
>>  logged so that, if you are doing regular repeats, you can see when
>>  the card is about to expire. You may of course log anything else you
>>  think useful (note though that the CV2 number should not be logged
>>  under Card Scheme rules).
>Ok. I have thought about it and think the default is ok.
>>  Their test server only really does a Luhn 10 check, but their live
>>  server takes the response from the bank and passes it on to you, so
>>  this one is definitive.
>Ok, cool.
>I have been trying to get the webpages protx and protxr working for 
>refunds etc.
>Initially i had a 'not null' modifier in the postgres table i was using, 
>but after removing that things started to happen.
>Basically, when i input a valid transaction into the webpage it gives 
>the web browser an internal error.  An error is generated in the error 
>log saying DBD::Pg::st fetchall_arrayref: there is no such statement 
>executing at lib/Vend/Table/DBI.pm line 1840

It's quite a while since I tested things with Postgres, but it worked then.
I don't recognise that error message at all, but it seems to imply that
Postgres can't find input values it needs. I don't have Postgres set up
here at the moment to test with, but I suspect that you haven't logged
the  values it is expecting to find. Try exporting the transactions table
after logging a purchase to see what is really there. 

Hmm.. Try this: in transactions.pgsql, define the field next as
'vachar(3) default 0' (or just update this field to be 0 in the table)

>Possibly some routine is exiting prematurely. I have the protx profile 
>in etc/profiles.order and the route in catalog.cfg. I also added the 
>extra lines to etc/log_transaction.
>Sometimes i get a 'This Transaction Type is not valid' error from 
>StatusDetail in the payment_results hash. I assume this is a reply from 
>protx and i dont think you can do certain TxTypes on the testvps server.

You can do everything on the test server that can be done on the live
server. Probably, you are trying to do an operation on a transaction
which is not allowed, eg, a 'refund' on a 'preauth'.

>Any hints? I have lots of not null modifiers in orderline, and was 
>wondering if this would affect it? I have the correct permissions on the 
>tables.  I am also using these pages directly (without the admin UI).

The orderline table is not used at all (though it should be, for doing 
refunds/returns - this creates a problem with negative amounts in the
system which is why I haven't got around to this part ..). I've never
tried to use this terminal separately to the Admin UI, as it was designed
to be part of it - though I suppose it should work more or less ...

>Thanks again,

Lyn St George
+ http://www.zolotek.net .. eCommerce hosting, consulting

More information about the interchange-users mailing list