3008 : The Vendor or Vendorname format is invalid.

[leehack]

I have nothing constructive to add Jane, but it's like reading a horror story this thread. Do yourself a favour and go for HSBC, it will probably setup quicker than PROTX. PROTX are past their best - HSBC, Barclays and Worldpay are far better solutions IMO.

I'm pretty sure what Bumpsy said is true, but they are now telling you the opposite, incredible, it really is.

[janeread]

I don't agree, Lee.

I have Protx running fine on another site, and I'm very happy with it there.

I do have merchant services already on the problem site where I process stuff offline, but many people don't like this as it is not that secure, and I think it is in breach of best practice, because even though the online encryption is secure, you then process them down an unsecure phone line from your office.

WorldPay etc. seem very expensive compared with the merchant service chrages I am paying and often you don't get access very quickly to your money.

What's that expression: what doesn't kill you, makes you stronger.

Jane

[leehack]

It's all down to opinions i guess as long as you are happy, that is all that counts. There are 20 PROTX problems to every 1 from the others I mentioned though, that is for sure. Maybe with PROTX it either sets up perfectly or you have a real pig of a job, so people either love or hate them etc.

So much IME is about who you get on the other end of the phone when you have a problem. It's even stranger if you have one site working and one not, that would lead me to compare the sites on all accounts.

As many of them seem to use the same system, perhaps you need a new secret key, that solved a number of Worldpay problems.

Can you do anything to try the details from your working site into the non working site or vice versa and confirm the problem lies with PROTX?

[TraceyHand]

Just had Protx phone me (which is very nice of them) and they've said I need to put proper vendor name and password encryption in even though I am at the testing phase.

yeh, sorry..I misunderstood as it sounded like you were putting your details into the "testvendor" area..not in Actinic itself.

[fergusw]

TBH - I wish PROTX would rewrite their PSP integration toolkit for Actinic to include all 4 fields in the "configure Method" screen instead of having to amend this screen AND the script template perl file.
If they did this then the whole process would be much, much simpler IMO, and would eliminate possibly 80% of PROTX integration problems we see.

[leehack]

Correct the email problem also and have a set procedure to adhere to when actinic users ring up, WHOEVER you get on the phone will then know how to help. Now that would be a 'serious' PSP provider for actinic.

[fergusw]

Correct the email problem also and have a set procedure to adhere to when actinic users ring up, WHOEVER you get on the phone will then know how to help. Now that would be a 'serious' PSP provider for actinic.

It really should be straight forward if the PSP toolkit for Actini is developed by PROTX properly.

1. Register with PROTX
2. They send; vendorname, secret key, encryption password
3. Bang details, along with email address, into configure method screen and "PSP test mode" on
4. Email PROTX to check and wait for all clear
5. Switch to PSP "live mode" and bob is your...... palindromic uncle

Foolproof

[leehack]

There should be no need whatsoever to go anywhere but the payments tab in actinic to setup a PSP IMO, period. If you have to, then frankly that is so 1990's.

[janeread]

I hope you are all sitting down to read this. Protx have now told me that the vendorname they gave me was too long!!!!!!!!

Is this worth posting prominently so that other people avoid the fiasco I have been through?. I also intend to write to the powers that be at Protx. It seems totally daft that their system allows someone to generate a vendorname that won't work because t's too long.

It has been shortened and the 3008 problem has gone, but now I'm getting error message 4006 TxType which is I understand about deferred payments. I don't want to accept deferred payments - does anyone know how I switch that off please?

[leehack]

Their incompetence has no boundaries it would appear, sheesh Jane, crap like that does nothing to make you stronger, all that does is scare the begeebers out of me. WTH are they playing at, yet another nail in their coffin from my side.

The setting you wish to change is on the configuration screen where you put in your secret key etc. You select pre auth or direct payment. Switch that and upload, hopefully that sorts it for you.

Glad you are on the road to correction anyway, you must be exhausted.

[janeread]

I thought it would get you going, Lee!

But I can't follow your instructions - when I go into Actinic Configure Method it gives me fields for vendorname and secret key plus two radio buttons for test mode or live.

Am I in the wrong place??

Jane

[leehack]

Sounds like you are in correct place to me but seeing different options, have you ran over a black cat lately Jane? Screenshot of what i see is attached below.

[TraceyHand]

that setting only appears in 8.5.2, Jane.
If you're not on 8.5.2, then you won't find it.

[leehack]

Well deduced Tracey Clueso, had me beat. What a dilemna, upgrade or stay on payment method you don't want. Stick with the payment method IMO. You'll be on pre-auth by law in the not too distant future anyway Jane.

[janeread]

The nice man from Protx phoned me this morning to see if it was sorted and I told him the problem I was having with the deferred payment error message.

He sent me instructions how to sort it, so i thought I'd post it in case anyone eles has the problem. The instructions are for changing to deferred payments, but I needed to change DEFERRED to PAYMENT rather than the other way round. Here's the instructions:


Actinic requires you to amend code in your shopping cart setup to use the DEFERRED transaction type.

Currently your TXType that you send to us will be 'PAYMENT'

If you wish to use 'DEFERRED' you will need to change the TXType in your OccProtxScripttemplate.pl file in your Actinic directory from:

'PAYMENT' to 'DEFERRED'



Amend your OCCProtxScriptTemplate.pl file

The OCCProtxScriptTemplate.pl file is located in the commonOCC folder in the OCCUpgrade folder within your Actinic directory. Open the file in an editor like notepad and search for 'TxType':

$sHiddenValues .= "INPUT TYPE=HIDDEN NAME=\"TxType\" VALUE=\"PAYMENT\">\n";

You will need to change the TXType from PAYMENT to DEFERRED

$sHiddenValues .= "INPUT TYPE=HIDDEN NAME=\"TxType\" VALUE=\"DEFERRED\">\n";

Then save the file.


Amend the OCCUgrade.ini file

The OCCUgrade.ini file located in the root of the OCCUpgrade folder in your Actinic directory. Open the file in an editor like notepad.

At the top of the file are the lines that look like this:

[Version]
Number=1045 (for example)

Increment this Number (so if it was 1045 for example, you will need to change the value to 1046) by 1 and save the file.


Open up Actinic

You should get a message informing you that a change has been made to your Payment Provider data and that it has been.

When you amend your Actinic code to use a certain transaction type, all your transactions will then be processed as that transaction type.