Signing the default VeriFone app

I bought two VeriShield File Signing Cards. Unfortunately, none of the cards work - each of them gives a "wrong output" error.

Entering the PIN: 3. Do we see any message if the cards are blocked? Can we sign the default file and upload the app to the terminal? Also will there be any ownership issues if I sign the default files for development?

+3


source to share


1 answer


Start by asking why you are getting the wrong PIN. There may be several reasons:

CHECK CORRECT PIN

When you first received your cards, each should have come with a welcome email telling you what the PIN is for that card. Note that each card will have a unique PIN and that you cannot mix them (that is, if you try to enter the PIN for card 1 on card 2 it will not work and vice versa).

NOTE. VeriFone is not infallible - when I was in my VF class, one student received a couple of cards that didn't work, and the teacher thought he had the wrong PINs sent to him. The only way is to contact the VF representative from whom you purchased the cards.

CHECK FOR TROUBLESHOOTING

  • Are you using the latest version of the File Signing Tool (FST)? I believe the latest version is 04.01.04. If you have an older version installed, go to the DevNet page and get the latest version.
  • I have a note that the FST installer needs to run with administrator privileges, although if I remember correctly it will bump itself up to be an administrator, so it shouldn't be too dangerous. My note also says that during installation, you might get a message that you can't change the folder permissions, but don't worry about it.
  • After installing FST, always install it as administrator. This is important, and it won't work if you don't.
  • When you start FST for the first time, you need to configure 2 officers and provide them with temporary passwords (you will need to change the passwords the next time you log in). Note that for some reason VF decided to make the USER NAMES case sensitive (not just passwords).
  • Once these users are configured, log in as these users and change the password to a "permanent" password ("permanent" since you don't need to change it again if you don't want to). If I am not mistaken, you cannot use one of the last (3?) Passwords, so you cannot use the same as the temporary password with which you set them.
  • Now log in with BOTH the users you configured and select Change PIN.

If you still have problems, please contact your VF representative.



Entering the PIN. Try 3. Will a message appear if the cards are blocked?

I know you have a very limited number of tries before the card blocks itself, but after seeing how mine worked on my first try, I really couldn't tell you what happens when you get close and / or cross that limit.

Can we sign the default file and upload the app to the terminal? There will also be ownership issues if I sign the default files for development.

It depends on what type of terminal you are using. If it's Verix or VerixV (since 3740, 3750, 3730, 510, 570), then yes, you can use the default signature (which I do regularly on these terminals) and no, it won't cause any problems, assuming all the rest that runs on this terminal is also signed by default. If you are using some of the things that are ARE protected by a subscription, I believe that all items must have the same sponsor to run on that terminal (I know this is true with the eVo platform, but I just assume that on Verix / VerixV platforms ).

HOWEVER, if you are using an eVo terminal (e.g. 520) you MUST use a secure signature - eVo will not accept the certificate by default. What else, after the secure subscription is loaded into the terminal, then ALL future applications MUST be signed using a certificate with the same sponsor or this program will not work. (One exception - if you run the program to remove certificates, then AFTER it starts, you can load a new sponsor. Note, however, that the removal tool will not start unless it was written by the same sponsor).

Trying to use the default certificate shouldn't cause ownership issues, it just won't work. I know that if I try to use the default certificate on my terminal that already has a sponsor, it will compare the signatures of the files after upload and say they don't match. I have not tried this on an empty (no sponsorship certificate yet) eVo, but I suspect you will get about the same result.

These file signing cards have gotten expensive recently, so if yours don't work I would quickly head out with a VF rep and try to fix it - the longer you wait, the less likely they will help you.

+2


source







All Articles