Micros RES3700 - FDMS CA/EDC Setup 1

[elite3vil]

Hello,

I'm trying to setup a client with their credit card processing, using the Nashville frontend. From what I can tell, I'm supposed to use FDMS for the driver, and it's asking for registry settings. I don't know what these are supposed to look like. I get an error "No configuration file exists for this driver" when I try adding it to the CA/EDC drivers in POS Configurator.

Can anyone assist me in getting this driver to work? I assume it needs something in \HLM\Software\Micros\Common\CCS\Drvrcfg\

Thanks in advance for any help
-Ryan McHugh

 

[elite3vil]

Anyone have any ideas about how to do this?

 

[NexusDigital]

I am going through the same nightmare. Here's some information I can help you with.

1) This driver is somewhat new. Experience and information is not widespread yet The instructions are good but if anything goes wrong the helpdesks dont' have a clue. The FDMS driver for Micros only works on the North Platform (CardNet), even though the Micros documentation and all the Micros techs I have talked to say that First Data on Micros works only on the Nashville platform (that is true, to an extent -- FD on Nashville through MerchantLink, which the majority of Micros users are on). So you will have to go back to your processor and request a change onto the North (CardNet) platform if you want to use the FDMS driver. Until you do that your FDMS driver will not accept your Nashville Merchant ID and Terminal ID.

2) In order to get internet-based high-speed processing working with the FDMS driver, you will need to ask your processor to get you DataWire ID's. I am still fighting this configuration to get the test working. I hope more information becomes available here soon. It's a nightmare.

Good Luck. Please post your findings.

 

[RestaurantGenius]

Sounds to me like its looking for the merchantlink config. Do you know if they're signed up with Merchantlink? Direct processing always scared me, so I've stayed away from it.

 

[NexusDigital]

MerchantLink wants 450 per store fee to change the processing on their end. Multiply that by all our locations and suddenly everyone chokes. The boss has mandated that we get away from MerchantLink, so we went with the new FDMS direct driver.

 

[paymentpro]

I suggest working with a payment processor who will support your Micros processing solution 24/7, do the configuration for you and has years of experience with a direct to processor driver configuration.

With the particular setups mentioned here, if you have not worked with this driver before, you're setting yourself up for problems and downtime down the road. It's also not that new. Been around for years and still no coherent support from Micros unless you're really big. There's multiple versions of it too.

Will you know how to handle a future version upgrade of your Micros system? It's not as easy as reinstalling the cc driver or copying the database because you won't be able to initialize datawire. Don't plan on any help from the Micros help desk.

What steps will you take when Micros drops an authorization? Merchant Link won't be there to recover it for you.

Do you need to configure multi merchant support where you have different merchant id's tied to different revenue centers? Unless you know the driver and the processor setup well, you'll strugle with this one for a long time.

There's numerous issues I've seen personally that all require professional support. So long as you have support from someone or some entity that has spent enough time with the driver and seen it installed across multiple sites and environments, it's a great solution. And there is at least one payment processor I know of that will support it 24/7 and do the conversion at no cost. There may be others.

Email or message me if you want details.

 

[eburks]

I was dealing with ALOHA EDC and First Data Independent Sales and had VERY similar problems

I flat out told them we would not be using their accounts till they helped me and that if they wanted to loose their commissions on several million in credit usage fine.... I would just stick with Heartland...... and I did


The person who finally got me fixed up was

Account Boarding & Implementation Specialist - Boarding Operational Services

This was after a call from the Chief Operations Officer to me asking why we were not using our account after >6 months.

They sent me MID TID info and then actually put me on the phone in a conference call and then alone with the datawire guy. That was when we found out we needed to switch from Nashville to the North platform (cardnet/CES) and had to have datawire reprovisioned for that TID. The nashville platform had a different number of digits in the TID and that would not work with the techs "provisioning code software"
(I think I remember he needed 6 digits not 7)


Another problem we ran into that was fixed by adding a line in a configuration file was a maximum of 250 transactions in a batch Thanks again to whoever it was in this forum that gave me the info to change transaction limit




FYI I find datawire to be less troublesome than SSL and am happier with it but if you have been getting lightning fast batch settlements on another processor be prepared for a 200 transaction batch to take a few minutes to settle