Is anyone using a signature capture device with POS and First Data? I've been getting a lot of conflicting information about what will work and what won't.
Any help at all would be appreciated.
*This post is locked for comments
Is anyone using a signature capture device with POS and First Data? I've been getting a lot of conflicting information about what will work and what won't.
Any help at all would be appreciated.
*This post is locked for comments
Is the motorolla/symbol pd8750 the same device? They look identical so I figured they are made with different branding on them.
Michael
Contact Brandon Klasen who has put in a few posts above yours. He has the most experience of anyone I know in integrating signature capture/pin pad and RMS.
Do any of you happen to know if this software works with Dynamics POS?
Furthermore, does anyone have any suggestions for any solutions that support both signature capture and barcode scanning, as well as interoperability between POS/RMS and Dynamics CRM? We are looking for a solid solution to help bring the two products together.
Okay, here's what I've found:
If you are running in a headquarters environment then you must edit your tender typed prior to installing the TPI RMS Plugin. If TPI does not see DESCRIPTIONS on the tenders that it is looking for then it will create new ones and those new tenders, being created in SO, will not have HQID's. So, you want your tenders to look good to TPI BEFORE you install. Note that this should work with any TPI supported payment terminal but I have only tried this on the Hypercom Optimum L4150.
You only need to edit the Description, everything else should remain exactly as you are currently set up. The code can stay at whatever you're currently using.
TPI wants to see:
Gift Card Certificate
Debit Card
MasterCard Credit Card
Discover Credit Card
AMEX Credit Card
Visa Credit Card
So, once you've edited your tenders in SO Manager to have these descriptions you can run the TPI installer and the RMS Plugin, set the hooks in the RMS Plugin, and you should be able to then select * from the tender table and see that your HQID's are still there in the tender entries AND note that TPI has taken over processing of the tenders correctly.
Pretty straightforward but not all that simple to suss out. Hypercom support was pleasant but wasn't helpful. They told me that the product wasn't designed for use with Headquarters. They informed me that we would have to push new tenders down from HQ, thereby invalidating all our old tender records. This method works just fine for running TPI on RMS in a HQ environment and your accountants will be happy to boot.
Brandon
Hi D.
I have installed and tested the Hypercom 4150 and 4250 using TPI and FirstData. These are very straightforward in a NON-HEADQUARTERS environment. What we discovered though is that since TPI creates new tenders when you install it in the store there is no HQID to move the tenders up into HQ. You still see the transactional info but the tender type does not get passed along to HQ. This makes sense since we know that the tenders have to be created in HQ in order to have a HQID. Just didn't occur to us until we were just about ready to deploy.
I'll update if I get a procedure from Hypercom for doing this kind of integration with TPI and Headquarters. Hopefully we can just edit the existing tender types that WERE created in HQ when the stores were created and this problem will be solved. I don't yet know what part of the tender the TPI hooks use to identify the transactions so I don't know for sure that it will work.
Anyone using TPI in a HQ environment please weigh in!
Thanks,
Brandon
Thanks Brandon where are you located?
Hey Wineman,
I just IM'd the vendor that's going to be delivering the SDK and he wasn't sure how soon it would be available for us. I will post back when I have more.
Brandon
If you don't mind please keep me updated on your progress with the advertising etc. on the 4150. I would like to use these in an install I am doing after the first of the year if they work well.
Thanks
So far so good. I don't really like the 4250 because it doesn't have a color screen and I think the standard signature capture form is garbage. We're going to go with the 4150 (yeah, lower number but is the "premium" product) because it's a more enterprise type of feel to it. The 4250 is ugly and less intuitive, in my opinion. Signature capture works great. Note that we use the TPI/Hypercom plugin so that software talks to the device and to RMS, so you don't have to make many changes on the RMS side. We want to customize the interface with branding and such and the vendor that we're buying them through has agreed to purchase the SDK in order for us to do that. However, the forms that the device ships with are not terrible on the 4150.
Good luck and let us know what works for you.
Brandon
Have you been able to get the signature capture to work with RMS? I'd like to use a consumer activated device I've looked at the Ingenico but RMS has a problem with sending graphics out so the Ingenico doesn't give a very good customer experience. Does the 4250 work seamlessly?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,214 Most Valuable Professional
nmaenpaa 101,156