Making Merchant Credentials Unique to Business

Some Rossware clients run multiple businesses, each managed by a separate ServiceDesk (SD) setup, but from the same set of computers within the same network.  Almost without exception, each such SD instance keeps track of its particular business's underlying data within a folder structure that's particular to that busines, so there is never interference (cross-talking, overwriting of data, etc.) between instances for different businesses.  Storage or payment gateway merchant credentials, however, is an exception -- because the Virtual Terminal program (VT) is programmed to store such credentials in what's called the Windows System Registry.  This is, essentially, a storage place that's specific to each particular Windows-User login (as opposed to any particular folder or business).  Because of this method, it's impossible for a station that's running multiple instances of SD to recognize different merchant credentials for different businesses (absent, at least, the expedient as described here). 

Another situation that compels exception from normal setup is if you want your techs in SD-Mobile (SDM) to be using a different merchant credential set than is used in the office.  That can likewise be accommodated via a method described here. 

Please be aware that, because very few need this facility, we have not invested in the programming to make a user-friendly GUI by which to handle it.  The methods as here described therefore require somewhat more effort (and of a more technical nature) as compared to otherwise. 

To Create a Merchant Credential Setup Specific to a Particular Business:

In normal operation, VT creates a registry section to hold merchant credentials, and this section is employed without attention to any particular business or usage criteria.  Normally, there is no need for either, for the section is employed only for the sake of one business, and that business is using but a single credential set.  Where you have a more specific need, your task (quite simply) will be to manually create a registry section that's designated for more specific usage.  

The Windows tool that's used for editing the system registry is called the Registry Editor.  You run it by picking Windows Run, typing in "regedit" (and of course hit Enter). 

Once the Registry Editor is open, drill down in the hierarchy as follows (the near-last node in this example, "ServiceDesk," assumes that it's within ServiceDesk where you're seeking the modification: if within VT itself or SDRB, use that app's name instead):

The bottom-level node, as above-shown, is called a "Key."  Each key is essentially the title for a section of settings.  In this case, the one above-shown is the title (and essentially container of) the section that holds your normal merchant credentials.  If desired, you can open it, to see what its contents look like.

Your task is to create another Key.  It's going to look much like the standard one (above), and exist on the same hierarchical tier, but with an extended name.  Specifically, it's name will consist first of "MerchantCredentials" (just like above), but then an underscore, then the applicable business name. 

In regard to the business name, it must be precisely the same as found in the first line of the applicable \sd\servdesk.ini file (this file can be found in the same folder as the instance of the ServiceDesk program file that will be running for the business in question).  Thus (and as an example), for my old business in southern California, this sub-node would have been titled "MerchantCredentials_Aardvark Appliance Service". 

In result of this action, you'll end up with a hierarchy as follows:

If you are with Altiras instead of with TSYS, you can use the same key as above except modified to indicate Altiras . . .  as in "MerchantCredentials_Altiras_Very Precise Business Name"

Then, one more step.  You need to create a "string value" entry within/under the above key.  To do so, right-click on the MechantCredentials . . . key you've created.  Then, in the popup, pick New, then String Value.  You must name the new item "UseThisNode", and it's value must be set to "True". 

That's it, in regard to the technical setup.  Now you can use the VT as per normal.  When you save credentials from it, it will use the new sub-node/key you've made, rather than the normal one.  When it needs to re-load, it will go to the same location. 

In terms of how the logic works internally to the VT (and FYI), it's very simple.  Before seeking to do anything with credentials, the VT looks for the above-described registry structure.  If it sees it, it knows to use the special key-section you've provided, rather than the normal one. 

To Create a Merchant Credential Setup Specific to SDM:

Here we'll follow a pattern much like we do if making a section that's particular to a specified business, except instead of extending the title of our new Key section with an underscore and then business name, we'll instead extend it with this specific text: "_ForMobile".  

Thus, what you should end up with is a new Key section that exists in the registry hierarchy as follows:

Plus (just as with the specified-business method), you need to put in that new "UseThisNode" string value, as an entry in your new Key.  Additionally, in this case there is still more work.  That's because, where you're setting up a section as particular to a specified business, you can use SD itself to populate operational values within the section.  Not so for this particular-to-Mobile Key.  This one you'll need to populate manually.  Just look in an already operational Key section and see what the string settings are.  Duplicate them in this new section, except changed for the particular credentials you want your Mobile techs to use.